Auf unserer Website setzen wir Cookies ein, um Ihnen den bestmöglichen Service zu bieten und unsere Website weiter verbessern zu können. Mit dem Button "Alle akzeptieren" stimmen Sie der Verwendung aller Cookies zu. Über "Auswahl akzeptieren" können Sie die verwendeten Cookies eingrenzen. Weitere Informationen und eine Option zum Widerruf Ihrer Auswahl finden Sie in unserer Datenschutzerklärung.

Notwendig:

Diese Cookies sind für die grundlegende Funktionalität notwendig. Dadurch können Sie sich auf unserer Website und im Forum anmelden oder Produkte mit unserem Online-Shop bestellen.

Statistik:

Mit diesen Cookies erheben wir anonymisiert Nutzungsdaten für unsere Website. So können wir beispielsweise sehen, welche Inhalte für unsere Besucher interessant sind und welche Auflösungen verwendet werden. Anhand der Informationen optimieren wir unsere Website, um Ihnen eine möglichst gute Benutzererfahrung bieten zu können.

Notwendig
Statistik

Mehr

PCAN-PassThru API Version History

2021-05-25 - Version 3.0.0

Improvements:

  • Added support to PassThru version 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 dependencies
    • 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

Bug fixes:

  • 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

Changes:

  • 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 exact
    • READ_MSG_EXTENSION: pInput must be a pointer to a message index
    • WRITE_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_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
  • 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 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


Download

2021-02-11 - Version 2.0.6

Bug fixes:

  • 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

2021-01-28 - Version 2.0.5

Improvements:

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

2021-01-25 - Version 2.0.4

Improvements:

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

Bug fixes:

  • Deadlock fixed when using multithreading and reading with timeout

2020-12-03 - Version 2.0.3

Improvements:

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

2020-07-16 - Version 2.0.2

Improvements:

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

2020-05-28 - Version 2.0.1

Bug fixes:

  • An outdated internal reference was causing a certificate validation error

2020-05-27 - Version 2.0.0

Improvements:

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

2019-07-17 - Version 1.1.7

Improvements:

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

2019-05-23 - Version 1.1.6

Improvements:

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

2019-02-05 - Version 1.1.5

Improvements:

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

2018-12-17 - Version 1.1.4

Improvements:

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

2018-03-05 - Version 1.1.3

Improvements:

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

2017-09-07 - Version 1.1.2

Bug fixes:

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

2017-05-11 - Version 1.1.1

Improvements:

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

Bug fixes:

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

2017-02-08 - Version 1.1.0

Improvements:

  • 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

Bug fixes:

  • 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

2016-07-21 - Version 1.0.2

Improvements:

  • 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

Bug fixes:

  • 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

2016-04-22 - Version 1.0.1

Improvements:

  • General code enhancements

Bug fixes:

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

2015-10-26 - Version 1.0.0

  • First Release