In the process of writing a Ruby client for the AC UDP data sent from the PS4, I uncovered a number of differences between what was received, and what was documented in the AC Socket document (link) for RTCarInfo. My working (successfully parses and displays all values) UDP definition is linked below. This implementation uses a Ruby library that allows me to declaratively define the structure of the data (Ruby is not normally typed like this) in C terms. It should be pretty easy to read, and I used names that match the official document. https://github.com/bradland/ac_telemetry/blob/master/lib/ac_telemetry/bin_formats/rt_car_info.rb I have observed the following discrepancies: 1) String encoding and format is not specified in the AC docs. I'm getting good results with UTF-16LE, and treating % as a string terminator. 2) The documentation specifies six, 1-byte flags for ABS (2), TC (2), pit status, and engine limiter. The float for vertical G force is supposed to start immediately after, but I had to pad two unknown bytes to get things working. Can you tell me what these two bytes are at offset 26 and 27? 3) The documentation doesn't specify unit of measure for many values. I'm guessing on man. 4) Slip angle contact patch always outputs zero. 5) Tyre slip always outputs zero. 6) ND Slip is undocumented (unsure of description and unit). 7) Load does not specify unit (assuming newtons). 8) Dy is undocumented. 9) Mz unit of measure is undocumented. 10) Tyre dirty level max value is undocumented. 11) Suspension height documentation is ambiguous. Assuming this is vertical travel available in meters. 12) Car slope always outputs zero.