Start with the meter's communication settings
Match the configured RS-485 baud rate, parity, stop bits, and slave address before importing any tags. The public definition deliberately contains no serial port or Unit ID because those belong to the installation, not the device model.
Import the reviewed definition
Open the public device catalogue, choose Eastron SDM630-Modbus V2, review the resources, and import them. Busloom copies the groups, tags, decoding, and views into the project. The project remains self-contained and does not depend on the catalogue at runtime.
The definition also preserves the meter's documented request limit: no more than 40 values, or 80 registers, in one request.
Verify one value before trusting the map
Read phase 1 voltage and compare it with the meter display or a known reference. Inspect the two raw registers beside the decoded float. Once one value is credible, check current and active power at a second operating point before treating the whole imported map as commissioned.
The catalogue entry is based on the manufacturer's published protocol map. It is not a substitute for the exact model revision, wiring diagram, safety procedure, or calibration requirements of the installed meter.
Read a small range before enabling the whole map
Start with one or two known measurements such as phase voltage and frequency. The SDM630 map represents measurements as two-register IEEE 754 values, so a single tag read requires a quantity of two. Inspect the two raw words and confirm their order before polling a larger source. This catches addressing and framing mistakes without turning eighty-five tags into eighty-five simultaneous questions.
When the first value is correct, add a contiguous block that remains within the meter's documented request limit. Do not create one oversized source simply because the imported definition contains many tags. Source boundaries should follow valid address spans and the maximum number of values accepted by the meter.
Use electrical relationships as plausibility checks
A plausible individual number is only the beginning. Compare the three phase voltages, currents, total active power, frequency, and energy direction with the installation. On a lightly loaded system, current and power should reflect that state. On a balanced source, phase measurements should be reasonably close. These are commissioning checks, not calibration claims, but they quickly expose wrong wiring mode, phase assignment, or decoding.
Some measurements only apply to particular wiring configurations. Keep the definition notes visible and do not treat an irrelevant value as a failed tag. Confirm the configured system type and meter variant against the nameplate and manual before investigating every zero or unavailable measurement.
- Confirm model and protocol revision
- Verify configured baud, parity, and Unit ID
- Read one float32 value as raw words
- Check frequency and phase values against the installation
- Observe one controlled load change
Keep installation settings outside the public definition
The public file describes the reusable register map: groups, offsets, types, units, and notes. Your serial port, assigned Unit ID, polling intervals, site name, and any local alarm thresholds belong in the project. Keeping that boundary makes the map reviewable without publishing details from an installation.
After import, save the tested firmware or protocol revision in project notes and retain the source link. If a later meter revision moves or adds registers, update the public definition through a reviewed change instead of silently editing the shared map for one site.