For mobile access, we recommend our BlackBird v2, which provides a REST api , which means that you can wirelessly connect to, and get data from, a BlackBird v2 from any device that has a web browser, such as an iPhone, Windows Phone or Android device.
You can find some examples and specifications in the REST api download in the download section of the Kvaser website.
If you want to stay on USB, it get’s a bit trickier.
We have an old Windows CE driver, but it’s not actively developed any more, so that is not a path we generally recommend, but it still works on some CE based operating system.
We do have an open sourced Linux driver, which can be used as a basis for creating you own driver for any platform.
Of course, with wireless you don’t get any guarantees, but we typically see a round trip time of less than 10 ms using a Kvaser Blackbird.
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.
1. Install your Kvaser hardware. Since the VI library calls the canlib32.dll directly, you must install Kvaser’s CANLIB driver package and your Kvaser hardware. Installations instructions can be found under the headline Drivers.
2. Install Kvaser’s CANLIB SDK. We recommend installing CANLIB SDK, i.e. Kvaser’s API to all Kvaser hardware. Installing the SDK should not be necessary for using the VI library but provides useful documentation. The API provides overview documentation on the order of the calls. This is useful when looking at the VI calls since they are just wrappers for the API. Download the CANLIB SDK from theSoftware Download Area
3. Kvaser’s VI library for LabVIEW. Do not start LabVIEW. Instead, double click on our VI library. This will launch the kvCanTree.vi and kvCanQuickStart.vi. kvCanTree is a list of all the VI’s in the library when you select show Diagram from the menu. kvCanQuickStart.vi is the example program which provides a dumbed down bus monitor. This is the easiest way to see what Kvaser’s VI library for LabVIEW is capable of. Shown below is a graphical demonstration. This is the results of double clicking on the kvCanVI.lib file. The window below shows the kvCanExample1.vi in the full screen. This VI replaced the original quickstart.vi. The window below shows the menu item to select on kvCanTree.vi to see the full diagram. The window below shows the full tree diagram which shows the individual VI’s in the library that can be called (compare these functions to functions in CANlib SDK)
This guide describes how to install a LAPcan card under DIAdem version 7 with Kvaser’s DIAdem driver. The information given here should also be valid for DIAdem version 6.Please not that this guide is only valid for Kvaser’s DIAdem driver. If you want to use Vector’s DIAdem driver, follow the “Installation instructions for Vector’s DIAdem driver on LAPcan” note.
- Install DIAdem version 6 or 7. Version 4 is 16-bit, and so out of the question.
- Install Kvaser’s CANLIB driver package and your LAPcan card.
- Copy the files kcandrv.dll and kcandrv.g5d into the DIAdem program
directory (e.g. c:\Program Files\Gfs\DIAdem.) If you can’t find kcandrv.dll, go to Windows Explorer, select View | Folder Options | View tab and make sure “Show All Files” is checked. Then go back to DIAdem.
- Copy the file kcandrv.bmp into the symbols directory of DIAdem
(e.g. c:\Program Files\Gfs\DIAdem\symbols).
- Start DIAdem. Select Options | GPI-DLL Registration. Press the Add… button. Select the directory where you installed the DIAdem driver, step 3 above, and select the file kcandrv.dll.
- Now you are back in the “Registration of GPI-extensions” dialog you opened in the previous step. Press the Close button. DIAdem asks you if you want to save the list of registered drivers in the desktop. Select Yes and do as DIAdem suggests, i.e. save the settings in desktop.DDD.
- DIAdem will now restart.
- After DIAdem has restarted, press the DAC button (the one with the green board on it).
- Select Options | Single Value Processing | Configure Driver…
- Press New Entry, check the Hardware/Driver button and press OK.
- In the list on the left, select “Kvaser CAN” and press OK.
- Optional: press the Info button to make a sanity test. A dialog with driver information should now display.
- Press Close.
- Press the “Inputs(driver)” button in the vertical toolbar on the left. Somewhere on the now appearing horizontal toolbar a button labeled CAN appears. Select it.
- Hooray! You now have a CAN block.
- Double-click on the CAN block. A combined CANdb editor and configuration dialog now appears.
- Select a suitable LAPcan channel and set the bit rate. Assign one or more CANdb files and select the signals you are interested in.
You will need to install the standard Kvaser Windows drivers and the Kvaser VI library. Both of these items are available on our website in the download section.
HS stands for “High Speed” CAN, “LS” stands for “Low Speed” CAN, and “SWC” stand for Single Wire Channel CAN.
The majority of current applications use HS – High Speed CAN. For more details on these different types of CAN networks, see Slide 6 of the CAN Protocol Tutorial which discusses the Physical Layers.
Galvanic Isolation is a combination of magnetic and optical isolation that is used to prevent ground-loops. A signal ground wire is often connected to prevent ground differential buildup between nodes on a CANbus. If the nodes are connected to the same power source, this type of isolation may be needed on your CAN interface.
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.
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:
Driver installation problems are often caused by antivirus software. A common issue is failing to install the enumeration service during the driver install.
Solution: Make sure your antivirus software is turned off and then install the driver again.
SocketCAN is a set of open source CAN drivers and a networking stack, and is included in many Linux distributions.
Many Kvaser CAN interfaces are supported by SocketCAN, including Leaf, USBcan and PCI cards. Supported hardware information can be found at http://elinux.org/CAN_Bus#SocketCAN_Supported_Controllers
Please note that SocketCAN is not maintained or developed by Kvaser, so we have very little influence over which interfaces will be supported.
Our Linux driver should work on any Linux distribution with kernel headers installed, but is only regularly tested on Ubuntu.
Just plug your MagiSync™ USB devices into your computer, the rest is automatic.
Yes, of course, but the Kvaser Leafs must be on the same root hub for the Kvaser MagiSync™ to work. This means that you need to connect your hubs in a tree-like structure so they all are connected to the same root hub.
Yes, use the “Kvaser Hardware” software program (it’s in the Control Panel) to identify a MagiSync™ group.
No, the 4GB storage component is soldered to the PCB.
The table below shows the current size of the SD card included with the product. The table also indicates whether the SD card can be removed from the unit and if the included SD card meets the Industrial temperature range or not.
Mat file, CSV file and Vector MFG Log files are compatible.
Kvaser’s ‘rugged’ branded products are designed to meet IP65 rating, which protects against moisture, vibration, shock, oil, and dust.
64 channels (in any combination of Kvaser hardware) into one PC with the appropriate Kvaser driver.
Use the Kvaser T-cannector v2 breakout box.
If the CAN bus network is accessed through an OBD diagnostic port, simply pair the Kvaser T-cannector v2 with Kvaser’s OBD II to DSUB9 Adapter Cable (00723-9) to connect multiple CAN devices to the network.
In any system with CAN – a car, for example – you may want to experiment with different ways of data logging and set different triggers or filters. To log standard fault conditions, a good choice is a Kvaser Memorator Light – a fully automatic datalogger that requires no set-up whatsoever. However, to configure different filters in order to determine how, when and what data should be logged on separate channels, you’ll need a more complex datalogger such as a Kvaser Memorator Pro. To connect both devices to the same CAN network, use the T-cannector v2 breakout box, which is compatible with most CAN interfaces or dataloggers and best of all, can distribute power to those that require it. Critically, you won’t need to do any soldering or wiring whatsoever – simple click and connect using the T-cannector v2, and get gathering data within minutes.
Error frames indicate a problem with the network topology/configuration.
You need to make sure:
1. The CAN bus is properly terminated. You should have 120 Ohm termination at the furthest points of the CAN network between CAN_H and CAN_L. This would mean you should measure approximately 60 Ohms between CAN)_H and CAN_L. We do not have termination in our products.
2. The software application talking through the Kvaser interface should be using the same bus parameter settings as the other nodes on the bus. This would be bit rate, sample point, and SJW. You will need to make sure the application you are using is setting the bus parameters correctly.
3. At least CAN_H, CAN_L, and SIG_GND nneds to be connected. In most vehicle scenarios, all nodes are using battery for V+ and GND, so the SIG_GND would be connected to this ground.
4. The network must have at least 2 active nodes on the network to have successful CAN communication. If there is just one other node on the network, you cannot be in silent mode. If no unit can acknowledge a sent frame, the sending unit will create error frames.
Azure Dynamics was a developer of electric and hybrid engines. Specifically, they developed an engine for the Ford Transit Connect. Azure went bankrupt in 2012 however, many of these vehicles are still on the road today. When there is a fault with the vehicle, the owner would need a Kvaser interface to read the DTC codes or even reset the codes once the actual problem has been fixed.
Though Azure Dynamics is no more, the necessary diagnostics drivers, some software and manuals have been archived by EVtv in their forums. To access their forums you will need a free account. The Azure Dynamics software suite is only compatible with Windows XP SP4. The software does not work with Windows Vista or 7.
The required Kvaser device is a Leaf Light HS v2 OBDII.