Windows Installation troubleshooting
- Windows will display the "Found New Hardware Wizard" the first time you plug in a USB device in a USB port where a device of this type hasn't been used before. This is a design feature in Windows. If the "Found New Hardware Wizard" is displayed, just click the Next and OK buttons and let Windows search for the drivers. It will find them automatically.
- If a device is marked with a yellow question mark in the Device Manager, try to right click at it and select Uninstall. Then physically remove the device and reinsert it, or reboot the computer. The "Found New Hardware Wizard" should then be displayed. As described above, just click the Next and OK buttons and let Windows reinstall the drivers automatically.
- If the installation still seems to be faulty, check the Control Panel | Kvaser Device Guide | Diagnostics tab. Look for error messages. (These are clearly labeled as such.)
- You should also check the Control Panel | Administrative Tools | Event Log. Errors from the driver routines are found in the System log. The Source column tells you which driver produced the error.
- Many installation problems are solved by a reboot followed by a reinstallation of the driver package.
- Many of our devices have LEDs that can tell you something about the health of the device. For example, a Kvaser Leaf or PCIcan II that flashes quickly (around one flash per second) with the green LED typically has a firmware configuration problem. The LED flashing is described in detail in the hardware manual of the device in question.
- There are a number of scripts installed together with the drivers that can be useful when solving some more awkward problems. Go to the directory where you installed the drivers (typically c:\Program Files\Kvaser\Drivers) and read the file 00readme-scripts.txt.
Running the installation in silent mode
You can run the installation packages in silent mode, meaning that no user interaction is required. (Please note that user action still is needed when inserting the hardware). To do this, use the /S switch when starting the installation, e.g.
kvaser_drivers_setup.exe /S
The installer may exit with an exit code:
0 Normal execution (no error)
1 Installation aborted by user (cancel button)
2 Installation aborted by script
100 The virtual CAN driver, and/or the network enumerator driver, failed to start.
You should restart the computer and run the installation again.
- Note
- You will still get popup messages from Windows when the drivers are installed. This is by design - newer versions of Windows warn the user that privileged code is about to be installed. To avoid this you can do either of:
- Install Kvaser's certificate in the machine's Trusted Publisher store.
- Deploy Kvaser's certificate automatically in a Windows domain using a GPO.
- Click the Always trust software from Kvaser AB button.
-
These three things will give the same result, namely the installation of Kvaser's certificate in the Trusted Publisher store. The popup message will then not be showed.
Custom Driver Install
If you want to include the driver installation program with your application, or deploy them within your organization, you are welcome to do so but you are invited to contact us first at suppo.nosp@m.rt@k.nosp@m.vaser.nosp@m..com to discuss the technical details, join pre-release notification mailing lists and so on.
If you want to integrate the driver installation program into your own setup program, you can run it in silent mode by using the /S switch. All drivers will then be installed into their default location and no questions will be asked.
You can also run the installer with the /DISABLE switch to opt-out from installing certain parts of the driver package. The syntax is
/DISABLE=section[,section...]
Section is one of:
- GUI : the GUI tools, such as Kvaser Device Guide, the Blackbird configuration program, and the network device selector (also used toghether with Blackbird)
- STARTMENU : the shortcuts in the Start Menu.
- J2534 : registering of the J2534 driver.
- ALL : all of the above as well as any sections that might be added in future releases.
Example:
kvaser_drivers_setup_whcp.exe /S /DISABLE=GUI,J2534
Using 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.