Error -89130: Device is Not Available for Routing

Updated Nov 26, 2025

Reported In

Software

  • LabVIEW
  • Measurement & Automation Explorer (MAX)

Driver

  • NI-DAQmx

Operating System

  • Windows

Issue Details

When I attempt to acquire data with my NI Multifunction I/O (MIO) module, I  receive the following error message:

Error -89130: Device is not available for routing. It is possible that the device needs to be reset or that the device is being reset.

 

Solution

If you encounter this error, please try the following steps:

  1. Review this article if you are communicating with a DAQ device on a real-time (RT) target.
  2. Reset the device in Measurement & Automation Explorer (MAX).  
    1. Open MAX and find your device under Devices and Interfaces.  
    2. Right-click your device and select Reset Device.
    3. If you encounter Error -88705, check the status of NI Device Loader. You can also reset the device programmatically using the DAQmx Reset Device VI.
  3. Reset the MAX configuration data. If the reset fails, try to reinstall the device: 
    1. Remove the device from the Windows Device Manager.
      1. Right-click My Computer and select Properties.
      2. Click the Hardware tab and select Device Manager.
      3. Find your device by expanding the Data Acquisition folder.
      4. Uninstall your device by right-clicking and selecting Uninstall.  (Follow the prompts to uninstall your device.) 
    2. Windows should automatically detect the device and allow the Add New Hardware Wizard to automatically choose the driver for your hardware. If your device is not detected initially, restart your computer.
      • In Window XP, navigate to your Control Panel and select Add Hardware. In Windows 7, select Add a Device in your Control Panel.
    3. After a successful reinstall, try self-testing and using test panels with the device in NI MAX
  4. If you are using DAQmx Connect Terminals VI for backplane routing, ensure:
    1. Source and destination terminals are correctly specified.
    2. Trigger source in the device’s trigger configuration is properly set.