Why does General Interrogation look incomplete?

Common causes include wrong Common Address, missing expected Type IDs, polling policy gaps, device profile differences, or event drain behavior.

What evidence should I collect?

Collect the GI request, activation confirmation, response ASDUs, termination if available, ACD/DFC or Class polling behavior, event log, and Smart Findings.

GI troubleshooting

General Interrogation started, but the expected snapshot did not complete.

Incomplete GI is a common FAT, SAT, and commissioning problem. The device may confirm activation, but values are missing, termination is not visible, or the result does not match the point list. ARIEC60870 helps connect the trace, event log, mapping profile, and Smart Findings.

Download ARIEC60870 GI basics

Normal evidence

GI should leave a readable trail.

A good session normally shows the GI request, activation confirmation, response ASDUs, quality/status evidence, and a clear completion or termination point depending on device behavior and protocol mode.

TXC_IC_NA_1General Interrogation activation

RXACTCONDevice accepted the GI request

RXProcess ASDUsValues, quality, timestamps, IOA/CA evidence

RXACTTERMTermination when provided by the device/profile

What usually goes wrong

GI gaps are usually address, profile, polling, or expectation problems.

Wrong CAThe request or response uses a Common Address different from the expected station.

Missing Type IDsThe point list expects values that the device profile does not send during GI.

Polling/event drainSerial Class 1/Class 2 behavior or ACD/DFC may affect when data becomes visible.

Mapping expectationRaw IOA/FUN/INF evidence may be present but not mapped to readable names yet.

ARIEC60870 workflow

Use Trace + Values + Events + Smart Findings before exporting the report.

Check raw frame interpretation first, then validate values, events, and findings. Export the PDF only after the evidence is reviewed.

CA mismatch Smart Findings PDF report