Error -88900 in NI MAX

Updated Apr 18, 2024

Reported In

Hardware

  • CompactDAQ Controller
  • cRIO-9040
  • cRIO-9041
  • cRIO-9043
  • cRIO-9046
  • cRIO-9045
  • cRIO-9048
  • cRIO-9049
  • cRIO-9042
  • cRIO-9055
  • cRIO-9054
  • cRIO-9056
  • cRIO-9057
  • cRIO-9053
  • cRIO-9058

Software

  • Measurement & Automation Explorer (MAX)

Operating System

  • Windows

Issue Details

  • When expanding the Devices and Interfaces subtree under my Linux Real-Time (RT) target compatible with the NI-DAQmx driver, I can see that the chassis and/or the C Series Modules connected to it have a red "x" next to them. When selecting them, NI MAX displays error -88900. 
  • When attempting to expand/open NI-DAQmx Global Virtual Channels under Data Neighborhood in an NI-DAQmx compatible RT target, NI MAX hangs for 4 to 6 minutes before it returns a list of global channels. After the list is returned, if I click on one of the global channels, the right pane displays error code -88900.
    Error -88900 occurred at Device Communication
    
    Possible Reason(s):
    
    The specified remote target is not reachable. Ensure that the target is running. 

The error is shown in the following dialog box:
error -88900.png

Solution

This error may be caused due to different reasons. The most common ones are software incompatibilities or hardware issues. If you are seeing this error in NI MAX, there are a few troubleshooting steps and considerations:
  • Check the Readme of the drivers to confirm compatibility of the driver version with the hardware/OS/software version. You can use the following documentation as a guide as well: Software Support for CompactRIO, CompactDAQ, Single-Board RIO, R Series, and EtherCAT.
  • Verify that the NI-DAQmx driver version you have installed on your real-time target is the same one available on your development PC. 
  • Check Windows Device Manager for the DAQ devices. If the device shows up in Windows Device Manager, try the steps listed in the following article: DAQ Device Not Listed in MAX But Shows Up in Windows Device Manager.
  • Check the pins on the modules and cables for any damage or bent pins. This can cause miscommunication if there is not good contact between the points.
  • Try different cables/ports for the hardware. Sometimes ports or cables can be corrupted or damaged.
  • It is important to be aware of the Installation Order for Multiple NI Software Products . If LabVIEW is installed after the drivers, LabVIEW will not be able to recognize the drivers to use. If the original configuration was correct and later you upgrade/update LabVIEW, you may need to repair your other software to allow them to be recognized as being installed after the upgrade/update.
  • This could happen due to a corrupted installation and dependency issue between NI-TimeSync and NI-DAQmx drivers. Make sure to upgrade those two driver versions together. Re-install NI-DAQmx on the target if the issue persists. 



 

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement may be required, and support options vary by country.