bp78
New Member
Posts: 5
|
Post by bp78 on May 29, 2020 18:40:19 GMT
I bought ODBeleven mostly because I wanted to reverse one of the changes made by the previous owner (auto lock). I figured it might also be helpful one day if there is an issue with the car.
They were a 4-6 fault codes when I ran the initial scan, and I accidentally cleared them. I hit "cancel", but it was already too late.
According to the history, the old value was 01FA6BA154230970807E20441C36880D62A90014982163600435051C00803, and the new value is 01FA6BA154230970807E20441C36880D62A90014982163600435051C00303
So basically ODBeleven replaced an 08 at byte 29/Hex 03 with a 03. What does this mean? Is it possible to mess things up by clearing fault codes accidentally?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 29, 2020 20:00:25 GMT
bp78 afraid I cant help on what the long coding changes mean as this is not my car. But if you want to see what the change is then go to Byte 29 and change the Hex from 03 to 08 (but dont save it)and you will be able to see which byte has been changed and hopefully it will have a long coding description that will make sense of the change. However personally not had this situation on my car as a result of scans However if you go history, select the filter {upside down triangle} and at the bottom of the list you will see Fault and Clear are both unticked (so that we still have the data but dont clog up the history screen} so just select them and you will be able to see the stuff you have deleted.
|
|
|
|
Post by dv52 (Australia) on May 29, 2020 21:38:14 GMT
According to the history, the old value was 01FA6BA154230970807E20441C36880D62A90014982163600435051C00803, and the new value is 01FA6BA154230970807E20441C36880D62A90014982163600435051C00803 So basically ODBeleven replaced an 08 at byte 29/Hex 03 with a 03 hmm..... I don't think so - the 2 x long code strings in your post above are the same - so Byte 29 = hex08 in both the old and new cases! So basically ODBeleven replaced an 08 at byte 29/Hex 03 with a 03. What does this mean? It means this: hex 08 is equivalent to Binary 0000 1000. Binary numbers are read from RIGHT to LEFT - so Bit 0 is the right-most digit. For the Binary number - count towards the left and you will find that Bit 3 is set for hex 08 Hex 03 is equivalent to Binary 0000 0011. So, for this number using the same Binary methodology, Bit 0 and Bit 1 is set In the long code strings on control modules, each of the 8 x Bits in every Byte is a kind-of software switch that turns -ON/OFF a particular facility. In the Brake module, lots of Bytes are also used to confirm other Byte settings (but the Binary pattern is reversed). I don't know what Byte 29 is used for! Is it possible to mess things up by clearing fault codes accidentally? Clearing fault codes does NOT alter any long-code values - it simply clears memory locations in the module that are dedicated to storing records (it's called a "mode 4 Parameter-ID" in OBD Standards speak". |
|
bp78
New Member
Posts: 5
|
Post by bp78 on May 29, 2020 21:56:49 GMT
Thanks your responses. There was a typo in the long code strings (it's fixed now).
So basically to revert the clearing of the code I could uncheck bit 0 and 1, and then check bit 3. However, this would have no effect on the car. Correct?
One of the faults that did not get cleared as I hit the cancel button is in control unit 44 (steering assistance). It says: "Steering angle sensor - no initialization". I didn't do really do anything in ODBeleven. Is this something that needs to be checked out by a mechanic? It was in the shop this morning for the door lock issue, but they didn't mention anything about the steering angle sensor.
|
|
|
|
Post by dv52 (Australia) on May 29, 2020 23:28:03 GMT
Thanks your responses. There was a typo in the long code strings (it's fixed now). So basically to revert the clearing of the code I could uncheck bit 0 and 1, and then check bit 3. However, this would have no effect on the car. Correct? One of the faults that did not get cleared as I hit the cancel button is in control unit 44 (steering assistance). It says: "Steering angle sensor - no initialization". I didn't do really do anything in ODBeleven. Is this something that needs to be checked out by a mechanic? It was in the shop this morning for the door lock issue, but they didn't mention anything about the steering angle sensor. hmm........ OK - I've re-looked at my MQB databse for Byte 29 tweaks. I'd forgotten in my first reply, but Byte 29 on the hex03 module controls the ASR/ESC switch behavior like this:
For the table below, the meaning is: HexCode = Default value / Short press / Press & hold for 3-5 secs
01 = ESC & ASR ON / Blank / Blank
02 = ESC & ASR ON / ASR OFF / Blank (Standard for most Golf’s)
03 = ESC & ASR ON / ESC SPORT / Blank
04 = ESC & ASR ON / ESC OFF / Blank
05 = ESC & ASR ON / ASR OFF / ESC OFF
06 = ESC & ASR ON / ESC SPORT / ESC OFF
07 = ESC & ASR ON / ASR OFF / ESC OFF
08 = ESC & ASR ON / ESC SPORT / ESC OFF
09 = ESC & ASR ON / ASR OFF / ESC SPORT (GTI & R)
So, I suspect at some point after you purchased your OBD11 dongle, you used an ESC App and this is why the change record appears on your history file. Did you do this?
Don
|
|
bp78
New Member
Posts: 5
|
Post by bp78 on May 29, 2020 23:51:53 GMT
Today was my first day using the ODB11 dongle, and I didn't make any changes besides accidentally clearing the codes and resetting the behavior of the door locking system. Since this is a used car, I am guessing that the previous owner may have used some of the apps, as indicated by the fact that the door lock was changed to autolock on exit. Maybe that's also why I am getting a "Steering angle sensor - no initialization" fault.
I could review the settings for the various apps and check whether any of them are different from the default value. Hopefully the previous owner didn't do any long coding himself or changed too many settings.
|
|
|
|
Post by dv52 (Australia) on May 30, 2020 1:43:46 GMT
Today was my first day using the ODB11 dongle, and I didn't make any changes besides accidentally clearing the codes and resetting the behavior of the door locking system. Since this is a used car, I am guessing that the previous owner may have used some of the apps, as indicated by the fact that the door lock was changed to autolock on exit. Maybe that's also why I am getting a "Steering angle sensor - no initialization" fault. I could review the settings for the various apps and check whether any of them are different from the default value. Hopefully the previous owner didn't do any long coding himself or changed too many settings. NO! - that's not the way the History records work on diagnostic devices (regardless of whether you use VCDS, VCP, or OBD11).
For OBD11, the records in the History part of the software are ONLY those that are linked to your google account. OBD11 doesn't know anything about changes that were made to the car before you purchased it. OBD11 is not that smart; it simply takes the "old value" from the car just before you press the green tick and the "new value" is taken from your change instruction (again, just prior to pressing the green tick).
I'm not sure why your steering sensor has the fault. If you don't post-up the complete unedited details of the actual DTC - I'm not able to comment (i.e. simply saying "no initialization" doesn't tell me much)
Don
|
|
bp78
New Member
Posts: 5
|
Post by bp78 on May 30, 2020 1:56:45 GMT
Got it. As far as I know I didn't touch the ESC. Here are the logs.
Fault
Control unit: 03 Brakes
Active faults: 0
Inactive faults: 5
System description: ESC
Software number: 5Q0614517AF
Software version: 0398
Hardware number: 5Q0614517AF
Hardware version: H62
Serial number: 52876000000480
ODX name: EV_Brake1UDSContiMK100ESP
ODX version: 035019
Faults:
B1168F2 - Steering angle sensor no initialization
Intermittent
Date: 2020-02-29 00:12:12
Mileage: 56142 km
Priority: 2
Malfunction frequency counter: 4
Unlearning counter: 120
Extended Freeze Frames: 0007001812000000AC0000000000000000000000000000
C101AF1 - Left front ABS wheel speed sensor Magnetic field too low
Intermittent
Date: 2019-11-11 07:40:32
Mileage: 50766 km
Priority: 3
Malfunction frequency counter: 8
Unlearning counter: 48
Extended Freeze Frames: 0000001832000000CF0000000000000000000000000000
C101AF1 - Left front ABS wheel speed sensor Magnetic field too low
Intermittent
Date: 2020-02-17 07:38:12
Mileage: 55816 km
Priority: 3
Malfunction frequency counter: 1
Unlearning counter: 73
Extended Freeze Frames: 0000001832000000D10002000000000000000000000000
C114602 - Tire pressure monitoring display Signal error
Intermittent
Date: 2020-05-29 00:02:02
Mileage: 56452 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 120
Extended Freeze Frames: 0002001A52000000AD0000000000000000000000000000
C114602 - Tire pressure monitoring display Signal error
Intermittent
Date: 2020-05-29 00:02:02
Mileage: 56452 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 120
Extended Freeze Frames: 0002001A52000000AD0000000000000000000000000000
Mileage: 56499 km
Date: 2020-05-29 12:19
---------------------------------------------------------------
Long coding
Control unit: 03 Brakes
Old value:
01FA6BA154230970807E020441C36880D62A90014082163600435051C00803
New value:
01FA6BA154230970807E020441C36880D62A90014082163600435051C00303
Mileage: 56499 km
Date: 2020-05-29 12:18
|
|
bp78
New Member
Posts: 5
|
Post by bp78 on May 30, 2020 1:58:23 GMT
However if you go history, select the filter {upside down triangle} and at the bottom of the list you will see Fault and Clear are both unticked (so that we still have the data but dont clog up the history screen} so just select them and you will be able to see the stuff you have deleted. Thanks, that was helpful. |
|
