An open specification for Modbus register maps (.mbmap) and a public-domain library of over 400 device maps from nearly 100 manufacturers.
Each file describes one device model: the manufacturer, how to connect to it and what every register means. Load a map into a compatible tool and you get the device's variables already named, scaled and typed. The spec is JSON with a JSON Schema, so any language can read it, and the spec, maps and tools are all CC0.
Tech Highlights
- Covers types, byte and word order, scale factors, bit fields, translation tables, sentinel values, write limits and the firmware versions a map fits.
- Reference and identity registers let a tool check the map against the connected device before trusting it.
- A shared conformance suite: valid, invalid and warning samples, each with the diagnostic codes any reader must produce.
Live Metrics
—
Device maps
—
Manufacturers
—
Registers described
Architecture
- SPEC.md defines the format, with RFC 2119 wording; schema/ holds its JSON Schema for editor validation.
- maps/<vendor>/<model>.mbmap.json, one register per line so each change is a one-line diff.
- Python tools validate every map in CI, rebuild index.json for apps that browse the library, and migrate the older CSV-based format.
- Maps converted from other open catalogues are marked unverified until someone checks them against the manufacturer's manual.