DISCOVERY GUIDE

How to scan a Modbus device without turning discovery into a stress test

A full scan of four 65,536-address spaces is not a harmless search box. It is sustained device traffic whose duration depends on latency, timeout, retry policy, function support, and how the client groups addresses.

01

Prove one exchange first

Before scanning, open the transport and send one documented or conservative read. On RTU, establish the Unit ID separately. If the basic request times out, scanning more addresses only creates a larger pile of identical failures.

02

Bound the first pass

Choose the most likely address space and a range suggested by the manual, device class, or known configuration software. Use a quick block-based search before single-address exhaustive probing. Watch the displayed request count and estimated time.

03

Treat the result as a map of responses

Readable does not mean documented, stable, writable, or safe. Build a view from the discovered block, observe it under controlled changes, and name only values you can explain. Never infer that adjacent holding registers are safe to write because they were readable.

KEEP THE EVIDENCE

Use the manual beside the live protocol.

Browse documentation