Resman Troubleshooting Guide
Resman doesn't find any or all devices, or Resman hangs
Resman Hangs
- Does vxiinit run properly? vxiinit must be run before Resman on all NI VXI driver versions exept for NI VXI driver versions 2.0 and later
on Windows 95/98/NT/2000.
If vxiinit fails, then this means that the NI VXI driver has not been installed properly,
or that there is some sort of resource conflict (hardware or software) that needs to be resolved.
Follow the steps listed under the "Resman does not find all devices" section below if vxiinit does not fail, or if you
are using NI VXI 2.0 or later on Win 32 systems.
Resman does not find all devices
- If using VME devices, these must be properly configured.
- Ensure that you have the latest version of NI-VXI/NI-VISA for your particular operating system.
- If you have a multiple mainframe configuration, please refer to the Multiple Mainframe System Configurations section
and the documentation which came with your controller to ensure that you have this configured correctly.
- Make sure that the MXI bus Controller end of the MXI-2 cable is closest to the MXIbus system controller (By default the AT-MXI-2 or PCI-MXI-2). The MXIbus Controller end of the cable has a label on that particular end.
- Check the connectors on the MXI-2 cable and on the PCI/VXI/VME-MXI-2 cards for bent or broken pins.
- Remove all other devices from the VXI or VME mainframe (except the one that isn't seen).
- If problems persist, make sure the VXI/VME-MXI-2 is in the leftmost slot and that it is is detected when no other instruments are installed.
- Run the VXI Interactive Control utility (VIC) to attempt to read from the configuration registers at the logical address that you have set for your device.
- Try using a different mainframe, VXI controller, or MXI cable if these are available.
- The "missing" device may be faulty. Try using a different device to help isolate the problem. Please contact that vendor for further assistance.
- Contact National Instruments for further assistance.
