verified connector library

SmartGen HGM6100N genset controller

Register map(s) for this device, each at the trust rung it earned. Addresses are 0-based as on the wire. Word order and scaling are confirmed at the hardware-verified rung and at no rung below it.

interop-verified

Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.

pointaddress (0-based)typescaleunit
engine_speed0U161
engine_temperature1I161
engine_oil_pressure2U161
fuel_level3U161
battery_voltage4U160.1
charger_voltage5U160.1
generator_frequency6U160.1
generator_phase_voltage_ua7U161
generator_phase_voltage_ub8U161
generator_phase_voltage_uc9U161
generator_line_voltage_uab10U161
generator_line_voltage_ubc11U161
generator_line_voltage_uca12U161
generator_current_ia13U161
generator_current_ib14U161
generator_current_ic15U161
generator_total_active_power19I161
generator_total_reactive_power23I161
generator_total_apparent_power27U161
power_factor28I160.01
mains_frequency29U160.1
mains_phase_voltage_ua30U161
mains_phase_voltage_ub31U161
mains_phase_voltage_uc32U161
mains_line_voltage_uab33U161
mains_line_voltage_ubc34U161
mains_line_voltage_uca35U161
generator_accumulated_energy36U32BE1

link settings as documented (unverified): RS485 connection is supported via terminals 35, 36, and 37.

bench facts as documented (unverified)
terminals35 (RS485 Common Ground), 36 (RS485-), 37 (RS485+)
terminationImpedance-120Ω shielding wire is recommended
isolationRS485 is isolated
shield/groundsingle-end connect with ground
power(8~35) VDC battery voltage
doc revision1.5

⚠ disputed: engine_speed @ 0 — disputed by HGM6100N/CAN Genset Protocol Guide, which maps Speed to Modbus address 0023 (decimal 35) [5.4.1]

⚠ disputed: engine_temperature @ 1 — disputed by HGM6100N/CAN Genset Protocol Guide, which maps Water Temp to Modbus address 0017 (decimal 23)

⚠ disputed: engine_oil_pressure @ 2 — disputed by HGM6100N/CAN Genset Protocol Guide, which maps Oil Pressure (OP Value) to Modbus address 0019 (decimal 25)

⚠ disputed: fuel_level @ 3 — disputed by HGM6100N/CAN Genset Protocol Guide, which maps Fuel Level (Level Value) to Modbus address 0021 (decimal 33)

⚠ disputed: battery_voltage @ 4 — disputed by HGM6100N/CAN Genset Protocol Guide, which maps Battery Voltage to Modbus address 0024 (decimal 36)

⚠ disputed: charger_voltage @ 5 — disputed by HGM6100N/CAN Genset Protocol Guide, which maps Charger Voltage (D+ Voltage) to Modbus address 0025 (decimal 37)

⚠ disputed: generator_frequency @ 6 — disputed by HGM6100N/CAN Genset Protocol Guide, which maps Gen Freq to Modbus address 0013 (decimal 19)

⚠ disputed: generator_phase_voltage_ua @ 7 — disputed by HGM6100N/CAN Genset Protocol Guide, which maps Gen UA to Modbus address 0007 (decimal 7)

field reports — community-sourced, unverified (checked 2026-06-11)
  • RS485 communication failure is commonly caused by reversed A and B polarity connections. The vendor recommends verifying polarity and ensuring a 120Ω resistor is connected between A and B. [source]
  • confirmed: Power: (8~35) VDC battery voltage — confirmed by HGM6100N Series User Manual Specification section [1.1.2]
  • confirmed: Terminals: 35 (RS485 Common Ground), 36 (RS485-), 37 (RS485+) — confirmed by HGM6100N-4G Series User Manual Terminal Connection Description
  • confirmed: Shield ground: single-end connect with ground — confirmed by HGM6100N/HGM6100CAN Genset Controller Communication Protocol
  • confirmed: Termination: Impedance-120Ω shielding wire is recommended — confirmed by HGM6100N/HGM6100CAN Genset Controller Communication Protocol

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

If your device isn't here, upload its register map. Generation is free, and the connector keeps the rung it earns under testing.

To prove a connector against your own device, order hardware verification. If it doesn't verify, you don't pay.

Platform builders can license the verified library: machine-readable maps, the firmware matrix, API access.