C Series Module is Not Supported by the Current Versions of LabVIEW and NI-RIO

Updated Apr 9, 2020

Reported In


  • NI-9862
  • cRIO-9048
  • NI-9262


  • LabVIEW


  • NI-RIO
  • NI CompactRIO
  • NI-WSN

Issue Details

I get the error "This C Series Module is Not Supported By This Version of LabVIEW and NI-RIO" when trying to add my C Series Module to my LabVIEW Project. What is going on? Should I be upgrading LabVIEW, or upgrading the CompactRIO Drivers?


General Troubleshooting Steps

Your version of the CompactRIO drivers may not support your hardware. You can reference our documentation regarding Software Support for CompactRIO, CompactDAQ, Single-Board RIO, R Series, and EtherCAT, select the device you'd like to see software support for, and upgrade your Modules or Drivers as necessary to ensure you are able to use the hardware.

This page is also a great resource when you are looking to acquire new hardware, as you can check in advance whether or not the hardware is supported by the software you already have.

If the Issue Happens on NI 986x XNET Modules

  • Make sure that you have NI XNET installed and that they are compatible with the version of LabVIEW you are using. You can check the LabVIEW XNET compatibility by viewing the Readme files in the XNET driver. 
  • Make sure that the XNET driver is installed on the cRIO itself. You can read the software installation tutorial for help on this step. 
  • Also check the Readme of your XNET driver version to ensure that the chassis that you are using supports XNET
    • Ethernet RIO Expansion Chassis (NI-9146, NI-9147, NI-9148, NI-9149) and EtherCAT RIO Expansion Chassis (NI-9144, NI-9145) are NOT compatible with 986x modules. 
    • This can be found under the Supported Hardware Section 

If the Issue Happens on NI-WSN Modules

  • NI-WSN is only supported by NI LabVIEW 2015 and some previous versions. You can check compatibility by viewing the ReadMe files in the NI-WSN driver .

Additional Information

  • For 904x series chassis, make sure to add the module under Real-Time Resources rather than under the FPGA target or Real-Time Scan Resources. This will result in a similar error.