Showing results for 
Search instead for 
Did you mean: 

What vi's do you use with compact rio?

Hi, im going to start using use my compact rio controller and modules soon. But i need a starting block, when i have used compact fieldpoint in the past. It had its own vi's, does compact rio have the same and if so is there any basic read multiple channel i/o examples?? that i can build on.



0 Kudos
Message 1 of 11

A good place to start would be to go to help > find examples. Then select Hardware Input and Output > Compact RIO. There are a lot of example VIs on how to work with the cRIO devices.


Knowing if you will be using scan engine, FPGA interface, or some hybrid of the two will tell you how in depth you need to go. I would say the basic IO examples would be a good place to start

[will work for kudos]
0 Kudos
Message 2 of 11



Did you use a RealTime cFP system or just an ethernet cFP?


Anyway: Programming a cRIO system is a little bit more complicated then programming a cFP, especially if you need to program the FPGA yourself. If you use the Scan Mode, then it's easier.


My tipps:

1. Go through the getting started steps.

2. Read the user manuals of your HW.

3. Use the "LV Example Finder". There are a lot of cRIO examples.

4. Read the cRIO Developer Guide.

5. Probably the best option: Attend a LabVIEW Real Time and LabVIEW FPGA course.

0 Kudos
Message 3 of 11

Hi guys thx for the replies. Think i am going to use scan mode on the rio and use the shared variables. Seems more simple, also i will have 300 inputs so it may be easier to organise in Labview.

0 Kudos
Message 4 of 11



If you are going to have 300 inputs you might want to consider the programmatic api for Scan Mode I/O.


See this white paper for more information.



0 Kudos
Message 5 of 11

Also if you have 300 inputs, you may not be able to use scan mode at all, depending on your desired data rate. As you add channels to your scan interface, your highest possible data rate decreases. You can look at the performance benchmark chart for scan engine here:


FPGA interface can be quite challenging if you are new to Labview. If you must use it, just be sure to start with example VIs and modify as necessary. Just a tip, each different module type should be in its own acquisition loop in your FPGA program because they have different clock speeds and types.

[will work for kudos]
0 Kudos
Message 6 of 11
(2,278 Views) a dilema. try scan mode or go with FPGA??. Then again i could use queues. The rio i will be using is the NI 9025, also ideally need to scan all channels within one second. Should be doo-able.

0 Kudos
Message 7 of 11

Yea if you only need to scan once per second (1 Hz) I think you will be fine using scan engine. The 9025 is a really sweet controller too, so I seriously doubt you would have a problem.


What modules do you plan to use?

[will work for kudos]
0 Kudos
Message 8 of 11

I plan to u NI 9208, 9213.

0 Kudos
Message 9 of 11

Both of those modules have 16 input channels. The maximum number of modules a chassis can hold is 8. So 8 modules at 16 channels each is 128 channels of input. So... how do you come up with having 300 inputs?

[will work for kudos]
0 Kudos
Message 10 of 11