Sorry, I do not think so. From memory, the firmware stores the lifetime usage so it is not possible for the UI to totally solve the issue. If you do some single phase and some three phase charging, the life time total will be wrong aand there is nothing the UI can do about it.
What I have done is create a flag in the firmware for single/three phase and I am using the Type 1/2 to change that (because Type 1 is irrelevant in Australia and to me).
So a proper solution requires a removal of the #DEFINE in the firmware for three phase and replacement with a flag (which does not need to be in EEPROM). Then ideally creation of an API call to set or clear that flag so the UI can make the change.
Then there would not need to be two firmware downloads for single/three phase and those of us with three phase EVSEs would be served as would those with single phase units. Also the Type 1/2 would still be fine for Europe and the USA.
Yes, if you moved the total kwhr counter to the UI then I think it can be made to work. So I am assuming you would have just a single firmware, behaving as single phase.
Then the UI would multiply by 3 if three phase and accumulate that amount. Plus the eco divert would also work with power *3. If single phase, then works as now.
Yes, I think itās worth doing. It is even simpler than my idea and simple is good!
Yes, when I say UI, I mean the code on the ESP which is under the control of the UI. I assume you will move the total kwhr counter from the EVSE firmware to the ESP32 firmware (which I have loosely been calling the UI).
Hello,
I have been using the new interface with pleasure for about a month.
Itās really a good job.
I have a small problem.
I am in service level 2, with a max of 32 A.
If I charge at 16 A for example, when I unplug the car and plug it back in, even if the set point is 16 A, the terminal charges at 32 A.
Is there a parameter to adjust that I missed?
With the old interface, I did not have this problem.
Reading the thread, I got the impression that there was a patch that fixed this.
I switched to the pre-release (V4.1.8) just now, but itās the same.
I had this problem and fixed it with the āAmpacity Fixā for EVSE firmware detailed earlier in this thread plus keeping up with the latest ESP firmware. Maybe it is now in production EVSE firmware but when I did it, I had to build the EVSE firmware and reload it. I am also on the latest WiFi ESP firmware. I quite often switch the OEVSE between 5kW inverter and mains power so that problem when it happened was a big problem for me if the system tried to take 32A from my inverter. No problem now for weeks.
When you set the charge current on the new UI main window, it sets this charge_current as an āoverrideā claim with auto_release = true.
This means when the session is ended ( when you disconnect your vehicle ) , it will go back to max_current_soft value set in the config / Evse section in ui2.
All settings from the main screen are for a charge session only and will be released to configured default thereafter.
If you have set max current_soft to 16A, and it starts a charge at 32, then itās the auto_ampacity bug from evse firmware. You will have to flash the evse module with latest version, not sure it has been released yet.
But, good news, thereās also a mitigation hack implemented now in latest builds ( strangely if you have tested with 4.1.8 it should already be there )
Hi Guillaume, for the 3 phase mods, are you going to make it so that you can use a standard 1ph EVSE firmware and then do the different calculations depending upon the setting of the 3ph switch or are you going to assume 3ph EVSE firmware where the firmware is multiplying by 3?
As a 3ph owner, I think I would prefer to go back to a standard 1ph EVSE firmware (so get rid of the 3ph builds) and only then need one EVSE firmware. Iām only too happy to re-program my EVSE firmware. But maybe there will be people who do not want to do thatā¦
So perhaps it is going to be a big compatibility argumentā¦
Thatās the plan yes.
Anyway three-phase firmware is only calculating kWh by factoring X3 , so if everything is brought back the the wifi fw, they wonāt need to update the Evse fw.
Thanks @doggy and @Guillaume_S for your answers.
I have just tested, if I set max current_soft to 16 A, the charging station starts charging at 16 A, and not 32 A.
I thought the main screen settings were a setpoint for all loads, not just the current load.
Itās annoying for me, because I have solar panels, and 32 A is way too much for them :).
If I understand correctly, all charging starts at max current_soft, and the set point is only there to adapt the current during a charge?
I donāt understand your issue. I have 4.7kw of solar panels, so max 20amps, but that is extremely rare. I can also switch to LFP battery bank and 5kW inverter (max 20A). In practice, there is never more than 16A that I can put into either of my EVs. So I leave the main switch set at 16A and normally have everything else set for Eco Divert and Auto. Then if I switch over to batteries I cannot accidentally exceed the inverter max. I could set the main switch to 20A and still be safe.
If I am travelling and plug into a 22kW three phase outlet, or 32A single phase, I move the main switch to 32A and select what I actually want on the secondary amps switch in manual mode.
Also if I want to fully charge fast the night before a long trip, I can set the timers and max amps to 32A for my Zoe or let the Tesla handle it if I am charging that car.
Yes thatās it. Charge current from main screen is dedicated to charge session. It canāt goes higher than , charge current from config ( max_current_soft ) which is the limit defined for all sessions.
Any charge will always starts using max available current.
If you want to prevent it to starts full amps when using solar you should consider using the divert mode ( self production in new UI )
Iāve āfinishedā somehow the new EnergyMeter class.
It nows publish: session_energy ( wh ) , and in kwh: total_energy, total_day, total_week, total_month & total_year
EnergyMeter nows factorize by 3 the kwh when threephase flag is set on wifi firmware.
OpenEvse firmware should be standard non threephase one ( Iāll probably later add a switch to allow keeping the old installed threephase fw )
It will import old counter in new one when migrating.
edit: I should have made another topic, you can answer me on pm for reporting this
Good idea about a future switch for people with 3ph firmware who do not have the possibility or knowledge to flash the EVSE firmware.
Iāve installed it but I need to reflash the EVSE firmware so Iāll PM you with how it goes. Might be a day or two because I have several busy days starting tomorrow.
By the way, minor spelling error:
āFirmware upgrade successfullā should be <successful>
Cheers,
Dave
[Edited to show the spelling correction - Moderator (RW)]
You can probably make a good guess from the EVSE firmware version number, it should be postfixed with .3P at least for the official EmonEVSE 3phase releases
There wonāt need any flag for this, it is compatible with booth fw. I had forgotten that the IS_THREEPHASE on evse is only factorising the kwh accumulated, so we donāt care at all.
