NI cRIO-9074 chassis connected but no modules shown

[stefanolandini2990]

Hi all,

I am working with Labview 2018 and I have a NI cRIO-9074 chassis.

I installed all software on the chassis as requested through Ni max/Softwares and the chassis is seen by the NI-MAX correctly in Remote Systems.

Also, I know this is not a chassis model that supports the cDAQ features; so I do not see the NI modules I inserted in the chassis on NI MAX.

However, if I create a project on Labview and target the Chassis I also do not see any modules.

Interestingly, if I use the application "NI Distributed System Manager" I can see the modules and even see some temperature readings from one temperature module NI-9210.

Could you help me in sorting this out?

Also, am I right that the DAQ Assist and the standard coding icons of a normal cDAQ chassis are not available to be used for this cRIO chassis?

There is any special version of Labview software for RIO?

Could you help me to understand how you can code with a cRIO which do not support the standard cDAQ icons that you can find in the Measurement tab in Labview?

[GerdW]

Hi Stefano,

---

@stefanolandini2990 wrote:

However, if I create a project on Labview and target the Chassis I also do not see any modules.

Could you help me in sorting this out?

---

Usually you need to detect/add the modules to your project. It should be a right-click menu entry on the "cRIO" item…

---

@stefanolandini2990 wrote:

Also, am I right that the DAQ Assist and the standard coding icons of a normal cDAQ chassis are not available to be used for this cRIO chassis?

There is any special version of Labview software for RIO?

Could you help me to understand how you can code with a cRIO which do not support the standard cDAQ icons that you can find in the Measurement tab in Labview?

---

Usual cRIO targets are no DAQmx devices (in the point of view of the DAQmx driver). (I know the recent cRIO targets like cRIO905x can also be used with DAQmx, but not those outdated cRIO907x.)

There is no "special version of LabVIEW" for cRIO: all you need is the RT module, which you apparently have as you can add the cRIO to your project…

The cRIO either uses the ScanEngine to communicate with the modules plugged in - or you employ the embedded FPGA, which requires the FPGA module with it's additional license cost…

Please look for the "cRIO basics" to learn about all those things - like this tutorial.