Please Note:
The development on the RP1210 version A implementation was discontinued since version A was superseded by version C.
2020-07-17 - Version 3.0.0
Changes:
- PCAN-RP1210 is now free of charge. A license is not required anymore
2017-08-17 - Version 2.6.0
Improvements:
- 64-bit version of the DLL is now called the same as the 32-bit version, PCANRP32.dll
- PCANRP64.dll and PCANRP64.ini are deprecated but still installed because of backward compatibility
2017-05-18 - Version 2.5.1
Bug fixes:
- License checking issue fixed
- It was not possible to register clients with Id between 33 and 64
- It was possible to register more than 127 clients
2017-01-23 - Version 2.5.0
- Improvement: Added support for PCAN-LAN devices
2016-02-17 - Version 2.4.7
- Bug fix: Wrong behavior of J1939 Re-CTS procedure was fixed
2015-06-23 - Version 2.4.6
- Bug fix: Platform identification shown in file properties was wrong
2014-07-15 - Version 2.4.5
Bug fixes:
- Misconfiguration corrected when applying a CAN filter to standard IDs over the function RP1210_SendCommand
- RTR messages were not being filtered but included into the incoming messages queue
2013-01-24 - Version 2.4.4
- Bug fix: The mechanism for recognizing and resetting BUS OFF situations was not giving the BUS enough time to recover itself after a hardware reset, before continuing working. This bug was mostly observed within J1939 connections, by claiming addresses
2012-11-09 - Version 2.4.3
- Some minor internal improvements
2012-07-04 - Version 2.4.2
- Bug fix: An access violation was occurring in multi-threading scenarios due to synchronization problems while assembling large messages from a read session
2012-06-19 - Version 2.4.1
Bug fixes:
- Receiving wrong large J1939 messages (large messages whose single packages have wrong indexes) was causing an access violation
- A bug within the message filter of the PCI driver was causing communication interferences when a client was being connecting/disconnecting several times
2011-11-17 - Version 2.4.0
Enhancement:
- The parameter RPCMD_SET_AUTORESET_ON_BUSOFF is now ON by default
Bug fixes:
- The RP1210_ReadMessage() did not return the correct error value when a hardware was not found. It was returning ERR_HARDWARE_NOT_RESPONDING instead of
(ERR_HARDWARE_NOT_RESPONDING * -1) - Several changes were made to avoid a deadlock that occurred when a bus-off condition was detected while reading or writing in blocking mode
Changes in the header files for .NET, PCAN_RP1210.cs and PCAN_RP1210.vb:
- The enumeration "RP1210AError" is now explicity a short value, in order to avoid marshaling problems
- The parameter nDeviceID (PCANDevice) was incorrectly marshaled as U1 instead of U2
2011-04-07 - Version 2.3.20
- Improvement: Support for redistributable license added (PCAN-Developer extension)
2011-02-03 - Version 2.2.19
- Bug fix: It was possible to connect clients to different PCAN devices within the same process
2010-10-19 - Version 2.2.18
- Bug fix: Problems solved within multi-threading scenarios
2010-10-12 - Version 2.2.17
- Improvement: TP.DT and TP.CM messages (address claiming) are now filtered out of the received messages queue
2010-10-11 - Version 2.2.16
- Bug fix: Memory leaks cleared
2010-10-08 - Version 2.2.15
Improvements:
- Connecting more than one channel per device is now possible (two or more USB at the same time, for example)
- Minor updates
2010-10-04 - Version 2.1.14
- Improvement: When claiming an address, a reset of the hardware is automatically done, if the hardware status is other than OK
2010-09-28 - Version 2.1.13
- Bug fix: A wrong code was being returned when trying to send a J1939 large message and the address was lost
2010-09-27 - Version 2.1.12
Improvements:
- General performance was improved (CPU usage was reduced)
- Speed of message processing was increased (40% faster)
2010-09-13 - Version 2.1.11
- Bug fix: CAN message filtering was wrong. The filter was being replaced instead of expanding it
2010-06-24 - Version 2.1.10
- Improvement: RP1210 was modified to work under 64-bit systems
- Bug fix: The function "RP1210_GetHardwareStatus" was returning always the status information within the bytes destinated for CAN-information on the parameter buffer, even if the connection was J1939
2010-02-17 - Version 2.0.9
Improvements:
- The minimum operating system version needed was changed to Windows XP (Windows 2000 no longer supported)
- A new connection checks now for the hardware status. A virtual connection (internal, no hardware plugged-in) will fail now
Bug fix:
- When an address claiming operation failed, the function did not return ERR_ADDRESS_CLAIM_FAILED
2010-01-29 - Version 2.0.8
- Improvement: The processing speed for J1939 messages was increased
- Bug fix: The C# and VB header files were modified due to wrong parameter types (string vs. StringBuilder)
2010-01-25 - Version 2.0.7
2009-12-18 - Version 2.0.6
- Improvement: Multimedia timer is now being used to achieve a better timing
- Bug fix: Setting a custom filter after having fully opened the filter didn't work
2009-12-04 - Version 2.0.5
Bug fixes:
- Bug with J1939 claiming process solved
- RE-CTS and retries were executed only once
- Memory leaks found and repaired
- The API tried to claim an address even if the Claiming protocol was not used
2009-09-25 - Version 2.0.4
Improvements:
- The processing speed for J1939 messages was increased
- Changes and improvements to the CAN core engine
Bug fix:
- Echo messages were enqueued even if they shouldn't
2009-06-24 - Version 2.0.3
- Imrpovement: Included a new Header file for Visual Basic.Net: PCANRP32.vb
- Bug fix: A wrong defined limitation was being used: only one protocol was allowed to be used for all processes working with the API
2009-06-08 - Version 2.0.2
2009-06-02 - Version 2.0.1
Bug fixes:
- CAN echo messages were incorrectly recognized
- After resetting a client, the messages count of the queue was not reset
2009-04-08 - Version 2.0.0