Stop/Start Not Working

Ah this is so weird!!! So after unplugging the dash cam I got the start-stop working for a bit. Last night I took the car for a shop run and the same error came out of nowhere. The dash is obviously unplugged - any ideas chaps???
 
Can you read fault codes from your engine control unit?
VCDS, CARISTA, OBDeleven?
 
  • Like
Reactions: mmi
Thank you @Robert Yes, I need to get my hands on a laptop with VCDS after Xmass and will post live data.

Is Carista so good to provide such level of data details? I’m considering buying one...
 
Hi @Robert,

Thank you for taking the time reading this... I've just run the Carista detailed ECU.

FEW BACKGROUND NOTES BEFORE:

1. As I've mentioned before, I've got an immobiliser installed by professionals and the car was running with no start-stop error.

2. The same day I got the immobiliser installed, I re-connected and powered my dashcam to the OBD. A few days later, I disconnected the dashcam from my OBD and it was working for a few hours. The next day error came back.

3. The error seems to appear only on the dashboard and start-stop not working.

Many thanks & regards,
L

### DETAILED ECU INFO ###

ECU info obtained with Carista 540099 for iOS:

VIN: WV2ZZZ7HZHH******

Engine
Part #: 04L906056AF
Component: R4 2.0l BTD
Software version: 6207
ASAM/ODX identifier: EV_ECM20BTD03004L906056AF
Coding: 0025401C432701080000 (hex)
Fault codes:
25665 Manufacturer-specific code
25670 Manufacturer-specific code


Transmission
Part #: 0BT300012C
Component: DSG DQ500-7A
Software version: 5302
ASAM/ODX identifier: EV_TCMDQ500021
Coding: 0014 (hex)
[No fault codes]

ABS
Part #: 7E0907379P
Component: ESC
Software version: 0133
ASAM/ODX identifier: EV_Brake1ESCCONTIVN75XGP2
Coding: 617EC0986568847E867B0377A6892192790000 (hex)
[No fault codes]

Instrument cluster
Part #: 7E0920970S
Component: KOMBI
Software version: 1107
ASAM/ODX identifier: EV_Kombi_UDS_VDD_RM09
Coding: 730F010300 (hex)
[No fault codes]

Airbags
Part #: 7E0959655H
Component: VW10Airbag01S
Software version: 0018
ASAM/ODX identifier: EV_AirbaVW10BPAVW12X
Coding: 000000000000000000000000000000003153 (hex)
[No fault codes]

Steering angle
Part #: 6R0959654
Component: LENKW.SENSOR
Software version: 0070
ASAM/ODX identifier: EV_LWSKLOVW25X
Coding: 01 (hex)
[No fault codes]

Parking/steering assist
Part #: 7E0919475AA
Component: PARKHILFE 8K
Software version: 0212
ASAM/ODX identifier: EV_VW75XParkAssis8K
Coding: 30810C (hex)
[No fault codes]

Heater & air conditioning
Part #: 7E0907040S
Component: ClimatronicT5
Software version: 0613
ASAM/ODX identifier: EV_ClimatronicT5
Coding: 0000000103 (hex)
[No fault codes]

