PXI system installation

Hello everyone,
I am having a PXI 1050 chasis with a PXI 8186 controller in it. I want to monitor thermocouple channels using SCXI 1328 modules. Can someone please provide me with step-by step procedure of configuring and programming this PXI system. I have labVIEW 8.6.
Thanks
faez

muks
Proven Zealot
What is the error you are getting?
HI, muks
Now I have attached the images with this message which shows sequence of process that was followed during installation of NI 488.2 in PXI system.
STEP-1...
STEP-2...
STEP-3....
STEP-4.....
STEP-5.....

Similar Messages

PXI System does not appear in MAX 4.0

Hello,
My system comprises LabVIEW RT 7.0, target PXI-8176 controller in PXI-1000B chassis, PXI-6608, PXI-6711, NI-4472, PXI-6704, PXI-6527, PXI-8423/4, PXI-8422/4. This has been stable for two years. I recently solved an RS-485 2-wire mode configuration problem, using information in a discussion forum thread, by upgrading to NI-VISA 3.4.1 and NI-Serial 2.5.5. MAX 4.0 was installed as part of this process. Everything seemed to work fine. I instructed a distant customer to do the same, but they experienced some difficulty. To ensure we were working from the same starting point, I re-initialized my PXI system, using PXI Format Hard Drive Disk, version 7.0, from MAX 4.0. I configured TCP IP address, and re-installed the RT software on the PXI controller.
Next, I attempted to configure the PXI controller and chassis, in MAX, to update the pxisys.ini file, but the PXI System (Unidentified) does not appear under Remote System>>IP address>>Devices and Interfaces. Similarly for the serial ports. This worked before, but I cannot get this back. What is wrong?
Best regards,
RonC

