Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
What is the Decode of the VO / FA ( vehicle order ) in hex in the ECU
14-01-2017, 19:59 PM,
(This post was last modified: 14-01-2017, 20:58 PM by Node.)
Post: #8
|
|||
|
|||
RE: What is the Decode of the VO / FA ( vehicle order ) in hex in the ECU
For now decoding the ending seems to be extremely easy. I will write my ideas when I will fully decode it all.
So complete decoding was even easier than I thought I wanted at least some challenge... So here it goes: 1. My first idea was that VO needs to contain numbers and English capital letters, so we have 36 values. Lowest number of bits required to encode that is 6, giving range of 0..63. So I tried to divide binary representation of the answer to groups of 6 bits. 2. I didn't know where exactly is the start, so I did that from the end, but now that I know where to start, I will explain it from beginning. So answer is as posted: 0000 : 62 3F 06 03 41 84 54 AD 05 16 42 44 50 42 E9 16 b?..A„T ..BDPBé. 0010 : 41 04 10 84 58 49 24 92 49 24 D2 49 44 92 61 24 A..„XI$’ I$ÒID’a$ 0020 : D5 49 75 53 61 45 53 61 56 50 65 94 91 61 14 58 ÕIuSaESa VPe”‘a.X 0030 : 4C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 L....... ........ Let's skip first 4 bytes 62 3F 06 03. I guess this is some kind of header. Protocol header containing actual number of bytes I think is already not shown by tool32. Now write all remaining bytes as binary: 0100000110000100010101001010110100000101000101100100001001000100 0101000001000010111010010001011001000001000001000001000010000100 0101100001001001001001001001001001001001001001001101001001001001 0100010010010010011000010010010011010101010010010111010101010011 0110000101000101010100110110000101010110010100000110010110010100 1001000101100001000101000101100001001100 Now as in idea #1 lets group them to the groups of 6 bits, convert each to hex, add 0x20 and lookup the resulting number as ASCII code (I will show operations for 2 first lines and just the resulting character later): 010000 = 0x10 + 0x20 = 0x30 = '0' 011000 = 0x18 + 0x20 = 0x38 = '8' 010001 = '1' 010100 = '4' 101011 = 'K' 010000 = '0' 010100 = '4' 010110 = '6' 010000 = '0' 100100 = 'D' 010001 = '1' 010000 = '0' 010000 = '0' 101110 = 'N' 100100 = 'D' 010110 = '6' 010000 = '0' 010000 = '0' 010000 = '0' 010000 = '0' 1000 - this probably marks the end of vehicle id and start of options, can't tell what it means from this single example, maybe it's always the same, or maybe it's some kind of checksum 010001 = '1' 011000 = '8' 010010 = '2' 010010 = '2' 010010 = '2' 010010 = '2' 010010 = '2' 010010 = '2' 010011 = '3' 010010 = '2' 010010 = '2' 010100 = '4' 010010 = '2' 010010 = '2' 011000 = '8' 010010 = '2' 010011 = '3' 010101 = '5' 010010 = '2' 010111 = '7' 010101 = '5' 010011 = '3' 011000 = '8' 010100 = '4' 010101 = '5' 010011 = '3' 011000 = '8' 010101 = '5' 011001 = '9' 010000 = '0' 011001 = '9' 011001 = '9' 010010 = '2' 010001 = '1' 011000 = '8' 010001 = '1' 010001 = '1' 011000 = '8' 010011 = '3' 00 - just the remaining unused bits I hope from this you will be able to see how it relates to the string representation of VO |
|||
Reputation: +1 - BMWS1000RR [+1] | |||
« Next Oldest | Next Newest »
|
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Return to TopReturn to Content