No, you only need one Blackbird.  A Blackbird can connect to an existing wireless router network in infrastructure mode or directly to a PC in ad hoc mode.  The PC will use our standard Windows drivers to configure the Blackbird and select the Blackbird for use.

No, Kvaser does not have this connectivity at this time.

Yes, by using our supporting library kvrlib.

Kvrlib can be used to connect to units connected to the host computer, scan for networks, and all other configuration that is usually done trough the Kvaser Hardware -> Tools -> Setup a Kvaser Blackbird / Select Kvaser BlackBird from the Network configuration tools.

Once a BlackBird or Blackbird v2 is configured and setup for use on a specific computer, Canlib can be used as usual, just as if the unit was connected on USB.

Kvrlib comes with the canlib install.

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.

1. Choose CAN->Driver Selection->Kvaser CAN

2. If this is the first time to choose Kvaser device, a “Hardware Selection” windows will be popped up. Otherwise go to CAN->Channel Selection to choose the Hardware Channel.

3. Choose CAN->Channel Configuration, to configuration the Bus Parameters such as Baudrate, Sampling Point, SJW, Filter..etc

4. CAN->Connect to go Bus On.

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.

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.

You may not have both LinuxCAN and SocketCAN on a Linux machine as by installing LinuxCAN the SocketCAN gets blacklisted.

• Follow the guide: https://www.kvaser.com/linux-drivers-and-sdk/
• Make sure that you follow the instruction below(Kvaser Hybrid x2 on Ubuntu 18.04):
  – unplug Kvaser device(s)
  – run
  $ sudo apt-get update
  $ sudo apt-get upgrade
  – reboot
  – run:
  $ sudo make uninstall
  – remove the “old” folder which contains uncompressed LinuxCAN:
  $ rm -rf linuxcan
  – run:
  $ wget –content-disposition
  “https://www.kvaser.com/downloads-kvaser/?utm_source=software&utm_ean=7330130980754&utm_status=latest”
  $ tar xf linuxcan.tar.gz
  $ cd linuxcan
  $ make
  $ sudo make install
  Now you may try your example code and see if it works!

If you want to have Secure Boot enabled and sign the drivers:

• https://www.kvaser.com/developer-blog/secure-boot-linux-systems/
• https://www.kvaser.com/developer-blog/build-install-signed-kvaser-driver-modules/

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.

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: [email protected]

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 [email protected].

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.

Yes, it is. An example on how to use it can be found in your CANlib directory, C:\Program Files (x86)\Kvaser\Canlib\Samples\Example\tScript\Misc. The lintest.t example will show a basic setup on how to set up a LIN t-script.

LIN Transceiver require reference voltage between 9-18V DC according to the LIN Protocol Specification. You need to have an external reference voltage to PIN9 of the DSUB connector. This is applicable to both the Kvaser Leaf Professional LIN as well as all Kvaser Hybrid series interfaces.

For users that do their own programing with canlib/linlib SDK, a status of linERR_NOTFOUND will be returned if the LIN Transceiver doesn’t have reference power.

The Kvaser U100 supports all features that the Kvaser Leaf Light HS v2 can handle. Normally no adjustments of the software is needed.

The Kvaser U100P supports all features that the Kvaser Leaf Pro can handle except one; the U100P does not support t programs.