Diagnose the physical layer first
Application errors often originate from wiring and signalling. RS-485 provides only an electrical interface; message framing and diagnostics depend on the higher-layer protocol. A structured investigation avoids changing configuration at random.
Record the symptoms
Note affected stations, exact timestamps, device diagnostics and whether faults occur under load, during start-up or after a mechanical event.
Verify basic configuration
Check protocol variant, addresses or frame identifiers, baud rates, timing and device-specific configuration files.
Inspect the segment
Confirm cable type, termination, connectors, shield strategy, grounds and power supplies according to the equipment manuals.
Measure and isolate
Use a compatible bus analyser and appropriately rated measurement equipment; compare healthy and faulty sections. Avoid probing energized or hazardous-area circuits without a suitable procedure and equipment.
Symptoms and likely directions
| Symptom | Potential causes to investigate | First diagnostic step |
|---|---|---|
| Entire segment offline | Supply loss, short, cable break, major wiring fault | Check segment power and physical continuity safely |
| Intermittent receive or framing errors | Noise, reflections, poor shielding, loose contacts | Inspect topology and obtain error counters or bus trace |
| One device missing | Device power, address, wiring, configuration | Verify the local node and its configured identity |
| Fails at higher speed | Length, termination, cable or timing limitations | Compare wiring limits with the selected bit rate |
Follow local electrical safety procedures, isolate equipment when required, and obtain authorization before disconnecting automation networks. Measurements may affect production and safety-related functions.