Block EMS OptimizerThis operating element belongs to a battery storage that is operated optimally according to electricity price, grid tariff and forecast. It shows how energy is flowing, what electricity costs and earns, and the schedule of the next 24 hours in quarter hours. The charts show past generation, consumption, grid import, costs and revenues. All settings of the block – storage, prices, grid tariff, optimization, forecast and controller – are made here.
The tile is laid out like the Block energy manager:
Moving dots on the connecting lines show where the energy is currently flowing. Tapping a field opens its chart. The battery has two areas: the upper part opens discharging, the lower part charging. Import and export open costs and revenues in euros. The three dots and any free area open the schedule; from there the computed data and the settings can be reached. -.-- instead of a number means there is no value. Small tiles omit the corners.
In the previous design the fields are boxes with lines between them, the setpoints are shown in brackets below grid and battery, and instead of the three dots a gear at the bottom right opens the schedule.
In landscape 12 hours are shown side by side, in portrait 6. The schedule is recomputed every quarter hour. Without a connection to the controller or as long as no schedule has been computed, “No schedule available” appears. If the price source is the reason, it is stated below, e.g. “Price source ENTSO: block missing in the project” or “Price source Portal: no connection to the portal”. In the computed data the row Price source shows the selected source or the same note.
The charts show the block's recording in quarter hours: production, grid (import and export with the state of charge), consumption, charging and discharging as well as costs and revenues in euros. The time range is chosen via the time range symbol; the bin there deletes, after a confirmation, the entire recording of this block. The amounts in euros are calculated continuously with the price of the respective quarter hour.
In the new design, the chart has a gear with the entries Time range (the same selection as the button below) and Export as CSV saves the displayed data as a CSV file, for example for evaluation in Excel: the selected time range, one column per line. The share symbol in the title bar passes on the chart as a picture, just as it is shown: on a PC the picture is then in the clipboard and can also be saved as a PNG file, on Android and iOS the share menu of the device opens.
Changed values are transferred to the controller only with Save; the schedule is then recomputed immediately.
| Operation | |
| Operating mode | Automatic follows the schedule, Self-consumption keeps the grid connection point at 0, Manual sets the battery power by hand, Off stops the storage. |
| Setpoint manual | Power in kW for manual mode, positive = charging. |
| Schedule | Own optimization or Platform. With platform the setpoint per quarter hour comes from the energy platform (block MQTT EMS platform); without a setpoint the block runs self-consumption. |
| Storage | |
| Battery capacity, charge and discharge power maximum | Storage data in kWh and kW. |
| State of charge minimum / maximum | Range in which the storage is operated. |
| State of charge end | Minimum state of charge at the end of the 24 hours. |
| Efficiency charging / discharging | Losses when charging and discharging. |
| Ramp | Largest change of battery power from one quarter hour to the next. 0 = no limit. |
| Grid | |
| Margin grid limits | The controller keeps this margin to the block's grid import max. and export max. |
| Electricity price | |
| Import markup, export discount | Import = spot price + markup, export = spot price − discount. |
| Fixed import / export price | Only with the price source Fixed prices; then instead of markup and discount. The price source itself is selected at the block Block EMS optimizer, not here. |
| Grid tariff | |
| Grid energy charge, energy charge low | Grid usage charge per kWh imported. |
| Low-price window | On: in summer (April to September) 10:00 to 16:00, in winter 23:00 to 5:00 the low energy charge applies. |
| Demand charge 1 and 2, tier | Demand charge in euros per kW and month (annual value ÷ 12): demand charge 1 up to the tier, demand charge 2 above. |
| Levies | Further levies per kWh imported. |
| Optimization | |
| Demand charge | Off: the monthly peak plays no role for the schedule. |
| Plan curtailment | The PV may be throttled in the schedule, for example at negative prices. Only effective with the parameter PV curtailable. |
| Cycle costs | Cost per kWh flowing into or out of the storage. Prevents cycling at small price differences. |
| Curtailment cost | Valuation of each curtailed kWh. |
| Residual value storage, fixed residual value | Value of one kWh in the storage at the end of the 24 hours. Automatic: mean export price times discharge efficiency. |
| Weight import, weight export | Additional valuation per kWh, for example to prefer self-consumption. |
| Penalty grid limit, penalty schedule | High costs so that grid limits and the fixed value of the current quarter hour are violated only in an emergency. |
| Forecast | |
| Learning window | Number of days the forecast learns from (1 to 60). |
| PV from irradiance | Below this the PV forecast is 0. |
| Holidays country, region | Holidays are treated like weekends. Region as a number as in the block Holidays, 0 = nationwide. |
| Irradiance | Source of the measured irradiance for learning: Automatic (input, otherwise Open-Meteo), input only or Open-Meteo only. |
| Controller | |
| Gain P, gain I | Gains of the PI controller on the remaining energy of the quarter hour. |
| Minimum remaining time | Towards the end of the quarter hour at least this remaining time is assumed, so the controller does not overshoot. |
| Diagnostics | |
| Diagnostics | Writes diagnostic messages to the log and stores the schedule as a CSV file after each run – like the block parameter Diagnostics. |
The operating element is linked to a block Block EMS Optimizer: right-click the operating element and select the block. The displayed measurements come from the addresses of the block's inputs – for the fields to show values, these inputs must be assigned addresses.