GeneratorFleet reference stack

Bench test

Pending bench test — controller Modbus maps vary by firmware; Validation status.

Fleet dashboard for diesel genset monitoring. Device type: generator.

The field device is usually a genset controller (not a single probe). Telemetry keys match common controller Modbus maps.

Telemetry contract

Key	Meaning
`gen_run_state`	String enum e.g. `RUNNING`, `STOPPED`, `STANDBY`
`gen_mode`	`AUTO` / `MANUAL`
`gen_on_load`	Boolean — on load
`gen_kw`, `gen_kva`	Output power
`gen_pf`, `gen_hz`, `gen_load_pct`	Power factor, frequency, load %
`gen_v_l1`…`gen_v_l3`, `gen_i_l1`…`gen_i_l3`	Phase voltages / currents
`gen_rpm`, `gen_oil_pressure`, `gen_coolant_temp`	Engine
`gen_fuel_level_pct`, `gen_battery_v`	Fuel day tank / starter battery
`gen_run_hours`, `gen_alarm_count`	Maintenance counters

Sample generators use bands aligned with typical standby diesel (e.g. 50 Hz, oil pressure bar, coolant °C).

Reference hardware (pending bench test)

Item	Detail
Controller	Deep Sea Electronics DSE7320 MKII (or DSE73xx family) with Modbus enabled
Datasheet	DSE Modbus register map PDF for your firmware revision — map registers to keys above
Auxiliary	CTs / VR inputs per controller install manual; qualified genset electrician

Status: Pending bench test — register addresses vary by DSE firmware; always use the map for your exact model/revision.

Alternates (same approach): ComAp InteliGen, Lovato RGK — different Modbus maps; create a matching child map or P2 edge translator.

Connectivity options

Profile	Edge	Link	Status
P2	ESP32 / industrial GW at panel	WiFi or Ethernet	Pending bench test
P3	Modbus TCP/RTU via serial server	Ethernet / 4G tunnel	Pending bench test
P1	4G DTU on RS485 to controller	4G	Pending bench test

Avoid assuming cloud Modbus polling interval exceeds controller minimum scan time in manual.

Wiring — controller on RS485 (P1 / P2 / P3)

mermaid

flowchart TB
  subgraph Genset_panel
    ENG[Diesel engine]
    ALT[Alternator]
    CTRL[DSE controller RS485]
    CT[CTs / VR]
  end
  EDGE[DTU ESP32 or serial server]
  AC[Autoconnecto]
  ENG --- CTRL
  ALT --- CTRL
  CT --- CTRL
  CTRL -->|RS485 A/B| EDGE
  EDGE <-->|MQTT or TCP| AC

Safety
Mains	Controller wiring by licensed installer only
RS485	Isolated transceiver recommended near noisy contactors
Fuel	Day-tank level may be separate 4–20 mA input mapped to `gen_fuel_level_pct`

Mapping workflow

Download Modbus map for exact controller model.
For each Solution key, record register, datatype, scale (document in child device Modbus table or P2 firmware).
Bench-test: compare controller front-panel kW/Hz with Autoconnecto telemetry.
Set alarms from operator limits (oil pressure, coolant, overspeed) per manual.

Autoconnecto checklist

[ ] Create gateway + child devices linked with parentDeviceId (Sample On demos this topology)
[ ] Child device type generator (one device per genset)
[ ] Telemetry on the child; string/boolean keys use correct JSON types
[ ] Optional hub health: publish gateway.heartbeat on the gateway token
[ ] Gateway shows Active from hub heartbeat and/or any active child
[ ] Do not expose breaker control on fleet home — control stays on detail or separate state if added later

GeneratorFleet reference stack ​

Telemetry contract ​

Reference hardware (pending bench test) ​

Connectivity options ​

Wiring — controller on RS485 (P1 / P2 / P3) ​

Mapping workflow ​

Autoconnecto checklist ​

Related ​