In a discussion today with one of our forum members I mentioned that I had read this...
Drivers Reaction Adjustment (Car must be fitted with Camera)
Adjusts the sensitivity in which the car will alert the driver due to lack of steering input.
Select Control unit A5 (camera)
Security access
Enter unlock code 20103
Adaptation
Select channel deactivation threshold driver activity
Value adjust accordingly Default: medium options: early, middle, late
Taken from here....https://www.autoinstruct.com.au/manufacturer/volkswagen/mk2-tiguan/mk2-tiguan-obdeleven-vcds-tweaks/
Now I have re-read it I am not sure if I interpreted it correctly, does this refer to the weight that must be applied to the steering wheel and torque sensor in the rack or to the time interval that the steering input must be made.
Hi all,
I'm attempting to enable rear fog lights for my highline. Has anyone had any luck with this? I looked at the Golf tweaks but they don't seem to match what I'm seeing.
Kyle: The short answer is that it is entirely possible to "brick" the car to the extent that it needs to be taken back to a dealer.
For example, I have never been "brave enough" to run a simple output test on the Airbag control module (@ address hex03) using any diagnostic device that I own (i.e. VCDS, OBD11, or VCP). As one of the cable manufacturer describes:" it won't deploy your airbags. But it MAY render the vehicle undrivable. Running Output Tests is supposed to make the airbag controller generate a simulated crash signal to the rest of the systems in the vehicle so that unlocks itself and shuts various things OFF.
Unfortunately, one of the things it shuts off is the power supply to at least the Engine Control Module, and possibly to other modules (I'm guessing). I suspect that resetting the car, so that it is drivable isn't just a case of clearing the Trouble Code.
But, this is an extreme example, and more likely, the type of problem that will be encountered is less severe. Generally, an unintentional, aberrant code change will result in an error message on the car's screen, or a more innocent Trouble Code on your OBD11 software. These type of errors are more-fixable by the user.
Alas, there is no "reset back to factory setting" on any diagnostic device that I'm aware-of. What happens when you make a change to either an adaptation channel, or to a Byte/Bit in the module's coding is that the new value over-writes the old value and the old value is lost forever. But ALL devices have a kind-of "remedial" facility to help the user back-track his/her steps. In OBD11, the function is called "History". The history report reveals the before/after values of every change that you make with your device. Here's a example of the type of information that is in the history report:
first, for a change to an adaptation channel:
Adaptation
Control unit: 09 Central Electrics
Name: Leuchte20BR LA71
Values:
Dimmwert EF 20:
Old value: 0
New value: 20
Mileage: 3949 km
Date: 2017-11-16 16:53
Second for a change to a module code -string:
Long coding
Control unit: 55 Headlight Regulation
Old value:
021801010B000400
New value:
021801003F000400
Mileage: 2473 km
Date: 2017-09-21 14:52
Notice the Old/New value entries. But to revert these values, you will need to manually make the change with your OBD11 device.
But, if I can provide one piece of advice for any new user of a diagnostic device, it would be to try and make a least a few errors in your learning experience. These events will invariably be your most useful learning tool
Don
Last edited by DV52; 18-02-2018 at 01:05 PM.
Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is on-line, in the forum proper. That way you get the benefit of the expertise of the wider forum! Thank you.
Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is on-line, in the forum proper. That way you get the benefit of the expertise of the wider forum! Thank you.
Bookmarks