Hello S. Bassett
The controller is definitely booting in RT mode -- I can still run my applications on the RT target. VISA seems configured properly also, I can make VISA calls without error in the application.
In fact, the RT system seems to work correctly, and I contemplated leaving it as it is. However, the fact that MAX does not recognize the PXI system makes me nervous, and I cannot do some of the things I may want to do, for example independently configure RS-485 port wire mode in MAX (the ports do not show up either). Traditional DAQ configuration in MAX works.
After your last post, I found a brief reference in MAX Help that indicated "PXI Services" had to be downloaded before the chassis could be configured. But there are no other mentions of what PXI Services is, what it does, or how to install them. PXI Services does not show up as RT Software in MAX. In the Windows Add/Remove Programs control panel in Windows, in the National Instruments software section, there are two apparently related entries:
- NI PXI Platform Services for LabVIEW Real-Time 1.5.1
- NI PXI Platform Services for Windows 1.5.1
But, I cannot get these to install on the RT target. Not knowing what was causing the problem, I uninstalled everything from National Instruments, deleted all folders, and reformatted the PXI platform. There was one problem during this process -- after uninstalling NI-Serial 2.5.5, it does not get removed from the Add/Remove programs control panel. There is still a registry key that the uninstaller did not remove -- presumably this is the problem.
I have rebuilt everything, but could not get NI-Serial to install -- the installer thinks there is a newer installed on the RT target (there isn't) and refuses to install NI-Serial 2.5.5. So right now, I cannot install NI-SERIAL (any version), or remove the 'existing' NI_SERIAL, because it isn't actually there, and there is no uninstaller.
Otherwise, everything seems to be back to where it was before I "upgraded" to NI-VISA 3.4.1. This was NI-VISA 3.0, LV RT 7.0, and MAX 3.0.2. I have not yet been able to install NI-Serial, so I cannot yet see if I have also restored my original problem -- the one that led me to have to upgrade NI-VISA and NI-SERIAL in the first place.
Most importantly, there is now a "PXI Services v1.1.2" installed on the RT target. I am quite sure the problem with MAX 4.0 not recognizing my PXI system has to do with the absence of this driver on the RT target.
Thanks again for your interest and help,
RonC

Error in installing NI 488.2 in PXI system

Hi, all
We have a VA-HR instrument and agilent power supplies, which we are being controlled through USB interface in one computer. all the supplies and VA-HR are controlled via single USB.
Now we want to controll these instruments from another computer which is a PXI system with NI PXI 8105 Embedded controller. (PXI system contains Windows XP service Pack 2)
When the USB cable was plugged into PXI system, it gave folowing message:
Found new hardware, USB serial controller D, and also the GPIB-USB-HS.
So we came to conclusion that it requires USB serial controller D drivers as well as GPIB-USB-HS(GPIB-USB-B) drivers.
For that i did download NI 488.2 2.7.3 from NI website and tried to install that into PXI SYSTEM. But during installation, the process rolled back from driver installation and gave an error. i tried this for atleast three times. In other PC the same .exe source of NI 488.2, successfully installed NI 488.2 software without any error.
I can't understand why this NI 488.2 is not being installed.
LABview 8.6 is already installed in the system.
In short i want to connect my Power supplies and VA-HR to PXI system. Please help me out in this installation error.
thanks and regards,
vishal sakarvadiya

muks
Proven Zealot
What is the error you are getting?
HI, muks
Now I have attached the images with this message which shows sequence of process that was followed during installation of NI 488.2 in PXI system.
STEP-1...
STEP-2...
STEP-3....
STEP-4.....
STEP-5.....

Possible to start MXI-3/PXI system after PC booted?

Hi,
I'm new here, so I just asked this question in another thread through a reply. I didn't notice that it was already marked as solved, so I'm going to ask again in my own thread.
My problem may seem very related to the one of Kobi, but there are some differences which are holding my hopes up that the problem could be solved. The system setup summarized:
- PC (MXI-3)
->PXI1002 (Chassis1)
   ->PXI8335 (port1 - in)
   ->PXI8335 (port2 - out)
   ->PXI5122 (measurement)
     ->PXI1002 (Chassis2)
      ->PXI8335 (port1 - in)
      ->PXI5122 (measurement)
The aim is, as it is easily guessed, to be able to start the additional measurement devices at any time, even while the pc is already running.
The situation differs to Kobis' in one specific point: in my case the cards and all the equipment is at all times visible in MAX, even though I startet it after the pc booted. What does change is the pattern of the leds, and that the PXI cards don't pass the self test in MAX. The following screenshot shows the konfiguration of the system how it is observed after both ways of starting the complete system (pc first or PXI first).
(Even though I'm using an english labview version my MAX partialy remains german, I hope this is no problem.)
I tried to identify the PXI system and chassis, but couldn't get a different result. The NIscope VIs are orderly initialising and resetting all the sessions, but only if I switch on the PXI systems first.
So what do you think, could it be possible to achieve the goal of making it work, or should i stick to booting the pc after switching on the PXIs? I did some research and I know, that the installation guides do specify the order of switching the devices on, but I thought that this was only meant for installation/first run.
I would be really thankfull for any advice in this.
Regards
Max1744
Solved!
Go to Solution.

Hi Max,
there is no way around to first start the PXI. You always have to start the PXI System an d then the PC.
regards
Tobias

How can I get MAX (Labtop) to see my PXI system?

I have a PXI system consisted of PXI 8184 (Microcontroller) and PXI 6552. I wish to run LabView 8 application on my labtop and run it and see how the PXI device respond to my application. TO establish the communication I read that I can use a CAT5 crossover cable or a hub. I couldn't get the PXI system to show up under Remote Systems in MAX residing in my labtop.
How can I solve this problem can any body clue me on that?
Thanks

Greetings!
   1) Are you using a PXI system which has an embedded controller
with Real Time (RT)?
   2) Did controller have RT installed / shipped with it. We can
confirm that in the bios if the LabVIEW RT menu options show up?
   3) Listed below are few links you can go through to get started
and troubleshoot. Specifically the chapter 2 in the manual for 8184
http://www.ni.com/pdf/manuals/370836b.pdf
http://digital.ni.com/public.nsf/websearch/A43DD6F680D123DD86256F870002B6A2?OpenDocument
http://www.ni.com/support/install/install_hardware_5.htm
   4) When you connect a monitor to the controller what do you see in
the screen?
   5) Did you get a chance to install the embedded sw CD that came
with the controller in your host computer?
   6) You can also verify if you have a folder similar to following
in your host computer after the installation (Similar to the following)
   C:\Program Files\National
Instruments\RT Images\Base\2.0\7151
Thanks and hope this helps to get you rolling
Good luck
Avi Harjani

How to connect a Compact RIO to a PXI System

