Testbench setup?

   #41  

mattylondon

Verified VCDS User
Verified
Joined
Apr 10, 2016
Messages
157
Reaction score
136
Location
United Kingdom
VCDS Serial number
C?ID=219022
1048574 km!!! What's happening there? I can't believe the donor vehicle really did cover that distance?

Thanks for your suggestion about the BCM, I shall give it a go! When I tested mine directly with my CAN analysing kit the BCM was alive and sending no stop data, so I'm confident it's powered correctly and alive.

On the VCDS bench setup I also had the parking aid module connected to the CAN Gateway, this is also on the convenience CAN and I had the same result of not being able the connect via VCDS. So I think the problem is the resistance on the convenience CAN.

I go away soon so it will be awhile before I start bench testing again.

This is a great thread, love it :thumbs:
 
   #42  

NEtech

VCDS Distributor
Joined
Feb 7, 2014
Messages
2,154
Reaction score
3,487
Location
Denmark
VCDS Serial number
C?ID=56995
(not sure where the DTC is getting the mileage number-from)?
My guess is, it is from some default values in the processor/program.
Dec 1048574
Hex FFFFE
Bin 11111111111111111110
There are no mileage/date values available in your CAN communication data.

There are a few DTC's, that probably are from when the BCM was installed in a car.
Mileage: 10430 km
Date: 2015.09.06
Time: 12:14:30
 
   #43  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,540
Reaction score
3,931
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
OK, discovering new stuff about this wierd thing called OBDII! Is anyone able to help with my latest conundrum (sorry to be a pest, but this is the best place to seek advice IMO). I've attempted to reduce the DTC's in the BCM on my testbench as much as possible and I'm down to a more respectable number (22 DTCs)

But in the process of deleting DTCs, I've now exposed the anticipate Component Protection message which was entirely missing from the autoscan report on my previous post (see below)

Code:
Thursday,28,April,2016,09:20:11:03521
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
VCDS Version: 16.3.1.1 (x64)
Data version: 20160325
www.Ross-Tech.com


VIN:    License Plate: TEST BENCH
Mileage: No Lamp DTCs   Repair Order: CAN G'way+BCM



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Chassis Type: 5Q0
Scan: 09 19


09-Cent. Elect. -- Status: Malfunction 0010
19-CAN Gateway -- Status: OK 0000
 
-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519)       Labels: 5Q0-937-08X-MV1.clb
   Part No SW: 5Q0 937 084 N    HW: 5Q0 937 084 N
   Component: BCM MQBAB M   H14 0106  
   Serial number: 00011309901220
   Coding: 030000000000000303200002000000000000000000000000000000000000
   Shop #: WSC 73430 790 00104
   ASAM Dataset: EV_BCMCONTI 010001
   ROD: EV_BCMBOSCH_VW37.rod
   VCID: 4385A3B4CA981924E9-8016

22 Faults Found:
135432 - Terminal S 
          B11A5 11 [009] - Short to Ground
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

136458 - Terminal 15 
          B1148 15 [009] - Open or Short to Plus
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

395273 - Control Circuit for Signal Horn 
          B1344 14 [009] - Open or Short to Ground
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

533269 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

539925 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

541973 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

542229 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

549141 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

549909 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

552213 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

554517 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

555029 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

555285 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

555541 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

556053 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

558101 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

558869 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

559125 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

559637 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

919560 - Light Switch 
          B126A 29 [009] - Signal Implausible
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 3
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

947204 - Control Module for Wiper Motor 
          U10A3 00 [009] - No Communications
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

15360256 - Component Protection 
          U1101 00 [009] - Active
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 4
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00


-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533)       Labels: 5Q0-907-530-V1.clb
   Part No SW: 5Q0 907 530 E    HW: 5Q0 907 530 E
   Component: GW MQB Mid    121 1109  
   Revision: --------    Serial number: 0000073193
   Coding: 000000342B086400EF0006481C0F00000001000000000000000000000000
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_GatewLear 006010
   ROD: EV_GatewLear.rod
   VCID: 3365F3749A38A9A479-8066

No fault code found.

End-------------------------(Elapsed Time: 00:36)-------------------------
There are some different Databus error messages in the latest auto-scan report, which I assume result from the fact that I have had to make coding changes to delete some of the DTCs from non existent equipment, but the latest emergence of the CP message (when none appeared previously) is baffling - to me at least!

