CompactDAQ Module Not Identified in NI MAX After Restarting the Computer

Updated Mar 11, 2019

Reported In

Hardware

  • CompactDAQ Chassis

Software

  • Measurement & Automation Explorer (MAX)
  • LabVIEW

Driver

  • NI-DAQmx

Issue Details

I have an Ethernet CompactDAQ (cDAQ) chassis with multiple c series modules.  My cDAQ chassis is connected to the local network. When I restart my computer, my Ethernet cDAQ chassis can be identified but the modules inside of the chassis are shown as disconnected in MAX. I must press the self-test button  in MAX for the cDAQ chassis or the modules themselves for the modules to be identified correctly. Is there any way to avoid needing to manually press self-test in MAX?
 

Solution

There are two solutions to avoid having to manually press the self-test button in MAX to identify all your modules in your cDAQ chassis:

Software programming

  • NI-DAQmx Data Acquisition API

    DAQmx Self-Test Device.vi located in Measurement I/O >> DAQmx-Data Acquisition >> DAQmx Device Configuration. Specific information can be found in the help documentation as shown in the following picture.

    When the name of the corresponding chassis input to this vi, the chassis will self-test automatically. If the device is disconnected, the error code -88705 will be received. If the device is not found, the error code -200220 will be received.
    Note: when self-checking, the corresponding equipment according to the name of the access device will be checked, not all the devices in the system.
  • System Hardware Self-Test API

    Self-Test.vi located in Measurement I/O >> DAQmx-Data Acquisition >> System Configuration >>Hardware Management. Specific information can be found in the help documentation as shown in the following picture.

Configure cDAQ's IP address

  • When the cDAQ is directly connected to the computer. It is recommended that you set the cDAQ's IP address as a static IP address, and the computer is set to acquire it's IP Address automatically (DHCP).
  • When the cDAQ is connected to local network. It is found that no matter how IP address is set, the module will not be recognized. In this configuration, it is recommended that you use the software programming solution mentioned in the previous section.

Additional Information

The following reasons will lead to the above problem:
  • IP (dynamic or) static setting causes unstable links
  • Restarting computer will allocate a certain amount of time to deal with other application service request, this will cause NI Device Loader and NI Configuration Manager Services out of time, so the computer can’t correct loading some startup items.
Example of DAQmx Self-Test Device.vi

If you want to know the module information under specific chassis, you can select the DAQmx device attribute node.ActiveDev to access the chassis name, and Chassis.ModuleDevNames can display the information of the module.
Example of System Self-Test.vi

The system hardware self-test API can cooperate with the following API (initialization session, create the filter, find the hardware), it can detect the hardware unification in the system, and choose the right way to use it according to its own requirements.

WAS THIS ARTICLE HELPFUL?

Not Helpful