CAN to USB Interface RKS+CAN, Developer Info & Drivers

The current CANHack.de CAN Interface Hardware is the RKS+CAN from Kaufmann Automotive GmbH. It is a CAN to USB diagnostic interface with a dongle function.

This topic is only relevant if you want to develop your own programs for the RKS+CAN or if it is to be used for already existing programs.

It offers a ASCII compatibility interface (LAWICEL compatible) as well as a Windows .dll to interface with existing software (Windows, Linux, Mac).
As a new development, it supports WCID (Windows Compatible ID), which means that it can be directly accessed by applications developed for current operating systems such as Microsoft Windows Vista, 7, 8, 8.1, 10, and 11, without the need to worry about driver issues.

The hardware used has an integrated license management system and offers significant reserves for future feature enhancements; the firmware of the CAN interface is upgradeable.
For larger quantities, branding is possible. A wireless WIFI version is in the planning stages.

End customers: The CAN interface can be purchased here, the full versions of the programs KCANMonitor, KOBD2Check (includes firmware and driver installation) are included, and the RKS+CAN is compatible with many other applications.
Manufacturer: For inquiries regarding branding or custom interfaces, please contact Kaufmann Automotive GmbH - Embedded Software Development directly.

Software package customizable; the following software is included by default:
- KCANMonitor CAN bus sniffer.
- CAN-API for C++ and further examples (VB.NET, etc.).
- OBD2 software, such as KOBD2Check, which means the system can also be used for reading OBD2 error codes.
- Visualize and analyze OBD2 data with KDataScope.

RKS+CAN Feature Requests: https://www.canhack.de/en/viewtopic.php?t=2059

CAN interface USB driver / Driver information for proprietary applications.

The RKS+CAN CAN interface provides two interfaces: a virtual COM port (VCP) for Linux and macOS, as well as Windows XP to 8.1, and WinUSB for Linux, macOS, and Windows XP to 8.1.

Driver installation Windows: This is fully automated with the RKS+CAN installation package. Starting with Windows 8, no manual driver installation is required due to WCID.

In Linux, add the following line to the file /etc/modules:
usbserial vendor=0x16d0 product=0x0870
The device will then be available as /dev/ttyUSB0.

However, with Kubuntu 18.04, I had to do the following:
text
sudo insmod /lib/modules/4.15.0-210-generic/kernel/drivers/usb/serial/usbserial.ko vendor=0x16d0 product=0x0870

Information about the driver can be obtained using the command: `modinfo usbserial`.

Update for Fedora 37 and Ubuntu 22.04 LTS:
compatible with the usb-serial-simple driver.

RKS+CAN Windows Interface DLL for utilizing the WinUSB interface within your own programs.

Version history:
- January 11, 2014: Initial release.
- January 21, 2014: Bug fixes for secure initialization and hardware timestamp mode.
- January 23, 2014: Bug fix - no more CAN messages after a brief disconnection from the bus.
- January 24, 2014: Feature: Voltage measurement at the OBD2 connector.
- 02/01/2014: Bug fix, bitrate selection below 83.333 bit/s.
- June 29, 2014: Bug fix for sending messages.
- 07/03/2014: Bug fix, handling of exceptional errors.
- 07/08/2014: Update, documentation in RKS-USB.H.
- 07/08/2014: Bug fix, discontinued use of the DLL.
- 04.12.2014: New feature: Configurable hardware CAN filter.
- 12/10/2014: New feature: RTR news.
- April 27, 2018: Asynchronous processing of commands, even with an open CAN bus and incoming messages. This means that while reading CAN messages, for example, the voltage at the OBD2 connector can be queried.

API Description:

Code:

// RKS-USB.h : main header file for the RKS-USB DLL // #pragma once #ifndef __AFXWIN_H__    #error "include 'stdafx.h' before including this file for PCH" #endif // CAN frame types #define FRAME_TYPE_NORMAL     0x1 #define FRAME_TYPE_RTR        0x2 #define FRAME_TYPE_NORMAL_EXT 0x3 #define FRAME_TYPE_RTR_EXT    0x4 #define FRAME_TYPE_ERR        0x5 // CAN data structure typedef struct {   DWORD dwID;   BYTE byDLC;   BYTE abyData[8]; // max 8 data bytes } can_data_t; // CAN error information structure typedef struct {   BYTE byError; } can_err_t; // CAN information structure typedef union {   can_data_t sData;   can_err_t sErr; } can_union_t; // The final CAN frame structure used for send/receive typedef struct {   BYTE byType;   DWORD dwTimeStamp;   can_union_t uFrm;  } can_msg_t; // DLL exports // Initialize USB driver, open connection to RKS+CAN hardware. Returns TRUE on success. //  This command must be done once before calling any other RKS... function, except //  RKSDeviceConnected. extern "C" __declspec(dllexport) BOOL RKSInitialize(void); // Free USB driver and RKS+CAN hardware. Should be called to release interface/driver. extern "C" __declspec(dllexport) void RKSFree(void); // Check if the RKS+CAN is connected to the computer. Returns TRUE on success. pcBufIfGUID can be NULL. //  If pcBufIfGUID is not NULL, copy the DeviceInterfaceGUID of the RKS+CAN hardware to it. //  If you check simply if the RKS+CAN is connected, it is recommended to call it with pcBufIfGUID = NULL. extern "C" __declspec(dllexport) BOOL RKSDeviceConnected(LPSTR pcBufIfGUID, DWORD dwBufSize); // Set the timeouts for reading / writing data to the RKS+CAN interface. The software waits at maximum the //  specified values for read/write operations to complete. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSSetTimeouts(DWORD dwMsTimeoutRead, DWORD dwMsTimeoutWrite); // Get the version of the of the RKS+CAN hardware. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSGetVersion(PUCHAR pucBuffer, DWORD dwBufferLength); // Get the serial number of the RKS+CAN hardware (printed on the cable case).  Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSGetSerial(PUCHAR pucBuffer, DWORD dwBufferLength); // Return time since RKS-USB driver initialisation. bReInit can be used to reset the time to zero. //  Can be used to get relatively exact time information, the time is returned in seconds. extern "C" __declspec(dllexport) double RKSGetTimeSinceInit(BOOL bReInit = FALSE); // Get the error status of the RKS+CAN interface in pbyStatus. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSCANGetLastStatus(BYTE* pbyStatus); // Set RKS+CAN hardware to listen only mode. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSCANSetListenOnly(BOOL bEnabled); // Set time stamp mode of the RKS+CAN hardware. E.g. 0, 1 or 2. //  For possible values check the ASCII interface description. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSCANSetTimeStamp(BYTE byMode); // Get time stamp mode. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSCANGetTimeStamp(BYTE*pbyMode); // Get the supply voltage of the RKS+CAN hardware. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSCANGetUb(DWORD* pdwVoltage_mV); // Set CAN hardware filtering of the RKS+CAN hardware. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSCANSetFilter(DWORD dwCode, DWORD dwMask); // Open CAN bus with the desired bitrate. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSCANOpen(DWORD dwBitrate); // Close CAN bus. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSCANClose(void); // Get one CAN message from the receive queue, RKSCANOpen(...) must have //  been called before. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSCANRx(can_msg_t* pMsg); // Add one CAN message to the send queue, RKSCANOpen(...) must have //  been called before. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSCANTx(can_msg_t* pMsg);

C++ project for Visual Studio, compatible with versions 2008 and later, providing an example of how to use the RKS-USB.DLL within your own programs.

VB.NET program (example code) for simulating speed on NEC 24c32/64 VDO tachometers, such as those found in vehicles like the VW Passat 3C, Golf 6, and T5.2.

Quote:

I take the chance and recommend our CAN-interface RKS+CAN in english. It has the... Sure, here is the translation of the text from German to English: "following advantages:" "the following advantages:" - No issues with either USB 2.0 or USB 3.0 host devices. - No drivers required (!!!), works with Windows once connected to the computer. installs (if needed) automatically the necessary driver. The user or a... Software developers using our cable need to do *absolutely nothing*. (Windows version must be newer than XP). - Compatible with Windows XP and Windows 10. - The firmware (commands) can be customized to meet your specific needs as a software developer. - Currently it is tested out and working perfectly. If later firmware... updates may be necessary, this is absolutely NO problem. The encrypted... Firmware can be easily included with your latest software package. Updating the firmware consists of a single line of code. - Secure license management: An application can verify the validity of a license. using asymmetric encryption via elliptic curves (curve25519). Even we as... Hardware developers don't know which license is embedded in the cable! - You can identify individual cables using the cable's serial number, which you can... Do you want to print directly onto your cable, or would you prefer to use the microcontroller's internal circuitry? Serial number. - A fast microcontroller that is difficult to copy, clone, or read out: LPC1756. - Demo code (C++) for license checking/storage/firmware upgrades/CAN communication. Communication is available. - You can use your own USB VID/PID or use one of ours (exclusive to...). YOUR cable version). - Competitive price, WE are the manufacturer. Please provide the text you would like me to translate from German to English. I will then give you only the translation, without any explanations. quantities and wishes, and what you would like to change to suit your needs.

Best, Rainer.

Linux:
Vendor/Device ID for the usb-serial-simple driver successfully tested.

Code:

[ 8061.025594] usbserial: USB Serial support registered for kaufmann [ 8061.025611] usb_serial_simple 2-1.3:1.0: kaufmann converter detected [ 8061.031722] usb 2-1.3: kaufmann converter now attached to ttyUSB0 [ 8061.031767] usb_serial_simple 2-1.3:1.1: kaufmann converter detected [ 8061.031871] usb 2-1.3: kaufmann converter now attached to ttyUSB1

and suggested for integration.

If anyone is still using a version of Linux where these IDs are not included, please refer to:
RKS+CAN with Linux Fedora 37

If, for some reason, "usb-serial-simple" is not listed when you run "lsmod" with the interface plugged in, try running "insmod usbserial" and then "insmod usb-serial-simple".

Test the success using "dmesg".

Best regards, Rainer.