new to compact RIO

[Clint1000]

Could anyone give me any suggestions on using COMPACT RIO or COMPACT DAQ to measure multiple pressure transducers.  Sorry for the stupid question but does that ( transducer measurement)  fall under strain??

thxs..

[Ahmed99]

compact RIO  is more powerfull and advanced

[crossrulz]

Is your goal to just read data or apply some control algorithm?  How remote is your application from your computer?

We need A LOT more information about your application to give you any real advice.

[AndyClegg]

There are a few high level pros and cons about compactrio and compactdaq in this recent forum post:

https://forums.ni.com/t5/Real-Time-Measurement-and/Best-Device-for-Control-and-Data-Acquisition/td-p...

[Clint1000]

thanks!!

[Clint1000]

I know.  This is still early in development and i was trying to get a feel for what each of these pieces of hardware are.  I come from a PXI background and trying to correlate the compact rio world to the PXI world.

thxs.

[crossrulz]

---

@Clint1000 wrote:

I come from a PXI background and trying to correlate the compact rio world to the PXI world.

---

Then think of a cRIO as an RT PXI controller with an R-series (FPGA based) DAQ.

I would correlate a cDAQ to a PXI DAQ in a remote chassis.

[Clint1000]

Do I need to know anything about programing a FPGA Card??  Or is that transparent to me?

thxs

[AndyClegg]

CompactRIOs can work without any FPGA programming (scan mode) but is for slower signals as only goes down to msec timing. FPGA is needed if you want to go faster, or if using certain IO modules which need FPGA coding to access (but there is usually some example code that is a good starting point and often do what you may need with just a few adjustments).

[AndyClegg]

To respond to your questions on the other thread:

"I come from a PC based LABVIEW PXI environment.  I'm trying to monitor a number of transducers ( yet to be picked out).  Knowing LV would LV RT be relatively easy to learn?  Or should I stick to LV and Compact DAQ?"

That depends - there are some subtle aspects that you need to be aware about, but as I said in the other thread, it can get more awkward if you have complex/multiple timing loops especially if you have loops that must be deterministic and some that are not, as you need to get the right balance between processor utilisation. For most simple / low CPU load applications you don't run into any issues, but choosing the right architecture for your code and data is important - just like with a non-RT application.

"How does the user interact ( if thats needed) if a PC isn't connected permanently ?? If I'm using COMPACT RIO I hook up a keyboard and monitor to the controller, program my application in LV RT then disconnect it ??  When the controller is powered up my application starts running??  Correct?"

A cRIO running in headless is exactly that, you deploy the LV code to it so that on power up the application starts running - and needs to be programmed to do that without user intervention. Basically the difference is that with a cRIO you either a) run the LV code interactively (which is what you do when developing, debugging, testing with connected PC with LV development) or b) deploy it so that it is basically building the compiled application and installing it to run on the cRIO (which means you don't need a development license for each application running on a CRIO).

Obviously in interactive mode you have a PC connected, but when deployed you can still connect a user interface (screen, keyboard, mouse) - some cRIOs have display ports and USB for keyboard mouse so you build UI into the cRIO application, whereas you can also build a separate UI application that is running on a PC (remote or local) that can see the variables on the CRIO. The other alternative is to build a web-browser based UI, and log into the cRIO via that.

"Don't understand this statement.  Aren't you comparing "apples to oranges"??  Isn't a chassis something the controller plugs into??  Much like a PXI8101 plugs into a PXI1062??"

This is referring to the difference between a "cRIO Chassis" and a "cRIO Controller" - they are two different categories of cRIO product with different capabilities (and both with slots for IO modules to be plugged in). You are maybe thinking about older cRIO Controllers were there controller was just the bit with the processor in and you had to physically attach a separate chasis to allow IO modules to be plugged in to

.