Cla-Val electronic valve 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 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 |
|---|
| di1 | 999 | U16 | 1 | |
| di2 | 1000 | U16 | 1 | |
| di3 | 1001 | U16 | 1 | |
| di4 | 1002 | U16 | 1 | |
| di5 | 1003 | U16 | 1 | |
| di6 | 1004 | U16 | 1 | |
| so1 | 1005 | U16 | 1 | |
| so2 | 1006 | U16 | 1 | |
| ro1 | 1007 | U16 | 1 | |
| ro2 | 1008 | U16 | 1 | |
| ai1 | 2999 | U32BE | 0.01 | |
| ai2 | 3001 | U32BE | 0.01 | |
| ai3 | 3003 | U32BE | 0.01 | |
| ai4 | 3005 | U32BE | 0.01 | |
| ai5 | 3007 | U32BE | 0.01 | |
| ai6 | 3009 | U32BE | 0.01 | |
| ao1 | 3035 | U32BE | 0.01 | |
| ao2 | 3037 | U32BE | 0.01 | |
| ao3 | 3039 | U32BE | 0.01 | |
| ao4 | 3041 | U32BE | 0.01 | |
field reports — community-sourced, unverified (checked 2026-06-11)
- In R-Engine version 2.2.0, when remote backup of the ValvApps to an FTP server (or Link2Valves server) is enabled, the active PID process could get corrupted during the backup process. [source]
- In R-Engine versions prior to 2.9.2, downloading a new R-Engine version via L2V (Link2Valves) could cause the device to get stuck in an infinite restart loop. [source]
- In R-Engine versions prior to 2.5.0, log export on USB was broken (bug introduced in version 2.4.0). [source]
- In older R-Engine versions, a device restart was required after switching between Modbus tables. [source]
- confirmed: di1 @ 999, di2 @ 1000, di3 @ 1001, di4 @ 1002, di5 @ 1003, di6 @ 1004 — confirmed by Cla-Val VC-22D / D22 Modbus Registers Table (registers 41000 to 41005, 1-based)
- confirmed: so1 @ 1005, so2 @ 1006, ro1 @ 1007, ro2 @ 1008 — confirmed by Cla-Val VC-22D / D22 Modbus Registers Table (registers 41006 to 41009, 1-based)
- confirmed: ai1 @ 2999, ai2 @ 3001, ai3 @ 3003, ai4 @ 3005, ai5 @ 3007, ai6 @ 3009 — confirmed by Cla-Val VC-22D / D22 Modbus Registers Table (registers 43000 to 43011, 1-based, 32-bit values)
- confirmed: ao1 @ 3035, ao2 @ 3037, ao3 @ 3039, ao4 @ 3041 — confirmed by Cla-Val VC-22D / D22 Modbus Registers Table (registers 43036 to 43043, 1-based, 32-bit values)
generated by gemini:gemini-3.5-flash · harvested from https://www.cla-val.com/wp-content/uploads/2023/08/Modbus-Registers-Table.pdf (Cla-Val); 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.