|
Post by pissat4motion on Dec 25, 2018 1:04:42 GMT
I'm finding the limitation to obd11 that it can be hard to navigate. Performed a steering wheel swap. Used obd11 to perform the angle sensor adaptation. During that time I went into #44 coding and mistakingly input 40168. It was accepted for coding😲😳😵 Not sure what the previous value was. Could have been 0's for all I know. Can anyone hero me out with the value that should be there? PFA of the mistake..
|
|
|
Post by pissat4motion on Dec 25, 2018 16:50:04 GMT
Anyone can give me the Christmas gift of checking their Coding II value??
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Dec 25, 2018 17:15:47 GMT
If you look in your history it should show you what you changed from and to - sorry just seen you screen shot have you tried emailing the history file to yourself just in case it shows the values.
Or if not did you have a backup before you started making changes (we always advise people to do this) so again you can see the original settings.
|
|
|
Post by pissat4motion on Dec 26, 2018 12:32:05 GMT
Every other coding change in history shows an old value and the new value. I'm thinking now that there probably wasnt a value there to begin with.. Going to try changing it back to zero. Think 0=no value??
|
|
|
Post by Matthew on Dec 28, 2018 23:10:04 GMT
40168, was just the security code as you now know. In my VCDS, My coding2 is just "00000". There is no coding for this module other than adaptations, basic settings when calibrating the sensors, etc.
If the car functions normally, you can ignore the mistake.
|
|