Sensor Errors on S5 only 10 days in

[jtrembath]

Only had the S5 10 days and already it's giving multiple errors today. Took it to the local dealer and all they did is reset the codes and said if it happens again, they'll need it for at least a full day to discuss the issues with MG. Not a good start, wondering already if I've got a lemon on my hands.

 

[Alb]

This may be down to something as simple as the camera getting confused. The owners manual lists a whole bunch of circumstances where this might happen.

 

[Rei]

Check if the windscreen is clean in front of the camera, and that when you turn the car on it's not pointing towards the sun. I've had both of those cause issues.

 

[James Dean Driving School]

Can happen when there is dew on the screen and a bit misty out.

 

[Lovemyev]

Had a similar experience with our S5 only today.
Returned to the car after about a 15 minute stop to pick up some items.
Booted up the car and went to move away.
The car gave out numerous bongs and warning lights on the dash.
Very similar list to yours.
It allowed me to drive home, but I noticed that there was absolutely NO Regen at all when reducing speed.
If I increased the Regen strength manually, although it changed the level on the drivers display, it made zero difference!.
The car had NO Regen at all and the fault codes stayed displayed all the way home.
When I reached home, I powered down the car and locked it.
I returned back to the car about 30 minutes later, because I needed to unexpectedly go out again.
Car booted up just fine and no return of the warning messages and the Regen had been resorted !.
I think, what may have caused this problem was when I booted up the car the first time.
The car was facing directly into very strong sun light.
This sudden influx of light, directly into the camera, is not liked by the car, in its normal boot up process.
The ZS EV did suffer from a very similar situation, when strong light hitting the camera suddenly, the car would react by throwing up numerous error on the dash panel.
After I returned home, I had to go back out again about one hour later.
All errors had reset and the Regen returned back to normal.
I tend to think, that when a false trigger happens, it set off a train reaction of errors that the car has difficulty dealing with and the error just multiply.

 

[jtrembath]

Thanks everyone. It happened after the car was left in a railway station carpark and it was raining. See what happens today, it's still raining. I can at least rule out the sun causing the errors.

 

[Ian Key]

Sometimes the various modules don't boot up in the correct sequence and when one is a little slow it throws up errors in the rest. The solution is the same as all IT departments tell you, is to switch it off, wait a minute then switch it on again.

I've had it where I opened the passenger window while the car was booting up and it wouldn't close again. I pulled up, got out of the car, locked it, waited a few seconds then got back in and the window would now close.

 

[jtrembath]

Sometimes the various modules don't boot up in the correct sequence and when one is a little slow it throws up errors in the rest. The solution is the same as all IT departments tell you, is to switch it off, wait a minute then switch it on again.

I've had it where I opened the passenger window while the car was booting up and it wouldn't close again. I pulled up, got out of the car, locked it, waited a few seconds then got back in and the window would now close.

Poorly written software by the sounds of it. Hopefully there will be some OTA fixes for these types of issues. In my case I powered off completely and restarted it and the errors were still there until the dealer reset them. Fortunately, I could still drive it but without some of the safety features working.