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

Endianness of binary data count incorrect #52

Open
Hisol opened this issue Nov 22, 2017 · 0 comments
Open

Endianness of binary data count incorrect #52

Hisol opened this issue Nov 22, 2017 · 0 comments

Comments

@Hisol
Copy link

Hisol commented Nov 22, 2017

The client documentation refers to the 32bit unsigned integer at the end of the point-cloud data as network byte order

These may be parsed as a 32-bit unsigned integer, transmitted in network byte order.

Which is defined as being Big-Endian [https://www.ibm.com/support/knowledgecenter/en/SSB27U_6.4.0/com.ibm.zvm.v640.kiml0/asonetw.htm](IBM network byte order article)

However it seems that the server is returning the data in Little-Endian format (when running on an Intel architecture)

EG for a response with 1456 entries the last 4 bytes of the response are:
0xb0050000
Rather than
0x000005b0

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

1 participant