Skip to content
Proxus 2.0.1 Licence and sign-in fixes after the 2.0 upgrade Release notes

Open data · CC BY 4.0

Open Modbus register maps

Every register of a device in one table: the address on the wire, the 30001-style reference, data type, byte order, unit and scale, with the vendor document it comes from. 60+ devices and 20,545 registers so far, free to use in any project.

devices
60+ devices
registers
20,545 registers
verified on hardware
0 verified on hardware
AI assistant · MCP Product UI · sample data
Map: eastron/sdm630-modbusRead-only

MCP · read_named reading… ✓ 4 values · 38 ms
read_named(device: "sdm630-1", keys: ["voltage_l1_n", "current_l1", "frequency", "active_power_l1"])
voltage_l1_n 230.4 V
current_l1 12.6 A
frequency 50.00 Hz
active_power_l1 8,420 W

Energy meters

Power analysers

Variable speed drives

How the maps are made

One address convention, and the source for every value

Zero-based wire addresses
Vendor manuals mix 30001, 0x0000 and "register 1". Every map stores the address sent on the wire; the 30001-style reference is derived from it, so the two never disagree.
Checked against the source
Maps are transcribed from the vendor document they list, with its version, and every address is checked back against that document by script.
Typed and scaled
Each register carries its data type, byte order, unit and scale (fixed, or a SunSpec scale-factor register) and the meaning of enumerated values.

Got raw values and not sure of the byte order? Decode them in the Modbus register decoder

Hardware verification levels

L1
The registers answer on a real device.
L2
The values pass automatic plausibility checks: floats, frequency, voltage, power factor, energy counters, model.
L3
A person compared values with the device’s own display.

A map without a level is transcribed from its sources and not yet read from hardware. Verifying one takes a few minutes with the Proxus MCP server.

Use them

Read a device by register name

The Proxus Industrial MCP Server ships with every map in this collection. Give a Modbus device its map, and an AI assistant reads voltage_l1_n instead of guessing that hr:0-1 is a word-swapped float.

The JSON file is attached to every proxus-mcp release (this page: v0.1.0-beta.8). Each map is also a YAML file in the repository.

Have one of these devices?

A hardware verification is the most useful contribution: read-only, a few minutes, and your name goes on the map’s verified list. Missing a device? Request it with a link to its Modbus document.