My ROS Client has a bug in reading the following subscribed message (bytes converted to HEX for portability). After reading two floats, there appears to be 3 extra characters between the float and message_definition. Those 3 hex characters are 169, and they are creating an ArrayIndexOutOfBoundsException on my Java Client because the pattern of length 4 bytes length + message is thrown out of whack. I've attached the hex in hopes that somebody might be able to offer me an idea of what my client is doing wrong. Thanks, Aaron

14000000176CB140176CB14000000000000000000000000014000000176CB140176CB14000000000000000000000000014000000176CB140176CB140000000000000000000000000383935616535323635636639670000006D6573736167655F646566696E6974696F6E3D666C6F6174333220780A666C6F6174333220790A666C6F617433322074686574610A0A666C6F61743332206C696E6561725F76656C6F636974790A666C6F6174333220616E67756C61725F76656C6F636974790A13000000747970653D747572746C6573696D2F506F7365