MMS discovery and reporting
Association, live IED directory, Functional Constraints, typed reads, DataSets, RCB planning, GI, monitoring, and evidence.
IEC 61850 · .NET 8 · GPL-3.0-or-later
ARIEC61850 combines an MMS client, guarded IED control, reporting, GOOSE, Sampled Values, SCL, PCAP diagnostics, simulation, CLI automation, and focused Windows engineering applications.
Validation boundary: a guarded command path has been exercised with a laboratory IED. Formal conformance, broad interoperability, and operational-substation approval are not claimed.
Control object LD0/CSWI1.Pos
Model Discovered from the IED
Status OPEN / CLOSED
Sequence Direct or SBO
Completion MMS / CmdTerm
Operator action OPEN or CLOSE
Control-model-aware workflow
Select a control Data Object such as CSWI.Pos. ARIEC61850 discovers the live control model and MMS type, then applies Direct Operate or Select-Before-Operate sequencing without asking the user to manually write Oper, SBO, or SBOw.
Engineering stack
Association, live IED directory, Functional Constraints, typed reads, DataSets, RCB planning, GI, monitoring, and evidence.
Frame codecs, SCL-backed profiles, bounded publishing, subscription, PCAP inspection, sequence supervision, and diagnostics.
Expected-vs-observed engineering profiles, readiness checks, deterministic simulation, Markdown/JSON reporting, and repeatable tests.
Quick start
Core libraries are cross-platform where the transport permits it. WPF applications and the current raw-Ethernet transport require Windows.
git clone https://github.com/masarray/ARIEC61850.git
cd ARIEC61850
dotnet restore .\ARIEC61850.sln
dotnet build .\ARIEC61850.sln -c Release
dotnet test .\ARIEC61850.sln -c Release --no-build
Responsible engineering
ARIEC61850 is intended for isolated laboratories, approved commissioning work, education, and protocol research. It does not claim formal third-party IEC 61850 conformance. Active control and process-bus publishing require an approved test plan, authority, isolation boundary, and independent verification.
Terminology: “native C#/.NET” means a project-owned managed implementation rather than an application wrapper. “Smart Control” means automated protocol discovery and sequence selection; it does not mean autonomous decision-making or permission to operate equipment.