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.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!
Thanks very much @n10n
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.Is it just auto detection of which modules are installed and their address?
Does VCDS load the same label-file for engine in manual vs. automatic?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.
I see what you;re thinking. Here are the results:Does VCDS load the same label-file for engine in manual vs. automatic?
View attachment 216356
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
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
Some further explanations about fault code extensions here - unfortunately nothing about the mentioned ones[036] instead of [44]...
***NERD ALERT***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.
Yes. However, for a single module a better and simpler way is:So could I make a custom auto scan with a single module, and collect cyclically polled block map data?
Ah. I didn’t see the repeat function. It was hiding in plain sight. I might do some more digging then. Thank you!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
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.
I think ‘haunted’ will be a very acceptable narrative. Good idea.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!