How to use Kvaser Virtual Device Channel and Bus

The purpose of this document is to show how to use the virtual devices created by Kvaser Drivers.

We will cover Virtual Device, Virtual Channel and Virtual Bus.

We will focus on the WINDOWS drivers, but some information can be used also for LINUX in appendix A.

Here you will find information how to install, modify and use them.

Key words:
Virtual Device Emulates a Kvaser CAN interface
Virtual Channel Emulates a Kvaser CAN Channel
Virtual Bus Provides a virtual cable connecting the virtual channels

The Kvaser Drivers are used in this guide.

• Download and install version 5.22 or newer.

You can find the drivers here: https://www.kvaser.com/download/

The CANlib Software Development Kit (Kvaser CANLib SDK) is used in this guide.

• Download and install version 5.22 or newer.

You can find the SDK here: https://www.kvaser.com/download/

• No hardware (Kvaser Can interface) is needed to use this guide.

When installing Kvaser CAN Drivers, one virtual device is automatically installed.

Use the “Kvaser Device Guide” to view installed devices.

Default is one device with two channels. The two channels are connected to each other with a virtual loopback cable (Virtual Bus).

It is possible to add up to 16 Virtual Devices which will be shown in the next section.

Before we add more Virtual Devices, we must change two values in the registry.

By default (2018-02-08) the value is set to 2 Virtual Devices, change this to 16 Virtual Devices or whatever you need. Windows allows maximum 16 devices.

Values are in HEX! (More information on hexadecimal format here.)

Copy the text above to a textfile, name it to “Allow16KvaserVirtualDevices.REG”, and “run” it by double clicking on it. You can also do the changes directly in the registry with Regedit.EXE.

I feel lucky! Pressing Yes!

Ok, check the value in RegEdit:

Done!

Start the “Hardware Wizard”, by pressing “WinButton + R”, and type HDWWIZ and click OK.

(Before you start creating 15 more devices, scroll down and read the section “Change number of channels”!)

Can also be started from a command prompt.

Press Next.

Select Manual Install (Advanced) and press Next.

Select “CAN Hardware (Kvaser)”, and press Next.

Scroll down to “Kvaser Virtual CAN Driver”, and press Next.

O yes! Press Next!

It is possible to add 16 Kvaser Virtual CAN Drivers, if you try to add one more, Windows will show you a message like this:

And in the Device Manager you will see:

But let us assume that 16 Virtual Devices with 2 Virtual Channels each are enough for this blog.

We shall now see the number of Devices we selected to install and also the CANLib channel numbers. In this example, there are 16 Virtual Devices and 32 Virtual Channels.

It is possible to change the number of channels on the virtual devices. By default, the driver creates two channels on each Virtual Device.

You must edit a setting in the registry and reboot your computer to be able to change the number of channels.

It is possible to create maximum 8 Virtual Channels on one Virtual Device.

A reboot of the system is required after changing this value.

My intention right now is to create two Virtual Devices with five Virtual Channels each. I need them for my tests with Virtual Buses in next section.

Each default Virtual Device has by default all Virtual Channels connected to one private Virtual Bus (normally Virtual Bus #0). When we create two devices with 5 channels, all five channels on each device is connected to Virtual Bus #0. However, there is no connection between the two Virtual Devices, even if they are connected to the same Virtual Bus number! Virtual Channels can only communicate with Virtual Channels located on the same Virtual Device.

Each Virtual Device, creates a private set of 32 Virtual Buses.

There are some errors in the example above. Channel 2 can not communicate with channel 5, and channel 3 can not communicate with channel 4. (Channel 0 and channel 1 can communicate).

The Virtual Buses are not shared between the Virtual Interfaces!

You can open the Virtual Channel in CANLib, with the same commands as a physical CAN interface. The only modification needed is that we must add a FLAG.

We must add the flag canOPEN_ACCEPT_VIRTUAL  when we use the command canOpenChannel(). You can keep this flag in your software, because it does not stop you from opening a regular channel.

There are 32 Virtual Buses on each Virtual Device, and you can connect any Virtual Channel to any Virtual Bus on the same Virtual Device.

We can disconnect a channel by using the command canIoCtl().

It seems like BusOff() and BusOn() is not needed, but I think it looks a bit better if we use them before modifying the buses, even if they are virtual.

But we must know the Virtual Bus number! If you have lost track of the bus number, then use something like this (disconnects all):

Now we are pretty sure that the Virtual Channel is disconnected from the Virtual Bus.

We can connect a channel by using the command canIoCtl().

(Always disconnect the channel first, sometimes it is possible to connect to multiple buses.)

Now we have connected to Virtual Bus no 7.

Important! You must disconnect a channel!

The channel is not disconnected from the “old” Virtual Bus when connecting to a “new” Virtual Bus. All disconnection and connections must be initiated by your software.

Let us set up two devices with five channels each (the code is not complete).

Virtual Device 0
CH0 and CH1 can communicate on VB1 (Virtual Bus 1).
CH2,CH3 and CH4 can communicate on VB3 (Virtual Bus 3).

Virtual Device 1
CH5-Ch9 can communicate on VB1.

But CH0 and CH1 can not communicate with CH5-CH9, even if they seems to be on the same bus, because they are on different Virtual Devices. Each Virtual device creates a private set of Virtual Buses.

Can I use Virtual Devices with LINUX?

– Yes, in Linux you make a change in the source code (virtualcan.h):

And start the devices with:
/usr/sbin/virtualcan.sh start

In all probability you need to build something before starting the virtual devices, but that is beyond my knowledge!

If you are a Linux user and need more help at this point, please get in touch with our support team.