First byte is lost when it's 0x11?
Posted: Thu 23. Mar 2023, 17:24
I am trying to read a non ISO-TP frame with CANTP_Read_2016.
When the first byte is 0x11 that byte is lost when reading.
A normal frame could look something like "44 0 0 0 11 0 C0 C3" where the first byte represents a status of the connected device which could be anything from 0x00 to 0x44. But if the first one is 0x11 that is removed and I read "0 0 0 11 0 C0 C3 0" instead of "11 0 0 0 11 0 C0 C3".
Any idea's what could be the reason? Am I wrong to assume that CANTP_Read_2016 can also read plain CAN frames that do not follow any standard?
When the first byte is 0x11 that byte is lost when reading.
A normal frame could look something like "44 0 0 0 11 0 C0 C3" where the first byte represents a status of the connected device which could be anything from 0x00 to 0x44. But if the first one is 0x11 that is removed and I read "0 0 0 11 0 C0 C3 0" instead of "11 0 0 0 11 0 C0 C3".
Any idea's what could be the reason? Am I wrong to assume that CANTP_Read_2016 can also read plain CAN frames that do not follow any standard?