Vxiinit Could Not Find The At-Mxi; Vxiinit Could Not Find Specific Files - National Instruments VXI-AT2022 Getting Started

Troubleshooting

vxiinit Could Not Find the AT-MXI

When you run vxiinit, it attempts to locate the AT-MXI board by accessing the I/O registers
that exist on the board. The AT-MXI board occupies 32 bytes of I/O space at a default base
address of 340h (hex). The base I/O address of the AT-MXI is set in both hardware and software
and the two settings must agree. If the hardware and software settings do not agree, you may
receive an error message that reads VXI device not found.
In hardware, you use a set of DIP switches on the AT-MXI board itself if you need to change the
setting of the base I/O address. Refer to the Base I/O Address Selection section of Chapter 2,
Hardware Configuration and Installation, for more information about selecting a base I/O
address for the AT-MXI. Keep in mind that if you change the base I/O address of the AT-MXI,
you must make a corresponding change to the AT-MXI configuration software.
To change the I/O address in software, you need to run the VXI resource editor program,
vxitedit, and use the Logical Address Configuration Editor to make the change. Refer to the
Configuring the NI-VXI Software section of Chapter 3, NI-VXI Software Installation and
Configuration, for instructions on how to use the VXI resource editor program.
After you verify that the software settings correspond to the hardware setting, try the following
methods to deal with this problem.
1. Ensure that you are using the proper vxiinit program for your system. For example, the
vxiinit program distributed with the VXIpc-486 cannot be used to initialize the AT-MXI.
2. If the hardware and software settings match, ensure that the I/O registers settings of the
AT-MXI do not conflict with any other hardware in the PC AT. If they do, change the
settings of the AT-MXI or the other device.
3. Make sure the AT-MXI is securely seated in the ATbus slot or try another ATbus slot.
4. If the message persists, there is still some reason that the NI-VXI software cannot access the
I/O registers of the AT-MXI. If possible, try the AT-MXI in another computer.

vxiinit Could Not Find Specific Files

vxiinit may inform you that it cannot find one or more of the configuration or table files, for
example, File vxila.cfg not found. Other files for which error messages are generated
include vxibus.cfg, vxidev.cfg, mfnameid.tbl, and model.tbl. There are two
possible causes for this error message.
1. The file(s) may have been deleted accidentally. If the file does not exist in your tbl
directory after you installed your software, you can find it on your original NI-VXI
distribution media and restore it manually.
2. The NIVXIPATH variable may be pointing to the wrong directory. The path should be set in
the .cshrc or .profile files, depending on the shell type you are using (Refer to the
Installing the Software section of Chapter 3). Set the correct path for the NIVXIPATH
variable, for example, /usr/nivxi.
VXI-AT2022/NI-VXI SCO UNIX Getting Started B-2 © National Instruments Corporation
Appendix B