Hello,
I want to connect my cRIO-9074 with my PXI System.
First of all my Hardware configuration:
1. "PXI-1036" Chassis with "PXI-8101" Embedded Controller and "PXI-8231" Ethernet
2. "cRIO 9074" Integrated 400 MHz Realt-Time Controller
3. "NI 9144" EtherCAT slave chassis
The PXI System is connected with my Network through the Ethernet-Port on the "PXI-8101" Controller. The "NI 9144" is connected with the "cRIO 9074" through their EtherCAT Ports. That works without a problem.
Now I want to connect my "cRIO-9074" with my PXI-System through the Ethernet Port on the "PXI-8321", but I can't find a way to get this work.
In MAX I configured the second Ethernet Port on the PXI as "TCP/IP" with a IP and Subnet. Then I connected the cRIO and turned it on.
But I can't find the cRIO anywhere in MAX or in a LabView Realtime Project.
When I configure the "PXI-8321" as a EtherCAT Port, I can connect my "NI 9144" with it and use it in a LabView Project. But configured as Ethernet and connected with the "cRIO 9074" it doesn't works.
Is there any way to get this working? Or is this not possible with my Hardware?
I know I could connect the cRIO and PXI through a Switch with my Network and then use both in a LabView Real-Time Project. But I want to build a mobile Measurement-Station with as few devices as possible. If there is no other way I will use a Switch, but without would be better.
Thankful
Daniel Löffler

Hi Daniel,
it is not possible to connect cRIO-9074 Controller with the PXI System through the Ethernet-Port, because the RT cRIO Controller can not behave as a slave. cRIO Controller is always configured as a master, never as slave. The extension Chassis 9144 is configured as a slave, so you can use it with your cRIO Ctrl or with PXI Ctrl as well. Connection PXI-Ctrl, cRIO-Ctrl, NI 9144 is not possible.
Best regards,
ENIA
NI Germany

Using Fieldpoint from Labview RT on a PXI System

I have a PXI system with Labview RT (PXI 8186 controller with LVRT ver 7.1).
I wanted to connect a FP remote I/O system to this controller. The Fieldpoint system I have has a FP-1000 RS-232 Network module.
I was hoping to be able to connect the FP-1000 to the serial port of the PXI-8186, and use the standard Fieldpoint VIs to write/read data (as you would from a Windows-based Labview app).
It doesn't seem to be that easy, trying to download any code with a Fieldpoint VI down to my RT target gives an error ("failed to load shared library FPLVMgr.dll on RT target device"). Looking through MAX I see that Fieldpoint drivers are not loaded on the RT target, and there is no option to load them there either.
So: Ho
w do I control my Fieldpoint units from my PXI System using Labview RT?
Any help would be much appreciated.
Thanks,
Ravid

Hi, Ravid.
Effectively, under LabVIEW RT, you cannot use the standard FieldPoint VIs to communicate to a FieldPoint module, since they are not supported. If you have a serial module, like the FP-1000 or FP-1001, you need to use Optomux commands to interface and communicate to it. You can find great examples on how to do the communication in the Example Finder of LabVIEW >> Hardware Input and Output >> FieldPoint >> Optomux >> and use any of the examples that use VISA to communicate to the modules. To run the examples, first target LabVIEW to your 8186 and open the example. Before running it, match the baud rate and address specified in your FP-1000 with the controls in the Front Panel. Also, verify that you have either an alias defined for COM1, or use AS
RL::INSTR1 for the VISA resource name. You will need to have VISA RT installed on your RT Target to be able to run this examples.
You can find the Optomux commands in LabVIEW under the Advanced FieldPoint palette. For more information on Optomux commands, you can take a look at the FP-1000/1001 Programmer Reference Manual
Let me know if you have further questions. I hope this helps!
Gustavo Valdes
Applications Engineer

Making own pxi system?

I currently am working on a project in which i am going to be placing a pxi system with some components inside a larger box with some other hardware connected to it. Basicly what i want to do is to get rid of my chassis. I would like to have my pxi cards just connected striaght to the backplane i believe, no shell/caseing. NI does not offer anyhting like this but I was wondering how I would go about it and what would i need. I found this backplane: http://www.comtel-online.com/pxi.htm but still im not sure if thats all I would need or what. I know PC hardware really well, but when it comes to PXI im a little foggy. Please let me know how i can accomplish this. I thank you for any help you can give.
Thank you very much!
-Mark

I currently am working on a project in which i am going to be placing a pxi system with some components inside a larger box with some other hardware connected to it. Basicly what i want to do is to get rid of my chassis. I would like to have my pxi cards just connected striaght to the backplane i believe, no shell/caseing. NI does not offer anyhting like this but I was wondering how I would go about it and what would i need. I found this backplane: http://www.comtel-online.com/pxi.htm but still im not sure if thats all I would need or what. I know PC hardware really well, but when it comes to PXI im a little foggy. Please let me know how i can accomplish this. I thank you for any help you can give.
Thank you very much!
-Mark

How to Generate Synchronized pulses across two separate cards on a PXI system

