Firmware 305 (haven't yet updated to 307 since BMS 3015 has voltage issues ?)
Just experimenting with the lower SoC limits on timed-discharge slots. I had stumbled on what I thought was a neat trick to implement a pause-discharge by setting the SoC limit to 100%. But trying to deploy it in anger a couple of nights ago, it didn't seem to work. Turns out that, apparently, the limit is only honoured if the end time is before midnight.
Eg with discharge time set from 20:00 to 23:59, it discharges as long as SoC is above the lower limit, but if I raise the lower limit to 100%, it stops discharging and pauses the battery (therefore importing from grid). So far so good - exactly as I'd intended. Now I change end time to 00:01 - it now discharges regardless of whether the SoC is above or below the lower limit set. (So it does at least realise that I wanted the timer to span midnight.) I can probably work around it by using two slots: one running until 23:59 and the other from 00:00.
Then separately, I realised there's a complication with charging from grid. There's one overall AC charge limit (shown at the top of the remote-control page), and then a separate one associated with charging-slot #1. (Settings 71 and 101 in the API.) When configuring AC charging from the app, it uses charging slot #1 for start and end time, but the "master" setting for the limit.
Unfortunately, it seems to be the slot-1 limit that the inverter actually honours. I'm rather surprised I'd not noticed this before. But I have a script that calculates a suitable charging power to take the whole offpeak period to reach the requested limit - I guess this works sufficiently well that the battery ends up at the SoC I'd asked for, despite the slot-1 limit being wrong. I think I had been assuming that when they added they extra charging slots, they had repurposed the single charge limit as the #1 limit (just as the single charging slot previously became slot #1, which is why the set is not contigious in the collection of settings).
Bit annoying since the app makes it very convenient to adjust the charge limit (depending on solar forecast).
I wonder if anyone else could verify these findings ?
(Just noticed that in the list of settings you get from the API, it misnumbers slot #1 as slot #2 -
settings:
17 Enable AC Charge Upper % Limit : Value must be either true or false
24 Enable Eco Mode : Value must be either true or false
28 AC Charge 2 Start Time : Value format should be HH:mm. Use correct time range for hour and minutes
29 AC Charge 2 End Time : Value format should be HH:mm. Use correct time range for hour and minutes
41 DC Discharge 2 Start Time : Value format should be HH:mm. Use correct time range for hour and minutes
42 DC Discharge 2 End Time : Value format should be HH:mm. Use correct time range for hour and minutes
...
77 AC Charge Upper % Limit : Value must be between 0 and 100
83 Restart Inverter : Value can only be 100
96 Pause Battery : Value must be one of: 0, 1, 2, 3 (Not Paused, Pause Charge, Pause Discharge, Pause Charge & Discharge)
101 AC Charge 1 Upper SOC % Limit : Value must be between 0 and 100
102 AC Charge 2 Start Time : Value format should be HH:mm. Use correct time range for hour and minutes
103 AC Charge 2 End Time : Value format should be HH:mm. Use correct time range for hour and minutes
104 AC Charge 2 Upper SOC % Limit : Value must be between 0 and 100
105 AC Charge 3 Start Time : Value format should be HH:mm. Use correct time range for hour and minutes
106 AC Charge 3 End Time : Value format should be HH:mm. Use correct time range for hour and minutes
107 AC Charge 3 Upper SOC % Limit : Value must be between 0 and 100I'd guess that 28 and 29 are slot #1, not slot #2. Question is why they introduced 101, rather than renaming 77. I do now vaguely recall this being mentioned before.
Looking back, I now see that there are lots of threads about the inverter ignoring the AC upper charge limit. I wonder if it's down to this.