5

Missing control via dynamicChargerCurrent


M
Mike Pieper

Control via dynamicChargerCurrent works only that I can start/stop charging. When using the app a stop sets dynamicChargerCurrent to 0 and a start sets it to 32 (in my case).

But, when I try to control the charging current it behaves different. Setting dynamicChargerCurrent to 6 starts loading but charger stays in state "Waiting in fully" for some time (seconds to minutes). Then it starts loading with 6A, but after some seconds it is ramping up via 8, 12,16 A up to the chargers maximum. Any change of dynamicChargerCurrent is ignored. Only setting it to 0 stops the charging.
So there is no control of the charging current anymore!

A

Activity Newest / Oldest

Avatar

Stian (VP Software & Services)

Status changed to: Identified

Avatar

Stian (VP Software & Services)

We can confirm the error. We will be working on a fix here soon


H

Han Fish

I am observering exactly the same behaviour.


M

Mike Pieper

Which API message is to be used for "APIs that message the charger that hey you can start charging now, or hey please stop"?
The commands start_charging/stop_charging seems to have to do with authorization only. So it must be resume_charging/pause_charging. On resume_charging is a note on Swagger UI that this will reset dynamicChargerCurrent, so this seems to be what I have seen when started loading via app. Alltogether for me it looked like "pause_charging" is a shortcut for calling the settings endpoint with a charger setting of "dynamicChargerCurrent": 0 and "resume_charging" is a shortcut for the settings endpoint with a current of 32A. At least other wallboxes can be controlled via changing the output current only.

I've tested again an started charging via "resume_charging" and set the dynamicChargerCurrent via the settings endpoint afterwards. But this shows the same behavior. The output current is not influenced by dynamicChargerCurrent. This leads to the question for what dynamicChargerCurrent is useful? If you would omit it completely from the API the behavior wouldn't change ...


M

Mike Pieper

OK, I see that the charging current follows dynamicCircuitCurrentP* of the circuit. But I understood that it is also possible to control an a per charger basis via dynamicChargerCurrent ...


M

Mike Pieper

??? I was talking about "dynamicChargerCurrent" of the REST API endpoint /api/chargers/{id}/settings . I try to limit the charger current to the currently available power from a solar generator. According to the docs this setting can be used for that. Also it gets not stored in EEPROM to avoid wear out.


A

Alek Slater

I'm a bit unsure how yer updating the dynamic charger current, but perhaps if I try to explain how the app functions, maybe it will clarify some things.

So first off, the app never changes or adjusts the dynamic charger current, ever. When you click to start charging, or to stop charging, we call APIs that message the charger that hey you can start charging now, or hey please stop.

So trying to control the dynamic charger current yourself will not help, its only going to change as it ramps things up and down itself.

One thing you could do if you wanted to limit the amount of charge current, is to go to the Power settings screen for the site (not charger), and adjust the "Max charging current" or the "Offline Max Charging current" (offline max is the same as max charging current really, but it just lets u have a different value to be used when the charger thinks its offline).

When you adjust the Max Charging Current, yer actually changing something called the "Max Circuit Current". Its a ceiling or limit you set. Any chargers on this particular site will then never end up with a dynamic charger current above this value.