RKS+CAN Software: Custom Application Development

Hello,

I'm interested in the RKS+CAN adapter and have a few questions about it.

With which software, other than the KCAN Monitor, can I use this cable?

"I would like to use the cable for my own application."
What does the DLL look like exactly? What API functions are available?
Is it possible to assign a custom address to the "cable" within the DLL, so that it functions like a self-developed door controller and sends messages under its own ID?

Sure, here's the translation:

"Best regards," or "Sincerely," (depending on the context).
Gerald.

Hallo Gerald,

es gibt diverse Programme die über die virtuelle serielle Schnittstelle ansprechbar sind, Details gerne per PN.
Explizite Programme für das Interface sind derzeit KCANMonitor und KOBD2Check.

Die Hardware stellt zwei Schnittstellen per USB zur Verfügung:
- Virtuelle serielle Schnittstelle mit ASCII Befehlssatz - USB Interface DLL, nutzbar entweder mit ASCII Befehlssatz oder beliebigen Programmiersprachen die DLLs einbinden und nutzen können.

Was genau mit welcher Programmiersprache bzw. IDE willst Du realisieren?

Am Ende von http://www.canhack.de/en/viewtopic.php?t=137 findest Du eine Beispielapplikation mit Visual C++ (Example.rar).
In diesem Fall könnte eine am Interface angeschlossene Software die Funktionen Deines Türsteuergeräts erledigen.

Die API des Interface sieht so aus:

Quote:

// 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); // Direct read from hardware USB pipes (low level). Not recommended for application use if you do not know what you do. extern "C" __declspec(dllexport) BOOL RKSReadPipe(PUCHAR pucBuffer, DWORD dwBufferLength, DWORD* pdwLengthTransferred, LPOVERLAPPED pOverlapped); // Direct write to hardware USB pipes (low level). Not recommended for application use if you do not know what you do. extern "C" __declspec(dllexport) BOOL RKSWritePipe(PUCHAR pucBuffer, DWORD dwBufferLength, DWORD* pdwLengthTransferred, LPOVERLAPPED pOverlapped); // Read from hardware using the specified timeout value as maximum time to finish the operation. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSRead(PUCHAR pucBuffer, DWORD dwBufferLength, DWORD* pdwLengthTransferred); // Write to hardware using the specified timeout value as maximum time to finish the operation. Returns TRUE on success. extern "C" __declspec(dllexport) BOOL RKSWrite(PUCHAR pucBuffer, DWORD dwBufferLength, DWORD* pdwLengthTransferred); // 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);

Die selbständige Abarbeitung von gespeichterten Programmen auf dem RKS+CAN ist angedacht, macht aber zur Zeit wegen keinen I/O Pins nur bedingt Sinn, da alle Eingaben entweder über CAN oder USB kommen müssten.

Viele Grüsse, Rainer

Hello Rainer,

Thank you for your comprehensive answer.

What exactly do you want to achieve, and with which programming language or IDE?
It's not yet decided. The plan is to use Microsoft Visual Studio with C or C++.

I definitely want to use the hardware for two different purposes:
* Log and create custom CAN messages using the KCANMonitor.
* Own application on the PC.
- Simulation of a control unit (e.g., for a university project in the near future: unlocking doors via CAN bus).
- Development of custom control units. The core functionality at the communication level should initially be implemented comfortably in C. The resulting functionality should then be transferred to a microcontroller.

> The independent execution of stored programs on the RKS+CAN is considered, but currently only makes limited sense due to the lack of I/O pins, as all inputs would have to come either via CAN or USB.
This would, for example, make sense for storing a message (sequence) to be sent via RKS+CAN at a specific interval (e.g., 100ms).
Then, within your own application, you would no longer need to worry about adhering to the intervals. On the RKS+CAN, this wouldn't be a problem (provided you still have enough free timers ).

Sure, here's the translation:

"Best regards," or "Sincerely," (depending on the context).
Gerald.