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
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
The text was updated successfully, but these errors were encountered:
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.
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).
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
The text was updated successfully, but these errors were encountered: