From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

PXI

cancel
Showing results for 
Search instead for 
Did you mean: 

NI PXI 4351 read temperature

Kevin-

 

You're right that the oversampling occurs on the device and this data does not get transferred via the PXI backplane. Everything else still applies, however. And I performed some simple mental math and I can agree that this seems to be within the PXI bandwidth, however, I am not a developer and I do not know all the reasoning behind their design choices; I was simply trying to relay some information to you as soon as possible. I think the simple fact remains that this device is intended to be synchronized with other devices in the family, which require the PXIe 100 clock, which is only present on PXIe chassis. I apologize if my information was unclear or irrelevant, but the fact remains that we currently do not have this device in the PXI form factor. I (or Jared) would be happy to relay your use case to the developers. Have a good day!

 

Thanks,

 

Sean N

Applications Engineering Specialist - Semiconductor Test
National Instruments
0 Kudos
Message 11 of 21
(1,346 Views)

It would seem to me that you should still be able to run the PXI-4351 on a PXI running RT even if you are using a WIN 7 / 64-bit computer to communicate with the PXI?

0 Kudos
Message 12 of 21
(1,270 Views)

Hi LidarLady,

 

The PXI-4351 drivers are based on the Traditional DAQ (legacy) drivers, which are not supported in Windows 7.

Message 13 of 21
(1,245 Views)

Kyle, So it is not possible to develop and compile/ build a PXI 4351 vi on an XP machine, load it on the PCI controller hard drive and run it as an executable from a WIN 7 to PXI RT configuration?

0 Kudos
Message 14 of 21
(1,240 Views)

Hi LidarLady,

 

Could you please describe what you mean by "run" on the Win7 machine?  Do you mean collecting the information via network shared variable or something else?

 

Regards,

Bobby Breyer
Applications Engineer
National Instruments
0 Kudos
Message 15 of 21
(1,216 Views)

ShishKeBobby, I have a project running on a laptop (currently Win XP / LabVIEW 2011) which communicates to a target PXI through ethernet connection of a PXI-8160 controller (running RT). I want to replace the laptop WIN XP with a laptop running WIN 7 / 64-bit. I need a quick (and temporary) solution to the incompatability of the PXI-4351 with WIN 7. I understand that even though the PXI-4351 VI is running on the PXI target under RT, it still needs to be compiled on the laptop.  So I wanted to know if I could use my XP machine to build an executable, load that executable on the PXI-8160  drive, then connect the PXI to my WIN 7 laptop, run the project (everything else is compatible), and call the executable from the main VI running on the PXI. Or have the 4351 executale running and writing data to the drive where it can be retrieved by the project.


@ShishKeBobby wrote:

Hi LidarLady,

 

Could you please describe what you mean by "run" on the Win7 machine?  Do you mean collecting the information via network shared variable or something else?

 

Regards,


 

0 Kudos
Message 16 of 21
(1,207 Views)

That actually sounds like it should work, LidarLady.  As long as the Traditional DAQ drivers are already installed on the target, and if the Windows 7 host has no reason to ever access the drivers or the 4351 directly, I think you've got a workaround.

 

Just out of curiosity, why the shift to Windows 7 from XP?  It sounds like the current setup may still be working ...

0 Kudos
Message 17 of 21
(1,195 Views)

@KBreezy wrote:

That actually sounds like it should work, LidarLady.  As long as the Traditional DAQ drivers are already installed on the target, and if the Windows 7 host has no reason to ever access the drivers or the 4351 directly, I think you've got a workaround.

 

Just out of curiosity, why the shift to Windows 7 from XP?  It sounds like the current setup may still be working ...



I need to figure out how to pass the data from the executable to the PXI application.  Any suggestions or examples on how to do that?  We are replacing the old host laptop with a faster, better laptop running WIN 7 because the XP machine is taking too long to boot and load.

0 Kudos
Message 18 of 21
(1,186 Views)

 


@LidarLady wrote:

We are replacing the old host laptop with a faster, better laptop running WIN 7 because the XP machine is taking too long to boot and load.




Try swapping your disk drive for an SSD in your lap top.  It should boot much quicker.  Also, max out your ram as much as possible.

 

I can't think of reason to switch to Windows 7, unless you need a 64bit OS to get at more than 4GB or RAM.

 

Windows Xp has now enjoyed 12 years of Moore's law.

 

Windows 7 could use a few more years of Moore's law.

 

 

 

0 Kudos
Message 19 of 21
(1,181 Views)

@kmcdevitt wrote:

 


@LidarLady wrote:

We are replacing the old host laptop with a faster, better laptop running WIN 7 because the XP machine is taking too long to boot and load.




Try swapping your disk drive for an SSD in your lap top.  It should boot much quicker.  Also, max out your ram as much as possible.

 

I can't think of reason to switch to Windows 7, unless you need a 64bit OS to get at more than 4GB or RAM.

 

Windows Xp has now enjoyed 12 years of Moore's law.

 

Windows 7 could use a few more years of Moore's law.

 

 

 


Agree on XP but got to move forward at some point. New laptop has SDD drive and max memory. Old laptop host has other issues than booting...

0 Kudos
Message 20 of 21
(1,177 Views)