The device library is missing my model, or a library point is wrong
Match the exact equipment and validate a small definition against its register map.
Verify the definition
- Record manufacturer, exact model, options, and firmware. Similar products can have different register maps.
- Check the selected library solution and its documented scope. A library match by name is not a verification of the connected device.
- If using a local library file, confirm it is the intended version and was imported successfully. Keep its source/version with the project.
- Compare one point's function/table, raw address, width, type/order, scaling, access, and states with the manufacturer's map.
- Read that point and retain the raw reply alongside the expected value. For an unsupported device, start with a small custom definition rather than copying an entire unrelated model.
- Submit a reproducible correction with the map excerpt, exact model/version, raw request/reply, and the definition that needs changing.
A library point used in SB1000 commissioning or MQTT/BACnet does not configure an external Modbus TCP client's decoder. Configure that client separately.
Expected result
The selected/custom definition produces a correct value and unit for the actual equipment. Avoid testing writable points by trial and error; follow their documented action and restore procedure.