Appendix F
Troubleshooting and Common Questions
©
National Instruments Corporation
F-5
PXI-846x and NI-CAN for Windows 98/95
Diagnostic Utility Failures
The following sections explain common error messages generated by the
NI-CAN Diagnostic utility.
Memory Resource Conflict
This error occurs if the memory resources assigned to a board conflict
with the memory resources being used by other hardware in the system.
Resource conflicts typically occur when your system contains legacy
hardware that uses resources that have not been reserved properly with the
Device Manager. If a resource conflict exists, write down the memory
resource that caused the conflict and refer to the Microsoft Windows user’s
guide for instructions on how to use the Device Manager to reserve memory
resources for legacy hardware. After the conflict has been resolved, run the
NI-CAN Diagnostic utility again.
Interrupt Resource Conflict
This error occurs if the interrupt resources assigned to a board conflict
with the interrupt resources being used by other hardware in the system.
Resource conflicts typically occur when your system contains legacy
hardware that use resources that have not been reserved properly with the
Device Manager. If a resource conflict exists, write down the interrupt
resource that caused the conflict and refer to the Microsoft Windows user’s
guide for instructions on how to use the Device Manager to reserve
interrupt resources for legacy boards. After the conflict has been resolved,
run the NI-CAN Diagnostic utility again.
NI-CAN Software Problem Encountered
This error occurs if the NI-CAN Diagnostic utility detects that it is unable
to communicate correctly with the hardware using the installed NI-CAN
software. If you get this error, shut down your computer, restart it, and run
the NI-CAN Diagnostic utility again. If the problem persists, try
reinstalling the NI-CAN software for Windows 98/95.
Missing Board in Diagnostic Utility
If a board is physically installed in your system, but is not listed in the
NI-CAN Diagnostic utility, check the Windows Device Manager to see if
Windows has detected the board. For more information, refer to the
section, earlier in this appendix.