Charge station fault

[mkhuffman]

I have almost the same error as mentioned except that it is happening only 10% of the time after completing a L2 charge and I use the Emporia charger and I get a notice of the fault in both the car and the FordPass app.

This is my office charger where I charge every weekday and about once every 2 weeks I get this fault. I have the MME set to charge to 80% at this location.

I've had the Emporia for about 1 years, 8 months. This fault only started happening maybe 7 months ago. The Emporia is supposed to automatically update its firmware just like the MME so I'm not sure I can correlate it with a specific change, but my mind has it that it started happening after some MME updates that came out around August of last year.

It mostly doesn't bother me since it always happens after the charge is complete. But every once in a while I'll want to charge a little more (e.g. 85%) after it reaches my target of 80% and if faulted then I must unplug and plug back in before it will allow the additional charging to occur.

I have mentioned this on the forums elsewhere.

Same thing happens to me. I do not have 6.6.0 yet, so per Lee, this is something that will get fixed when we get that OTA.

Sponsored

 

[HoosierMME]

I’m up to 6.14, and have most of the charging updates. I’m concerned that if/when I contact the Grizl-e folks, they’ll be like, “sounds like it’s charging your car, so nothing wrong. “

 

[Pmullin7]

I’m up to 6.14, and have most of the charging updates. I’m concerned that if/when I contact the Grizl-e folks, they’ll be like, “sounds like it’s charging your car, so nothing wrong. “

Ford disagrees. They told me that chargers that fault shouldn't be used.

I never made any progress with support, so after 2 months of back and forth, I replaced it with a Tesla universal.

Magically, and in spite of their insistence that it must be my car, it works fine.

So I no longer recommend Grizzl-e when asked. Their product works well until you need support, and then you're rollin the dice. Some folks get quick results. Some of us get the run around.

 

[hack-e]

I have all the 6.x updates through 6.14.0 except I never got the notorious 6.13.0. However, I got what people said was the replacement for 6.13.0, the CMR-FX2.

Edit:
Correction: they said 24-PU0102-SVD-FX2 was said to be the fix for 6.13.0.

 

[Mach-Lee]

Same thing happens to me. I do not have 6.6.0 yet, so per Lee, this is something that will get fixed when we get that OTA.

I think the way some of the EVSEs terminate charge is not fully in compliance with J1772 protocol which can cause errors. The correct way to do it is to switch off the 1 kHz pilot signal but leave the +12V signal active to indicate standby. But I think some EVSEs shut the pilot off completely or use an invalid duty cycle setting which causes faults.

Another issue I see is the EVSE doesn't switch off power immediately when requested for whatever reason. When the car drops down to status B the voltage needs to shut off within about one second. That may not happen on time, or the sequencing with the pilot signal may not be correct. Could be sticking contactor too.

Any decent EVSE will have integrity monitoring to verify the power has indeed been switched off when the contacts open, but IDK if Grizzl-E will detect that or not. They have some questionable software and engineering sometimes.

So don't rule out the EVSE as the cause.

Sponsored