E+E EE872 CO2 probe

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 only confirmed at the hardware-verified rung.

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	unit
co2_average	1060	F32LE	1	ppm
co2_raw	1062	F32LE	1	ppm
pressure_mbar	1200	F32LE	1	mbar
pressure_psi	1202	F32LE	1	psi
relative_humidity	1020	F32LE	1	%
temperature_c	1002	F32LE	1	°C
temperature_f	1004	F32LE	1	°F
temperature_k	1008	F32LE	1	K
dew_point_temperature_c	1104	F32LE	1	°C
dew_point_temperature_f	1106	F32LE	1	°F
dew_point_temperature_k	1146	F32LE	1	K
co2_average_int	4030	I16	1	ppm
co2_raw_int	4031	I16	1	ppm
pressure_mbar_int	4100	I16	0.1	mbar
pressure_psi_int	4101	I16	0.01	psi
relative_humidity_int	4010	I16	0.01	%
temperature_c_int	4001	I16	0.01	°C
temperature_f_int	4002	I16	0.02	°F
temperature_k_int	4004	I16	0.02	K
dew_point_temperature_c_int	4052	I16	0.01	°C
dew_point_temperature_f_int	4053	I16	0.01	°F
dew_point_temperature_k_int	4073	I16	0.01	K

link settings as documented (unverified): RTU; baud 9600/19200/38400; unit ID 237; FC 03,04,06; The recommended settings for multiple devices in a Modbus RTU network are 9600, 8, even, 1. The EE872 represents 1/10 unit load on an RS485 network.

bench facts as documented (unverified)

connector	M12x1 5 poles
wiring notes	Pin 1: Supply voltage, Pin 2: B RS485 (D-), Pin 3: GND, Pin 4: A RS485 (D+), Pin 5: Configuration pin
protocol notes	When reading information that spans multiple registers, it is always necessary to read all registers, even if the desired information requires less. To obtain the correct floating point values, both registers have to be read within the same reading cycle.
model register	0x09
serial register	0x00
firmware register	0x08
identification notes	Sensor name (as ASCII) is at 0x09 (size 8), Serial number (as ASCII) is at 0x00 (size 8), Firmware version is at 0x08 (size 1)
power	15 - 35 V DC (Current output) or 12 - 30 V DC (RS485 interface and voltage output), max. voltage 30 V DC for USA & Canada Class 2
environment	Storage conditions: -40...+60 °C, 700...1100 mbar, 0...95 %RH, non-condensing. Protection rating: IP65 probe body
accuracy	CO2: <±(40 ppm + 1.8 % of mv) for 0...2000 ppm. RH: ±3 %RH (20...80 %RH). Temp: ±0.5 °C (5...60 °C)
certifications	CE, UKCA, FCC Part 15 Class A, ICES-003 Class A
doc revision	Version v1.6 \| 05-2026

generated by gemini:gemini-3.5-flash · harvested from https://www.epluse.com/fileadmin/data/product/ee872/BA_EE872_e.pdf (E+E Elektronik); manual-faithful — the document's claims, panel risk: LOW — panel concurs, no field disagreements; proved interop-verified on 2026-06-10 · recorded 2026-06-10

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.

Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.

Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.

Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.