Prepare an itemised CT burden worksheet, count the complete cable loop and compare 1 A with 5 A through a clearly hypothetical worked example.

Distinguish an illegal-data-address response from a timeout, check the complete requested register range and retain a useful diagnostic record.

Counting mode and restart persistence are separate settings. Build a controlled acceptance test that checks the raw count and its interpretation after maintenance.

A connected level sensor can still have an unreliable pressure reference. Check the documented vent arrangement before adjusting offsets or replacing the probe.

Preserve original recorder exports, document clock offsets and check timestamp evidence before and after a clock adjustment.

Create a practical monitoring handover pack that connects each sensor to its engineering units, dashboard point, alarm owner and acceptance evidence.

Saving a change in iMonnit does not prove that the sensor has received it. Use transaction status, communication evidence and a careful recovery record to verify the result.

Validate a Dragino decoder against the exact model, firmware, message port and engineering units before rolling it out to operational dashboards.

A practical acceptance-test plan for iMonnit alarms: review rule actions, warn recipients, test delivery and verify the final armed state.