Engineering design example
Hybrid mini-grid controls
A controls example for a PV, battery, generator, and load system, covering operating states, permissives, interlocks, alarms, HMI structure, fail-safe responses, and testing.
Control philosophy example · Representative ratings, operating modes, and interfaces.
Operating states
Define system behaviour before writing control logic
Control logic should begin with a clear operating philosophy. This state model defines normal operation, generator support, battery protection, and fault handling.
Control philosophy
- Prioritise available PV while bus conditions, equipment limits, and battery constraints remain healthy.
- These are operating modes, not a fixed sequence. Fault lockout overrides dispatch; disabled dispatch selects standby.
- A connected generator takes dispatch precedence. Otherwise PV covers demand or the battery supplies the deficit within its limits.
- Generator start, warm-up, connection, unloading, and cool-down are separate equipment phases. An unsupported deficit requires the approved load-shed or standby response.
- Form generator requests from enabled, validated SOC, load, schedule, or approved manual conditions; apply timing and hysteresis to each relevant request.
- Prevent unsynchronised closure, unintended backfeed, and generator/BESS paralleling unless the approved design permits it.
- Log every automatic state change for commissioning review.
Automation logic
Interlocks, alarms, and I/O mapping
Generator request and sequence
- Request: enabled low-SOC condition OR load-support request OR scheduled exercise OR approved manual request. The model’s 180-second delay applies only to the low-SOC branch.
- Start readiness: request AND generator available/remote AND required auxiliaries healthy AND no emergency stop, protection trip, or start inhibit; breaker proven open for this example.
- Crank with bounded attempts, prove running, then complete warm-up. A failure to start raises a fault and follows the approved retry rule.
- Connect only on a permitted connection request, valid speed/voltage/frequency, and approved synchronisation or dead-bus conditions with interlocks and breaker proof.
- Stop only after request-clear and minimum-run conditions, replacement-source readiness, unloading, breaker opening, and cool-down. Scheduled exercise may remain unloaded.
I/O map snapshot
Alarm matrix
Operator screens
HMI structure for operations and fault review
The HMI shows the active source, the reason for a transition, and the conditions that must be cleared before reset.
Mini-grid dashboard concept
PV inverter Battery
Bidirectional PCS Generator
Genset breaker
AC-coupled concept. Site design defines the grid-forming source, earthing, switching and permitted source combinations.
Screen list
- Overview screen with source status, load, SOC, generator state, and alarms.
- Energy screen with PV, battery, generator, load, and daily totals.
- Alarm screen with severity, timestamp, acknowledgement, and operator note.
- Settings screen with protected thresholds and commissioning records.
Commissioning handover
Test requirements before site commissioning
Factory test plan
Simulate SOC, PV availability, breaker status, generator readiness, and communication loss.
Site acceptance test
Verify state transitions, interlocks, alarms, HMI values, manual reset, and event logging.
Operator handover
Provide alarm response notes, reset rules, operating limits, and support escalation path.
Next step
Discuss a similar controls project
A project controls package is developed from the approved operating philosophy, equipment interfaces, protection scheme, and test plan.