Openevse not holding max current value

MikeC · 15 March 2021 03:03

Hi team,

Im having trouble with my new openevse not holding the max current value and occasionally reverting to 32a. Im running the latest 3.3.2 wifi firmware.
Ive downloaded the firmware to compile with hardcoded max current but am struggling to find my way around the code and unsure on board type etc. Is there any info out there how To do this?

Thanks, Mike.

TrystanLea · 15 March 2021 09:40

@glyn.hudson any idea about this one? something I’ve experienced as well I think. Seems to drop down to 20A limit? Im running 2.9.1

MikeC · 15 March 2021 21:53

Another weird thing, not sure what the numbers represent on the display? Ive tried a factory reset but the problem persists. 165:165:85

glyn.hudson · 17 March 2021 14:26

Ah, your unit has the latest version of the LCD display without a physical real-time-clock. You should use WiFi V4 firmware. This should have been loaded before the unit was shipped. You will have an OpenEVSE WiFi V1 Module WiFi module. You should upload this firmware.bin via the web interface: https://github.com/OpenEVSE/ESP32_WiFi_V4.x/releases/download/V4.0.0.BETA/firmware.bin

If you want to set a hard limit for max current that can never be exceeded e.g 20A you should use this RAPI command to set a hard limit for your unit. This command can only be issues once and cannot be undone:

$SC 20 M

For explanation of this command see the RAPI documentation:

github.com

openenergymonitor/open_evse/blob/master/firmware/open_evse/rapi_proc.h#L170

    
      
           - temporarily disables delay timer until EV disconnected or limit reached
          response:
           $OK - accepted
           $NK - invalid EVSE state
          S4 0|1 - set auth lock (needs AUTH_LOCK defined and AUTH_LOCK_REG undefined)
            0 = unlocked
            1 = locked - EVSE won't charge until unlocked
            when auth lock is on, will not transition to State C and a lock icon is
            displayed in States A & B.
          SA currentscalefactor currentoffset - set ammeter settings
          SC amps [V|M]- set current capacity
          response:
            if amps < minimum current capacity, will set to minimum and return $NK ampsset
            if amps > maximum current capacity, will set to maximum and return $NK ampsset
            if in over temperature status, raising current capacity will fail and return $NK ampsset
            otherwise return $OK ampsset
            ampsset: the resultant current capacity
            default action is to save new current capacity to EEPROM for the currently active service level.
            if V is specified, then new current capacity is volatile, and will be
              reset to previous value at next reboot
            if M is specified, sets maximum L2 current capacity for the unit and writes

You can send a rapi command via the web interface once advanced developer mode is enabled. You should receive an OK response.

MikeC · 18 March 2021 18:34

Thanks Glyn,

Ive updated to the wifi 4.0.0 and ease 7.1.3 and everything working as expected now!

Thanks very much for taking the time to help me!

Regards,

Mike.