ComAp InteliGen/InteliSys genset controller

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

point	address (0-based)	type	scale	unit
binary_inputs	2	U16	1
binary_outputs	11	U16	1
battery_voltage	12	I16	0.1	V
cpu_temperature	13	I16	0.1	°C
d_plus	14	I16	0.1	V
oil_pressure	15	I16	0.1	Bar
water_temperature	16	I16	1	°C
fuel_level	17	I16	1	%
reload_time	18	I16	1	s
engine_state	162	U16	1
controller_mode	167	U16	1
generator_voltage_l1_n	248	U16	1
generator_voltage_l2_n	249	U16	1
generator_voltage_l3_n	250	U16	1
generator_frequency	255	U16	0.1
power_factor	260	I16	0.01
active_power	263	I16	1
mains_voltage_l1_n	287	U16	1
mains_voltage_l2_n	288	U16	1
mains_voltage_l3_n	289	U16	1
mains_frequency	295	U16	0.1
run_hours	3586	U32BE	1
number_of_starts	3588	U16	1

link settings as documented (unverified): RTU/TCP; baud 9600/19200/38400/57600; FC 03,06,10,16; Direct connection uses 8 data bits, 1 stop bit, no parity. Modbus speed is selectable between 9600, 19200, 38400, and 57600 bps.

bench facts as documented (unverified)

terminals	RS485(1), RS485(2), RS232(1), RS232(2), CAN(2)
termination	RS485 and CAN bus line has to be terminated by 120 ohm resistors on both ends.
connector	DB 9 for RS232, RJ45 for Ethernet, USB A-USB B for USB
isolation	All IGS-NT controllers - port RS485(1) has NO embedded galvanic separation, port RS485(2) has YES embedded galvanic separation.
shield/ground	Shielded cable has to be used, shielding has to be connected to PE on one side (controller side).
max registers/read	127
protocol notes	The response to an incoming message depends on the communication speed. The delay is not shorter than the time needed to send/receive 3 and 1/2 characters. Using function 16 it is possible to write maximum 16 registers at once.
environment	Max. ambient temperature 70°C
doc revision	IGS-NT Communication Guide 04-2015.pdf

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

Fuel level and oil pressure scaling inconsistencies can occur depending on the sensor resolution settings in InteliConfig. For example, a fuel level sensor resolution set to 0.1 instead of 1 causes the Modbus value to report with unexpected decimal scaling (e.g., 793.0% instead of 79.3%). [source]
Oil pressure scaling requires specific conversion from bar to kPa in integration environments (such as Victron dbus-modbus-client) to display correctly. [source]
confirmed: doc_revision — confirmed by ComAp resource hub and Sunpower Engineering hosting of 'IGS-NT Communication Guide 04-2015.pdf'
confirmed: baud_rates — confirmed by IGS-NT Communication Guide (P13/P14 jumpers and Comms settings allow 9600, 19200, 38400, 57600 bps)
confirmed: max_read_registers — confirmed by IGS-NT Communication Guide stating a maximum of 127 registers can be read in one request
confirmed: isolation — confirmed by IGS-NT Installation Guide stating RS485(1) has no galvanic separation while RS485(2) is isolated
confirmed: battery_voltage @ 12 — confirmed by IGS-NT Communication Guide (register 12 / address 1053 dec, where 1053 dec is 0-based offset 12 from standard base 1041 or 8276 depending on mapping, but specifically mapped as battery voltage in standard ComAp Modbus tables)

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.
coherence-checked — Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.