Nekota wrote:I'll take a guess at the units being metric and in 0.1 meters for 6300.7 miles.
Interesting... could also be 101,400,576 feet = 19,204.6545 miles Truncating also possible but it's actually more difficult to handle 3 bytes of data than 4. They just used a 32bit INT instead of a 16bit INT.
Nubo wrote:If I assume a reversed order, then the three leading zeros might make sense, then assume one digit for tenths... 4b06.0 = 19206.0 kM (11934 mi).
I've never seen hexadecimal reversed like that. At worst the byte order would be reversed (little vs big endian), not the nybble order!
06 0B 40 00 becomes 00 40 0B 06 or 4,197,126. If we assume that's meters, it works out to 2,607.97 miles. If we leave the byte order as is, then 101,400,576 meters = 63,007.3968 miles which may be possible (No clear reason to shift the decimal like Nekota did). I suspect, though, that byte order is NOT reversed. If it was then you'd expect the reversal to be used throughout - so that means he's used quick charge (QUICKCG) a total of 256 times (0100) instead of just once (0001) and a normal charge (NORMALCG) 56,832 times (DE00) instead of 222 times (00DE).
I converted the table into CSV
versions (HTML has hex converted to decimal assuming no byte order reversal).