4.0.10 04/05/2026

Bug fixes

• Fixed an issue preventing PCAN-PCIe chip solutions from being added as RP1210C devices
• Fixed an issue preventing PCAN-USB FD devices from being added as RP1210C devices

4.0.9 31/03/2026

Improvements

• General code enhancements

Bug fixes

• Fixed a bug where reading CAN Classic messages in blocking mode resulted in a race condition in some scenarios
• Fixed a bug where the test application crashed when changing randomly generated data of CAN CC Tx messages

4.0.8 10/09/2025

Improvements

• Added support for PCAN-USB XL as a compatible RP1210C device

Bug fixes

• Fixed an issue in RP1210_SendMessage related to the ISO 15765-2 protocol: in some scenarios, an empty consecutive frame was being sent

4.0.7 18/12/2024

Bug fixes

• The return value of the RP1210_GetHardwareStatus function was wrong
• It was possible to connect to the channels of only one PCI card, although several cards were connected to the PC
• It was not possible to connect to any PCAN-LAN channel (PCAN-Gateway devices)

Changes

• Adjustments to comments in the code and in the help document for better understanding

4.0.6 24/04/2024

Improvements

• Test application supports sending J1939 request commands
• Test application now colorizes received echo messages

Bug fixes

• When the API was configured to receive echoes, all large J1939 messages received were marked as echoes, regardless of whether they were echoes or not
• When the API was configured to receive echoes, self-transmitted and normally received J1939 single-frame and CAN messages had their reception status inverted

4.0.5 12/07/2023

Improvements

• General enhancements and adjustments within the test application

Bug fixes

• When a channel had associated PCAN networks configured for CAN FD communication, trying to connect to that channel ended with the 'HARDWARE_NOT_RESPONDING' error
• PCAN-PCI Express cards were being registered and shown with a wrong name
• The test application was showing wrong PGN values when using the J1939 protocol

Changes

• The test application is suitable for 64-bit Windows operating systems only

4.0.4 07/03/2023

Improvements

• Enhancements regarding ARM64

Bug fixes

• Fixed issue retrieving file version using the RP1210_ReadVersion or RP1210_ReadDetailedVersion functions

Changes

• RP1210_ClientConnect now returns ERR_CAN_BAUD_SET_NONSTANDARD only if another RP1210 application has initialized the hardware with a different bit rate than 250 kbit/s, not when a general CAN application like PCAN-View does

4.0.3 21/10/2022

Improvements

• New ARM64 API library

4.0.2 30/08/2022

Improvements

• General code enhancements

Bug fixes

• Attempting to connect to an existing and registered channel resulted in HARDWARE_NO_RESPONDING in some scenarios
• When registering a device, its ID value was saved in the wrong format in some scenarios
• Test app bug fixed: Creating a message to transmit over CAN with DLC 0 was causing the app to crash

Changes

• There is no single RP1210 setup anymore. A RP1210 package is now delivered containing documentation, header files, and a test application

4.0.1 10/12/2021

Improvements

• RP1210_Test Application updated to support broadcast messages configuration for all three protocols, CAN, J1939, and ISO15765

Bug fixes

• RP1210_SendCommand failed when trying to set the same bitrate several times in a row (commands: RPCMD_SET_CAN_BAUD, RPCMD_SET_J1939_BAUD, RPCMD_SET_ISO15765_BAUD)
• The configuration of some commands via the function RP1210_SendCommand returned OK when the protocol of the underlying client did not support the command (e.g. J1939 client issuing RPCMD_SET_BROADCAST_FOR_CAN)
• Broadcast messages for J1939 and ISO15765 were not working
• Newly configured CAN broadcast messages were first sent after the specified time interval had expired and not at the time of inclusion

4.0.0 16/07/2020

Improvements

• Support for ISO 15765-2 added
• Automatic registration of attached devices as RP1210 devices at installation time
• New sample application for testing the connection with devices from PEAK-System

3.0.0 09/07/2020

Changes

• PCAN-RP1210 is now free of charge. A license is not required anymore

2.1.0 05/08/2019

Bug fixes

• J1939 protocol: The duration of a blocking call to RP1210_ReadMessage from the actual receive time of a message to the return of the function was too long in some systems

