Frequently Asked Questions

Yes, the Kvaser Blackbird v2, Blackbird Semipro HS and Kvaser Blackbird Semipro HS/HS can all be used in either WLAN mode or in a direct USB-to-CAN mode.

CAN has undergone many updates since it was launched in 1986. As a result, CAN in Automation (CiA), the international users’ and manufacturers’ group, has introduced new terms to describe the different CAN protocols now available:

• CANclassic (abbreviated to CAN CC)
• CANflexible data rate (abbreviated to CAN FD)
• CANextended data-field length (abbreviated to CAN XL)

CiA also specifies and maintains two application protocols that run on CAN:

• CANopen (application running on CANCC)
• CANopen FD (application running on CANFD)

Throughout the Kvaser website, when the term CAN is used, we refer to CAN classic. Similarly, when CANopen is mentioned, we refer to CANopen Classic.

We do not have drivers for Apple Macbooks or desktop computers.  We have drivers for Windows and Linux.  You can run a virtual machine on your Apple computer running Linux or Windows if your machine is based on an Intel x86 or x64 architecture.  This will not currently work with the M1 based Apple computers.

The two virtual channels that comes with the driver installed are connected, working as for example two Leafs connected by a loopback cable.

If you want more virtual channels, or channels not connected, you can use the Add Hardware Wizard to add a second pair. These will be connected to each other, but not to the first pair.

1. Press Windows + R, and type hdwwiz and click OK
2. Click Next, and manual install. Select CAN Hardware (Kvaser) and Next
3. Scroll down to Kvaser Virtual CAN driver, and then Next until it finishes.

You should now have an additional pair of virtual channels ready to use.

The two virtual channels that comes with the driver installed are connected, working as for example two Leafs connected by a loopback cable.

If you want more virtual channels, or channels not connected, you can use the Add Hardware Wizard to add a second pair. These will be connected to each other, but not to the first pair.

1. Press Windows + R, and type hdwwiz and click OK
2. Click Next, and manual install. Select CAN Hardware (Kvaser) and Next
3. Scroll down to Kvaser Virtual CAN driver, and then Next until it finishes.

You should now have an additional pair of virtual channels ready to use.

To configure the Memorator, Memorator Professional, or Memorator R Semipro, you must have:

1) the Kvaser driver installed, and
2) the Memorator Tools software installed (available on our downloads page).

Using the Memorator Tools software, you can configure your Memorator device.  For a thorough walk-through, watch the instructional video below:

1. Download the latest drivers from www.kvaser.com.
2. Make sure you have administrator privileges on the computer before attempting to run the driver installation.
3. Run the driver installation package
4. Check the optional J2534 support and press Next.
5. Follow remaining dialogs until driver installation is complete.
6. Attach Kvaser hardware to the PC and complete the found new hardware wizard.

Yes, in Kvaser Memorator Config Tool, you could merge multiple log data record by selecting(highlight) the record that you need, then follow the regular steps to extract the data into the log file format you want.

Noted: This feature only works with records that are coming from the original data file in the SD Card(.kmf) format.

The Memorator series of dataloggers does not have a built-in way to perform playback.

In order to playback a stream of recorded CAN messages onto the bus, there are two options:

1.  Extract the recorded data from the Memorator to a desired format.  Then write a software application using our CANlib SDK to play the messages back on the bus using the Memorator Professional or other Kvaser USB to CAN interface (see products).

2. Kvaser also has several Technical Associates (TA’s) whose software supports playback.  This would mean:

a) extracting the data from the Memorator to a format that the TA software supports, then

b) running the TA software to play the data back on to the bus using the Memorator Professional or other Kvaser USB to CAN interface.

TA software can be found on our “Associate Software” page: https://www.kvaser.com/products-services/associate-software/

Use the filters on the right side of the screen to limit the number of applications to only “Bus Analyzers”.  Visit these software pages to confirm the playback feature.

Error-frames are very rare and in a good system there should be no Error-frames.

Even if you have Error-frames there main cause in a system is a delay of information.

It is better to handle problem on a system level where communication Errors are covered as any other error in a control system.
It should also be noted that in a real time system is one sample error like a small glitch than have very short duration in time and in most cases cannot be recognized.

The best to test a system is to place a test unit between the unit and the CAN-bus. By this test unit it is possible to delay CAN-frames and even remove CAN-frames to check how the system handle loss of information.

By this it is even possible to modify the data to check that the system can handle wrong input data without causing dangerous conditions in the system.

With good cabling there will be no Error-frames to handle.

If you get Error frames it should be registered by date and time.

This will help you to find the reason for the Error-frames.
There is no reason to have a CAN-bus with Error frames and if they occur regular with a certain intensity there is reason to find the cause of the Error-frames and take action to remove the cause of the Error-Frames.