Does anyone have a hypothesis for this revelation - for example, is there an upper limit in the number of DTCs that can be reported by ODBII, or RT's software for a single control module- and If so, which DTCs are prioritised?

Don

PS: for anyone with an MQB platform vehicle, the way to delete bulb-out errors is to change the setting on the appropriate Leuchte channel (3)-Leuchte ****** -Fehlerort mittleres Byte DTC-DFCC * to Hex00
 
Last edited:
   #44  

Eric

Active Member
Staff member
Joined
Jan 29, 2014
Messages
2,896
Reaction score
4,129
Location
Lansdale, PA, USA
VCDS Serial number
HC800000
for example, is there an upper limit in the number of DTCs that can be reported by ODBII, or RT's software for a single control module- and If so, which DTCs are prioritised?
Blasphemy! :) Out of two systems, one with gigabytes of addressable memory, and the other one being an embedded controller, you're asking if our software is the limiting factor? ;) Granted, some embedded systems do have tons of memory (probably navigation), but I don't think that's the case for 09. I could be wrong and you could have a 64bit ARM in there with 8GB of RAM, but I somehow doubt it :D
I checked our code and it looks like it should be able to buffer just about 75 UDS DTCs for processing (that's of course per control module). We could no doubt make that many times bigger, but it seems so far either control modules just hang in the middle of giving their DTCs, or don't have enough room reserved in their EEPROM for this (a supposition on my part). I don't see a limiting factor on the OBDII (really, VAG) protocol side either, and in any case the first one to hit would be 255, and then 65535.
 
   #45  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,540
Reaction score
3,931
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
Blasphemy! :) Out of two systems, one with gigabytes of addressable memory, and the other one being an embedded controller, you're asking if our software is the limiting factor? ;) Granted, some embedded systems do have tons of memory (probably navigation), but I don't think that's the case for 09. I could be wrong and you could have a 64bit ARM in there with 8GB of RAM, but I somehow doubt it :D
I checked our code and it looks like it should be able to buffer just about 75 UDS DTCs for processing (that's of course per control module). We could no doubt make that many times bigger, but it seems so far either control modules just hang in the middle of giving their DTCs, or don't have enough room reserved in their EEPROM for this (a supposition on my part). I don't see a limiting factor on the OBDII (really, VAG) protocol side either, and in any case the first one to hit would be 255, and then 65535.
Eric: Thanks for the reply - I guess then that hidden CP message might have been a consequence of the unusual configuration of the BCM in a test-jig (i.e. perhaps the CP test process in the CAN Gateway needs a certain amount of data from other modules (which aren't present) before it signals the error message - granted this is a wild supposition on my uninformed part)!

Don

PS: I will seek absolution and do serious penance for my sacrilegious and thoroughly reprehensible inference about RT software limitations!!:D
 
   #46  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,540
Reaction score
3,931
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
I really do recommend building a test-jig to anyone who is on the "OBDII learning curve" (like me) - it's an informative and convenient way of finding-out how the network topology works on these vehicles! But alas it's not all beer-and-skittles as is evidenced by my latest conundrum for which I seek help!

A good use of the test-jig is to trial Leuchte programming scenarios - without the need for an actual car! This can be easily done by adding a string of LEDs (with suitable ballast resistors) to the BCM pins to simulate the lamps and small PCB switches to emulate the car's lighting switches. This is all simple until I try to simulate the turn signal switch!

The WD for the mk7 shows that the turn-signal switch is connected to the steering column control module (unfortunately the inside switch contacts aren't shown on the WD) and there appears to be no physical wire connection to the BCM. The network arrangement for the control modules on a mk7 shows that both the BCM and the steering column control module share the convenience CAN bus, so I assume that this is the way that the turn signal message is passed-onto the BCM (and the door control modules - for the repeater lamps on the mirrors) - see diagram below:



So my question is this: Assuming that my understanding above is correct (and I hope that it isn't correct), is there any way to simulate the turn signal in the absence of any physical blinker switch pins on the BCM - without having a bulky J527 control module connected to the test jig? I'm aware that the turn-signal can be enabled through the "Output test" screen, but this only lights-up the specific blinker lamps- it doesn't engage any Leuchte commands that are applied to additional lamps.

Thanks in advance for any advice

Don
 
   #47  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,671
Reaction score
21,155
Location
USA
VCDS Serial number
HC100001
So my question is this: Assuming that my understanding above is correct (and I hope that it isn't correct), is there any way to simulate the turn signal in the absence of any physical blinker switch pins on the BCM - without having a bulky J527 control module connected to the test jig?
I doubt it.

Well, I suppose one could monitor a real J527 to see what CAN telegrams it produces that correspond to the various turn signal switch states (or change of states) and then substitute something some smaller device capable of simulating them, but that seems like far more work than just wiring up a real J527.

-Uwe-
 
   #48  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,540
Reaction score
3,931
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
^^^ Uwe: Advice appreciated and accepted - Thanks. I've sourced a second-hand J527 locally - I'll see if I can strip everything that's superfluous from the control module to get it down to its bare-bones)
Don
 
   #49  

Jack@European_Parts

NostraJackAss
Joined
Jan 29, 2014
Messages
20,227
Reaction score
8,685
Location
Montgomery, NY, USA
VCDS Serial number
C?ID=57337
I doubt it.

Well, I suppose one could monitor a real J527 to see what CAN telegrams it produces that correspond to the various turn signal switch states (or change of states) and then substitute something some smaller device capable of simulating them, but that seems like far more work than just wiring up a real J527.

-Uwe-
Well I sure wish someone would turn on the recorder for the ESCL command authorization packets, and build an emulator already for these old A8 and T-rigs.
 
Last edited:
   #50  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,540
Reaction score
3,931
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
OK, its been some time since I first contemplated the concept of a test bench (thanks again to those here who helped me take my fledgling steps) and my embryonic musings have matured somewhat. Because of a local interest down here in Leuchte adaptation channels, the focus of the test bench has been somewhat hijacked towards this direction. It's now a purpose-built training tool for the occasional tutorial to forum members that happen to wonder down this way and are crazy enough to express an interest in wanting to learn about Leuchte programming!! Works quite well for this purpose because all errors are trivial - hasn't been broken yet!!

Here's what it looks like (I had to raid the LED junk-box to make-up the simulated taillight/headlight board and the simulated rotary light switch still needs more work):


But my real purpose in writing is to ask a couple of perhaps "cheeky" questions.
Question 1: I'm interested in understanding more about the VIN that's recorded in these control modules. It seems that the number is held no where else but in the CAN Gateway (at least this appears to be the case in the limited number of control modules in my test bench). Is this true?.
Question 2: is there any way that I can get access to the memory location that holds this number in the CAN Gateway. I assume that this isn't a firmware matter, so it must be held in accessible memory (I would think). I'm comfortable trying anything on the CAN Gateway on the test bench that might not be prudent on my actual car - so all suggestions welcomed


Don
 
   #52  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,671
Reaction score
21,155
Location
USA
VCDS Serial number
HC100001
But my real purpose in writing is to ask a couple of perhaps "cheeky" questions.
Question 1: I'm interested in understanding more about the VIN that's recorded in these control modules. It seems that the number is held no where else but in the CAN Gateway (at least this appears to be the case in the limited number of control modules in my test bench). Is this true?.
While it may or may not be in the gateway, I'm confident it's in the ECU due to regulatory requirements, i.e. the ECU needs to report it when it's talking generic OBD-II for emissions testing purposes. It's probably also in the Immo or Kessy.

-Uwe-
 
   #53  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,540
Reaction score
3,931
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
While it may or may not be in the gateway, I'm confident it's in the ECU due to regulatory requirements, i.e. the ECU needs to report it when it's talking generic OBD-II for emissions testing purposes. It's probably also in the Immo or Kessy.

-Uwe-

Arrrhhh................... the ECU!! I entirely forgot about the ECU-makes sense (thanks)!!! Might be time to introduce my "virtual mk7" (test-bench) to an ECU?


Don

Nope.........

Log away...........:rolleyes:
Thanks Jack: "Log away" - I will!!

Don


Anyone have any suggestion about hacking (perhaps "accessing" is a better term) the VIN memory location?
 
Last edited:
   #54  

Jack@European_Parts

NostraJackAss
Joined
Jan 29, 2014
Messages
20,227
Reaction score
8,685
Location
Montgomery, NY, USA
VCDS Serial number
C?ID=57337
:thumbs:

I think in your mission you will find the VIN in many of the eeproms of the modules.
The VIN and all security data is constantly actually broadcasted on the CAN........can you say security breach gapping hole?
 
   #55  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,671
Reaction score
21,155
Location
USA
VCDS Serial number
HC100001
I think in your mission you will find the VIN in many of the eeproms of the modules.
The VIN and all security data is constantly actually broadcasted on the CAN........can you say security breach gapping hole?
You know, if the MQB platform were an RT product, we would encrypt (or at least obfuscate) the VIN and security data before broadcasting and storing it. People have been hacking at our products for a well over a decade now and we've learned some lessons from that. ;)

-Uwe-
 
   #57  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,540
Reaction score
3,931
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
OK, so eager to try an ECU, I promptly sourced a "wrecker" unit and connected to the test bench. Wired-up all the +12Volt and earth points that I could find in the WD for the engine type and connected the two CAN wires to the gateway module.

Auto-scan report follows:

Code:
Saturday,27,August,2016,15:21:35:16808
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
VCDS Version: 16.8.0.3 (x64)  HEX-NET CB: 0.4321.4
Data version: 20160803 DS255
www.Ross-Tech.com


VIN: WVWZZZAUZEP018310   License Plate: TEST BENCH
Mileage:    Repair Order: with ecu



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Chassis Type: AU (5Q0)
Scan: 01 09 16 19

VIN: WVWZZZAUZEP018310   

01-Engine -- Status: Malfunction 0010
09-Cent. Elect. -- Status: Malfunction 0010
16-Steering wheel -- Status: OK 0000
19-CAN Gateway -- Status: OK 0000
-------------------------------------------------------------------------------
Address 01: Engine (J623-CXSA)       Labels: 04E-907-309-V1.clb
   Part No SW: 04E 906 016 DF    HW: 04E 907 309 A
   Component: 1.4l R4 TSI   H08 5673  
   Revision: WAH08---    
   Coding: 01250032242405082000
   Shop #: WSC 00028 028 00070
   ASAM Dataset: EV_ECM14TFS01104E906016DF 002002
   ROD: EV_ECM14TFS01104E906016DF_VW37.rod
   VCID: 699A78CC88384A0A17-803C

8 Faults Found:
18062 - Coolant Pump 2 
          P261A 00 [039] - Open circuit
          Not Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Date: 2000.00.00
                    Time: 00:00:00

                    Engine speed: 0.00 /min
                    Normed load value: 0.0 %
                    Vehicle speed: 0 km/h
                    Coolant temperature: -40 °C
                    Intake air temperature: -40 °C
                    Ambient air pressure: 1010 mbar
                    Voltage terminal 30: 11.473 V
                    Unlearning counter according OBD: 40
                    Mass flow through throttle valve: 0.0 kg/h
                    Median injection timing: 0.000 ms
                    Engine operating condition: Part. load
                    Engine operating condition-Test_Program_Channel 87: 6

4238 - Engine Coolant Temp Sensor on Radiator Outlet (G83) 
          P2185 00 [039] - Signal too High
          Not Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Date: 2000.00.00
                    Time: 00:00:00

                    Engine speed: 0.00 /min
                    Normed load value: 0.0 %
                    Vehicle speed: 0 km/h
                    Coolant temperature: -40 °C
                    Intake air temperature: -40 °C
                    Ambient air pressure: 1010 mbar
                    Voltage terminal 30: 11.379 V
                    Unlearning counter according OBD: 40
                    Mass flow through throttle valve: 0.0 kg/h
                    Median injection timing: 0.000 ms
                    Engine operating condition: Part. load
                    Engine operating condition-Test_Program_Channel 87: 6

2813 - Accelerator Position Sensor (G79) 
          P2122 00 [167] - Signal too Low
          MIL ON - Not Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Date: 2000.00.00
                    Time: 00:00:00

                    Engine speed: 0.00 /min
                    Normed load value: 0.0 %
                    Vehicle speed: 0 km/h
                    Coolant temperature: -40 °C
                    Intake air temperature: -40 °C
                    Ambient air pressure: 1010 mbar
                    Voltage terminal 30: 11.308 V
                    Unlearning counter according OBD: 40
                    Mass flow through throttle valve: 0.0 kg/h
                    Median injection timing: 0.000 ms
                    Engine operating condition: Part. load
                    Engine operating condition-Test_Program_Channel 87: 6

2815 - Accelerator Position Sensor 2 (G185) 
          P2127 00 [167] - Signal too Low
          MIL ON - Not Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Date: 2000.00.00
                    Time: 00:00:00

                    Engine speed: 0.00 /min
                    Normed load value: 0.0 %
                    Vehicle speed: 0 km/h
                    Coolant temperature: -40 °C
                    Intake air temperature: -40 °C
                    Ambient air pressure: 1010 mbar
                    Voltage terminal 30: 11.308 V
                    Unlearning counter according OBD: 40
                    Mass flow through throttle valve: 0.0 kg/h
                    Median injection timing: 0.000 ms
                    Engine operating condition: Part. load
                    Engine operating condition-Test_Program_Channel 87: 6

16436 - Turbocharger Boost Control Position Sensor Circuit 
          P2562 00 [167] - Electrical Malfunction
          MIL ON - Not Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Date: 2000.00.00
                    Time: 00:00:00

                    Engine speed: 0.00 /min
                    Normed load value: 0.0 %
                    Vehicle speed: 0 km/h
                    Coolant temperature: -40 °C
                    Intake air temperature: -40 °C
                    Ambient air pressure: 1010 mbar
                    Voltage terminal 30: 11.355 V
                    Unlearning counter according OBD: 40
                    Charge pressure actuator: specified position: 23.54 %
                    Bypass valve f high press turboch turbine inlet: actual value: 0.00 %
                    Charge pressure actuator: adaptation for lower stop: 3500.0 mV
                    Bypass valve for high press turbocharger turbine inlet: status-Bit 0: 0
                    Bypass valve for high press turbocharger turbine inlet: status-Bit 16: 0
                    Bypass valve for high press turbocharger turbine inlet: status-Bit 24: 51
                    Bypass valve for high press turbocharger turbine inlet: status-Bit 8: 2
                    Bypass valve for high press turboch turbine inlet: uncond volt: 4999.8 mV
                    Charge air pressure: actual value: 3227.34 hPa

4630 - ECM Power Relay Control Circuit 
          P0686 00 [039] - Short to GND
          Not Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Date: 2000.00.00
                    Time: 00:00:00

                    Engine speed: 0.00 /min
                    Normed load value: 0.0 %
                    Vehicle speed: 0 km/h
                    Coolant temperature: -40 °C
                    Intake air temperature: -40 °C
                    Ambient air pressure: 1010 mbar
                    Voltage terminal 30: 11.426 V
                    Unlearning counter according OBD: 40
                    Engine torque: 0.0 Nm
                    Time since ignition off: 0 s
                    Irregular shutdown of the counter control mod-Bit 0: 1
                    Current system status: SYC_PREDRIVE
                    Current system status-Test_Program_Exe Con State 02 UBYTE: 3

4629 - ROD - Unknown Error Code 
          - 00 [039]
          Not Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Date: 2000.00.00
                    Time: 00:00:00

                    Engine speed: 0.00 /min
                    Normed load value: 0.0 %
                    Vehicle speed: 0 km/h
                    Coolant temperature: -40 °C
                    Intake air temperature: -40 °C
                    Ambient air pressure: 1010 mbar
                    Voltage terminal 30: 11.379 V
                    Unlearning counter according OBD: 40
                    Engine torque: 0.0 Nm
                    Time since ignition off: 0 s
                    Irregular shutdown of the counter control mod-Bit 0: 1
                    Current system status: SYC_PREDRIVE
                    Current system status-Test_Program_Exe Con State 02 UBYTE: 3

2778 - Engine Coolant Temp. Sensor (G62) 
          P0118 00 [039] - Signal too High
          Not Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Date: 2000.00.00
                    Time: 00:00:00

                    Engine speed: 0.00 /min
                    Normed load value: 0.0 %
                    Vehicle speed: 0 km/h
                    Coolant temperature: -40 °C
                    Intake air temperature: -40 °C
                    Ambient air pressure: 1010 mbar
                    Voltage terminal 30: 11.473 V
                    Unlearning counter according OBD: 40
                    Coolant temperature at engine start: -22.5 °C
                    Coolant temperature at radiator outlet: actual value: -40.0 °C
                    Coolant temperature modeled value: -39.8 °C

Readiness: 1110 0001

-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519)       Labels: 5Q0-937-08X-MV1.clb
   Part No SW: 5Q0 937 084 N    HW: 5Q0 937 084 N
   Component: BCM MQBAB M   H14 0106  
   Serial number: 00011309901220
   Coding: 030000000000004303200002000000000000000000000000000000000000
   Shop #: WSC 73430 790 00104
   ASAM Dataset: EV_BCMCONTI 010001
   ROD: EV_BCMBOSCH_VW37.rod
   VCID: 43C68A64CAD4705AFD-8016

29 Faults Found:
5130 - Bulb for Front Left Turn Signal 
          B11E8 15 [009] - Open or Short to Plus
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

5386 - Bulb for Front Right Turn Signal 
          B11EA 15 [009] - Open or Short to Plus
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

7178 - Bulb for High Beam Headlamp Left 
          B1219 15 [009] - Open or Short to Plus
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 3
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

7434 - Bulb for High Beam Headlamp Right 
          B121A 15 [009] - Open or Short to Plus
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 3
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

10506 - Bulb for Left Tail Light 
          B12BE 15 [009] - Open or Short to Plus
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

10762 - Bulb for Right Tail Light 
          B12BF 15 [009] - Open or Short to Plus
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

11274 - Bulb for Center Brake Light 
          B12C6 15 [024] - Open or Short to Plus
          Intermittent - Confirmed - Not Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 1
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

18186 - Bulb for Rear Left Side Marker Lamp 
          B12BC 15 [009] - Open or Short to Plus
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

136458 - Terminal 15 
          B1148 15 [009] - Open or Short to Plus
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

395273 - Control Circuit for Signal Horn 
          B1344 14 [009] - Open or Short to Ground
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

533269 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

539925 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

541973 - Databus 
          U1121 00 [008] - Missing Message
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 4
                    Reset counter: 23
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

542229 - Databus 
          U1121 00 [008] - Missing Message
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 4
                    Reset counter: 23
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

549141 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

549909 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

552213 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

554517 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

555029 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

555285 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

555541 - Databus 
          U1121 00 [008] - Missing Message
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 4
                    Reset counter: 23
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

556053 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

558101 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

558869 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

559125 - Databus 
          U1121 00 [008] - Missing Message
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 3
                    Reset counter: 23
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

559637 - Databus 
          U1121 00 [009] - Missing Message
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

919560 - Light Switch 
          B126A 29 [008] - Signal Implausible
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 3
                    Fault Frequency: 7
                    Reset counter: 23
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

947204 - Control Module for Wiper Motor 
          U10A3 00 [009] - No Communications
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00

15360256 - Component Protection 
          U1101 00 [009] - Active
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 4
                    Fault Frequency: 1
                    Reset counter: 238
                    Mileage: 1048574 km
                    Date: 2000.00.00
                    Time: 00:00:00


-------------------------------------------------------------------------------
Address 16: Steering wheel (J527)       Labels: 5Q0-953-549.clb
   Part No SW: 8V0 953 521 E    HW: 5Q0 953 549 A
   Component: Lenks. Modul  007 0070  
   Revision: --------    Serial number: 08121100010724
   Coding: 0000
   Shop #: WSC 06314 790 00021
   ASAM Dataset: EV_SMLSKLOMQB 009001
   ROD: EV_SMLSKLOMQB_VW37.rod
   VCID: 3C34F198B72A0FA2BC-8068

No fault code found.

-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533)       Labels: 5Q0-907-530-V1.clb
   Part No SW: 5Q0 907 530 E    HW: 5Q0 907 530 E
   Component: GW MQB Mid    121 1109  
   Revision: --------    Serial number: 0000073193
   Coding: 000000342B086400EF0006481C0F00000001000000000000000000000000
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_GatewLear 006010
   ROD: EV_GatewLear.rod
   VCID: 3326DAA49A74C0DA6D-8066

No fault code found.

End----------(Elapsed Time: 00:29, VBatt start/end: 12.0V/12.0V)-----------
Of course lots of DTCs (which are to be expected) - these don't worry me for the moment, but the odd thing is that the inclusion of the ECU to the test-bench (not connected to any external devices) causes the brake lights on my simulated tail-light board to illuminate. I'm guessing that there is some form of fail-safe mechanism whereby the ECU instructs the BCM (via a CAN message) to illuminate the brake lights if connection to the brake-light-switch is lost (I'm guessing)

But more concerning (and the real reason for this post) is the fact that whilst I can readily access all screens related to the Engine module with the latest software- I don't appear to be able to change any coding, or adaptation channel settings (the SA is accepted by the control module and I can use the long coding helper and I can access the 12 x adaptation channels in the module). The error message that is returned after I press Doit! is shown below



As I said, the connections to the ECU are just those related to +12V and earth connections, and the 2 x CAN wires - nothing else! Is this insufficient for changing the control module variables?

Does anyone have any insights to solving this problem - please?

Don

PS: It's interesting (to me at least) that whilst the test bench now has (at least?) 2 x different VINs, the one that HEX NET has chosen to report is the Engine VIN (not the VIN registered in the CAN Gateway)!!
 
   #58  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,671
Reaction score
21,155
Location
USA
VCDS Serial number
HC100001
I'll speculate that the "Conditions not correct" rejection of the request indicates that the software in this ECU has some logic that decides to disallow those changes under the conditions it's seeing on your test bench. I'll give you an example from an earlier era: Some ECUs would not allow themselves to be flashed without having had a handshake from an immobilizer.

As for why the VCDS reports the VIN from the ECU: Simple -- that one is easiest/fastest to get. In modern cars, it's difficult to to do proper diagnostics w/o knowing what the the car is. This can usually be determined from the VIN, and real cars (as opposed to test benches) almost always have an ECU. ;)

Some tools actually force you to manually select the car make, model, year, engine type, and other data like that. We prefer to avoid burdening our users with such nonsense. Why? You should see how often we have someone on the phone wanting help who claims he's working on a Jetta, when it's actually a Passat. Then the fool will tell us he's got such and such a fault code in the engine, and we'll ask: "OK, which engine does the car have?" and the answer is: "I don't know". "OK sir, maybe you should open the <censored> hood and have a <censored> look?" :banghead:

-Uwe-
 
Last edited:
   #59  

jimmyq

Verified VCDS User
Verified
Joined
Sep 3, 2014
Messages
55
Reaction score
11
Location
UK
VCDS Serial number
C?ID=139879
hi guys just been reading through the posts a well done and some nice rigs :) i have been trying to power mk7 golf clocks on the bench but can only get them to light the needles lol tried mk6 ones with mk6 plug easy but mk7 wont work

basically


Connector assignment of control unit in dash panel insert -J285-








-T18- (A) Designation -T18- (A) Designation
1 Terminal 30 10 Terminal 31
2 11 Fuel gauge sender -G- , terminal 31
3 12 Fuel gauge sender for auxiliary fuel tank -G292-
4 13 Fuel gauge sender for auxiliary fuel tank -G292-
5 14 Fuel gauge sender -G-
6 15 Fuel gauge sender -G- l
7 Parking brake pressure switch -F234- 16
8 Immobiliser reader coil -D2- 17 B507 Connection (convenience CAN bus, low), in interior wiring harness
9 Immobiliser reader coil -D2- 18 B506 Connection (convenience CAN bus, high), in interior wiring harness


first i tried just the live and earth with 12 volts (needles light up) no mileage or ignition lights

i then connected the can wires with a can gateway unit rigged to obd port and powered the can gateway and clocks i can communicate with gateway via vcds but not the clocks what ele do i need to power the clocks steering control?
 
   #60  

DV52

Verified VCDS User
Verified
Joined
May 16, 2014
Messages
3,540
Reaction score
3,931
Location
Melbourne, Australia
VCDS Serial number
C?ID=194404
hi guys just been reading through the posts a well done and some nice rigs :) i have been trying to power mk7 golf clocks on the bench but can only get them to light the needles lol tried mk6 ones with mk6 plug easy but mk7 wont work

basically


Connector assignment of control unit in dash panel insert -J285-

-T18- (A) Designation -T18- (A) Designation
1 Terminal 30 10 Terminal 31
2 11 Fuel gauge sender -G- , terminal 31
3 12 Fuel gauge sender for auxiliary fuel tank -G292-
4 13 Fuel gauge sender for auxiliary fuel tank -G292-
5 14 Fuel gauge sender -G-
6 15 Fuel gauge sender -G- l
7 Parking brake pressure switch -F234-
8 Immobiliser reader coil -D2-
9 Immobiliser reader coil -D2-
16
17 B507 Connection (convenience CAN bus, low), in interior wiring harness
18 B506 Connection (convenience CAN bus, high), in interior wiring harness

first i tried just the live and earth with 12 volts (needles light up) no mileage or ignition lights

i then connected the can wires with a can gateway unit rigged to obd port and powered the can gateway and clocks i can communicate with gateway via vcds but not the clocks what ele do i need to power the clocks steering control?
Jimmy: Hi. Damn-you beat me to it!!:) I have been trying to source a cheap instrument control module for my updated test jig (see pic below) for a while now, but without success. Sounds like you might be the first to do this - respect!!



Anyhow, as to your question, if you look at the connections that you listed in your post, the pins basically are in three categories: Power, Peripherals and CAN bus. Notice that there is no Terminal 15 pin in this connector - see later discussion

From a "physical" perspective, the illumination of the clock dials (and every other light-up component) in the instrument cluster on the mk7 happens via a photo-transistor that is faintly visible as a small circle between the "7" and the "8" numerals (see below) - see below. Not sure how familiar you are with these devices, but a photo-transistor is a semiconductor device (usually has a transparent body) in which the amplification, or "gain" varies with the amount of light that it sees.



From a "control" perspective, the mk7 introduced a novel way of manipulating the manner in which the dash board illumination was managed. It does this via a bunch of adaptation channels with the label "dimming_characteristic_curve_adjustment". This grouping is generally arranged as "X" values and "Y" values. If you look at the admap for your instrument control module, you will find a grouping of these channels for the following 5 x functions:

• clock dial day
• clock dial night
• gauge
• indicator lights
• middle display main field

Here is adaptation channels for the dimming curve grouping for the photo-transistor


So, from here-on I'm guessing, but what appears to happen is that the "X" values relate to increasing brightness levels in the cabin and the "Y" values correspond to decreasing darkness levels in the cabin. I can write more stuff about my guess of how these X/Y values operate, but it's probably more than is required for this response

You can manipulate the illumination level by altering the values in the adaptation channels in the table above, but an easy way of testing the effect is to simply shine a torch into the photo transistor. This mimics strong sunshine conditions in the cabin thereby selecting the X5 point in the dimming-curve which maximizes the dash board illumination. Covering the photo transistor which mimics night-time conditions in the cabin has the effect of selecting the Y1 point in the dimming curve which dims illumination to a minimum -this happens because VW have programmed a visual signal into the dash lighting that gives the driver a prompt to turn-on the headlights at twilight.

In addition to this, cluster illumination is affected by the position of the rotary light switch. Since there appears to be no physical connection between the instrument control module and the BCM in the WD, I suspect that this communication happens over the CAN bus. I was going to test this hypothesis on my test-jig, but perhaps you could do this for me -please?

Finally, I found with my test-jig set-up that not much happened without the seemingly insignificant "ignition-key simulator". Makes sense if I had have thought about it correctly and the more experienced folk here would doubtless think that this is obvious, but for me it was on my learning-curve.

Unfortunately, it's not possible to simulate the ignition key without adding the steering wheel controller into the test -jig. Since my principal objective for the test-jig became an education tool for "Leuchte programming", and because the steering wheel module fortuitously contained the blinker and high-beam flasher stalk, I got an added advantage by its inclusion into the test-jig.

But I suspect that the omission of the ignition key simulator may be a serious impediment in your set-up (I think) because the connector pin-out on the instrument module doesn't have a terminal 15 wire. My suspicion is that this means that the message that tells the instrument module that the ignition is switched-on happens over the CAN bus (I think). With your current arrangement, the instrument module never receives the T15 message (I think)

Don

PS: If you do include an ignition-key simulator into your test-jig, I suggest that you remove the spring inside the white circular switch shown in my picture. Whilst you have the switch apart, you should permanently bridge (solder) the mating connectors together that close when the physical key is inserted into the barrel-lock (not said well, but I hope that this makes sense)!
 
Last edited:
Top