Cheap Grid Charging not "fast-charging"

[dyde121]

I have just started testing the "Cheap Grid Charging" feature.
My expectation is that in this mode, it should use the Max current (30A).

However looking at the logs from last night, I can see that is was charging at only 5A, which is the Min. Current configured.
EVCC was set to "Solar" mode at the time, and I can see in energy logs that it started and stopped charging at the correct times, however only at 5A charge rate, not the 30A charge rate I get if manually choosing "fast" charge at any other time.

What do I need to change?

[mfuchs1984]

What kind of charger and car are you using? Is there a logfile?

[FrankvdAa]

As I need to scan the RFID tage, before charging starts, I reckon the charger would be awake, right?

I'm using Modbus TCP to connect EVCC to my Peblar and yesterday evening I've build an integration with Node Red on Modbus, so next time this happens I should be able to see what's in the register.

@dyde121 how do you wake up the car? My Volvo has an API, but that requires weekly, manual intervention to have a valid token, which is not really handy.

[dyde121]

If your charge current is controlled by the charge station, I wouldn’t expect you to have the same issue.
Tesla is different in that the car controls it, I am using the Tesla Bluetooth integration

[FrankvdAa]

Thanks, I just checked modbus holding register 40000 (ChargeCurrentLimit) and this seems to be set to 0 on the Peblar. As the line 'set charge current limit' appears in the logs for the last time at 14th of December at 9.54h (start of last charge session), where is sets it to 16A.

Is this to be expected? Or is this reset to 0 when the Peblar isn't charging?

[mfuchs1984]

Did you check 40001 as well? It's in two registers since it's a 32 bit value.

[mfuchs1984]

Had a look, evcc sets it to 0 when stopping charging.

[FrankvdAa]

Yes, requested two registers uint32, but it was expected to be 0 by now then. Will keep an eye on it next time.