Appendix D Common Questions
PCI-MXI-2 for Linux D-4 ni.com
Whenever I try to execute any of the NI-VXI utilities, I receive a
message that it could not find a particular file even though the file does
exist. What is wrong?
When a NI-VXI utility cannot find a file that it needs, it usually means that
one of the environment variables is set incorrectly. Check the environment
variable NIVXIPATH and your /etc/ld.so.conf file. NIVXIPATH
should be set only to the directory where you in stalled NI-VXI
(/usr/local/nivxi by default). /etc/ld.so.conf should
includethe directory where you installed the NI-VXI library
(/usr/local/nivxi/lib by default). Run ldconfig to reread this file.
You can also receive this error message if you do not have full permissions
to some of the NI-VXI files and directories. Users who will be using
NI-VXI should have full permissions to the tbl and examples directories.
They should also have read-write permissions for all the files contained in
those directories.
Whenever I try to run resman without the MXI-2 cable plugged into
my PCI-MXI-2, it hangs. This also happens if I have the wrong end of
my cable plugged into the PCI-MXI-2. Why?
The PCI-MXI-2 uses the MXI-2 cable to find out if it is the MXIbus System
Controller. If the correct end of the cable is not securely attached to the
PCI-MXI-2, Resman and other NI-VXI applications can hang. The MXI-2
cable has a label indicating which end should be plugged into the system
controller. If you need to run Resman with the MXI-2 cable unattached, you
can force the PCI-MXI-2 to be system controller by setting the MXI
System Controller field to yes in vxitedit.