IEC 61850 client control
Guarded IED control without exposing raw MMS writes to the operator.
The ARIEC61850 control tester turns a live control Data Object such as LD0/CSWI1.Pos into an OPEN/CLOSE workflow. The engine discovers the IED's control model, exact MMS value type, status reference, and required sequence.
Operator workflow
Process intent first.
The user selects CSWI.Pos, verifies the current protocol status and approved test conditions, stages OPEN or CLOSE, reviews the exact target, and confirms the command. Advanced parameters remain visible without dominating the normal workflow.
- Live control-object and status discovery
- Automatic Direct or SBO sequence selection
- Interlock and synchrocheck request bits
- Test mode, originator, and Orig ID
- Command timeout, Cancel, and association cleanup
- Request, response, termination, and feedback evidence
Protocol sequencing
All four IEC 61850 control models are represented explicitly.
| Control model | Sequence | Completion boundary |
|---|---|---|
| Direct normal | Oper | Confirmed MMS result |
| SBO normal | SBO → Oper | Confirmed MMS result |
| Direct enhanced | Oper → CommandTermination | Positive or negative termination |
| SBO enhanced | SBOw → Oper → CommandTermination | Positive or negative termination |
The stack keeps ctlVal, origin, ctlNum, timestamp T, Test, and Check values consistent across the sequence. Generic application writes to control-service members are blocked so application code uses the typed control session.
Failure diagnosis
Accepted is not the same as completed.
Enhanced-security commands remain pending until matching CommandTermination evidence arrives. Rejection, timeout, association loss, caller cancellation, negative termination, application error, and feedback mismatch remain separate outcomes.
- Immediate result
- MMS service acceptance or rejection
- Enhanced completion
- Positive or negative CommandTermination
- Application error
- ControlError and AddCause
- Sequence evidence
- ctlNum, T, origin, request/response data
- Process evidence
- Discovered status readback and independent indication
Validation boundary
One laboratory command path has been exercised; broader validation remains ongoing.
This evidence does not replace model- and firmware-specific validation, negative-case testing, independent process indication, long-duration testing, site procedure approval, or formal conformance assessment.
Read the public validation record →