Two PXI systems in MAX

Hi!
I have PXI 1036DC system with 8101 RT controller. In MAX I see some second PXI system with the same name (see dup.jpg). Why it occures and what it means?
Jury
Attachments:
Dup.JPG ‏176 KB

I'm not so familiar with your hardware. However, the 6682, among other things, is designed to let you synchronize hardware with another PXI, perhaps reached through its Ethernet port. Your picture seems to show a second PXI (PXI2) that has a 4462 card in it (why it shows as a VISA connection is beyond me, but that may be the method of communication).
You appear to have hardware capable of "reaching out" to other systems. If so, MAX will show all of the systems it can reach. For example, I have a single camera in my office that I use with IMAQ, yet MAX shows me something like 30 cameras because they are all on the network and, potentially, MAX (and I) can "reach" them.
You might be able to temporarily edit MAX's internal file and "remove" that 4462 card from your display, but if my understanding of MAX is right, the next time it starts up, it will survey its surroundings, and if the device is there, it will show it.
Bottom line -- MAX is showing you what is available. It does not mean you need to (or even can) use it.

Similar Messages

Installed PCI-6025E recognized by Windows XP but only in PXI system by MAX

I installed a PCI-6025E DAQ board on a Windows XP machine. Upon startup it recognized the new hardware and installed the driver from the NI-DAQ 6.9.3 CD. All seemed to work fine. When I try to bring up the device in MAX it only shows up in the PXI system section. This doesn't assign a device number or allow a test panel. So I don't know how to access the signal from Labview programs. Is there something I haven't done right?

Hello magicjoecuda,
In general it sounds like you have done everything right and it is not that surprising that the 6025E shows up as a PXI device, but it is unexpected that it does nost appear as a DAQ device. I would try 2 things to work around this:
1) Try installing the card in a different PCI slot on the computer.
2) Uninstall the 6.9.3 driver and try installing the newest version of the driver. A link to the newest version of the driver for your board can be found here:
http://www.ni.com/support/daq/versions_pci_pxi.htm
Take care,
E.Lee
Eric
DE For Life!

Synchronize 2 PXI Systems through GPS using PXI 6552

I want to synchronize two PXI systems separated by a distance of 5kms through GPS.
PXI 6682 is a timing and synchronization card which can be used to achieve this. I also have a requirement to use PXI 6552 HSDIO in my application. Few channels in PXI 6552 are free. So i want to know if it is possible to achieve GPS Synchronization of the two PXI systems using PXI 6552.
Regards,
Sundar Ganesh

Hi Ryan,
This is a system configuration which i am doing for a requirement. The requirement is RF Generation in one PXI system and RF Acquisition in another PXI system separated by a distance of 2kms. The applications that will be running at both these PXI systems may be started at different times. So i am thinking of using a PXI card in both the chassis to synchronize them through GPS.
Regarding this, i have already contacted the local NI FSE and together with him only we have decided to go ahead with PXI 6552 for GPS Synchronization. But i started doubting the usage of 6552 for GPS synchronization when i couldnt see the card in the list of Timing and Synchronization cards.
I have attached a schematic of the configuration. Let me know which PXI card should be used for synchronising these two systems.
Regards,
Sundar
Attachments:
PXI Configuration.JPG ‏21 KB

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

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

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

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

Unable to see PXIe-8133 in MAX on host computer

Hi,
I seem to be running into a very basic problem. I'm trying to use the PXIe-8133 system in Real-Time but I am unable to detect the system in MAX. I can't even see an "Unconfigured RT System" with IP Address of 0.0.0.0 as it shows in the documentation. I've installed all of the drivers for the PXIe 8133 on my host computer found here:
http://joule.ni.com/nidu/cds/view/p/id/2030/lang/en, but this has not solved the problem.
One thing to note, when I attach a monitor to the PXIe-8133, it says: "System State: No Software Installed" and also "Can't Find Suitable Device for Drive C". But only one of our 2 PXIe-8133's is displaying this and we are not able to see the PXIe-8133 system in MAX even in the system which does not display these warning messages.
Thanks very much in advance for your help!
Steven

Hey Steven,
So a couple things to make sure of:
1. Reboot your PXI and when it is rebooting up keep hitting the delete key until you see an output on your screen that gives you different options to select.
2. Go over to Real Time menu (think it is like the fourth option from the left on the top).
3. Once in here the first option is what mode of Real-Time do you want to access. Select LabVIEW Real-Time Safe Mode.
4. Go to the last menu option and save changes. This will reboot into the mode we just set.
Once it is rebooted, go into MAX on your computer that is on the same subnet as this PXI and refresh remote systems. You should now see a device with an IP address of 0.0.0.0. Make the changes to the IP address that you want. Once you save those changes it will reboot the PXI. If you are still not able to get the target showing, try to go back into the bios and there is also another option to choose under the Real-Time heading to reset IP by hardware switch, software or none. Change that to software. Save again and then it will reboot and see if you can now see it in MAX and make the corresponding IP changes.
David A.
National Instruments
Applications Engineer

PXI system configuration using GPIB interface

Being new to PXI systems, I'm trying to determine if there is a need to have a PXI-GPIB controller if I am configuring a PC(PCIe) controlled MXI Express kit???

