Red Power System Malfunction Warning.

[NeilH]

Red Power System Malfunction Warning. Serious fault, stop as soon as safe and turn off.

Just joined, first time EV owner purchased a Feb 2023 ZS Trophy LR today from Cars2 in Bradford with 5700 on the clock. Dealer serviced for sale so under warranty and recovery.

Stopped to conduct first CCS charge for the experience at Gridserve. Car at ~85%.

Charger would not connect to car. Followed 'troubleshooting', second attempt same outcome. On re-entering car big fault display, a red "Power System Malfunction Warning", saying stop as soon as safe and turn off. It also had a High-voltage Battery Pack Cutoff Warning.

After 5 mins or so it cleared.
Tried the adjacent charger with the same outcome. Went for lunch, and it had cleared on return so completed journey with no problem.

I will try once more at a local CCS before taking to local dealer under warranty.

Posting to start thread for others either to pass their experience if they've seen this and can help, also to start a record for others should this get sorted or even if the car is returned and refunded.

Hello to everyone

 

[Bricktop X PWR]

Have a look here....

Thread 'High-voltage Battery Pack Malfunction Indicator Lamp' High-voltage Battery Pack Malfunction Indicator Lamp

 

[salty]

Neil.

 

[NeilH]

Have a look here....

Thread 'High-voltage Battery Pack Malfunction Indicator Lamp' High-voltage Battery Pack Malfunction Indicator Lamp

Thanks for the reply Bricktop.
I had seen that thread but since theirs happens while driving and mine at connection for charge I didn't join their thread. My thinking was same code symptoms may not have the same cause.

I could have mentioned I'd seen it :/

I'm trying 3 pin charge later (no home charger yet) to see what happens. Then as mentioned BP Pulse tomorrow and off for warranty whatever the outcome. I guess I'm doing a bit of the diagnosis for them.

I'll do my best to get every bit of recorded info about the work and fixes as this progresses to keep the community educated.

At sale they said it had no prior service history (in writing), but seems odd to have occurred only on my first CCS charge attempt

 

[Gadget Geek]

It's also helpful if you can take photos of all the warning displays to show to the technicians at the dealership.

 

[NeilH]

I'd taken a video the second time I tried and it faulted. I've put it in a shared photos folder that I will add to each time it happens and I've shared it to the dealer. What I see, they see.

But guess what at the BP charger today.... worked fine. Type 2 at Lidl worked as well but I expected that since that's the charging they did at the dealer. I'll still be following up with the dealership as I assume there will be fault codes.

I don't want to get stranded with this fault in the future. Also as its just purchased I've emailed with a reminder of the Consumer Rights Act 2015 and my right to reject the goods.

 

[Jto]

I'd taken a video the second time I tried and it faulted. I've put it in a shared photos folder that I will add to each time it happens and I've shared it to the dealer. What I see, they see.

But guess what at the BP charger today.... worked fine. Type 2 at Lidl worked as well but I expected that since that's the charging they did at the dealer. I'll still be following up with the dealership as I assume there will be fault codes.

I don't want to get stranded with this fault in the future. Also as its just purchased I've emailed with a reminder of the Consumer Rights Act 2015 and my right to reject the goods.

Just make sure schedule charging is not turn on.

 

[MG4cherry]

Just make sure schedule charging is not turn on.

Hi
I had the same problem. Aircon failed when in Europe at 30°, battery overheated, couldn't charge with CCS afterwards. Had new Aircon complete, never sorted. I think it damages insulation somewhere and is a serious issue. I got my local dealer (not the vendor) to take it in for another newer one. The new one is perfect.

 

[NeilH]

Just make sure schedule charging is not turn on.

Thanks for checking Jto, but it wasn't.