Hello,
We will have an internal release candidate in two weeks, it will include support to PassThru 04.04 and 05.00.
The official release should follow quickly. We will update this thread to let you know.
Search found 143 matches
- Tue 30. Mar 2021, 15:08
- Forum: PCAN-PassThru API
- Topic: BUG: J2534 API does not set ISO15765_ADDR_TYPE on reception
- Replies: 5
- Views: 158
- Thu 25. Mar 2021, 09:20
- Forum: PCAN-ISO TP
- Topic: Issues with PEAK-ISO-API v3.1.1.227 with CAN-FD
- Replies: 9
- Views: 199
Re: Issues with PEAK-ISO-API v3.1.1.227 with CAN-FD
Hello David,
The field in cantp_mapping is can_tx_dlc: the value must be a valid DLC (and not a length), so you should change your value from 64 to 0x0F.
The field in cantp_mapping is can_tx_dlc: the value must be a valid DLC (and not a length), so you should change your value from 64 to 0x0F.
- Wed 24. Mar 2021, 14:36
- Forum: PCAN-ISO TP
- Topic: Issues with PEAK-ISO-API v3.1.1.227 with CAN-FD
- Replies: 9
- Views: 199
Re: Issues with PEAK-ISO-API v3.1.1.227 with CAN-FD
Hello David, In your application, can you globally enable debug message by calling function CANTP_SetValue_2016 with PCANTP_PARAMETER_DEBUG before any initialization? Here is a C++ sample: uint8_t buf; // set debug mode buf = PCANTP_VALUE_PARAMETER_ON; sts = CANTP_SetValue_2016(PCANTP_HANDLE_NONEBUS...
- Wed 17. Mar 2021, 10:39
- Forum: PCAN-PassThru API
- Topic: BUG: J2534 API does not set ISO15765_ADDR_TYPE on reception
- Replies: 5
- Views: 158
Re: BUG: J2534 API does not set ISO15765_ADDR_TYPE on reception
Hello, I was merely suggesting beta to speed up testing and validate the fix on your side, no worries. Something happens to the PCAN J2534 DLL where even if I clear it and reset everything, I do not get any data back anymore from the J2534 DLL until I power cycle the interface. While in this state, ...
- Tue 16. Mar 2021, 16:46
- Forum: PCAN-PassThru API
- Topic: BUG: J2534 API does not set ISO15765_ADDR_TYPE on reception
- Replies: 5
- Views: 158
Re: BUG: J2534 API does not set ISO15765_ADDR_TYPE on reception
Hello, Thank you for your feedback, we have indeed internally reported and already fixed an issue related to a missing flag ISO15765_ADDR_TYPE for Rx messages. It will be included in the next release, you can contact support [at] peak-system.com if you'd like to subscribe to beta testing. We are in ...
- Wed 24. Feb 2021, 13:23
- Forum: PCAN-UDS
- Topic: Problem with sending Diag session control using CAN FD
- Replies: 8
- Views: 313
Re: Problem with sending Diag session control using CAN FD
Glad to hear that! For completeness and as knowledge base, here is an example of how one could send a UDS request with a 64 bytes single CAN FD frame (using UUDT): // Initialize channel const String BITRATE = "f_clock_mhz=80, nom_brp=1, nom_tseg1=127, nom_tseg2=32, nom_sjw=32, data_brp=2, data_tseg1...
- Wed 24. Feb 2021, 09:48
- Forum: PCAN-UDS
- Topic: Problem with sending Diag session control using CAN FD
- Replies: 8
- Views: 313
Re: Problem with sending Diag session control using CAN FD
The issue I described is only valid for ISO-TP single frame. ISO-TP segmented messages have by definition a data length bigger than the configured TX_DL, so the segmentd frames will use the dlc you set (apart from the last Consecutive frame which will adapt the dlc to fit the remaining data). So, yo...
- Tue 23. Feb 2021, 17:46
- Forum: PCAN-UDS
- Topic: Problem with sending Diag session control using CAN FD
- Replies: 8
- Views: 313
Re: Problem with sending Diag session control using CAN FD
You can change the can data padding value to 0x00 with the parameter PUDS_PARAMETER_CAN_PADDING_VALUE . You will then send a UDS request with the following 8 bytes data: 02 10 03 00 00 00 00 00. However you will NOT be able to send a UDS request with an actual UDS data size of 2 in a CAN FD frame wi...
- Tue 23. Feb 2021, 16:34
- Forum: PCAN-UDS
- Topic: Problem with sending Diag session control using CAN FD
- Replies: 8
- Views: 313
Re: Problem with sending Diag session control using CAN FD
Hello, "can_tx_dlc" is a parameter that allows you to configure the transmit data link layer data length (TX_DL) as defined in ISO 15765. But be careful as TX_DL only configures the maximum usable payload length of the data link layer. This means that UDS requests will actually use the smallest dlc ...
- Fri 19. Feb 2021, 12:00
- Forum: PCAN-UDS
- Topic: UDS Service TransferData with MAX_DATA (4093 bytes) length
- Replies: 24
- Views: 897
Re: UDS Service TransferData with MAX_DATA (4093 bytes) length
If you are using PUDS_PROTOCOL_ISO_15765_2_29B, you don't have to configure extra mappings: it is handled automatically by the API as the CAN IDs used to communicate are standardized. 1) Is it require to use PUDS_PARAM_MAPPING_REMOVE to remove when we are using PUDS_PROTOCOL_ISO_15765_2_29B? No 2) I...