Smart Findings

Protocol diagnosis that explains the problem, proof, and next step.

Smart Findings are designed for the moment when a basic protocol tester only says timeout, error, or no data. ARIEC60870 keeps the raw frame visible and explains what likely went wrong: CA mismatch, incomplete GI, missing ACTCON, bad quality, unknown IOA, Class 1 congestion, or IEC-104 session instability.

Download ARIEC60870 Learn IEC 60870

What it means

Smart Findings are not magic. They are evidence summaries.

A finding should not hide the protocol. It should summarize the symptom, point to the frame or counter that proves it, explain why the symptom matters, and suggest a practical next check.

ProblemA short statement of what looks wrong: CA mismatch, GI incomplete, ACTCON missing, bad quality, unknown IOA, or unstable session.

ProofThe raw frame, address, COT, sequence counter, quality flag, event, or timeout pattern behind the finding.

Likely causeThe engineering reason the symptom usually happens: wrong CA, mapping mismatch, unsupported command, busy link, or missing report flow.

Next stepA practical check: verify address, re-run GI, inspect IOA mapping, check ACTCON/ACTTERM, compare sequence counters, or export report evidence.

Examples

Findings should read like troubleshooting notes, not cryptic errors.

Common Address mismatchDevice responds, but the ASDU CA differs from the configured project CA. The link is alive, but application data belongs to another station context.Read CA guide

GI incompleteGeneral Interrogation starts but the expected snapshot, confirmation, or termination evidence is missing. The report should show exactly which proof is absent.Read GI guide

ACTCON missingCommand TX is visible, but activation confirmation, feedback, or termination does not arrive. The finding links the command to the missing response evidence.Read command guide

IEC-104 session issueTCP is connected, but STARTDT, TESTFR, I/S-frame acknowledgement, or sequence counter behavior suggests protocol-level instability.Read IEC-104 guide

Report value

Findings become stronger when they are exported with proof.

For FAT, SAT, commissioning, troubleshooting, homologation support, certification attachment, vendor comparison, or handover, a finding is useful only when the evidence remains traceable. ARIEC60870 keeps the finding, raw frame, decoded meaning, value/event context, and PDF report workflow connected.

PDF evidence report Watch demo

For junior engineersLearn why the protocol behavior matters without memorizing every byte first.

For reviewersSee the frame proof behind each finding before accepting a conclusion.

For project handoverTurn symptoms, evidence, and next steps into clean PDF documentation.