cRIO vs cFP

[UNIX]

Hi All,

 I am thinking of either using cfp or cRIO for my new DAQ control and monitoring project. I still did not see a lot of diferent that I have to go with cRIO and you have an overhead to compile vhdl code everytime you make some change to vi. It sound like you have to make more effort to write more complex code and doing the same thing as cFP. I have done application in the past with cFP 2000 and it work very well with real time packpage and data logging. Can any one tell me the big benefit  to go with cRIO instead of cFP since they both have the same functionaty in term of I/O modules. Thank you.  

 Taylor

[Wayne.C]

Taylor,

I/O modules may have similar functionalities, but there is a big difference in sample rates.  cFP I/O is more like PLC hardware.  Very rugged, not particularly fast.  As an example, I am currently testing a cFP-2220 controller with a cFP-AI-118.  The fastest overall sample rate I have been able to achieve to date is about 4Ks/s.  The cRIO is capable of sample rates greater than a 100 times faster than that.  The other part of the cRIO is the reconfigurable partition and its flexibilty to create custom hardware.

It still comes down to your system requirements and which platform best meets those needs.  If cFP sampling rates are fast enough and $$ are right, then by all means stick with what works

[Bassett_Hound]

Taylor,

Also, if your using LabVIEW 8.6 you might want to look into using the CompactRIO Scan Interface.  It gives a similar experience to Field Point without the need for compling FPGA code for every change and still allows for the flexiblity to do so in the future if desired.

Using NI CompactRIO Scan Mode with NI LabVIEW Software

Basset Hound

[Robbob]

 I work with the cRIO daily, so this may be biased, but these are my deciding factors:

The cRIO uses C series modules, new ones are always being developed, they generally sample faster, and they are compatible with several other devices(CompactDaq Chassis, C-Series USB Sleeves, Wireless DAQ)

Yes, the FPGA takes time to compile every time you make changes, but you can emulate it and test it before compilation.  Once you have the FPGA how you want it, you never have to touch it again(and it is FAST!)

The cRIO chassis is smaller, more durable(metal, not plastic), and just looks better.

Also, as has been mentioned, you can get cFP functionality with the 8.6 Scan Interface without any FPGA programming, but still have the FPGA there if you ever do want to add more functionality.