3.2.0 24/07/2025

Améliorations

• The maximum number of logical channels was increased from 10 to 64
• PCAN-ISO-TP API updated to version 3.6.0
• Implemented changes to comply with specification J2534-1_0500_202201: Recommended Practice for Pass-Thru Vehicle Programming
• Implemented changes to comply with specification J2534-2 (J2534-2/BA_0500_202201 / J2534-2/RE_0500_202201): Base and Resource Documents
• Implemented changes to comply with specification J2534-2_202012: Optional Pass-Thru Features
• Implemented changes to comply with specification J2534-2/11_5_00_202201: Pass-Thru Extended Features – CAN with Flexible Data Rate

Corrections de bugs

• The value of ECHO_PHYSICAL_CHANNEL_TX was corrected

Changements

• The function PassThruOpen was adjusted to accept the connection patterns: "J2534-1:", "J2534-2:", and “PEAK 0x51”

3.1.1 05/10/2023

Améliorations

• The protocols CAN, CAN_PS, CAN_FD_PS, and FD_CAN_PS are now handled directly with PCAN-Basic API to improve the performance
• General code enhancements

Changements

• The parameter buffer for firmware version of the function PassThruReadVersion now includes version information about PCAN-Basic API (default) plus PCAN-ISO-TP API and device firmware if available

3.1.0 23/03/2023

Améliorations

• Improved API logging to prevent entanglement of multiline entries in multithreaded context
• PCAN-ISO-TP API updated to v3.4.0
• Enhancements for installation on Windows 11 ARM64

Changements

• PCAN-Basic API library is no longer installed by the PCAN-PassThru setup
• Dropped support for Windows versions older than Windows 10
• Setup can no longer be installed on Windows x86 systems
• PCAN-ISO-TP API installation path changed back to be Windows\System32 and Windows\SysWOW64

3.0.2 01/09/2022

Améliorations

• General code optimizations

Corrections de bugs

• ISO15765 messages with RxStatus flag START_OF_FRAME were having the size of the full package expected. Now they have a DataSize of 4 or 5 and a ExtraDataIndex of 0
• The logging process within the functions PassThruReadMsgs and PassThruWriteMsgs was causing a NULL pointer exception in some scenarios

Changements

• The setup copies the PCAN-ISO-TP API files now to the installation folder instead of directories Windows\System32 and Windows\SysWOW64
• The path to the PCAN-ISO-TP files is now included into the global environment 'PATH' variable

3.0.1 27/10/2021

Corrections de bugs

• Automatic ISO-TP 29-bit mappings were being enabled when initializing a raw CAN channel

3.0.0 25/05/2021

Améliorations

• Added support to PassThru revision 05.00
• Added support to FD options from SAE-J2535-2:2019
• Restricted use of GMW extension to protocol ISO15765 FD only (SAE-J2535-2:2019 or GMW)
• Added PassThru parameter ISO15765_PAD_VALUE
• Added PassThru parameter N_CR_MAX
• New versions of dependenciesPCAN-Basic API updated from v4.5.3 to v4.5.4PCAN-ISO-TP API updated from v3.1.1 to v3.1.2
• PCAN-Basic API updated from v4.5.3 to v4.5.4
• PCAN-ISO-TP API updated from v3.1.1 to v3.1.2

Corrections de bugs

• Fixed issue in PassThruWriteMsgs where ISO15765 FD messages with a length from 4100 to 4128 failed
• Fixed issue in PassThruWriteMsgs to check minimum and maximum message's sizes (based on ISO15765_ADDR_TYPE)
• Fixed internal 'ISO15765-filter' search to take into account ISO15765 Extended Address byte if applicable
• Maximum value for 29 bit and 11 bit CAN IDs was not being checked
• Fixed issue with periodic messages

Changements

