What is the endianness of ROS message fields?
The documentation on ROS messages omits an essential detail for anyone implementing a new client library: what is the endianness of multi-byte fields such as uint32
and float64
?
Are these fields to be interpreted as little-endian (some of the bag serialization code would seem to imply that) or big-endian (which is generally the standard network byte order)?
Not an answer, but I just noticed Guillaume Autran (Clearpath) has written / is in the process of writing a Wireshark dissector for TCPROS (see TCPROS - Initial implementation for the Robot Operating System TCP protocol). Might be interesting.
All references to Endianness I can find in that dissector point to little-endian being used.
Thanks, @gvdhoorn. I also posed the question on IRC but didn't receive a response.