-
Notifications
You must be signed in to change notification settings - Fork 638
Adding CAN FD 64 frame support to blf reader #568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #568 +/- ##
===========================================
+ Coverage 63.91% 64.04% +0.13%
===========================================
Files 63 63
Lines 5708 5712 +4
===========================================
+ Hits 3648 3658 +10
+ Misses 2060 2054 -6 |
bitrate_switch=bool(fd_flags & BRS_64), | ||
error_state_indicator=bool(fd_flags & ESI_64), | ||
dlc=length, | ||
data=can_data[:length], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would probably be more efficient something like this instead of unpacking the raw data above:
data_offset = pos + CAN_FD_MSG_64_STRUCT.size
data[data_offset:data_offset + length]
Also I've realized it should really be the valid payload length and not the DLC to support remote frames correctly, but it is more of a sanity thing.
Could we add such a CAN FD 64 frame to |
The test file was copied from Toby’s C++ library. Maybe we should create our own and check that it is correct in a Vector application. I however do not have access to one anymore. |
Okay, so maybe just open a new issue for that and merge this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sound good to me!
See #581. |
No description provided.