POWER_NODE_ENERGY_SHARING
Share energy between nodes in a power-node group.
| Mode string | POWER_NODE_ENERGY_SHARING (EMS_OP_POWER_NODE_ENERGY_SHARING) |
| Dispatcher | ems_main.py → dispatch stub (logs, does not actuate) |
| Config block | functions.Power_Node_Energy_Sharing |
| Status | Registered, awaiting specification |
Current state
Registered and selectable. Reaches an explicit dispatch branch which logs:
[EMS] cycle=<n> mode=POWER_NODE_ENERGY_SHARING has no control strategy yet -> no action (see docs/modes/)
No power setpoint is written. The plant stays at its last setpoint.
Why it is a stub
You indicated the details would follow. The mode is registered now so that it is selectable and the plumbing (config block, dispatch branch, documentation) exists and is testable, without inventing control behaviour that would write to a live BESS.
Configuration
functions.Power_Node_Energy_Sharing — scaffolding only; no key is read by any code yet.
| Key | Live value | Meaning |
|---|---|---|
enabled |
false |
Intended master switch. |
spec_status |
awaiting_specification |
Marks the block as a placeholder. |
priority_rule |
power_node_over_local_dispatch |
Intended precedence. |
What I need to implement it
- Topology — what a "power node" is here: a group of sites, a set of BESS units behind one POI, or a logical cluster. Where is the group defined?
- The sharing objective — equal SOC across nodes, proportional-to-capacity, priority ordering, or a target per node?
- The signal path — how nodes see each other: a shared API, MQTT, file exchange, the blade backend, or a coordinator node?
- Constraints — per-node SOC limits, connection capacity, whether a node may be taken over remotely.
- Conflict handling — what happens when a node is also running a local mode such as PEAK_SHAVING.
Related
emsConfig/pcs_register.jsondocuments per-PCS registers, which is the level a node-level allocator would eventually write to.