Fault Code U112500 Additional Installations Detected

[Rems]

I just went back to read the MFSW Upgrade thread and I saw that nemesis also activated KLR in the A5 Driver Assistance control module, but our van does not have that module, which isn't very surprising since we didn't order Travel Assist.

[Guide] T6.1 MFSW Steering Wheel Upgrade

Just noticed yours is the same as mine with the travel assist on the bottom right of the left side. As std the T6.1 has driver assist, so should really have 1EA959442A buttons. Does your travel assist button bring up the dash driver assist menu? Mine doesn’t.

www.t6forum.com

This has me thinking that maybe this missing control module is why I can't enable KLR in the Gateway control module.
Rems - do you know if the vehicle you've shown as your example has the A5 Driver Assistance module?

Yes A5 is installed in the T6.1

 

[DMcCook]

Yes A5 is installed in the T6.1

OK. Our T6.1 does NOT have this control module so I am guessing this is why I can’t enable the KLR option.
With no better information I’d have to also guess that the easiest way to remove this error is to replace the steering wheel buttons, just like ASE did according to his comment on my other thread.
Post in thread '[Guide] T6.1 MFSW Steering Wheel Upgrade'
[Guide] T6.1 MFSW Steering Wheel Upgrade

 

[nemesis03]

If there is not A5 control unit there is no benefit of using a steering wheel with touch detection. So using a steering wheel without touch detection might solve the issue.

You could also try to disconnect the touch detection module from the steering wheel buttons. That way there will be messages from the touch detection module on the bus. But maybe that won't work if you steering wheel buttons expect the touch detection module to be present. I think it is worth a try.

Another workaround might be to tell the Gateway that A5 is present (which of course will result in errors, because the corresponding bus messages are missing). But maybe you can than activate Sollverbau_klr and deactivate A5 afterwards. The logic is that maybe the gateway wants the A5 module to be present to accept the Sollverbau_klr coding. I think the A5 module can be activated in the adaptions of the gateway and sould be "Front Sensors Driver Assistance System" (at the position of Node_0x4F).

 

[DMcCook]

If there is not A5 control unit there is no benefit of using a steering wheel with touch detection. So using a steering wheel without touch detection might solve the issue.

You could also try to disconnect the touch detection module from the steering wheel buttons. That way there will be messages from the touch detection module on the bus. But maybe that won't work if you steering wheel buttons expect the touch detection module to be present. I think it is worth a try.

Another workaround might be to tell the Gateway that A5 is present (which of course will result in errors, because the corresponding bus messages are missing). But maybe you can than activate Sollverbau_klr and deactivate A5 afterwards. The logic is that maybe the gateway wants the A5 module to be present to accept the Sollverbau_klr coding. I think the A5 module can be activated in the adaptions of the gateway and sould be "Front Sensors Driver Assistance System" (at the position of Node_0x4F).

Hi Nemesis - that's nice / clever lateral thinking!
I will have to investigate disconnecting the touch module when I have the energy to deal with removing the airbag. Those clips are such a pain to release. This would obviously save me buying more buttons - but doesn't solve the mismatched button on the left side. ;-)
I'll see if I can try adding the A5 in the mean time.

 

[DMcCook]

No surprises with trying to enable the A5 Module - it gave exactly the same response as trying to enable the KLR. Function not available.
I guess I have to try unplugging the touch detection next, if I can be bothered - forgetting about it is sounding like the best option right now.
Thanks for all your help.

 

[DMcCook]

If there is not A5 control unit there is no benefit of using a steering wheel with touch detection. So using a steering wheel without touch detection might solve the issue.

You could also try to disconnect the touch detection module from the steering wheel buttons. That way there will be messages from the touch detection module on the bus. But maybe that won't work if you steering wheel buttons expect the touch detection module to be present. I think it is worth a try.

Another workaround might be to tell the Gateway that A5 is present (which of course will result in errors, because the corresponding bus messages are missing). But maybe you can than activate Sollverbau_klr and deactivate A5 afterwards. The logic is that maybe the gateway wants the A5 module to be present to accept the Sollverbau_klr coding. I think the A5 module can be activated in the adaptions of the gateway and sould be "Front Sensors Driver Assistance System" (at the position of Node_0x4F).

Hey Nemesis, (or anyone?) do you know which of the plugs on the back of the buttons is for the touch detection?
I know that the DSG plug is the smaller 2 pin plug.
Is the touch detection the one beside the DSG or the one beside the label with the scan code?
Thanks again.

 

[DMcCook]

Hey Nemesis, (or anyone?) do you know which of the plugs on the back of the buttons is for the touch detection?
I know that the DSG plug is the smaller 2 pin plug.
Is the touch detection the one beside the DSG or the one beside the label with the scan code?
Thanks again.

YAY! I can answer my own questions now!
THANKS EVERYONE FOR YOUR HELP - especially Nemesis for your suggestion of unplugging the detection wires. So obvious in hindsight.
Once I took my airbag off again, I could see the pair of wires going to the nearest plug in the back of the left button pad and running to the little control module I hadn't noticed in the bottom of the steering wheel.
The best bit was that I could just see that plug with a mirror and reached it and unplugged it with some tweezers.
Plugged the airbag back in, but left it unclipped until checking OBDeleven.
BINGO! No red errors - and no errors at all once I cleared them.
Weirdly, there was a new green error, "Control unit in steering wheel" "No Communication". but I cleared that and it didn't come back. Funny how it didn't know what the new installation was until I unplugged it! LOL