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

Feature Request: Byte order #420

Closed
cyko69 opened this issue Apr 5, 2018 · 5 comments · Fixed by #428
Closed

Feature Request: Byte order #420

cyko69 opened this issue Apr 5, 2018 · 5 comments · Fixed by #428
Labels

Comments

@cyko69
Copy link

cyko69 commented Apr 5, 2018

It would help if I could choose the byte order for every message field.

@jopohl
Copy link
Owner

jopohl commented Apr 5, 2018

Could you explain your use case a bit more?

You can already

  1. choose the byte order in label view to change it for certain labels at the bottom of analysis
    screenshot_20180405_111321
  2. choose "Change Bitorder" in decoding to apply it for all messages.
    screenshot_20180405_111542

@jopohl
Copy link
Owner

jopohl commented Apr 11, 2018

I will close here. Drop a comment with some more detailed information if you feel it should be reopened.

@jopohl jopohl closed this as completed Apr 11, 2018
@cyko69
Copy link
Author

cyko69 commented Apr 16, 2018

Was on vaccation, so sorry for the late answer.
Both options are changing the BIT order, i need to have a different BYTE order (endianess).
e.g. I got a 0111110000000001 (0x7c 0x01) and i need to interpret this as ‭000101111100‬ (0x01 0x7c),
so the decimal value i want to have is (dec) 380 (and not 31745).

@jopohl jopohl reopened this Apr 16, 2018
@jopohl jopohl added the feature label Apr 16, 2018
@jopohl
Copy link
Owner

jopohl commented Apr 16, 2018

Ah thanks for the clarification. So we are talking about a new column "endianess" next to "Bit order" in the label table at the bottom?

@cyko69
Copy link
Author

cyko69 commented Apr 16, 2018

Yes, this would be perfect.

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

Successfully merging a pull request may close this issue.

2 participants