Appendix B
Windows 98/95: Troubleshooting and Common Questions
©
National Instruments Corporation
B-3
is to look at the
Resource settings
list on the
Resources
tab to verify
that the CAN interface was not assigned a Memory Range. To solve
this problem, free up an 8 KB Memory Range (such as D0000 to
D1FFF hex) that is being used by another device in the system.
•
Code 15—The CAN interface was not assigned an Interrupt Request
level. If your computer does not have any available Interrupt Request
levels, Windows 98/95 might configure your CAN interface without an
Interrupt Request level. The NI-CAN software cannot function without
an Interrupt Request level. Another way to verify this problem is to
look at the
Resource settings
list on the
Resources
tab to verify that
the CAN interface was not assigned an Interrupt Request level. To
solve this problem, free up an Interrupt Request level that is being used
by another device in the system.
•
Code 22—The CAN interface is disabled. To enable the CAN
interface, check the appropriate configuration checkbox in the
Device
Usage
section of the
General
tab.
•
Code 24—The CAN interface is not present, or the Device Manager is
unaware that the CAN interface is present. To solve this problem,
select the interface in the Device Manager, and click on the
Remove
button. Next, click the
Refresh
button. At this point, the system
rescans the installed hardware, and the CAN interface should show up
without any problems. If the problem persists, contact National
Instruments.
•
Code 27—Windows 98/95 was unable to assign the CAN interface any
resources. To solve this problem, free up system resources by disabling
other unnecessary hardware so that enough resources are available for
the CAN interface. The resources required for a single CAN interface
are an Interrupt Request level and an 8 KB physical Memory Range
(such as D0000 to D1FFF hex).
Troubleshooting 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 resource assigned to a CAN interface
conflicts with the memory resources being used by other devices in the
system. Resource conflicts typically occur when your system contains
legacy boards that use resources that have not been reserved properly with
the Device Manager. If a resource conflict exists, write down the memory