01Cannot open RTU port
Close other serial tools, reselect the discovered port, confirm OS permission and adapter presence, then reconnect.
Symptom-led diagnosis and precise terminology.
01Close other serial tools, reselect the discovered port, confirm OS permission and adapter presence, then reconnect.
02Verify Unit ID, serial framing or TCP gateway routing. On RTU, test Unit-ID discovery before scanning addresses.
03Inspect the exception code. Illegal Function points to FC support; Illegal Data Address points to space/range; Illegal Data Value points to quantity or payload.
04Confirm the source is running, its Read Plan contains the address, and Health shows completed requests rather than only an open connection.
05Inspect raw words, verify PDU address, width, signedness, byte/word order, then scale and offset—in that order.
06Start every attached source, use numeric/Boolean tags, and ensure the current time window overlaps collected data.
07Check latency, retries, RTU utilization, oversized ranges, illegal gaps, and whether automation currently owns the connection.
08Check Professional entitlement, active connection profile, validation errors, required parameters/dataset, and read-only status for writes.
One precise request and its evidence is more useful than an unbounded traffic dump.