Can Multiple Instances of .NET programs connect via the CANLib to the same IO Card at the same time , if so Is the .NET library Thread Safe ?

13/09/2019 by Kvaser

In general, all our SDK are thread safe.
If the card has one, two or four channels does not matter. One channel does not know if it has a “neighbour” or not. In the SDK you can open a HANDLE to a channel. It is important that all instances opens its own HANDLE to the channel, even if it is the same channel.

Can Filters be setup via software for each program calling the card (i.e. does it support software filtering as well as hardware filters ?)

I will not answer this question until I have been able to talk to the developers.

  • Do the CAN cards contain a visible firmware revision from the API that can be BOM controlled ? If so can it be checked by the .NET lib
    Yes! You can read (in your software using our SDK) the serial number, the EAN code, the SW version and some more information. The same information can be read with our software “Kvaser Device Guide” that is installed when installing the drivers.
  • Do you plan to support the .NET UWP Platform (Universal Apps)
    It is our list of things todo in the future. There are no plans for the moment.
  • Is there a .NET Core Implementation of the library , if not can they provide one ?
    Same answer here, we have not yet started this implementation, but it is not forgotten…

How long has the .NET library and its associated C++ API been released (i.e. how many years). What was the reason for the last major change V4 – > V5?

The first time I can find .NET in our releases is in V4.5 (Release 02-MAY-2011), but it was not fully implemented until V4.6 (Release 16-SEP-2011).
V4 vs V5 , When I check the documentation I do not find anything extraordinary, some regular bugfixes, minor addons and some fixes.
When I read the press release I find this:
The latest version of Canlib, the software development kit that is used across Kvaser’s interface range, is now available. Canlib v5.0 adds support for SAE J2534, the so-called ‘Pass-Thru’ standard for vehicle programming. Whilst J2534 CAN traffic could be read in previous versions, it will now run three times faster than in earlier releases. Canlib 5.0 also includes the latest version of Kvaser’s t compiler, an important element of the programming language used to develop customised applications for Kvaser’s Eagle CAN datalogger (Memorators).

Well I have never used SAE J2534… I do not think it was so dramatic.

(This info added 2019-01-23) Main reason: Harmonizing the WINDOWS SDK with the LINUX SDK. Earlier the WIN and Linux had been separated, but we try to make them as similar as possible.