Which one to choose, PXI or CRIO

[university of nottingham]

Hi all,

I have read some info about both systems.I couldn't decide which system to choose, PXI or CRIO.

The system will be used as a measurement and control system for a machine test rig. I want something functional that will do the right level of data logging (temperature, vibration), communication for equipment control (power supply and power analyser) and interfacing with high level drive control (issuing references).  I am not after any fast turnaround times or ultra fast control. It will be important to keep the system as simple  as possible, I mean less manpower to develop and maintain.

The application requiremetns include:

1. Temperature measurements 10 channels thermocouple

2. 4 channels A/D and D/A for to give references

3. 4 channels USB and Serial port for communication with power supply and power analyser

4. Any vibration measurement module recommended?

Thanks for your help.

Best Regards,

HZ

[preston_johnson]

Thanks for the Post. 

1) DAQmx (the I/O driver you will use on PXI) is much easier to work with.  In CompactRIO, you need to build the DAQ driver or use some references. 

2) CompactRIO is much smaller and more rugged.  Sounds like you are inside a building at a machine test cell.  PXI should do fine here.

For test cell applications I typically recommend PXI, for its flexibility, higher channel count, and ease of programming.

For rugged outdoor or in field applications, with smaller I/O counts (30 or so or less) I recommend cRIO.

An in-between answer is CompactDAQ.  Here you have the benefit of DAQmx and small form factor.  In the event you want to upgrade to CompactRIO in the future, you can use your CompactDAQ modules in a future cRIO chassis. 

My Answer based on what you have provided (use PXI if your channel count is more than 30) or use CompactDAQ if the channel count is smaller and cost is a factor.