NI-XNET Modules Not Found in cDAQ-9185 or 9189 Using an NI Linux Real-Time Controller

Updated Sep 13, 2018

Reported In


  • cDAQ-9189
  • cDAQ-9185
  • cDAQ-9132
  • cDAQ-9133
  • cDAQ-9134
  • cDAQ-9135
  • cDAQ-9136
  • cDAQ-9137
  • cRIO-9035
  • cRIO-9039
  • IC-3171
  • IC-3172
  • IC-3173


  • Measurement & Automation Explorer (MAX)


  • NI-DAQmx

Issue Details

I am using a cDAQ-9185 or cDAQ-9189 chassis as expansion I/O for my NI Linux Real-Time controller. I have noticed that my NI-XNET modules are missing or do not show up in MAX when using this system configuration, but the modules do show up in MAX when I am not using an NI Linux Real-Time controller as a host. How can I make my modules show up in MAX so that I can use them in this system configuration?


The root cause of this issue is a bug in the NI-DAQmx driver documented in Corrective Action Requst (CAR) 664727. Your system will be affected if any of the following are true:
  • You are using a version of NI-DAQmx prior to 17.1.1. The steps to find your driver version will depend on your OS.
  • You are using a cDAQ-9185 or cDAQ-9189, specifically as expansion I/O for certain supported NI Linux Real-Time controllers, such as the IC-317x, cRIO-9035 Sync, cRIO-9039 Sync, or cDAQ-9132/9133/9134/9135/9136/9137 for LabVIEW Real-Time.
  • You are using an NI-XNET module with the cDAQ-9185 or cDAQ-9189.

This issue has been resolved in NI-DAQmx 17.1.1 and later. You can obtain this update through NI Update Service or you can download this driver at NI Downloads.

Additional Information

Additional information about the NI-DAQmx 17.1.1 patch can be found in the NI-DAQmx 17.1.1 Patch Details.


Not Helpful