The Reality of Plant Connectivity
Most solar plants run on bonded 4G or low-grade leased lines. Connectivity drops happen weekly. An ingestion stack that assumes always-on connectivity will quietly lose hours of generation data — and the analytics that depends on it.
Enlyra's Edge Architecture
The Enlyra Edge Device family (MCR + ICR) and the Enlyra PC Client share a common contract:
- MQTT transport: Devices publish to
site/{site_id}/devices/{device_id}/telemetrywith topic ACLs and per-device JWT authentication. - MCR/ICR hierarchy: ICRs collect Modbus RTU data and forward to the MCR, which aggregates and ships every device as a single JSON message over MQTT.
- Offline replay: When connectivity drops, the PC Client persists telemetry to a local store. On reconnect, it replays at a configurable rate (default 50 msg/sec) — bandwidth-friendly, never bursty.
- Server-side deduplication: Replays often overlap with live streams. The ingestion service deduplicates on (device_id, timestamp) so the historical record stays clean.
Bidirectional Config Sync
The other half of edge architecture is configuration. Modbus register maps, parameter mappings and topology definitions need to stay aligned between the platform and the field. Enlyra's config sync engine pushes or pulls configuration from either side, with version tracking and explicit conflict resolution. First-time device registration triggers a full sync from the server.
What Operators Get
The result is a fleet that stays fully observable through bad networks, brownouts and rolling outages — and a control plane where Modbus updates happen from the office, not the substation.