Use Debug DLLs
CANLIB SDK is shipped with a number of debug DLLs and drivers; look in the …\sys\debug directory of the CANLIB SDK. The debug DLLs will send information to the debugger (using the Win32 OutputDebugString API) and might help you in trouble-shooting your application or a particular installation.
To use the debug DLLs or drivers, you have to copy them yourself to the Windows system directory, overwriting the existing DLL or driver. Then remove and reinsert the hardware or restart the computer.
- Note:
- Never attempt to deploy the debug DLLs or drivers with your application. End users are likely not to appreciate it.
To see the debug information, you can use the excellent dbgview.exe program freely available from http://technet.microsoft.com/sysinternals.
Troubleshoot hardware problems
If your software doesn't work, although you think it should, check the following things:
- Are driver and hardware properly installed? Check Kvaser Hardware in the Control Panel for error messages.
- If you have a two-channel board, connect the two channels to a short terminated CAN bus segment. Run simple.exe from the samples section in CANLIB SDK. Are there any error messages?
- Again, ensure that the CAN cable is terminated. For the standard 82C251-type transceiver (ISO11898 compliant) you must always use at least one terminator.
- For LAPcan/LAPcan II, check that pin4 in the DSUB connector is left unconnected. Connecting it somewhere might lead to unpredictable results.
- For 82C252/TJA1053/TJA1054 transceivers, check that you are not using a bit rate higher than 125 kbit/s.
- For SWC transceivers, the max bit rate is 50 kbit/s unless you are using the high-speed mode (check the software); then you can go up to around 100 kbit/s.