2.0.9 24/05/2019

Bug fixes

• It was only possible to connect the first channel of a multi-channel PCI device

2.0.8 05/04/2019

Bug fixes

• The following PCAN hardware could not be registered: PCAN-M.2, PCAN-PCI/104-Express FD, and PCAN-miniPCIe FD

2.0.7 12/12/2018

Improvements

• Support for new PCAN-Hardware added:PCAN-miniPCIe FDPCAN-Chip PCIe FDPCAN-M.2PCAN-Chip USBPCAN-USB X6
• PCAN-miniPCIe FD
• PCAN-Chip PCIe FD
• PCAN-M.2
• PCAN-Chip USB
• PCAN-USB X6

Bug fixes

• In some scenarios, messages were being lost/discarded when using RP1210_ReadMessage in blocking mode (synchronization problems)
• The device selection logic in RP1210_ClientConnect was working wrong for USB devices in some scenarios
• Some connection resources (nets) were being left initialized after unloading the PEAKRP32.dll

2.0.6 07/05/2018

Bug fixes

• Calling the function RP1210_SendCommand with the command RESET_DEVICE was causing a deadlock condition

2.0.5 05/03/2018

Improvements

• New help files, *.chm and *.pdf, for PCAN-RP1210 C

Bug fixes

• When connecting to CAN without using Auto-Bitrate recognition the API was not able to receive messages
• The CAN filtering was not working properly

2.0.4 16/11/2017

Bug fixes

• The configuration of CAN or J1939 filters (function RP1210_SendCommand) was only working for the first element of the data passed to the function. Further items were discarded

2.0.3 17/08/2017

Improvements

• A bug in PCAN-USB firmware 8.3 is now recognized and handled within the library, so that devices that are not up-to-date can still keep working well
• Code improvements

Bug fixes

• API was not checking for presence/absence of a device after connection, when trying to send messages or commands. The error 'ERR_HARDWARE_NOT_RESPONDING' is returned when the device is plugged-out or deactivated
• API was failing to check the CAN bus status when trying to send messages/commands in an open network. The error 'ERR_MESSAGE_NOT_SEND' is returned when a CAN bus error is recognized

2.0.1 18/05/2017

Improvements

• Added support for new PCI and USB devices: PCAN-PCI Express FD, PCAN-USB X6, and PCAN-Chip USB

Bug fixes

• It was not possible to register clients with Id between 33 and 64
• It was possible to register more than 127 clients

2.0.0 23/01/2017

Improvements

• Complete code revision
• Code enhancements
• Implemented J1939-16 for automatic bit rate detection

Bug fixes

• Wrong return code of functions in multi-processes environment
• Deadlock when unloading the DLL

1.1.0 13/04/2016

Improvements

• Potential deadlock situation at finalization time (DLL detach) found and repaired
• General code enhancements

Bug fixes

• Solved problem regarding claiming a J1939 address, when bus state was ERR_BUSHEAVY or ERR_BUSLIGHT
• Solved problem generated due to concurrent access of resources (multi-threading)

1.0.4 15/02/2016

Bug fixes

• Wrong behavior of J1939 Re-CTS procedure was fixed
• Shared information between processes was getting corrupted, causing sometimes errors at connection time in multi-process environments

1.0.3 20/10/2015

Improvements

• General code enhancements done
• Internal components were updated

Bug fixes

• Access violation / stack overflow problems solved

1.0.2 19/01/2015

Bug fixes

• The function RP1210_ReadDetailedVersion was returning an empty string as Firmware version

1.0.1 16/09/2014

Improvements

• Now is possible to connect RP12010 applications to hardware that are being used from another applications
• A send queue for J1939 messages is used now. This avoid the return of the error “ALREADY_SENDING” when the function RP1210_SendMessage was called too fast when sending peer to peer messages

Bug fixes

• A problem within the Setup logic was avoiding the installation of the RP1210-A
• The auto Baud rate recognition algorithm was failing to share information about the status of the recognition process within all RP1210 processes. This was causing connection problems and generating bus error

1.0.0 15/07/2014

Changes

• First Release of the Recommended Practices 1210, Version C