You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
For some buses (e.g. LIN, or CAN with extended addressing), packet type information is located in the second byte of raw_data.
Function get_raw_packet_type is not always correct, therefore this peace of code requires minor rework.
Execute get_raw_packet_type for CAN with extended addressing
See the result is not correct.
Expected behavior
Value of packet type can only be assessed when bus and its configuration is known (for example CAN with normal or extended addressing have different results)
The text was updated successfully, but these errors were encountered:
Describe the bug
For some buses (e.g. LIN, or CAN with extended addressing), packet type information is located in the second byte of raw_data.
Function
get_raw_packet_type
is not always correct, therefore this peace of code requires minor rework.To Reproduce
get_raw_packet_type
for CAN with extended addressingExpected behavior
Value of packet type can only be assessed when bus and its configuration is known (for example CAN with normal or extended addressing have different results)
The text was updated successfully, but these errors were encountered: