Deeper dive into these fault codes

Well that lead went cold very very quickly. 5A fuse on the purple wire. Old lights somewhere?

The search continues…

Now onto the BCM.

IMG_5338.jpeg

IMG_5339.jpeg
 
That 6-pin connector is the instrument dimmer, right? If so, the fuse is just a tap into ignition live, not dimmed. Could have been a feed for anything… for example a tracker :geek:

Edit: and that plastic conduit might indicate it’s gone through bulkhead in it’s prior life. But just maybe. I wouldn’t use such conduit unless exposed to elements.
 
Last edited:
That 6-pin connector is the instrument dimmer, right?
It would be in a Highline. On mine it’s just the headlight range control. I can’t find the right diagram for it. On the H4 Headlight diagram it shows the motor but not the this pot.

When I followed the cable, it was either headed up the A Pillar or into the engine bay. Could have been either.

At least I’ve ruled out a device behind the dash. Had everything out even the clocks to fit the MFSW wiring.

Next weekend it’s into the engine bay for the cruise control so there might be a week delay. Boo!
 
It would be in a Highline. On mine it’s just the headlight range control. I can’t find the right diagram for it. On the H4 Headlight diagram it shows the motor but not the this pot.

When I followed the cable, it was either headed up the A Pillar or into the engine bay. Could have been either.

At least I’ve ruled out a device behind the dash. Had everything out even the clocks to fit the MFSW wiring.

Next weekend it’s into the engine bay for the cruise control so there might be a week delay. Boo!
1696693195616.png
Edit: this was what I was looking at. Connector T6ac seemed to have matching wire colors considering starred remarks and cannot see from your photo if the red is just red or red/blue
 
Last edited:
If I set VCDS auto scan to 7E, SF or SG (one of those must be right, probably the last) instead of letting VCDS determine it automatically, then only the ‘starter circuit’ fault occurs, not the relay fault. Not sure if that gives any clues because I don’t know what might be different between specify vs auto.

IMG_5355.jpeg
 
Is it just auto detection of which modules are installed and their address?
 
Is it just auto detection of which modules are installed and their address?
I think so but not sure to be honest. I think the manual setting could be useful in some bench testing scenarios or if ECU/BCM are in fault so that they can’t communicate normally.
 
If I set VCDS auto scan to 7E, SF or SG (one of those must be right, probably the last) instead of letting VCDS determine it automatically, then only the ‘starter circuit’ fault occurs, not the relay fault. Not sure if that gives any clues because I don’t know what might be different between specify vs auto.
Does VCDS load the same label-file for engine in manual vs. automatic?
1696793784427.png
 
Does VCDS load the same label-file for engine in manual vs. automatic?
View attachment 216356
I see what you;re thinking. Here are the results:

Auto :
Address 01: Engine (J623-CAAC) Labels:. 03L-906-022-CAA.clb

7E0 (which may well be the right variant, as it is a 7E0 chassis):
Address 01: Engine (J623-CAAC) Labels:. 03L-906-022-CAA.clb

SG (which is part of my sales code and was essential for finding, say, the right CCS kit):
Address 01: Engine (J623-CAAC) Labels:. 03L-906-022-CAA.clb

Yes - the same.
 
The fault has changed slightly - here's the fault from the very first AutoScan I did, which showed two faults, but this is just the circuit fault from that:

Code:
5459 - Control Circuit for Starter Relay 2
          P3048 00 [044] - Short to Ground
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 75
                    Mileage: 259846 km
                    Date: 2023.09.09
                    Time: 10:18:12

                    Engine RPM: 861.00 /min
                    Normed load value: 22.0 %
                    Vehicle speed: 0 km/h
                    Coolant temperature: 71 °C
                    Intake air temperature: 31 °C
                    Ambient air pressure: 1010 mbar
                    Voltage terminal 30: 13.300 V
                    Unlearning counter according OBD: 40
                    Starter control: terminal 50 feedback-Bits 0-7: 0
                    Starter control: relay 1-Bits 0-7: 0
                    Starter control: release conditions-Bits 0-7: 2
                    Starter control: release conditions-Bits 0-7: 12
                    Starter control: shut-off conditions 1-Bits 0-7: 0
                    Starter control: shut-off conditions 1-Bits 0-7: 0
                    Number of manual engine starts-Bits 0-7: 0
                    Number of manual engine starts-Bits 0-7: 0
                    Number of manual engine starts-Bits 0-7: 0
                    Number of manual engine starts-Bits 0-7: 44
                    Number of automatic engine starts-Bits 0-7: 0
                    Number of automatic engine starts-Bits 0-7: 0
                    Number of automatic engine starts-Bits 0-7: 54
                    Number of automatic engine starts-Bits 0-7: 14

And from one just now using the 7E0 manual setting, which only shows one fault:

Code:
5459 - Control Circuit for Starter Relay 2
          P3048 00 [036] - Short to Ground
          Intermittent - Not Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 1
                    Mileage: 260802 km
                    Date: 2023.10.08
                    Time: 15:33:21

                    Engine RPM: 0.00 /min
                    Normed load value: 0.0 %
                    Vehicle speed: 0 km/h
                    Coolant temperature: 39 °C
                    Intake air temperature: 26 °C
                    Ambient air pressure: 1010 mbar
                    Voltage terminal 30: 12.120 V
                    Unlearning counter according OBD: 40
                    Starter control: terminal 50 feedback-Bits 0-7: 0
                    Starter control: relay 1-Bits 0-7: 0
                    Starter control: release conditions-Bits 0-7: 2
                    Starter control: release conditions-Bits 0-7: 86
                    Starter control: shut-off conditions 1-Bits 0-7: 0
                    Starter control: shut-off conditions 1-Bits 0-7: 0
                    Number of manual engine starts-Bits 0-7: 0
                    Number of manual engine starts-Bits 0-7: 0
                    Number of manual engine starts-Bits 0-7: 0
                    Number of manual engine starts-Bits 0-7: 44
                    Number of automatic engine starts-Bits 0-7: 0
                    Number of automatic engine starts-Bits 0-7: 0
                    Number of automatic engine starts-Bits 0-7: 54
                    Number of automatic engine starts-Bits 0-7: 230

Fault is P3048 00 [036] instead of [44]...

EDIT: P3048 00 [036] instead of [044]
 
Last edited:
[036] instead of [44]...
Some further explanations about fault code extensions here - unfortunately nothing about the mentioned ones
 
I think the manual setting could be useful in some bench testing scenarios or if ECU/BCM are in fault so that they can’t communicate normally.
***NERD ALERT***

Well, there are ways to exploit manual setting - by creating an entry of your own with only few controllers in it - a custom autoscan list.​
Setup file C:\Ross-Tech\VCDS\MyAutoScan.txt​
1696875502018.png
Combining the above with Debug level 2 (under VCDS Options) would force VCDS Auto-Scan to create blockmap and adpmap files of the selected few controllers only (instead of the normal Auto-Scan)​
VCDS (Auto-Scan) can be even forced to LOOP the controllers continuosly. Thus one could keep on recording blockmaps of the selected controllers (instead of just one). E.g. continuos stream of blockmaps from engine+DSG+4Motion - all at one go.​
Setup file C:\Ross-Tech\VCDS\MyAutoScan.txt​
1696876967132.png
1696876303449.png
(L) for LOOPing - with Debug level 2 (under VCDS Options)​
Sourced from​
 
So could I make a custom auto scan with a single module, and collect cyclically polled block map data?
 
So could I make a custom auto scan with a single module, and collect cyclically polled block map data?
Yes. However, for a single module a better and simpler way is:

VCDS > Applications > Controller Channel Map >

1696882564849.png

Just check first how long it takes to record one block map (elapsed time is found on last line) and use that to calculate number of repeats needed/desired.

1696882979981.png
 
Yes. However, for a single module a better and simpler way is:

VCDS > Applications > Controller Channel Map >

View attachment 216429

Just check first how long it takes to record one block map (elapsed time is found on last line) and use that to calculate number of repeats needed/desired.

View attachment 216431
Ah. I didn’t see the repeat function. It was hiding in plain sight. I might do some more digging then. Thank you!
 
  • Like
Reactions: mmi
Combining the above with Debug level 2 (under VCDS Options) would force VCDS Auto-Scan to create blockmap and adpmap files of the selected few controllers only (instead of the normal Auto-Scan)
VCDS (Auto-Scan) can be even forced to LOOP the controllers continuosly.

Nice trick, thanks!

Of course, recording adaptation maps in a loop is largely waste so would be nice to record blockmaps only.

Even better would be just a text file with IDExxx numbers for the VCDS to run through in a loop, perhaps even from mixed controllers ;)

Anyway this feature can be very useful to catch measuring values around intermittent problems.
 
Today was the day to get the CCS installed so I had a good look under the battery. I changed both starter relays for known-good. I checked the wiring, the connections, nothing had corroded - all squeaky clean. Put it all back together again - cleared the codes and... still get two fault codes :slow rofl:

Definitely no aftermarket devices or wiring under there either.

Next on the list of things to try is an ECU reset.
 
Have you considered that your van is just haunted Chris?

I don't believe in ghosts in general but I have a wireless microphone channel in the am dram theatre I help look after (Mic 5) where I have physically replaced every item of kit and cable and moved frequencies but it's always 5 that plays up, we just regard it as haunted and use it last!
 
Have you considered that your van is just haunted Chris?

I don't believe in ghosts in general but I have a wireless microphone channel in the am dram theatre I help look after (Mic 5) where I have physically replaced every item of kit and cable and moved frequencies but it's always 5 that plays up, we just regard it as haunted and use it last!
I think ‘haunted’ will be a very acceptable narrative. Good idea.
 
Back
Top