Sorry if I wasn't clear before but you probably will not want to connect both a PCI-GPIB card and your PXI-GPIB card to your instrument. You will probably only want to use one or the other. I was just saying that you could have 2 different cards in your system to connect to different instruments if you wanted. MAX recognizes that there are 2 different GPIB cards and you choose which card to use before you communicate with an instrument. So if you are just wanting to communicate with a single instrument there is no need to have 2 GPIB cards unless you just want your GPIB card to be in your PXI chassis.
Brian Platt

PXI system cannot be identified by the PC

PC doesn't see the PXI system. When I tried to install the service platform for chassis and controller ver 2.5. A message states that a higher version is already installed.

Hi Gordoo3,
Can you expand on the hardware you are using (Chassis, Controller, Devices, etc.)? Do you have a MXI connection to your PC? Have you identified the chassis in MAX? Here is a Knowledgebase article that describes this process.
Best,
Adam
Academic Product Manager
National Intruments

I am using XNET CAN on a PXI system. When I modify the can database I get the error "the interface has already been opened.."

I have tried both building the XNET session from project explorer and by building a signal list in the VI.
Any suggestions? Thanks in Advance.

Thanks for the reply. I don't think I have any interface open. But to be sure, I rebooted everything - same result.
Is there some step in the project config that I am failing to do? In the PXI systems I had before XNET, I had to setup some CAN configuration stuff in MAX to get it to work, but I don't see that option anymore with XNET....
I have been sucessful in running XNET CAN VIs reading and writing the data from my database, but I stumble every time I add a signal or rename the database.
I made a simplified VI to illustrate, using a previously working database I now get the empty name message.(screen capture attached)
This is connected to a working CAN link, and I can see these signals in MAX properly.
Thanks in advance for your assistance!
Attachments:
vi_issue1.jpg ‏136 KB

Configure DAQ cards in RT PXI system

Greetings all,
I'm just trying to learn how to use Real Time and I'm having trouble setting up the DAQ cards in the PXI chassis.
I am able to successfully connect to the PXI RT system and run simple VI's that have no DAQ or VISA access.
What I can't any info on is how to setup and access the DAQ and serial ports on the RT system. A quote from teh help file says,
"To configure remote DAQ devices, select your DAQ device from the Devices and Interfaces category under My System. Select Tools»NI-DAQ Configuration»Remote DAQ Configuration from the MAX menu to launch the Remote DAQ Configuration dialog."
I've tried this and it wants to see the RDA server running on the PXI, which of course isn't there sin
ce it's running RT.
What am I doing wrong here?
I'm running a PXI-8156B with a PXI-6071E and PXI-6713. This also has NT4 installed. Both PXI and host machine have LVRT 6.0.3, NI-DAQ 6.9.1
The host is running Win200.
Thanks
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

I'm using:
LabVIEW 6.1
NI-DAQ 6.9.2f4
MAX 2.2.0.3010
This may be obvious to others, but it certainly was not to me...
I wanted to configure devices on my remote PXI RT system, and I experienced the exact situation described above.
All the instructions and help I could find seemed to suggest that I should select the following menu item:
Tools >> NI-DAQ Configuration >> Remote DAQ Configuration...
But when I went there and entered the name or IP address of the Remote System, MAX couldn't find it. The PXI system was listed in the "Remote Systems" folder, and I could set up its networking parameters and software downloads from the "Remote Systems" folder.
It turns out the
key is to:
right-click on "Devices and Interfaces" in the "My System" folder
select "Create New..." to bring up a dialog<\li>
selec "RDA/Ethernet Device" then click "Finish" to bring up yet another dialog
specify the remote systems address, then click "Next"
The List of Remote Devices Appears!!! (Hallelujah!)
select a device, "Next", specify a local device number, "Finish"
Now the Remote Device is listed in the "Devices and Interfaces" folder of "My System" (strange that it's not listed under the Remote System - but who cares at this point).
repeat for each device
Now you can go back and select that original menu item (Tools >> NI-DAQ Configuration >> Remote DAQ Configuration...), specify the address, and (Behold!) there are those pesky remote devices.
(NOTE to NI... If this process is described anywhere in documents or help files relating to configuring devices on a remo
te RT PXI system I couldn't find it. Perhaps my trouble is that I've never used a PXI system or remote devices prior to trying to us LabVIEW Real-Time, but I'm probably not the only person in this situation.)

Diadem DAC support for PXIe systems?

Hello,
I want to know if it's possible to install and run Diadem on a PXIe System (Controller and chassis) and use the DAC
for a fast measurement configuration and setup. Does somebody have experience with such configuration?
I know that I could use Labview but for fast measurement setups DAC in Diadem is quite perfect.
Thanks in advance.
Solved!
Go to Solution.

Just to complete Walters post above.
DIAdem DAC works with any NI PXIe hardware that is supported by NI MAX (Measurement and Automation eXplorer), including global virtual channels. If you have Windows XP or later on the PXIe system, this will work fine ...
Otmar
Otmar D. Foehner
Business Development Manager
DIAdem and Test Data Management
National Instruments
Austin, TX - USA
"For an optimist the glass is half full, for a pessimist it's half empty, and for an engineer is twice bigger than necessary."

Two PXI systems in MAX

Similar Messages

Maybe you are looking for