early E85 then.
Bulb out warning light.
- Thread starter chanlon1
- Start date
Started the car. No dash errors. As I have said, it only happens every now and again.
Decided to check the fog light per the comment above. It’s working fine, however the fog light is only on the rear driver side, whereas the Scanner software says left side. I presume this is irrelevant. I’ll look at pulling the fig light bulb out as that should throw a dash error and I can check what Scanner says.
Why is nothing straightforward…….
Decided to check the fog light per the comment above. It’s working fine, however the fog light is only on the rear driver side, whereas the Scanner software says left side. I presume this is irrelevant. I’ll look at pulling the fig light bulb out as that should throw a dash error and I can check what Scanner says.
Why is nothing straightforward…….
Took the cluster out and the fog light bulb looked okay, however the reversing light looked a tad black/burnt on one side, so replaced it with a spare I had in the garage. It had never appeared on any warnings but it's a new one in now.
Bought a new fog bulb, installed it - what a faff trying to pull the bulb holder out, the designers could have made the holder a bit more ergonomically friendly.......reinstalled the cluster, switched engine on.....dash light reappears and the new fog light isnt even switching on. A quick wiggle of the connector block at the back of the lights and now it's working.
So, I think the issue is more than likely a dodgy connection somewhere in the connector block at the back of the cluster. Something to add to the list of things that need doing, but its not high up the list as its intermittent.
Bought a new fog bulb, installed it - what a faff trying to pull the bulb holder out, the designers could have made the holder a bit more ergonomically friendly.......reinstalled the cluster, switched engine on.....dash light reappears and the new fog light isnt even switching on. A quick wiggle of the connector block at the back of the lights and now it's working.
So, I think the issue is more than likely a dodgy connection somewhere in the connector block at the back of the cluster. Something to add to the list of things that need doing, but its not high up the list as its intermittent.
