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.
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.
Some of our customers use QNX and other RTOS. But not enough for us to justify developing and maintaining drivers for these OS environments. We find we can better support our customers by helping them develop drivers for their environment. With this in mind, we do not obfuscate our Linux driver source. We also provide the address locations for chips on our boards in the User’s Guide for the product. These documents are available on our website. We will also try to answer any questions our customer has while developing their driver.
Yes, the Linux driver is released under a dual GPL/BSD license, to allow it to be safely used in your projects.
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. The elinux.org site currently lists supported Kvaser hardware as:
**UPDATE – October 25, 2018**
Linux Kernel v4.19, is updated with support for the following devices:
- Kvaser Leaf Pro HS v2 (EAN: 73-30130-00843-4)
- Kvaser Hybrid 2xCAN/LIN (EAN: 73-30130-00965-3)
- Kvaser Hybrid Pro 2xCAN/LIN (EAN: 73-30130-01042-0)
- Kvaser Memorator 2xHS v2 (EAN: 73-30130-00821-2)
- Kvaser Memorator Pro 2xHS v2 (EAN: 73-30130-00819-9)
- Kvaser Memorator Pro 5xHS (EAN: 73-30130-00778-9)
- Kvaser USBcan Light 4xHS (EAN: 73-30130-00831-1)
- Kvaser USBcan Pro 2xHS v2 (EAN: 73-30130-00752-9)
- Kvaser USBcan Pro 5xHS (EAN: 73-30130-00779-6)
- ATI Memorator Pro 2xHS v2 (Go to ATI website)
- ATI USBcan Pro 2xHS v2 (Go to ATI website)
- Supports all PCI-[mini]PCI[e] variants
- Supports USB Leaf / Memorator / Blackbird / R
- Kvaser USBCan-II HS/LS
- Kvaser USBCan-II HS/HS
- Kvaser USBcan Rugged (“USBcan Rev B”)
- Kvaser Memorator HS/LS
- Kvaser Memorator HS/HS
- Scania VCI2 (if you have the Kvaser logo on top)
Full details can be found at http://elinux.org/CAN_Bus#SocketCAN_Supported_Controllers
If you require SocketCAN support for Kvaser products designated “v2”, please contact [email protected] for more information.
* Please note that SocketCAN is not maintained or developed by Kvaser, so Kvaser does not have direct control 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.
The battery in the Memorator Professional is used to keep track of the real time clock in the unit, and to make sure that the log files are correctly closed. It is automatically charged when the unit is used, but can get worn out after a couple of years.
If you notice your Memorator Professional loses the clock settings, it is probably a battery problem. If it has been unused for years, it might help to leave it connected to the computer over night. If this doesn’t help, it is possible to change the battery, but please note that you have to open the unit, and thereby voiding warranty. Since we don’t expect batteries to get worn out for quite a few years it is not a problem. If you have battery problem within the 2 years warranty time, we will of course replace the unit at no cost for you.
Please contact us at [email protected] if you think you need a battery change.
This quick guide details how to extract data logged by a Kvaser Memorator datalogger, without using a Memorator device.
The Memorator products store the raw CAN frames in a binary format. That data can be extracted, using the Memorator Tools, into several formats, including: .kme, .csv, .asc, .dat, .log and plain text.
Our goal is to support commonly used file formats for ease of use by the engineer.
Yes, the Ethercan Light HS can be powered by either by Power over Ethernet, or by providing power to the CAN channel.
Also receives power over CAN, so the Ethercan can be powered through devices like our T-Cannector v2 (click to view product).
- 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)
$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo make uninstall
– remove the “old” folder which contains uncompressed LinuxCAN:
$ rm -rf linuxcan
$ wget –content-disposition
$ tar xf linuxcan.tar.gz
$ cd linuxcan
$ sudo make install
Now you may try your example code and see if it works!
(48 devices connected on one bus with a cable length of 20m)
To optimize the CAN-bit-rate it is necessary to have more information about the cable layout.
The optimal cable is a straight line with a termination in both ends, where all units are connected directly to this bus-line with only recessive load.
The delay in such cable is typically 5 ns/meter cable.
With a 20 meter cable that will result in a delay of 100 ns at the propagation segment in the CAN-bit must be twice this length in time ( 200 ns).
If everything else is perfect in the CAN-system it could be possible to have a bit-length of 250ns which indicate a bit-rate of 4 Mbit/s. (1/250*1000)=4)
Unfortunately is there a number of other factors that has to be considered, that will reduce the maximum usable bit-rate.
In most cases is the installation not this perfect. Below is a list of parameters that must be known before it is possible to define the best bit-configuration.
Longest signal delay
One important factor for CAN is the longest signal delay between any two nodes connected to the CAN-bus. The main source for delays is the CAN-bus wire which the units are connected to but there is other parts in signal chain that could cause considerable delays and phase shift in the CAN-bit edges;
- The drop-length: typically is there some wire extension from the bus line down to the CAN-driver in the installed unit and that length must be known. This drop-line will add some delay time that has to be considered, but worse it will cause distortion to the signal which will show up as oscillation at the bit-edges where there is a signal level switch.
- The EMC-filter: the best is to have a clean connection between the drop-line wires and the CAN-driver. In some cases it is necessary to add on EMC-filters which could include inductors and/or capacitors. This LP-filter could cause some signal-delay that would add up to the signal delay over the CAN-bus. Such energy storage components will also be part in the signal oscillation in the same way as the drop-lines.
- The CAN-driver delay: the CAN-driver have some internal delay from the TX-pin out to the CAN-bus. There will also be a delay from the level change at the CAN-bus to the RX-pin. This delay will add up to the total signal delay over the CAN-bus (20 meter). This delay is in the range from 50 to 500 ns, depending on the CAN-driver model and the temperature.
- The galvanic isolation delay: An galvanic isolation between the CAN-driver and the CAN-controller will delay the signal both to the CAN-driver TX-pin and from the RX-pin back to the CAN-controller. For fast galvanic isolators could this delay be between 5 to 50 nanosecond, but there is devices with delays far above 1000 nanosecond.
- The delay between CAN-driver and galvanic-isolation and CAN-controller: Normally is the wire distance between components on the PCB short and negligible but if the distance is long also this delay must be considered. Normally is the wire length less than 0.1 meter which is a delay less than 1 nanosecond.
The second important factor is the oscillator tolerance. By using good oscillators, like a crystal oscillator it is possible to more or less neglect this problem. If the oscillator tolerance is worse than +/-100 ppm it is necessary to use correct compensation for this problem. It should be noted that it is the two units with lowest tolerance that will set the rules for all installed units. In other words if you have 46 units with a tolerance of +/-30 ppm and two units with +/- 800 ppm all 48 units have to adjust to the worse tolerance of 800 ppm.
By knowing the worse oscillator tolerance and the maximum delay it is possible to assign minimum propagation segment, Synch-Jump Segment, Phase Segment 1 and Phase Segment 2.
If those values are assigned to the CAN-bit you will get the highest possible bit-rate. In many cases is a lower bit-rate selected and that will provide a slack in the CAN-bit.
This slack can be be used to extend the propagation segment and by that make the system robust to future delays caused by extension of the CAN-bus or possible units with more delays in the CAN-driver, galvanic oscillation or EMC-filter. It could also be used to extend the SJW to make it possible to use future units with less oscillator tolerance. It should also be noted that a larger Phase segments that necessary to handle the oscillator tolerance will move the sample point further away from the edge and by that less sensitive to edge phase offset caused by noise.
Yes, FreeMASTER 2.0.7 has just been released on www.nxp.com/freemaster and it contains an early support of the Kvaser CAN interfaces. Support for Kvaser will continue to be developed; Kvaser LIN devices are not supported at this time of writing.
FreeMASTER is a user-friendly real-time debug monitor and data visualization tool that you can use for application development and information management. Supports non-intrusive monitoring of variables on a running system. You can display multiple variables changing over time on an oscilloscope-like display, or view the data in text form. As well, FreeMASTER supports additional capabilities and targets with an on-target driver for transmitting data from the target to the host computer.
Ideal for automotive, industrial or consumer applications.
CANlib is the shorthand name for Kvaser’s CANlib Software Development Kit (SDK). It is also the name for the first library contained in CANlib SDK. CANlib is used to interact with Kvaser CAN devices connected to your computer and the CAN bus. At its core you have functions to set bus parameters (e.g. bit rate), go bus on/o and read/write CAN messages. You can also use CANlib to download and start t programs on supported devices. If you can see your device listed in the Kvaser Device Guide tool, it is connected and you can communicate with it through CANlib.
The Kvaser CANlib SDK is available for free download.
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]
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 need 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.
The required Kvaser device is a Leaf Light HS v2 OBDII.