Troubleshooting
Practical checks for no response, CA mismatch, GI gaps, command issues, mapping issues, and report findings.
Use this page to separate physical link problems, addressing problems, protocol state problems, mapping problems, and reporting problems before escalating to vendor or site teams.
No response
Start with transport and addressing before assuming the protocol decoder is wrong.
- IEC-101/103: check COM port, baud rate, parity, stop bits, RS-485 direction, and wiring.
- IEC-104: check IP address, TCP port, firewall, routing, and whether the endpoint accepts the client.
- Confirm link address and common address against the device configuration.
Common Address mismatch
The device may respond while using a different ASDU Common Address than the test profile expects.
- Open Frame Trace and compare decoded CA with project documentation.
- Check whether the connected endpoint is the expected station or bay controller.
- Update ARIEC60870 setup only after confirming the device configuration.
General Interrogation incomplete
GI gaps often come from addressing, device profile, polling policy, or expectation mismatch.
- Verify COT and common address in Frame Trace.
- Watch ACD/DFC and Class 1/Class 2 activity for serial links.
- Confirm the expected Type IDs or FUN/INF values exist in the device profile.
Command confirmation missing
A command can be sent but still fail to produce a clear ACTCON, feedback, or ACTTERM sequence.
- Check command type, select/execute policy, IOA, and Common Address.
- Review event log and Frame Trace together instead of checking only the operator message.
- Use Smart Findings as a guide, then validate against the approved test procedure.
IEC-104 session unstable
Look at TCP reachability first, then session control frames.
- Confirm STARTDT/STOPDT/TESTFR behavior.
- Review I/S/U frames and sequence counters.
- Check reconnect behavior and timing in the Event Log and Frame Trace.
Report looks incomplete
The report reflects the evidence currently available in the session.
- Run the session long enough for GI and event drain.
- Check Diagnostics and Findings before exporting.
- Use Frame Trace when high-level evidence does not explain the issue.
Escalation package
What to collect before asking for help.
A good escalation package saves time because it separates project configuration mistakes from protocol or device behavior.
ConfigurationProtocol mode, serial/TCP parameters, link/common address, ASDU profile, expected points, and mapping profile version.
EvidenceOperator Evidence, Value Viewer, Event Log, Diagnostics, Findings, and relevant Frame Trace rows.
ReportExport a PDF after reviewing sensitive project data. Keep raw traces private unless the project allows sharing.
ARIEC60870IEC 60870 protocol tester