PEAK-System Forum

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 USB driver download page and in the folder of the driver once installed and we don't see a change log, but we could have missed it.

Thanks,
David

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 37947.773 FB 00A1 Rx 64 10 FB 02 F0 00 55 00 AA 00 F0 80 00 00 00 80 FA 00 00 00 06 00 04 00 FA 00 8E 80 E8 00 80 08 78 00 00 40 EB 00 00 4F 78 00 0E 80 E8 00 90 00 78 00 00 20 20 00 00 80 60 00 00 00 E0 00 02 00 32

160 37947.885 FB 00A2 Rx 3 30 00 01

161 37950.488 FB 00A1 Rx 64 21 00 10 C0 B3 00 00 4F 78 00 1E 40 78 00 00 80 FA 00 00 00 06 00 04 00 FA 00 8E 80 E8 00 80 08 78 00 00 40 EB 00 00 4F 78 00 0E 80 E8 00 90 00 78 00 00 08 20 00 00 80 60 00 00 00 E0 00 02 00

162 37952.675 FB 00A1 Rx 64 22 32 00 10 C0 B3 00 00 4F 78 00 1E 40 78 00 00 80 FA 00 00 00 06 00 04 00 FA 00 8E 80 E8 00 80 08 78 00 00 40 EB 00 00 4F 78 00 0E 80 E8 00 90 00 78 00 00 04 20 00 00 80 60 00 00 00 E0 00 02

163 37954.302 FB 00A1 Rx 64 23 00 32 00 10 C0 B3 00 00 4F 78 00 1E 40 78 00 00 80 FA 00 00 00 06 00 04 00 FA 00 8E 80 E8 00 80 08 78 00 00 40 EB 00 00 4F 78 00 0E 80 E8 00 10 00 78 00 70 00 60 00 00 00 E0 00 02 00 32 00

Using the same code on driver version 4.3.0.16563 we get the following CAN frames on the bus:

8 13628.132 FB 00A1 Rx 64 10 FB 02 F0 00 55 00 AA 00 F0 80 00 00 00 80 FA 00 00 00 06 00 04 00 FA 00 8E 80 E8 00 80 08 78 00 00 40 EB 00 00 4F 78 00 0E 80 E8 00 90 00 78 00 00 20 20 00 00 80 60 00 00 00 E0 00 02 00 32

9 13628.243 FB 00A2 Rx 3 30 00 01

10 13629.465 FB 00A2 Rx 8 30 0A F6 55 55 55 55 55

It appears to be the same Frist frame, our flow control, but then we get a second flow control on the bus but this one isn't sent by us. This is being sent by the Peak but to CAN-ID 0xA2 (I have confirmed that this frame is not being generated by our hardware). The Peak hardware doesn't try to continue to try to send out the rest of the ISO-TP message. It just hangs there until the message times out.

Thanks,
David

Hi,

here the link to our driver history: https://www.peak-system.com/CAN-Geraete ... %5D=driver

Which API and version do you use for your tests?

regards

Michael

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 size work as expected still. It is only messages larger than the frame size that have the problem.

I'll look over this change log to see if there are some hints into what we might be doing incorrectly in the driver usage that might have changed.

Thanks,
David

Hi,

as a first step, please also use the latest PCAN-ISO-TP.dll V3.2.0 with the latest driver 4.3.0. See also the history for the PCAN-ISO-TP API for more details:

https://www.peak-system.com/PCAN-ISO-TP-API.372.0.html

regards

Michael

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

Thanks again,
David

thanks for the feedback. Yes, with a driver update we also recommend to update all used APis to the latest version, to prevent any incompatibility

regards

Michael