OpenEVSE state flow chart and testing

Question

OpenEVSE state flow chart and testing

jeremypoulter opened this issue 2 years ago · comments

Looking at a test procedure for OpenEVSE and found this flow chart in the OpenEVSE knowledge base. @lincomatic / @chris1howell can you confirm this is still valid as I think a good place to start would be to validate that the flow chart is followed.

Is there any other existing process and/or documents describing the test procedure?

Jeremy Poulter commented 2 years ago

Thanks

Jeremy Poulter · Answer 1 · Thu Jan 20 2022 07:24:22 GMT+0800 (China Standard Time)

Also assuming the flow chart is correct, why is the ground check dependant on the auto service level? I would assume that this check is disabled when the Auto service level is disabled as with the EU builds (@glynhudson)?

lincomatic · Answer 2 · Thu Jan 20 2022 08:29:43 GMT+0800 (China Standard Time)

The ground check is done whenever the relay is closed, so it's monitored continuously when the EV is charging. When the new CGMI hardware is released, and CGMI is enabled in the firmware, it will be checked continuously, even when the EV isn't charging.

lincomatic · Answer 3 · Thu Jan 20 2022 08:32:22 GMT+0800 (China Standard Time)

The only thing I see missing in your flowchart is that if the EV is plugged in during POST, we can't do auto service level detection, so it's done at the beginning of the transition into STATE C, and the max current is adjusted on the fly.

Jeremy Poulter · Answer 4 · Sat Jan 22 2022 05:31:10 GMT+0800 (China Standard Time)

Thanks for the info

lincomatic · Answer 5 · Sun Feb 06 2022 12:21:54 GMT+0800 (China Standard Time)

I forgot to add 2 more things.:

GFCI self test is performed every time a charging is requested (this is why there is always a delay before the contacts close). If it fails, it is a hard fault.
any fault which occurs within 2sec of the start of charging is treated as a hard fault
The difference between a hard fault and a soft fault is that soft faults can auto reset and hard faults require user intervention (usually unplugging the EV or rebooting the EVSE)