Pilot current drops to 6A for some max current settings

[jdunphy2]

Firmware 7.1.3, openevse_wifi_v1 just upgraded to 4.1.7
Some settings (32A, 33A) of the max current pulldown are limiting the maximum current to 6A, while others (31A, 34A) are working as expected. When the limiting occurrs, the debug window shows {"pilot":6}

[glynhudson]

Please could you test the least FW version and post a screenshot / video illustrating the issue?

[fhteagle]

I can partially confirm this on a unit with 4.1.9 / 8.2.2 firmwares. Right after selection of a charge_current setting, my Tesla Model Y will start to throttle up charging, but after 5-25 seconds, the Tesla goes back down to ~6 amps actual intake. The Tesla app does not refresh fast enough to show the increased amp limit before it goes back down, but the app is very clearly showing only 6 amps offered to the car.

Unlike the OP, though, /status endpoint always had "pilot: 16" for me, even when the Tesla was pulled down to 6A.

Trying the nightly GUI V2 build to see if the behavior remains there as well.

[fhteagle]

I do not think I have seen this again since upgrade to 4.2.1 on the unit that serves the Tesla. Can you confirm its fixed, @jdunphy2 ?

[olivpod]

Hello

I have this same trouble with my EVSE:

OpenEVSE | 8.2.3
OpenEVSEWIFI | V4.2.2 on node MCU32s

The charge limit sutck at 6A, if i change the mesured curent on the EVSE page, the curent grow up for 2 ou 3 seconde and immediatly down to 6A.

For "solve" i need to reboot my EVSE, and randomly.. this work and stay stable at 32 A...

a+

[olivpod]

vidéo for this bug
https://youtu.be/7pkXfT_V0p4

olivier

[KipK]

What openevse firmware build is installed ( openevse, openevse_eu , emonevse, ? )

[olivpod]

hello

For the wifi card :

For the EVSE:
openevse 8.2.3 Pre-release

Olivier

[KipK]

I mean what build version of openevse module ? Is it standard tethered openevse or untethered one with T2 socket like emonevse ?

There's different build version ( not the version number ): https://github.com/OpenEVSE/open_evse/releases/tag/8.2.3
look at the file names

[olivpod]

it's a standard tethered openevse

[KipK]

but what fw build ( file name ) you've loaded on it ?
Are you in USA or Europe, somewhere else ? If in europe, should load europe fw as US version level mode is dedicated to split phase setup . other part of the world should be always fored to level 2

Check you are set to level 2 and not level 1, or auto ( for europe, it should always be level 2 )

[olivpod]

The file name is openevse.hex ( not Emonevse or openevse_EU )
I'm in europe ( france ) and in setting, i correctly set Level 2 ( not auto, not level 1 )

[KipK]

Can you put the Europe version on it instead, and retest? As US build has auto-service level + different over current settings.

[olivpod]

Unfortunately no, I also tried the "openevse_EU" version but my AC driven relay does not work (state never change) with the "openevse_EU" firmware

[KipK]

I would investigate that first as it should work

Also relay only switch when a car is plugged in.

[olivpod]

Yes of course, the relay does not change state when the car is connected and a recharge is required by evse with openevse_EU firmware

[KipK]

You should find why It doesn't work with eu version. There's no reason but something is wrong in your wiring perhaps, as it also fail somehow differently with us fw too.

Look at the build flag for eu fw, there's no big difference but the over_current threshold and default to level 2. https://github.com/OpenEVSE/open_evse/blob/master/platformio.ini

Have you checked there's no error displayed on the monitoring section? ( Also with eu fw to see why it doesn't switch )

[olivpod]

hello

I probalby found my problem for the pilot current ! My wiring is ok, the SW too... but not my EVSE AC/DC converter.

The +12VDC of my converter is not suffisant in term of current and don't support the new current need of the ESP32 wifi card.
+12VDC is not monitored by EVSE and
obviously, no error are displayed in monitoring section.

I have plug a new AC/DC converter just for the ESP 32 and the bug is probalby fix.

I bench this new parameter for few day and come back for confirm..

[monfiston]

GOOD MORNING
I also have the same problem with my tesla I now power my esp32 with a 1A usb power supply, it works better, but I still have problems, the current is not stable
have you solved your pb?

[olivpod]

hello

I probalby found my problem for the pilot current ! My wiring is ok, the SW too... but not my EVSE AC/DC converter.

The +12VDC of my converter is not suffisant in term of current and don't support the new current need of the ESP32 wifi card. +12VDC is not monitored by EVSE and obviously, no error are displayed in monitoring section.

I have plug a new AC/DC converter just for the ESP 32 and the bug is probalby fix.

I bench this new parameter for few day and come back for confirm..

hello

For me, the additional ACDC converter doesn't fully solve the trouble.
Sometime without any reason, and only at the beginning of the recharge the current stuck at 6amp.
I only need to reboot the wifi module for "unsticking" the current value.

Olivier

[olivpod]

Hello, after a new update of my scenario on Jeedom.
I now start the recharge with 8amp value.
Since 3 weeks, I do not need to reboot my evse for my 2 ev.