Opto22 groov EPIC processor

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
temperature_unit_select	1024	U16	1	F or C
float_format_select	1028	U16	1
analog_output_module_0_chan_0	1030	F32BE	1
analog_output_module_0_chan_1	1032	F32BE	1
analog_output_module_0_chan_2	1034	F32BE	1
analog_output_module_0_chan_3	1036	F32BE	1
digital_counter_module_0_chan_0	512	U32BE	1
digital_counter_module_0_chan_1	514	U32BE	1
digital_counter_module_0_chan_2	516	U32BE	1
digital_counter_module_0_chan_3	518	U32BE	1
analog_input_module_0_chan_0	4608	F32BE	1
analog_input_module_0_chan_1	4610	F32BE	1
analog_input_module_0_chan_2	4612	F32BE	1
analog_input_module_0_chan_3	4614	F32BE	1

link settings as documented (unverified): TCP; unit ID 1; FC 01,02,03,04,05,06,15,16,17; Modbus/TCP default port is 502. Supports up to 8 connections from Modbus masters (requires firmware R9.4B or higher for SNAP, R1.2a or higher for E1/E2).

⚠ CAUTION: If you use PAC Control, be careful that Modbus writes to I/O channels don't conflict with strategy logic. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)

max registers/read	127
protocol notes	Modbus checksum is not used; instead, the Ethernet TCP/IP link layer checksum guarantees data. Packet size is limited to 256 bytes.
identification notes	Function code 0x11 (Report Slave ID) returns hardware, firmware, and loader versions.
FC 43 device ID	not supported
doc revision	Form 1678-250827—August 2025
firmware applicability	SNAP Ethernet-based controllers require firmware R9.4B or higher. E1 and E2 require firmware R1.2a.

generated by gemini:gemini-3.5-flash · harvested from https://documents.opto22.com/1678_Modbus_TCP_Protocol_Guide.pdf (Opto 22); manual-faithful — the document's claims, panel risk: ELEVATED — panel is not confident; 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.