Deep Sea DSE7310/7320 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.

point	address (0-based)	type	scale
oil_pressure	1024	U16	1
coolant_temperature	1025	I16	1
oil_temperature	1026	I16	1
fuel_level	1027	U16	1
charge_alternator_voltage	1028	U16	0.1
engine_battery_voltage	1029	U16	0.1
engine_speed	1030	U16	1
generator_frequency	1031	U16	0.1
generator_l1_n_voltage	1032	U32BE	0.1
generator_l2_n_voltage	1034	U32BE	0.1
generator_l3_n_voltage	1036	U32BE	0.1
generator_l1_l2_voltage	1038	U32BE	0.1
generator_l2_l3_voltage	1040	U32BE	0.1
generator_l3_l1_voltage	1042	U32BE	0.1
generator_l1_current	1044	U32BE	0.1
generator_l2_current	1046	U32BE	0.1
generator_l3_current	1048	U32BE	0.1
generator_l1_watts	1052	U32BE	1
generator_l2_watts	1054	U32BE	1
generator_l3_watts	1056	U32BE	1
mains_frequency	1059	U16	0.1
mains_l1_n_voltage	1060	U32BE	0.1
mains_l2_n_voltage	1062	U32BE	0.1
mains_l3_n_voltage	1064	U32BE	0.1
mains_l1_current	1076	U32BE	0.1
mains_l2_current	1078	U32BE	0.1
mains_l3_current	1080	U32BE	0.1
engine_run_time	1798	U32BE	1
generator_positive_kwh	1800	U32BE	0.1
number_of_starts	1808	U32BE	1

link settings as documented (unverified): RTU; baud 110/150/300/600/1200/2400/4800/9600/14400/19200/28800/38400/57600/115200; unit ID 10; FC 03,16; The 73xx family is an exception to the RS485 2 stop bits rule as they always use 1 stop bit. RS232 link also uses 1 stop bit.

⚠ Control is performed by sending System Control Keys to register 4104 and its bitwise opposite to register 4105 in the same write operation. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)

termination	Termination resistors must be correctly fitted and cable length must not exceed 1.2km
wiring notes	DSE recommend and supply BELDEN 9841 cable for RS485 use
max registers/read	125
broadcast	supported
sentinel values	0xFFFF for Unimplemented, 0xFFFE for Over measurable range, 0xFFFD for Under measurable range, 0xFFFC for Transducer fault, 0xFFFB for Bad data, 0xFFFA for High digital input, 0xFFF9 for Low digital input
protocol notes	Maximum allowable writing frequency to Modbus registers should be limited to 10 times per second.
firmware register	Page 11, Register 0 (Software version)
doc revision	REV A

⚠ disputed: comms.baud_rates: [110, 150, 300, 600, 1200, 2400, 4800, 9600, 14400, 19200, 28800, 38400, 57600, 115200] — disputed by DSE7310/7320 Operator Manuals which state that the actual hardware only supports baud rates from 1200 to 115200 (or up to 19200 on older non-MKII models), even though the GenComm standard defines codes for lower baud rates

⚠ disputed: comms.notes: The 73xx family is an exception to the RS485 2 stop bits rule as they always use 1 stop bit — disputed by DSE73XX MKII Product Change Notification (v5.0, 15.04.19) which added support for configuring 1 or 2 stop bits and parity on the RS485 port

field reports — community-sourced, unverified (checked 2026-06-11)

Writing System Control Keys to register 4104 and its complement to 4105 requires a single Modbus Function Code 16 (Write Multiple Registers) command with a quantity of 2. If a Modbus master/scanner splits this into two separate single-register writes (FC6), the DSE controller will reject the command with Exception Code 02 or ignore it. [source]
Since firmware version 5.0 (released April 15, 2019), the RS485 port on DSE73xx MKII controllers is no longer restricted to 1 stop bit and no parity; it can be configured for 1 or 2 stop bits and Even, Odd, or No parity. [source]
confirmed: comms.default_unit_id: 10 — confirmed by DSE7200/7300 Operators Manual (057-074) which states default Modbus slave address is 10 [1.2.5]
confirmed: comms.framing: ['RTU'] — confirmed by DSE7310/7320 MKII Operator Manual and GenComm standard
confirmed: comms.function_codes: [3, 16] — confirmed by GenComm standard detailing Function 3 (Read Multiple Registers) and Function 16 (Write Multiple Registers)
confirmed: facts.control_warning: Control is performed by sending System Control Keys to register 4104 and its bitwise opposite to register 4105 in the same write operation — confirmed by Gencomm Control Keys document (056-051)
confirmed: facts.doc_revision: REV A — confirmed by GenComm standard document SP-228 REV A
confirmed: facts.identification.firmware_register: Page 11, Register 0 (Software version) — confirmed by GenComm standard Page 11 - Diagnostic - General
confirmed: facts.physical.notes: DSE recommend and supply BELDEN 9841 cable for RS485 use — confirmed by DSE Gencomm Control Keys document
confirmed: facts.physical.termination: Termination resistors must be correctly fitted and cable length must not exceed 1.2km — confirmed by DSE Gencomm Control Keys document

The trust ladder

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

generated — A prompt produced it. Unproven — anyone can regenerate this.
structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
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.
simulator-verified — Decoded correctly against a protocol emulator seeded with known-true values — catches word-order/scaling errors vs the emulator, not the physical device.
hardware-verified x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

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.