NI-MRU Error Code Family
Below are all of the Error Codes that belong to the NI-MRU Error Code Family (see Error List for list of Families).
| Code | Description |
|---|---|
| -89169 | The installed version of the driver for this device is no longer supported. Install the current version of the driver for this device. |
| -89168 | Could not connect to the NI Route Coordinator service. Ensure that the NI Route Coordinator service is installed and started. |
| -89167 | PXIe_DStar<n> (A, B, or C) is available as a destination terminal only for devices in a system timing slot.
To use PXIe_DStar A, B, or C (without any numbers), do not specify a star line number. To use PXIe_DStar<n> (A, B, or C), move your device to a system timing slot. |
| -89166 | PXIe_DStar<n> (A, B, or C) is available as a source terminal only for devices in a system timing slot.
To use PXIe_DStar A, B, or C (without any numbers), do not specify a star line number. To use PXIe_DStar<n> (A, B, or C), move your device to a system timing slot. |
| -89165 | PXIe_DStar (A, B, or C) is not available as a source terminal in your device's current slot.
Move your device to one of the slots connected to the DStar Trigger bus, or select a different source terminal. |
| -89164 | PXIe_DStar (A, B, or C) is not available as a destination terminal in your device's current slot.
Move your device to one of the slots connected to the DStar Trigger bus, or select a different destination terminal. |
| -89162 | PXI_Clk10In is available as a destination terminal only for devices in a star trigger slot.
Move your device to a star trigger slot. |
| -89161 | PXI_Clk10In is available as a destination terminal only for devices in a system timing slot.
Move your device to a system timing slot. |
| -89160 | PXI_Star<n> is available as a destination terminal only for devices in a star trigger slot.
To use PXI_Star (without any numbers), do not specify a star line number. To use PXI_Star<n>, move your device to a star trigger slot. |
| -89159 | PXI_Star<n> is available as a destination terminal only for devices in a system timing slot.
To use PXI_Star (without any numbers), do not specify a star line number. To use PXI_Star<n>, move your device to a system timing slot. |
| -89158 | PXI_Star<n> is available as a source terminal only for devices in a star trigger slot.
To use PXI_Star (without any numbers), do not specify a star line number. To use PXI_Star<n>, move your device to a star trigger slot. |
| -89157 | PXI_Star<n> is available as a source terminal only for devices in a system timing slot.
To use PXI_Star (without any numbers), do not specify a star line number. To use PXI_Star<n>, move your device to a system timing slot. |
| -89156 | PXI_Star is not available as a source terminal in your device's current slot.
Move your device to one of the slots connected to the Star Trigger bus, or select a different source terminal. |
| -89155 | PXI_Star is not available as a destination terminal in your device's current slot.
Move your device to one of the slots connected to the Star Trigger bus, or select a different destination terminal. |
| -89154 | PXI_Star is not available as a destination terminal for devices in a star trigger slot. A star trigger slot has specific PXI_Star<n> lines, such as PXI_Star3.
Move your device to one of the other slots connected to the Star Trigger bus, or select a different destination terminal. |
| -89153 | PXI_Star is not available as a destination terminal for devices in a system timing slot. A system timing slot has specific PXI_Star<n> lines, such as PXI_Star3.
Move your device to one of the other slots connected to the Star Trigger bus, or select a different destination terminal. |
| -89152 | PXI_Star is not available as a source terminal for devices in a star trigger slot. A star trigger slot has specific PXI_Star<n> lines, such as PXI_Star3.
Move your device to one of the other slots connected to the Star Trigger bus, or select a different source terminal. |
| -89151 | PXI_Star is not available as a source terminal for devices in a system timing slot. A system timing slot has specific PXI_Star<n> lines, such as PXI_Star3.
Move your device to one of the other slots connected to the Star Trigger bus, or select a different source terminal. |
| -89150 | The value specified does not correspond to any terminal connection behavior. |
| -89149 | PXI_Clk10In is available as a destination terminal only for devices in the star trigger controller slot (slot 2).
Move your device to PXI slot 2. |
| -89148 | PXI_Star<n> is available as a destination terminal only for devices in the star trigger controller slot (slot 2).
To use PXI_Star (without any numbers), do not specify a star line number. To use PXI_Star<n>, move your device to slot 2. |
| -89147 | PXI_Star<n> is available as a source terminal only for devices in the star trigger controller slot (slot 2).
To use PXI_Star (without any numbers), do not specify a star line number. To use PXI_Star<n>, move your device to slot 2. |
| -89146 | PXI_Star is not available as a source terminal for devices in PXI slots 16 and above.
Move your device to one of slots 3 through 15, or select a different source terminal. |
| -89145 | PXI_Star is not available as a destination terminal for devices in PXI slots 16 and above.
Move your device to one of slots 3 through 15, or select a different destination terminal. |
| -89144 | PXI_Star is not available as a destination terminal for devices in PXI slot 2. PXI slot 2 has specific PXI_Star<n> lines, such as PXI_Star3.
Move your device to one of slots 3 through 15, or select a different destination terminal. |
| -89143 | PXI_Star is not available as a source terminal for devices in PXI slot 2. PXI slot 2 has specific PXI_Star<n> lines, such as PXI_Star3.
Move your device to one of slots 3 through 15, or select a different source terminal. |
| -89142 | Route failed because the PXI chassis is not identified. The existence of the destination terminal depends on the chassis being identified.
Use the Measurements & Automation Explorer (MAX) to identify your chassis. |
| -89141 | Route failed because the PXI chassis is not identified. The existence of the source terminal depends on the chassis being identified.
Use the Measurements & Automation Explorer (MAX) to identify your chassis. |
| -89140 | Driver cannot complete the route, because the only way to make the route requires a trigger bus line, and no trigger bus has been configured in MAX for this device.
If you have a PXI chassis, make sure it has been properly identified in MAX. If you are using a PCI device, create a RTSI cable in MAX that includes your PCI device even if you are not using any RTSI cables. |
| -89139 | There are no shared trigger lines between the two devices which are acceptable to both devices. While each of these two devices support some shared trigger lines, none of these shared trigger lines work for both devices for the specified property and corresponding value.
Consider routing the signal through the I/O connectors of the two devices, if applicable. |
| -89138 | Specified route cannot be satisfied, because it requires resources that are currently in use by another route within this task. |
| -89137 | Specified route cannot be satisfied, because it requires resources that are currently in use by another route. |
| -89136 | Specified route cannot be satisfied, because the hardware does not support it. |
| -89135 | Specified inversion cannot be satisfied, because it requires resources that are currently in use by another route within this task. |
| -89134 | Specified inversion cannot be satisfied, because it requires resources that are currently in use by another route. |
| -89133 | Specified inversion cannot be satisfied, because the hardware does not support it. |
| -89132 | Specified property value cannot be used, because it requires resources that are currently in use. |
| -89131 | An attempt has been made to perform a route when the source and the destination are the same terminal.
In many cases, such as when configuring an external clock or a counter source, you must select a PFI, PXI Trigger, or RTSI line as the source terminal. |
| -89130 | Device not available for routing. It is possible that the device needs to be reset or that the device is being reset.
If you are resetting the device, wait for the reset to complete. For example, if you have used the device through Traditional NI-DAQ, you must reset the device before the requested route can be made. For SCXI devices, you must reset the communicator DAQ device. Call the Traditional NI-DAQ Device Reset VI or the Init_DA_Brds function. To reset all devices in Traditional NI-DAQ, right-click the Traditional NI-DAQ Devices folder in MAX and select Reset Driver for Traditional NI-DAQ. |
| -89129 | Terminal for the device is invalid. |
| -89128 | Terminal could not be tristated because the hardware cannot tristate this terminal. |
| -89127 | Terminal cannot be tristated because it is busy.
Disconnect any routes spanning this terminal, or stop using this terminal. |
| -89126 | Trigger line requested could not be reserved because it is already in use. |
| -89125 | No registered trigger lines could be found between the devices in the route.
If you have a PXI chassis, identify the chassis correctly in MAX, and make sure it has been configured properly. If you are using PCI devices, make sure they are connected with a RTSI cable and that the RTSI cable is registered in MAX. Otherwise, make sure there is an available trigger line on the trigger bus shared between the devices. |
| -89124 | Route cannot be made between the source and destination terminals.
Either the hardware does not support this route or other routes might be interfering with this route. |
| -89123 | Hardware necessary for this route is in use by another route or routes. |
| -89122 | Inversion requested is not possible.
Either the hardware between the source and destination terminals does not support the inversion, or other routes might be interfering with this route. |
| -89121 | Destination terminal to be routed could not be found on the device.
Make sure the terminal name is valid for the specified device. Refer to Measurement & Automation Explorer or your hardware documentation for valid terminal names. |
| -89120 | Source terminal to be routed could not be found on the device.
Make sure the terminal name is valid for the specified device. Refer to Measurement & Automation Explorer for valid terminal names. |
| -89119 | An internal error occurred. |
| -89118 | An internal error occurred. |
| -89117 | An internal error occurred. |
| -89116 | An internal error occurred. |
| -89115 | An internal error occurred. |
| -89114 | An internal error occurred. |
| -89113 | An internal error occurred. |
| -89112 | An internal error occurred. |
| -89111 | An internal error occurred. |
| -89110 | An internal error occurred. |
| -89109 | An internal error occurred. |
| -89108 | An internal error occurred. |
| -89107 | An internal error occurred. |
| -89106 | An internal error occurred. |
| -89105 | An internal error occurred. |
| -89104 | An internal error occurred. |
| -89103 | An internal error occurred. |
| -89102 | An internal error occurred. |
| -89101 | An internal error occurred. |
| -89100 | An internal error occurred. |
| -54023 | An internal error occurred. |
| -54022 | An internal error occurred. |
| -54021 | An internal error occurred. |
| -54020 | An internal error occurred. |
| -54012 | An internal error occurred. |
| -54011 | An internal error occurred. |
| -54010 | An internal error occurred. |
| -54002 | An internal error occurred. |
| -54001 | An internal error occurred. |
| -54000 | An internal error occurred. |