“Using the Kvaser 2x CAN/LIN device, find and example program to send LIN
commands through python so i can test the interface. Do you have any example for it or at least a program that i might use to test the commands cause I only seen python CAN commands in your site”

If you have CANlib SDK installed on your PC, you can find a tutorial for using LIN at the linlib.html in the following CANlib SDK install directory:
C:\Program Files (x86)\Kvaser\Canlib\Samples\Python\pycanlib.zip\pycanlib\docs\tutorials\

Don’t forget that when using a channel as a LIN interface, you must provide power V+ on pin 9 of the channel connector and GND on pin 3.

Originally proposed by CiA in 2015, and completely revised in 2019, Signal Improvement Capability (SIC) is a technology to improve the quality of signals sent and received between devices on a CAN FD bus. This is done by suppressing the ringing caused by imperfect network topology. In CAN FD, arbitration ends after the arbitration segment, and the bit rate is no longer limited by arbitration, so it can be increased according to the specification (ISO 11898-1). During the data phase of a CAN FD frame the bit rate is limited by the network topology, and SIC improves the signal to allow a higher bit rate during the data phase.

Ringing is worst when the transmit signal goes from a zero to a one, or after a dominant to recessive transition. SIC can be implemented in the transmitter to suppress the ringing when transmitting, or in the receiver to filter the ringing when receiving. Both implementations enable an increased data bit rate, but they differ slightly in the details. SIC is not usually needed in Classical CAN because the bit rate is limited by arbitration and does not change during the data phase. Since Classical CAN does not increase the bit date after arbitration, SIC is not needed and would not add any benefits.

More information can be found at https://can-cia.org/can-knowledge/can/cia601/ and by downloading the CiA document 601 series: CAN FD guidelines and recommendations.

The Kvaser USBcan Pro 4xCAN Silent is a ‘listen-only’ CAN interface. It is used by developers of highly sensitive autonomous or safety-critical systems to ensure that the interface has no impact on the bus or surrounding systems. It is also selected to prevent any application or third-party, such as a hacker, from impacting the CANbus and its related systems through the Kvaser device.

In contrast to a CAN interface with software-implemented silent mode, the Kvaser USBcan Pro 4xCAN Silent is internally wired by hardware to be permanently silent. This means it is not capable of transmitting any CAN data frames, error frames, or any other frames, and it will not participate in the normal CAN protocol by transmitting an Acknowledge (ACK) slot after receiving a proper frame from another device. More simply stated, in ISO 11898 terminology, the Kvaser USBcan Pro 4xCAN Silent interface will never drive the CAN bus to a dominant state.

The Kvaser CANlib SDK works at the raw CAN frame level.  This means the API  can be used to implement software that communicates using J1939, CanOpen, NMEA2000, DeviceNET, UDS, etc.  The implementation of these protocols is the responsibility of your application.

GEMAC, a German manufacturer of fieldbus diagnostics devices, is supporting Kvaser CAN interfaces in the latest version of its CANvision protocol monitor, version 1.3.4.1. The bus monitoring and decoding software, which handles CAN, CANopen, CANopen FD and SAE J1939 (including NMEA 2000® and ISOBUS) messages, supports Kvaser in interface mode only.

For more information on CANvision, please visit gemac-fieldbus.com/en/ or address questions to support@gemac-fieldbus.com.

AutonomouStuff has created ROS (Robot Operating System) support for Kvaser interfaces using the Kvaser Linux driver. You can find the Kvaser ROS support package and dependency information here: https://github.com/astuff/kvaser_interface

If you still have questions, please contact AutonomouStuff support at: support@autonomouStuff.com

Multiple handles to the same channel work like a virtual bus extension.  When a message is successfully placed on the CAN bus through the canWrite call, a copy of the message is placed in every handle’s receive buffer associated with the same channel.  This is the default behavior.  You can change this behavior for a handle using the canIoCtl function with a func parameter value of canIOCTL_SET_LOCAL_TXECHO.  See the API documentation for more detail.

The Kvaser U100 will run on almost any hardware. With no repacking and bundling in the USB communication, the Kvaser U100 creates more USB packets when compared to a Kvaser Leaf Pro or Leaf Light. The load on the host CPU will be higher, so it is recommended that the host application has access to enough CPU cores. The Kvaser U100 also requires USB controllers and hubs that are quick and have adequate capacity. (Almost all PCs sold in the last 5 years will have the proper capacity).

Internally: The Kvaser U100 uses a much more powerful processor compared to the Kvaser Pro and Light interfaces. Even though it is more powerful, it still consumes less power.

Externally: The USB communication is much more optimized, both in the Kvaser U100 hardware and also in the Kvaser Drivers. There is no need to do any smart “repacking and bundling” of the CAN frames as the Kvaser U100 has the capacity to handle both USB and CAN communication at the same time.