PXI

cancel
Showing results for 
Search instead for 
Did you mean: 

Running a PXI with Windows 7

Hey,

 

  I have access to three NI machines (PXI-1042 chassis, PXI-8186 controller) that can dual-boot with Windows XP and Labview RT.  Previously, these machines were used in the following setup: two computers attached via ethernet port, one running Windows XP and Labview 8.2 controlling the other running Labview RT.  However, I recently obtained a set of Dell Optiplex 780s, all running Windows 7, and have since installed Labview 2010 on each.  I have attempted to replace the Windows XP computer in the above setup with a new Windows 7 machine (with both the latest DAQmx drivers and the latest pxi drivers), and labview always tells me I don't have the correct plugins installed.  Are there better drivers out there? If not, how can I control a PXI machine with a Windows 7 machine?

 

Many thanks

0 Kudos
Message 1 of 8
(4,492 Views)

Update: I downloaded the evaluation version of Labview RT and now the two machines acknowledge the other's existence (I can manipulate the target machine with the Windows 7 machine via MAX), but when I try to connect the two in a Labview project I get this message:

 

'Unable to resolve with current dialog / Failed to connect with target'

 

I'm posting this in the Labview board as well, but is there any alternate setup I could try that would avoid this problem?

0 Kudos
Message 2 of 8
(4,485 Views)

Hello bjw5,

 

At what point does this error pop up, when you click on Add device in the project>>existing devices>>and then choose the PXI? Was this project originally built in LabVIEW 8.2 and now saved to 2010? Do you have any other hardware you can try adding to the project? There should be no compatibility problems having a Windows 7 host computer. What version of the PXI platform software and DAQ mx drivers do you have?

 

Researching this error dialog it usually occurs when the project contains .dlls or DAQmx custom scales or tasks. Are all three PXI systems exhibiting this behavior, or are you just setting up this one to start? I appreciate your answers to these questions. On a side note, please keep your posts to one forum, this helps us focus our resources on the support side. This most likely has to do with the network/RT setup versus the actual LabVIEW project.

 

Thank you,

Deborah Y.

Deborah Burke
NI Hardware and Drivers Product Manager
Certified LabVIEW Architect
0 Kudos
Message 3 of 8
(4,468 Views)

Deborah,

 

The error pops up when I open the project on the host machine, right click on the target IP address, and select 'connect'.  This project was built in Labview 8.2, the host machine is running Labview 2010 and the PXI is still running Labview 8.2.  I've tried this with another of the PXIs I plan to use and I get the same result, but I'm concentrating on one to start.  Both machines (Windows 7 computer and PXI computer) have the most recent DAQmx drivers, and can interface with a myDAQ.  In terms of connection methods, I'm using a crossover cable.

 

Hope some of this helps,

Many thanks

0 Kudos
Message 4 of 8
(4,461 Views)

Hello bjw5,

 

I appreciate those details. Both the Windows PC and the PXI controller will need to have the same version of DAQmx. It gets dicey because no compatible versions are overlapping, NI-DAQ and LabVIEW version compatibility (for Windows). Is it possible to upgrade the Real-Time module version you're using? If so, a complete uninstall/reinstall of DAQmx is needed to change the driver version, Upgrading and Downgrading Versions of NI-DAQmx on LabVIEW RT Target Systems. Also have you tried running the project on the Windows 7 computer in XP mode? What version of the PXI Platform software do you have running on each?

 

Thank you,

Deborah Y.

Deborah Burke
NI Hardware and Drivers Product Manager
Certified LabVIEW Architect
0 Kudos
Message 5 of 8
(4,440 Views)

Hello bjw5,

 

It looks like you're going to need to upgrade the controller to have the same version of the LabVIEW Real-Time module as the version of LabVIEW on the host, 2010. If you already have LabVIEW 2010 Real-Time module purchased for the host, it includes one license to push that software to the target. If not, you can try an evaluation version by logging in to www.ni.com/src. Then navigate to By Product>>LabVIEW>> NI LabVIEW 2010 Modules>>  LabVIEW 2010 Real-Time module. This knowledge base article explains how to push the software over in MAX, Why Do I Get a LabVIEW RT Communication Protocol Version Mismatch When Connecting to a Real-Time Tar...

 

Regards,

Deborah Y.

Deborah Burke
NI Hardware and Drivers Product Manager
Certified LabVIEW Architect
0 Kudos
Message 6 of 8
(4,423 Views)

Deborah,

 

The last link you sent seems to be working, I just resolved a messy string of dependencies and reinstalled RT on the controller.  After one of the fastest install times I've ever seen, Labview 10.0 is flashing on the controller screen where 8.2 used to be, and the connectivity issues seem to be gone.  Thank you very much for your help

0 Kudos
Message 7 of 8
(4,420 Views)

Deborah,

 

  Do you remember earlier when I said both computers were running the same daqmx drivers?  Apparently the computers do not agree.  When I open the Data Neighborhood of the target in the host machine, I get the same error message shown here: http://digital.ni.com/public.nsf/allkb/A47734CC1E03922186257435004D0C49?OpenDocument.  I am using driver 9.1.7f2, and when both computers are booted into Windows, these drivers appear in the 'Installed Software' section in MAX.  However, when I boot the PXI into real time and view it remotely, these drivers (or any drivers at all) do not appear, and I am given no option to update them in the Add/Remove Software section.  I tried to downgrade to the fixed drivers in the link above, but couldn't resolve dependency issues and had to leave 9.1.7f2 installed.  I checked the compatibility chart and saw no problems, do you have any suggestions?

 

Many thanks

0 Kudos
Message 8 of 8
(4,377 Views)