Command troubleshooting
Command sent, but ACTCON or final feedback is missing.
Command problems are painful because the operator can see a command action, but the protocol evidence may not show a clean activation confirmation, feedback, or termination. ARIEC60870 helps engineers read the command frame sequence instead of relying on a vague timeout.
Normal evidence
A command should be traceable from request to confirmation and feedback.
Depending on the device and command mode, evidence can include select, execute, ACTCON, process feedback, ACTTERM, or a negative confirmation. Missing one of these does not always mean the transport is down.
RequestCommand Type ID, CA, IOA, qualifier, select/execute state, and direction.
ConfirmationACTCON proves whether the device accepted or rejected activation.
FeedbackEvent/value change proves whether the controlled object moved or changed state.
TerminationACTTERM may mark the end of the command flow when supported.
Likely causes
Do not stop at timeout. Check the command profile.
Smart evidence
ARIEC60870 connects raw command frames to findings and report proof.
Use the Trace, Event Log, Smart Findings, and PDF Report together before escalating to vendor or commissioning teams.