PCAN-RP1210 API Version History

17.11.2011 - Version 2.4.0.100

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

 

07.04.2011 - Version 2.3.20.77

  • Improvement: Support for redistributable license added (PCAN-Developer extension)

 

03.02.2011 - Version 2.2.19.76

  • Bug fix: It was possible to connect clients to different PCAN devices within the same process

 

19.10.2010 - Version 2.2.18.75

  • Bug fix: Problems solved within multi-threading scenarios

 

12.10.2010 - Version 2.2.17.72

  • Improvement: TP.DT and TP.CM messages (address claiming) are now filtered out of the received messages queue

 

11.10.2010 - Version 2.2.16.71

  • Bug fix: Memory leaks cleared

 

08.10.2010 - Version 2.2.15.70

Improvements:

  • Connecting more than one channel per device is now possible (two or more USB at the same time, for example)
  • Minor updates

 

04.10.2010 - Version 2.1.14.59

  • Improvement: When claiming an address, a reset of the hardware is automatically done, if the hardware status is other than OK

 

28.09.2010 - Version 2.1.13.58

  • Bug fix: A wrong code was being returned when trying to send a J1939 large message and the address was lost

 

27.09.2010 - Version 2.1.12.57

Improvements:

  • General performance was improved (CPU usage was reduced)
  • Speed of message processing was increased (40% faster)

 

13.09.2010 - Version 2.1.11.51

  • Bug fix: CAN message filtering was wrong. The filter was being replaced instead of expanding it

 

24.06.2010 - Version 2.1.10.50

  • 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

 

17.02.2010 - Version 2.0.9.45

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

 

29.01.2010 - Version 2.0.8.43

  • 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)

 

25.01.2010 - Version 2.0.7.41

  • Minor updates

 

18.12.2009 - Version 2.0.6.40

  • 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

 

04.12.2009 - Version 2.0.5.39

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

 

25.09.2009 - Version 2.0.4.33

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

 

24.06.2009 - Version 2.0.3.28

  • 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

 

08.06.2009 - Version 2.0.2.23

  • Minor updates

 

02.06.2009 - Version 2.0.1.22

Bug fixes:

  • CAN echo messages were incorrectly recognized
  • After resetting a client, the messages count of the queue was not reset

 

08.04.2009 - Version 2.0.0.16

  • First release

Back to Top