• The binary name of the configuration tool was changed from PCANPT32Config.exe to PCANPTConfig.exe
• ISO15765 messages with ERROR_IND flag can only be read with using the ISO15765 GMW extension protocol. By other protocols those messages are discarded
• Changes made regarding compliance with GM extension specification:READ_MSG_EXTENSION: number of bytes passed as input must be exactREAD_MSG_EXTENSION: pInput must be a pointer to a message indexWRITE_MSG_EXTENSION: only the first message may be extended
• Added missing ISO15765_ADDR_TYPE flag in RxStatus when applicable
• Some configuration parameters are now limited to ISO15765 protocols:ISO15765_PAD_VALUE, ISO15765_BS, ISO15765_STMINN_CR_MAX, N_CR_MAX_GMBS_TX, STMIN_TXFD_ISO15765_TX_DATA_LENGTH, CAN_FD_TC_DATA_LENGTHCAN_MIXED_FORMAT
• PassThruWriteMsgs and PassThruReadMsgs now set the parameter for message number to zero, when no messages were read or written
• When setting PassThruhru parameters (ex. FD_ISO15765_TX_DATA_LENGTH), the function will fail if provided values is not accepted by the specification
• Changed the default values of PassThru parameters to strictly match SAE-J2535 specifications:FD_ISO15765_TX_DATA_LENGTH: 64 instead of 8ISO15765_BS: 0 instead of 10ISO15765_STMIN: 0 instead of 10ISO15765_WFT_MAX: 0 instead of 16CAN_MIXED_FORMAT: OFF instead of ALLISO15765 Timeout Cr (N_CR_MAX) for GMW protocols : 150000 instead of 1000000Padding byte value for GMW protocols: 0xCC instead of 0x55Padding byte value for FD protocols (excluding GMW): 0x00 instead of 0x55Padding byte value for ISO15765 non-FD protocols: remains equal to 0x55 for backward compatibility
• READ_MSG_EXTENSION: number of bytes passed as input must be exact
• READ_MSG_EXTENSION: pInput must be a pointer to a message index
• WRITE_MSG_EXTENSION: only the first message may be extended
• ISO15765_PAD_VALUE, ISO15765_BS, ISO15765_STMIN
• N_CR_MAX, N_CR_MAX_GM
• BS_TX, STMIN_TX
• FD_ISO15765_TX_DATA_LENGTH, CAN_FD_TC_DATA_LENGTH
• CAN_MIXED_FORMAT
• FD_ISO15765_TX_DATA_LENGTH: 64 instead of 8
• ISO15765_BS: 0 instead of 10
• ISO15765_STMIN: 0 instead of 10
• ISO15765_WFT_MAX: 0 instead of 16
• CAN_MIXED_FORMAT: OFF instead of ALL
• ISO15765 Timeout Cr (N_CR_MAX) for GMW protocols : 150000 instead of 1000000
• Padding byte value for GMW protocols: 0xCC instead of 0x55
• Padding byte value for FD protocols (excluding GMW): 0x00 instead of 0x55
• Padding byte value for ISO15765 non-FD protocols: remains equal to 0x55 for backward compatibility

2.0.6 11/02/2021

Corrections de bugs

• Due to an error in the included PCAN-Basic API, a CAN connection could not be established if the version of the PCAN device driver used was older than 4.2.1

2.0.5 28/01/2021

Améliorations

• General code enhancements
• PCAN-Basic API updated from v4.5.1 to v4.5.2

2.0.4 25/01/2021

Améliorations

• New versions of dependencies (PCAN-ISO-TP and PCAN-Basic)

Corrections de bugs

• Deadlock fixed when using multithreading and reading with timeout

2.0.3 03/12/2020

Améliorations

• New versions of dependencies (PCAN-ISO-TP and PCAN-Basic)

2.0.2 16/07/2020

Améliorations

• New versions of dependencies (PCAN-ISO-TP and PCAN-Basic)

2.0.1 28/05/2020

Corrections de bugs

• An outdated internal reference was causing a certificate validation error

2.0.0 27/05/2020

Améliorations

• Implementation of the GM extension to SAE J2534 standard, GMW17753, to support CAN FD
• General code enhancements

1.1.7 17/07/2019

Améliorations

• The configuration of the underlying certificate checking was changed to avoid delays at initialization time due to certificate revoke-search online
• New versions of dependencies (PCAN-ISO-TP and PCAN-Basic)

1.1.6 23/05/2019

Améliorations

• New versions of dependencies (PCAN-ISO-TP and PCAN-Basic)

1.1.5 05/02/2019

Améliorations

• New versions of dependencies (PCAN-ISO-TP and PCAN-Basic)

1.1.4 17/12/2018

Améliorations

• New versions of dependencies (PCAN-ISO-TP and PCAN-Basic)

1.1.3 05/03/2018

Améliorations

• New versions of dependencies (PCAN-ISO-TP and PCAN-Basic)

1.1.2 07/09/2017

Corrections de bugs

• ISO-15765 user-defined mappings could not be found due to priority problems regarding 29-bit standard mappings

1.1.1 11/05/2017

Améliorations

• The PassThruOpen function returns a more accurate error code when it fails to open a device

Corrections de bugs

• Fixed issue with J2534-2 options when connecting multiple times to different devices

1.1.0 08/02/2017

Améliorations

• Added J2535-2 multiple channels support
• ISO15765 enhancement: the self-receive mechanism was improved in order to avoid unnecessary delays between data when transmitting long messages

Corrections de bugs

• ISO15765 issue: a "SingleFrame" response was generating an RxStart indication
• ISO15765 issue: the "TxDone" indication was containing more data as the addressing information
• CAN MIXED issue: when CAN MIXED was ON, the receive queue contained message indication of CAN messages
• CAN MIXED issue: when CAN MIXED was ON and if no flow control was defined/matched, message indication of single ISO-TP frame was retrieved as CAN protocol

1.0.2 21/07/2016

Améliorations

• With ISO-TP protocol, TxDone message status now combines the following RxStatus bits: (TX_INDICATION | TX_MSG_TYPE_LOOPBACK)
• Added automatic hardware reset when Bus-Off is detected

Corrections de bugs

• Timing issue corrected regarding the minimum separation time of packages of a ISO-15765 message
• Fixed timestamp with function PassThruWriteMsgs (timestamps were in milliseconds instead of microseconds)
• When sending ISO-TP single frames with no corresponding mapping, the loopback message still contained ISO-TP PDU information. The PDU is now removed, and the frame is padded if padding is activated

1.0.1 22/04/2016

Améliorations

• General code enhancements

Corrections de bugs

• Fixed deadlock when calling FreeLibrary on PCANPT32.dll
• Fixed timing issue between packages when sending large messages, using the ISO-15765 protocol

1.0.0 26/10/2015

Changements

• First Release