Getting Started with Layer 4 Coordination
Set up command dispatch and asset coordination in minutes. This guide walks you through converting a Layer 3 optimization schedule into real device commands.Installation
Quick Examples
Dispatch an EV Charging Schedule
End-to-end: optimize with Layer 3, then dispatch with Layer 4.Battery Dispatch from Peak Shaving
Configuration Reference
CoordinatorConfig
| Parameter | Default | Description |
|---|---|---|
site_id | required | Qubit site identifier (sit_*) |
dispatch_interval_seconds | 5.0 | Seconds between dispatch cycles |
command_timeout_seconds | 30.0 | Default command timeout |
max_retries | 3 | Max retries for failed commands |
retry_backoff_factor | 2.0 | Exponential backoff multiplier |
stale_state_seconds | 60.0 | Asset state staleness threshold |
Command Defaults
| Parameter | Default | Description |
|---|---|---|
max_retries | 3 | Retries before marking FAILED |
timeout_seconds | 30.0 | Seconds before TIMED_OUT |
priority | 1 | 1=normal, higher=more urgent |
Next Steps
Dispatch Engine
Deep dive into command lifecycle and change detection
State Machines
EV charger and battery state machine details
Protocol Adapters
OCPP, Modbus, and writing custom adapters
Layer 3 Optimization
Generate the schedules that Layer 4 dispatches
You’re now ready to dispatch optimization schedules to real energy assets! Layer 4 coordinates the execution of Layer 3’s intelligence.