Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI

Resman Troubleshooting Guide

Resman Errors and Warnings

  • Device did not respond to MODID.

  • Device(s) not listed.

  • Resman lists devices at every logical address.

  • Unable to initialize VXI driver.

  • More than one device configured for slot 0 operation.

  • Read Protocol Error.

  • Unable to Initiate Begin Normal Operation (BNO).

  • A32 or A24 Address Space Overflow.

  • Devices in different slots found with same logical address (logical address conflict).

  • Device did not respond to MODID

    If you get a warning indicating that a device is not responding to Modid lines, this may be normal as some devices do not use the P2 connector which contains the Modid lines. In particular, many B-size VXI devices do not contain a P2 connector and VME devices do not have Modid lines.



    Resman lists devices at every logical address

    Unable to initialize VXI driver

    These errors are indicative of the fact that the NI-VXI device driver is not installed properly, or that it is not loading properly, possibly due to a conflict with some other memory resident program or device driver. Make sure that you have installed the appropriate NI-VXI driver and disable any memory resident programs and non essential device drivers:

  • Disable screen savers, virus checkers, or any other memory resident programs.

  • Disable sound card and ethernet drivers.

  • Set the Display Adapter driver to the "Standard VGA" Microsoft driver (Microsoft operating systems).

  • Exclude the region of memory from 0xD000 - 0xEFFF from other device drivers (Microsoft operating systems).

    This is accomplished by adding the line "device = emm386.sys x=0xD000-0xEFFF" to your config.sys file and the line "emmexclude = 0xD000 - 0xEFFF" to the [386Enh] section of your system.ini file.

  • (PCI-MXI-2) Contact your computer vendor to verify that you are using the latest BIOS revision and that it complies to revision 2.1 (or later)of the PCI specification. In addition, check your BIOS configuration options for a "Plug and Play" (or similar) setting and/or a "PCI bus mastering" setting. These should be disabled and enabled respectively. Note that not every BIOS has these options and that every computer manufacuter uses different naming conventions for the settings.


  • More than one device configured for slot 0 operation

    A VXI devices model code register specifies wether the device is capable of slot 0 operation. Slot 0 devices must have a model code value between 0 and 256. Therefore, this error maybe due to an error that occurred while reading a configuration register. You may be able to resolve this error by increasing the VXI/VME bus timeout setting on the VXI/VME bus controller. Note that the VXI/VME bus timeout should only be enabled on one device in the system - this should be a MXI device in systems that contain multiple bus mastering devices.



    Read Protocol Error

    You may see this error as a result of running Resman multiple times. The VXI specification does not technically allow you to run Resman more than once per chassis power cyle and some devices will not allow you to configure them once you have run the resource manager.

    This error may also be due to an error reading the devices word serial configuration registers. You may be able to resolve this error by increasing the VXI/VME bus timeout setting on the VXI/VME bus controller. Note that the VXI/VME bus timeout should only be enabled on one device in the system - this should be a MXI device in systems that contain multiple bus mastering devices.



    Unable to Initiate Begin Normal Operation (BNO).

    Early revisions of the VXI specifications differed in the way that an instrument suppported Begin Normal Operation. Therefore, one possible reason for this error is that the device does not support the modern specification.

    This error may also be due to an error reading/writing the devices word serial configuration registers. You may be able to resolve this error by increasing the VXI/VME bus timeout setting on the VXI/VME bus controller. Note that the VXI/VME bus timeout should only be enabled on one device in the system - this should be a MXI device in systems that contain multiple bus mastering devices.



    A32 or A24 Address Space Overflow.

    The Resource manager algorithm is responsible for dynamically allocating the A24 and A32 resources for all of the VXI devices in a system and this error may be encountered when using VME devices and/or in multi chassis systems. Several factors need to to be taken into consideration when implementing a multi chassis system as discussed in the Configuring Multi Chassis Systems trouble shooting section.

    The following rules should also be observed for all systems, particularly systems that use VME devices:

  • Do not use more than 8 MB in A24 space/chassis. Configure devices to use A32 resources instead of A24 resources if possible.

  • Ensure that the address offset between any devices that use A32 resources is less than 2 GB.

  • Configure the VME instruments in each chassis to use a contiguous block of A24 or A32 memory and ensure that this region does not overlap an 8 MB (A24) or 2 GB (A32) boundary. As an example two VME instuments that each require 1 MB of A24 memory might be configured at 0x000000 and 0x100000 to form a contiguous 2 MB block.


  • Devices in different slots found with same logical address (logical address conflict).

    There are three possible reasons for this error:

    1. There is a logical address conflict between two VXI devices.

    2. There is a VME device in the system that uses resources in the upper 16 KB of A16 space (0xC000-0xFFFF) and you have not added this devices resource requirements to the system configuration information.
    3. There is a defect in the MODID lines on the device/chassis. The MODID lines are located on the outer rows of the P2 connector and are used to detect the presence of a module in a slot in VXI systems.


      Your Feedback! poor Poor  |  Excellent excellent   Yes No
       Document Quality?   Answered Your Question? 
        1 2 3 4 5
      Please Provide Additional Feedback below
      Please visit Request Support for product support inquiries. submit