Skip to content
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

Vector ASCII Format: message IDs < 0x100 should be zero-padded #26

Open
Bokonon79 opened this issue Jan 21, 2019 · 0 comments
Open

Vector ASCII Format: message IDs < 0x100 should be zero-padded #26

Bokonon79 opened this issue Jan 21, 2019 · 0 comments
Assignees
Labels

Comments

@Bokonon79
Copy link
Collaborator

Vector's ASCII exports do not zero-pad message IDs to the expected three digits. Examples:

432.77720 1  16              Rx   d 1 01  Length = 107914 BitCount = 58 ID = 22
434.04737 1  C               Rx   d 7 3B 0F 79 05 80 02 02  Length = 209910 BitCount = 109 ID = 12

This results in CANBusAnalyzer reporting spurious message IDs that contain a portion of the message data (example: ID "C" + data "3B F0 00 00" --> ID "C3B" + data "F0 00 00").

The Vector log reader should zero-pad these IDs to three digits (e.g. 016 and 00C) before handing them back to the main timer loop.

@Bokonon79 Bokonon79 added the bug label Jan 21, 2019
@Bokonon79 Bokonon79 self-assigned this Jan 21, 2019
@Bokonon79 Bokonon79 added this to To do in Log import formats via automation Jan 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

1 participant