|
Post by andre1980 on Aug 3, 2021 10:08:15 GMT
Just connected my OBDeleven to my ID.3 car to remove an airbag light that appeared after removing fuse 19 because the 4G communications needed resetting.
In the history tab in the OBDeleven tab, it now says that I initiated the full scan 2021-08-03 11:18:47. This scan probably took between 2 and 5 minutes.
In the history tab in the OBDeleven tab, it now says that long coding was done on control unit (03) Brakes at 2021-08-03 11:18:49. It changed the value from the following: 09954A84153C903E5241A8E411D 911A648294916443111492888886 512949268228C889214CECBBCF C0073D33D3F00
To the following: 09954A84153C903E5241A8E411D 911A648294916443111492888886 512949268228C889214CECBBCF D0073D33DBF00
What is this? I never asked OBDeleven to do this.
|
|
|
Post by dv52 (Australia) on Aug 5, 2021 2:48:26 GMT
Here's a more readable view of the long-code string for the hex03 module:
| Old
| Old
| New
| New
| Byte 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
| Hex 09 95 4A 84 15 3C 90 3E 52 41 A8 E4 11 D9 11 A6 48 29 49 16 44 31 11 49 28 88 88 65 12 94 92 68 22 8C 88 92 14 CE CB BC FC 00 73 D3 3D 3F 00
| Binary 00001001 10010101 01001010 10000100 00010101 00111100 10010000 00111110 01010010 01000001 10101000 11100100 00010001 11011001 00010001 10100110 01001000 00101001 01001001 00010110 01000100 00110001 00010001 01001001 00101000 10001000 10001000 01100101 00010010 10010100 10010010 01101000 00100010 10001100 10001000 10010010 00010100 11001110 11001011 10111100 11111100 00000000 01110011 11010011 00111101 00111111 00000000
| Hex 09 95 4A 84 15 3C 90 3E 52 41 A8 E4 11 D9 11 A6 48 29 49 16 44 31 11 49 28 88 88 65 12 94 92 68 22 8C 88 92 14 CE CB BC FD 00 73 D3 3D BF 00
| Binary 00001001 10010101 01001010 10000100 00010101 00111100 10010000 00111110 01010010 01000001 10101000 11100100 00010001 11011001 00010001 10100110 01001000 00101001 01001001 00010110 01000100 00110001 00010001 01001001 00101000 10001000 10001000 01100101 00010010 10010100 10010010 01101000 00100010 10001100 10001000 10010010 00010100 11001110 11001011 10111100 11111101 00000000 01110011 11010011 00111101 10111111 00000000
|
I'm not sure how familiar you are with hex-to-binary conversions- but as you can see, each row in the Binary column in my table contains 8 x digits called Bits. You can think of these Bits as 8 x software switches and each switch has a value of either 1 (meaning the Bit is switched-ON), or 0 (meaning switched-OFF).
So a hex number contains 8 x Bits - the standard nomenclature for these switches is Bit 7, Bit 6, Bit 5 ......Bit 0 - in this order. Hence, in my table above and for each row - the extreme left-most digit is Bit 7 and the extreme right-most digit is Bit 0. I hope this makes sense
I've highlighted the changed Bits: - Byte 40, Bit 0 has been set
- Byte 45, Bit 7 has been set
I don't have any information about the hex03 module on an ID.3 - so I can't help identify what these switches do on your car.
Have you used any one-click-Apps in the past- maybe? Don
|
|