- 0USD 0.00
- CAN HardwareBy Kvaser
- CAN SoftwarePartner Directory
- About CAN
- SupportKvaser Help Support
- Kvaser Career00
- About Us
- Kvaser Career
The first step is to think about which protocol(s) you’ll be using, and then look up the Protocol Basics and Sequence of Operation for said protocol(s). This is because the protocols are fundamentally different, and you will need to know how to treat each one to get your desired result.
If you ever get confused about why the API works a certain way, or which standards document you should consult History and Concept for how we got here.
To get access to Kvaser’s J2534 DLL you need to install the CANlib drivers, making sure “J2534 driver” is selected to be installed (which is the default).
This will both install the J2534 DLL and set up the Windows registry in accordance with the standard. If you wish to configure the DLL you do so through Kvaser’s J2534 Options Tool. This is most easily accessed via the Kvaser Device Guide, under the “Tools” menu:
This program allows you to do things such as enable logging and where the J2534 should put the log file (if enabled). This file contains information such as which DLL you’re using, what channels you connect, and all error statuses — information which Kvaser Support will find very useful if you end up needing to contact us.
The J2534 Options Tool will also show you where the J2534 DLL has been installed (as that is configurable in the Windows Registry; all the options in this tool are saved into the registry). This can be useful if you want to load the DLL directly without going through the Windows Registry.
And next to the installed DLL is the very important readme-file.
The first thing to do now is to check the readme file. If you installed the CANlib drivers to the default path then the readme can be found at C:\Program Files\Kvaser\Drivers\j2534api-readme.txt (otherwise it will be in the corresponding location). This readme contains up-to-date information about the modifications Kvaser has made to the standard in order for the API to fit cleanly on top of CANlib.
The information in the readme is important, and not included in these articles because it is all subject to change as Kvaser implements new features and receives customer feedback.
Then you’re ready to load the DLL into your favorite environment and start developing. Remember to check all status codes returned by the API, and if any errors are indicated call PassThruGetLastError() to get a more detailed description of what went wrong.
You will now be able to use your favorite Kvaser device to diagnose vehicles using any “Generic PC running a Win32 (or indeed Win64) Operating System”!