Central electronics
Part #: 7E0937090B
Component: BCM PQ25 Max4
Software version: 0744
ASAM/ODX identifier: [none]
Coding: B8AC39BA0B63341293284B647CEB9E549D94698960CC6960320400BF0840 (hex)
Fault codes:
00978 Lamp for Low Beam; Left (M29) (IGNORE THIS - THAT's CAUSED by MY NEW Philips Ultinon PRO9000 HL)
00979 Lamp for Low Beam; Right (M31) (IGNORE THIS - THAT's CAUSED by MY NEW Philips Ultinon PRO9000 HL)
01495 Bulb for High-Beams, Left (M30) (IGNORE THIS - THAT's CAUSED by MY NEW Philips Ultinon PRO9000 HL)
01499 Bulb for High-Beams, Right (M32) (IGNORE THIS - THAT's CAUSED by MY NEW Philips Ultinon PRO9000 HL)

CAN network gateway
Part #: 7E0909901
Component: GW-K-CAN TP20
Software version: 0744
ASAM/ODX identifier: [none]
Coding: 042305 (hex)
[No fault codes]

Immobilizer
Part #: 5K0953234
Component: IMMO
Software version: 1107
ASAM/ODX identifier: EV_Immo_UDS_VDD_RM09
Coding: 000000 (hex)
[No fault codes]

All-wheel-drive system
Part #: 0AY907554L
Component: Haldex4Motion
Software version: 7620
ASAM/ODX identifier: EV_AllWheelContrHA1VW37X
Coding: 0505 (hex)
[No fault codes]

Auxiliary heater
Part #: 7E0963273A
Component: STH-T5GP2
Software version: 0009
ASAM/ODX identifier: EV_AuxilParkiHeateWOST5G2
Coding: 4101 (hex)
[No fault codes]

Battery regulator
Part #: 7E0907534
Component: Batt.regelung
Software version: 0744
ASAM/ODX identifier: [none]
Coding: 530B1A73 (hex)
[No fault codes]

Infotainment system
Part #: 5K7035200G
Component: MU-S-D-ER
Software version: 0363
ASAM/ODX identifier: EV_MUStd4CTSAT
Coding: 06570000FF00000011111101008808001F0100D60020010003 (hex)
[No fault codes]

Obtained with Carista 540099 for iOS.
 
  • Like
Reactions: mmi
25665 Manufacturer-specific code
25670 Manufacturer-specific code
25665 - Output for Starter Relay - P0615 00 [032] - Open Circuit
25670 - Control Circuit for Starter Relay 2 -- P3049 00 [032] - Open Circuit
 
That’ll be the immobiliser, they have tapped into the bcu feed that goes through the 5a fuse that supplies the 2 starter relays.
 
Thank you @mmi & @Loz - I could say these two Open Circuit errors are expected because of the immobiliser. Theoretically, this should not affect start-stop right?

The error hasn't come up straight away, just after a while - therefore if it was down to the immobiliser, the errors would always be there from the start without going on & off when unplugging dashcam.

Another bit of info is that the error only appears after like 2-3 seconds with the following logo:

IMG_1BD636E71049-1.jpeg
 
Does it clear after you cycle the ignition? as I get this if I don’t get the ghost code correct.
 
No it does not clear. Error stays until engine’s off.
So is your immobiliser only closing the circuit long enough to start it, then going open circuit until you de immobilise again?
This is what it sounds like to me, the stop start has to be confident it can automatically restart the the engine if it stops it at a junction.
 
As soon as you switch the ignition and start the car,
the circuit is closed for the whole period of driving unless you take the key out out for at least 10 seconds.

The start-stop was working fine first couple of days - then the error showed up.
 
Have you experimented with the timings? like, insert key, turn on the ignition, turn off, wait 20 seconds, turn on, wait 10 then crank?
I say this, as I noticed that start-stop is very fussy about seeing all the components that it needs on the can bus, being ready.
Also, you will need to clear any code you have before doing this test.

The fact you have these open-circuit codes leads me to believe that the immobiliser is not acting fast enough. you may have to turn on, clear codes and then start it up.
 
Hi @Loz, thanks for the tips.

I've tried with the ignition, clear the codes but these didn't exactly work as expected. However, I've managed to get rid of the errors three consecutive times. Please see the steps below:

1. Insert key in the ignition
2. Clear immobiliser
3. Start the engine (an error would appear after a few seconds)
4. Drive maybe 50-100m (to the nearest traffic lights) and stop
5. Turn off the vehicle and take out the key
6. Put the key back on, clear immobiliser and start the engine - no more error until next time the key is turned off.

NOTE: Cleared errors come back almost instantly

BR,
L
 
I’m a newbie and useless with electrics/computers anyway but was considering getting a tracker and a ghost immobiliser for an under conversion T6.1 6-speed manual. As you describe here, were these immobilisers bringing up the fault code incorrectly fitted? Or can I expect to have similar problems if I go ahead and get a ghost fitted?
 
I’m a newbie and useless with electrics/computers anyway but was considering getting a tracker and a ghost immobiliser for an under conversion T6.1 6-speed manual. As you describe here, were these immobilisers bringing up the fault code incorrectly fitted? Or can I expect to have similar problems if I go ahead and get a ghost fitted?
We don't get these issues with a Ghost
 
I’ve started getting the same issue. Not sure if it’s down to the ghost immobiliser. I get the glow plug light flashing when I turn on the ignition. I input the ghost code and re cycle the ignition and get the stop/start error up on the display. If I cycle the ignition off and on 2 or three times the fault goes. So I’m not sure if it’s linked to the ghost or something else. I have had the immobiliser fitted for 6 months prior to the faults starting
 
I spoke with an installer last week about immobilisers. He fits Ghost and recommended I didn’t fit one to my new 6.1 when it eventually arrives, as he frequently finds that Ghost causes issues like the one you’re describing on the 6.1 He seemed to think it was caused by over the air updates. Can’t explain it any more than that as I’m no expert.

Suffice to say I won’t be getting a Ghost and will probably get Metatrak instead
 
Back
Top