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

Data Table view displays bytes as 64 bit values #9

Open
RudolphRrr opened this issue Feb 19, 2024 · 3 comments
Open

Data Table view displays bytes as 64 bit values #9

RudolphRrr opened this issue Feb 19, 2024 · 3 comments

Comments

@RudolphRrr
Copy link

I just tried the LIN analyzer with my Logic Pro 8 using Logic 2 2.4.13.
And while the decoder seems to work just fine, all the bytes in the "Data Table" view are printed as 64 bit values.

This also ends up in the export:
name type start_time duration protected_id data index checksum
LIN header_break 0.00245888 0.00075392
LIN header_sync 0.00329216 0.00049392
LIN header_pid 0.00381296 0.00049392 0x0000000000000012
LIN data 0.00432672 0.00049392 0x0000000000000000 0x0000000000000000
LIN data 0.00484752 0.00049392 0x0000000000000000 0x0000000000000001
LIN data 0.00536832 0.00049392 0x0000000000000000 0x0000000000000002
LIN data 0.00588912 0.00049392 0x0000000000000000 0x0000000000000003

@timreyes
Copy link

Thanks for writing this in. This is currently a known issue, and we're also keeping track of this below. Sorry for the trouble with this in the meantime.
https://ideas.saleae.com/b/feature-requests/shorten-lin-bus-hexadecimal-representation/

@RudolphRrr
Copy link
Author

I am usually working with the SPI analyzer but rarely check the "Data Table" view.
Now I am looking at a trace that was provided to me and it does not have the same issue.
The comments in the thread suggest that this is a general issue but looks like this is not a common issue.

@timreyes
Copy link

The Data Table showing 64 bits is only an issue with certain analyzers (LIN analyzer in particular, though, I don't remember which other analyzers are affected).

Our SPI analyzer does not have this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants