PEAK-System Forum

Thank you for this suggestion. This resolved the issue. I did not think that these would be associated.

Thanks again,
David

Michael,

Thanks for the reply.

Our working system was using USB driver 4.2.3.16490 along with the ISO-TP API 3.1.1.227.

We updated to the latest USB driver 4.3.0.16563 and now the messages that are larger than 64 bytes (our frame size) no longer work correctly. Messages smaller than the frame ...

The issue we are facing is trying to send a CAN-ISO-TP frame that is larger than 64 bytes. We are trying to send a 251 byte message.

On driver version 4.2.3.16490 the frames come out of the Peak driver as expected:

//First frame, flow control, Consecutive(1), Consecutive(2), Consecutive(3)

159 ...

Is there a change log for the PCAN-USB drivers? Our PC solution works with driver version 4.2.3.16490 but not 4.3.0.16563. We are curious if there is a change log so we can more quickly debug what has changed to we can figure out where to look to fix the broken functionality.

We've looked in on the ...

Hello,

We used your PCAN series of devices because of your support of the ISO 15765-2 API library. I do not see something similar for LIN (ISO 17987-2). These two transport protocol layers are nearly identical from my understanding. Is there a software module that I am overlooking for ISO 17987-2 ...

Fabrice,

Thank you for your patience. We always use TXDL in our software so even though this field is clearly DLC and not TXDL, we read it as TXDL. You are correct. Converting the TXDL to the DLC makes this work for the current and previous version of the driver for all valid lengths.

Thank you ...

I've traced it back to when we try to set the TXDL length of the mapping to 64 bytes in CAN-FD mode. If I don't touch the TXDL in mapping object it defaults to 8 and works, but transmits at 8 bytes. If I set the TXDL to 64 it fails to set the mapping with the latest driver (worked with the last ...

With this switch enabled I can see that the SetMapping() function is reporting an invalid mapping where it was valid in the last version. The function is properly reporting "KO". When we mapped the status returns of the functions to the UI console this function didn't get remapped and it was still ...

Marvin,

I updated the PCANBasic API to 4.2.2 as suggested in your post. No change in behavior.

CAN + ISO-API v3.0.1.186 = works
CAN + ISO-API v3.1.1.227 = works
CAN-FD + ISO-API v3.0.1.186 = works
CAN-FD + ISO-API v3.1.1.227 = does not work

Thanks,
David

We have a solution working with PEAK-ISO-API v3.0.1.186 with both CAN and CAN-FD.

We just updated to the v3.1.1.227 DLL. The CAN portion still works. The CAN-FD no longer works. We did not change anything on our usage.

None of the APIs are returning errors, but no messages come out on the bus. We ...