unable to access module

[ms1083]

2004 A6 allroad.
Trying to change code in module 35 (central locks) so they lock automatically at 15mph.
When I try to access this module VCDS tries 3 times then says "no response from module/application".
Any help please? Is there a setting I need to change in options or is there something switched on in the car causing interference?

 

[Grant]

Try accessing module 46 (Central Conv.) instead.

+32 Auto lock/unlock of doors (Doors lock at 15 mph and unlock when key is removed)

 

[ms1083]

Thank you for your reply. I have actually worked out that all modules on the K2 lead are not working despite VCDS saying K2 ok on its test and these modules are readable by my hand held fault code reader. Any help?

 

[NHN]

VCDS Log of car please.

 

[a6_chris]

C5 or C6?

Ok must be a C5 as the C6 is defaulted from factory with the locking.

As Nigel says - post a log of your car.

I presume you're not using a genuine cable?

 

[ms1083]

Seems like its all the K2 links? K2 link says ok on testing the cable in options.

Address 01: Engine
Protocol: KW1281
Part No: 8E0 907 401 J
Component: 2.5l/4VTEDC G000AG 0006
Coding: 06006
Shop #: WSC 02334

Address 02: Auto Trans
Protocol: KW1281
Part No: 4Z7 927 156 N
Component: AG5 01V 2.5lTDI RdW 2222
Coding: 00001
Shop #: WSC 00000

Address 03: ABS Brakes
Protocol: KW1281
Part No: 4Z7 907 389 A
Component: ABS/ESP allrad D56
Coding: 06457
Shop #: WSC 02334

Address 15: Airbags
Protocol: KWP2000
Part No: 4Z7 959 655 M
Component: Airbag 8.4EP 1000
Coding: 0001106
Shop #: WSC 02334

Address 17: Instruments
Protocol: KW1281
Part No: 4B0 920 981 J
Component: KOMBI+WEGFAHRS. VDO D15
Coding: 04460
Shop #: WSC 00116

Address 25: Immobilizer
Protocol: KW1281
Part No: Bitte Adress
Component: e 17 eingeben

Address 33: OBD-II
Protocol: ????
Part No: OBD-II/EOBD, Protocol Keyword: $0808

Address 34: Level Control
Protocol: KW1281
Part No: 4Z7 907 553 F
Component: - 2C1A1 D060
Coding: 25500
Shop #: WSC 02334

Address 7E: Ctrl Head Dash
Protocol: KWP2000
Part No:
Note: Excessive Comm Errors

 

[NHN]

Either you've removed allot of log data or thats a very old piece of software, is it a genuine cable, if so update to latest release then post a log.