We upgraded the dlls to v3.1.227 without touching the code. Looking at the .cs files, there seem to be no important updates as long as only ISO 15762-2, revision 2004 is used.
With the new dlls we are facing some issues. An update of the driver to the current version did not help.
Usually we use Can and CanFD with usual mapping, this works fine with both dll versions.
However, at some point we are also reading Can/CanFD messages with various CanIDs using the parameter PCANTP_CAN_UNSEGMENTED_ON. Here we face different behaviour of the two dll-versions. In the returned TPCANTPMsg, we see:
- Message length LEN has an offset of -4 with the new version (in the example: 8 instead of 12, larger values than 8 have been observed for other messages, so the value is not fixed to 8).
- Data array DATA shows the complete data, however the upper nibble of the CanID seems to be missing with the new version (in the example 0x09 instead of 0x49).
I could imagine that our problem is due to incorrect initialization/usage and was somehow working up to now. Can you suggest a solution?
Thank you for your request.
We have contacted our development team regarding this issue and
we will report back to you, as soon as we have new information regarding this.
Our development team will replicate the issue and assess the cause.
Due to the coming easter holidays in germany this might takes some time,
as soon as any new info is available to us, we'll share it with you.
Our development team informed me that this was a bug which has been fixed, the bugfix
will be included in the next release of the PCAN-ISO TP API.
If you are interested in testing the prerelease version with the bugfix for this, please
send us an email to support[at]peak-system.com
Please let us know
thanks for the info, email sent.