Hey,
I'm trying to generate three pulses from my PXI System for triggering purposes. I have two cards (PXI 6259 and PXI 6115) , each with two counter/timers on them. The 6259 has 32 bit timers, and the 6115 has 24 bit timers.
Up until now, I only needed two pulses. One was 180us long at 20 Hz, and the other is 5us at 20 Hz, starting 150us after the beginning of the first pulse. I was able to achieve this by generating both pulses on my 6115 card by triggering the shorter pulse off of the rising digital edge of the longer pulse and giving the DAQmx Counter/Timer task an initial delay of 150us.
The third pulse needs to be identical to the short pulse, only it needs to occur 20us early (130us after the start of the wide pulse). I tried to generate it using the same technique as I used when generating the short pulse, only generating the pulse and reading in the rising digital edge trigger on my 6259 card instead of the 6115.
The result was that my pulse trains were asynchronous and the pulse generated on the 6259 card was constantly shifting to the left.
This puzzled me, so I wrote up a little dummy program to test generating triggered pulses. The results were that when I generated two pulses on the same card, they were always synchronized; however when I generated pulses on separate cards, one of the pulses always shifted.
I was hoping somebody could suggest a reason that the pulses across cards are asynchronous even though I'm reading in a digital trigger and hopefully a way to rectify the situation and synchronize all of my pulses.

The problem, in a nutshell, is that the timebases on the two boards have manufacturing tolerances that will cause them to differ from one another. The accuracy error is a small fraction of a percent, but the effect on the phasing of your pulses will be cumulative. That's why you saw the one set of pulses "shifting to the left."
The solution is to make sure each board derives its pulse timing from a single common timebase. Fortunately, this is pretty easy to specify with DAQmx, just a little tricky to find. In the chain of VI's you call to configure the counter pulses, insert a DAQmx Channel property node. From memory, I *think* you should be looking under something similar to "Counter Output->General->Timebase->Timebase.Src"
Right click and create a constant or control to define the timebase source. You should get a dropdown list that includes a wide variety of choices. Among them are each of the boards' 20 MHz clocks. By default each task will use a timebase from its own board but this technique lets you route one board's timebase over the PXI backplane with that single property node setting. DAQmx does most of the dirty work behind the scenes.
-Kevin P

Object oriented programming on PXI-System

Greetings,
i've developed some object-oriented LV classes, wich i've succesfully tested on my desktop pc. The next step would have been to test them on a PXI-controller. However, the LV 8.20 methods of object oriented programming seam to be incompatible to PXI-systems.
All i'm getting is an broken arrow with an error message like that
HardwareIOAnalog.lv.class:setTimingNP.vi
Frontpanel-Anschluss 'HardwareIOAnalog in': Der Typ wird für das aktuelle Ziel nicht unterstützt (means: Type not supported by current target)
Does that mean that object-oriented design is not supported in general by PXI, or is it depending on the type of the PXI-System. Is there an easy way around, or do i have to re-program all my classes to conventional (Sub)VIs?
Help appriciated! ;-)
Regards,
Bennet Gedan
Student (Electrical Engineering/Mechatronics)
Darmstadt University of Technology
Bennet Gedan
Student (Electrical Engineering / Mechatronics)
Darmstadt University of Technology

Okay, thanks. Meanwhile I reprogramed the whole thing and set OOP aside (at least on the PXI-Target). It's a pity to loose some advantages of OOP, but it brougth me some interesting new programing techniques i could transfer to non OOP stuff.
Regards,
Bennet Gedan
Student (Electrical Engineering / Mechatronics)
Darmstadt University of Technology

Is it possible to interface a USB Gamepad to a RT PXI system?

We currently use a RT PXI system to control a subsea ROV.
We would like to interface a Logitech Wingman Gamepad with USB interface to our RT PXI system as a Human Interface Device (HID) to control the ROV. Is it possible?
The gamepad supplier has informed me that the gamepad is "a fully compliant HID device and can be read by any HID-capable platform"

While the application sounds interesting, unfortunately USB devices are not supported on any of our PXI controllers when booted into the Real-Time operating system.

Accessing a SWTICH and DMM cards in a PXI System remotely

