BUSLOOM MANUAL

Discovery & diagnostics

Network and RTU discovery, Auto Scan, Protocol Diagnostics, Health, and Raw Traffic.

09 · PROTOCOL EVIDENCE

Discovery & diagnostics

Diagnostics observe the same native transaction stream as ordinary polling and writes. Start with the narrowest question; do not run an exhaustive scan when one known request can identify the fault.

NETWORK / RTU

Endpoint discovery

Finds RTU Unit IDs or confirmed TCP/TLS endpoints in a bounded subnet and reports network results as explicit IP:port pairs.

AUTO SCAN

Auto Scan

Quick discovers practical readable ranges in all four address spaces. Exhaustive probes every single address and can issue 262,144 requests.

FC43 · MEI 0E

Device Info

Reads paged device identification and preserves standard and vendor-specific objects.

FC08 / 11 / 12 / 17 / 22

Protocol Diagnostics

Runs safe specialist diagnostics, decodes returned fields, and retains attempts, latency and exact TX/RX frames. FC22 remains a confirmed write.

MEASURE

Connection Health

Explains request lifecycle, latency distribution, throughput, retries, errors, connection state, and RTU utilization by source.

PROVE

Raw Traffic

Shows chronological frames, decoded fields, source attribution, timings, exceptions, filters, bounded recording, and export.

Choose Quick or Exhaustive scan

ModeUse whenBehaviorCost / limitation
QuickUnknown practical mapAdaptive block probesMay miss isolated readable addresses surrounded by illegal gaps
ExhaustiveQuick missed a known isolated addressEvery address in all four spacesHours of traffic on a slow RTU link; use deliberately

A diagnostic sequence that preserves evidence

  1. Reduce the test

    Stop unrelated views and reproduce with one address, one profile, and one expected value.

  2. Check Health

    Decide whether the failure is connection, timeout/retry, Modbus exception, malformed response, TLS, or CRC-related.

  3. Open the transaction

    Use Raw Traffic source attribution to inspect the exact request and response bytes.

  4. Compare protocol fields

    Verify Unit ID, function, PDU address, quantity, byte count, exception code, and timing.

  5. Record a bounded artifact

    Capture only the interval needed to reproduce. Export a session when another person must inspect it without the device.

Use Protocol Diagnostics deliberately

FC08 exposes safe serial-line diagnostic subfunctions, FC11/12 communication event state, FC17 server identification, and FC22 a masked holding-register write. Busloom excludes state-changing FC08 operations from this workbench. FC22 obeys the active profile's read-only policy and requires explicit write confirmation.