Hi everybody,
I use a PXI system with a NISwitch PXI-2503 and NiDMM PXI-4070. The embedded controller PXI-8176 is running WinXP.
From a client machine I want to access remotely this cards. Via VISA Server it is possible to interact with the Switches using NI's driver NiSwitch. On the ther hand, I did not succeed so far to access remotely the DMM using the driver software NiDMM. I receive always the following error:
"Error -1074135030 occurred at niDMM Initialize.vi
Possible reason(s):
Error: (Hex 0xBFFA000A) Failure loading driver module."
My Software Versions are:
Labview 7.1, VISA 3.1, NI-DAQ 2.10, NiSwitch 2.20, NI-DMM 2.2.1
I have read that there are some incompatibilities between VISA and RDA conc
erning the TCP-IP port, but this problem should be solved in the versions I currently use.
Anybody out there who knows a workaround?
Thanx for any help in advance
Hannes Schmidt, Swiss Federal Institute of Technology, Lausanne

Hannes,
Unfortunately I don't think anybody here knows of a workaround because the application is not one that anybody has recently tested using NI-DMM. The easiest work around to me would be to use LabVIEWs remote front panels to do the acquisition. The only reason why using this might cause a problem is if you need to save data to file on a remote PC. So the only consideration to work with is to save the file on the host PC and then grab the file saved using FTP or something along those lines. That may be a much easier work around than trying to figure out what is going on with the low level DMM driver call. Hope this helps. Good luck with your application.
Best Regards,
Jeremy Ross
NI - Applications Engineer

Windows server 2012 Datacenter Hyper-V Cluster -- Failed to validate Operating System Installation Option?

Hi I have a 4 node Windows server 2012 Hyper-V cluster. When I try to run a cluster validation report, everything else is fine but it fails at validate the Operating System Installation Option step. I did some research but couldn't really find any solution.
Anyone knows how to pass this test? Thanks.
Here's the error I get when run the test:
An error occurred while executing the test.
The operation has failed. An error occurred while getting the operating system installation option for node "server1"

Hi JasonLiu2002,
Please post the original error information, the current information is so wide that difficult to determine where may have issue and please offer more information about your
server configuration, you can refer the following article to prepare your cluster environment first.
Windows Server 2012 Hyper-V Best Practices (In Easy Checklist Form)
http://blogs.technet.com/b/askpfeplat/archive/2013/03/10/windows-server-2012-hyper-v-best-practices-in-easy-checklist-form.aspx
When you preparing the new cluster on Server 2012 please install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters updates.
http://support.microsoft.com/kb/2784261
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

System installer disk

i have heard about using your system installer disk to "clean-up" your mac. i have two disks, is it the first or second?
and is this the correct route:
1. start mac using disk: (do i insert the disk as the computers turning on.)
2. run app and check/repair permissions: (will this fix any probs automatically or do i have to go in and do it manually)
anything i missed?

Hello and welcome to Apple Discussions,
Using your system installer disc, you can use Disk Utility to Verify/Repair disks as well as system permissions. With the machine powered on, insert the first disc. Then, restart your Mac holding down the "c" key until you see the apple. It will now boot from the disk and you can utilize Disk Utility via the Utilities menu. I hope this helps! Here is a website that show you visuals.
Jason

BDD 2007 -- ZTI -- OSD error "The Operating System Installation Failed Unspecified Error (80004005)

Hi there
Wonder if anyone can advise me on a BDD 2007 OS deployment issue? (Apologies if this is in the wrong forum, I couldn't see a forum for BDD 2007.)
First of all, this BDD 2007 server and the OSD config was not done by me. For info, it is part of a SMS 2003 infrastructure.
I am trying to get the XP Pro build process working. I am led to believe the config has been completed.
Unfortunately, after booting the pc from the nic, I get an error. This is the order:
- the 'Initializing Windows PE' splash appears for perhaps 15 seconds
- very briefly, the text changes to 'Initializing Network'
- for a second or two only 'Initializing Windows PE' appears again
- then this error message appears:
"SMS Operating System Deployment - The Operating System Installation failed. Please contact your system administrator for assistance. Unspecified Error (80004005)"
I've spent some time looking into this error (80004005) and from what I can gather it possibly means 'access denied'.
I'm assuming after Windows PE loads the first Task Sequence begins, and if this possibly is where the issue lies?
One thing I cannot understand - the first Task Sequence (Initialization) has this command line (as do most, with different .wsf file):
cscript.exe "%SCRIPTROOT%\ZTIGather.wsf" /localonly
However, I cannot access %SCRIPTROOT% at all, Windows says it can't find it. I can run other variables such as %USERPROFILE%, %SYSTEMROOT%, etc, but cannot open %SCRIPTROOT%.
Is it simply the case that I should create a new system variable (that has not been created by whoever built the server)?
Thanks
John Henry

Since no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

PXI system installation

Similar Messages

Maybe you are looking for