Verify that the intended IED answers
Separate basic network reachability, TCP port 102, MMS association and usable model discovery instead of calling all four “connected.”
Practical tutorial · read-only first · IEC 61850 MMS
Connect an IED. Discover its live model. Read one trustworthy value.
Use ARSAS as an IEC 61850 MMS client to move from an approved IP address to a model you can inspect and a value you can explain. A green connection indicator is only the beginning: the useful result is the correct IED, object reference, value, quality, timestamp and acquisition source kept together.
30-second takeaway
MMS is the client/server doorway into an IEC 61850 IED.
Through MMS, ARSAS can associate with the IED, discover its named functions and data, read typed values, inspect DataSets and Report Control Blocks, transfer supported files and prepare approved control workflows. The important distinction is simple: connection proves reachability; discovery proves a model; value, quality, time and identity make an observation useful.
When to use the MMS Client
Start here when the task begins with an IED endpoint.
This workflow is useful before deeper Reporting, SCL, file-transfer or control testing.
Inspect what the running server exposes
Use live discovery when a vendor file is unavailable, stale or needs comparison against the online IED.
Find values, DataSets and RCBs
Confirm object references and Functional Constraints before selecting points for Reporting or bounded polling.
Preserve a reusable model baseline
When discovery is complete, continue toward IID Edition 2 or ICD Edition 1 generation and explicit receiving-system validation.
Collect the target facts.
- Approved IED name, bay or function
- IP address, subnet and approved route
- Expected TCP port 102 availability
- Expected vendor or model identity
- Permission to connect from this workstation
Keep the first session read-only.
Live discovery and value reads should be separated from active control, RCB modification and IED configuration changes. Do not write or operate until the project procedure, plant authority and rollback plan explicitly permit it.
Step-by-step in ARSAS
From approved IP address to one attributable value.
Do not skip identity and quality checks merely because the association succeeds.
Confirm the target and network path
Record the expected device identity and verify the approved network interface, subnet, route and VLAN. Ping can help with basic IP reachability, but it does not prove IEC 61850 MMS service.
Select Add IED
Open General IEC 61850 Testing, choose Add IED, enter a clear device name, the approved IP address and port 102 unless the project specifies another endpoint.
Complete the MMS association
Connect and retain the exact diagnostic if the association is refused, times out or closes. A successful TCP socket is not the same as an accepted MMS association.
Inspect identity and live-model discovery
Confirm that the discovered physical identity is plausible, then inspect Logical Devices, Logical Nodes, Data Objects, Data Attributes, DataSets and RCBs. An unexpectedly small or empty tree is evidence to investigate.
Find the intended object and Functional Constraint
Search for a familiar indication or measurement. Keep the complete IEC reference and choose the correct Functional Constraint—for example status, measurement, configuration or control context—rather than selecting a similar-looking name.
Verify the first trustworthy value
Read the value together with IED identity, full reference, MMS type, quality, device timestamp, ARSAS capture time and acquisition source. Compare it with an independently known plant state before treating it as evidence.
Success criteria
A useful first session answers more than “connected or not.”
Correct endpointThe expected IED identity answered at the approved address
Usable modelLogical hierarchy, data and engineering objects were discovered
Correct referenceThe intended object and Functional Constraint are explicit
Trustworthy observationValue, quality, timestamp and source are understandable
Concepts behind the screen
Five terms make the browser easier to understand.
MMS association
The application-level client/server session. It comes after network and TCP reachability and before useful IEC 61850 services.
Object reference
The full identity of the data inside the IED. Preserve it; a short display label is not enough for reproducible evidence.
Functional Constraint
The service context of an attribute, such as status, measurement, configuration or control. Similar names under different FCs are not interchangeable.
Quality and timestamp
Quality says whether the observation can be trusted. Timestamp says when the IED or process associated the change with time.
DataSet and RCB
A DataSet selects members; a Report Control Block governs how selected changes are delivered. Discovery is preparation—not proof that reporting works.
Live model versus SCL
The live model is current server evidence. SCL represents configured engineering intent. Compare both when integration depends on consistency.
If it fails
Use the failed milestone to choose the next check.
No IP reachability
Check cable, adapter address, subnet, route, VLAN, duplicate IP and approved network boundaries.
Ping works, TCP port 102 fails
Check MMS enablement, firewall, ACL, service binding and whether another IED interface is intended.
Port 102 works, association fails
Capture the exact diagnostic. Investigate server limits, concurrent clients, access policy, authentication or edition-specific behavior.
Association works, model is incomplete
Check access rights, discovery diagnostics, model limits and whether the connected endpoint is really the intended server.
Value looks wrong or stale
Confirm the object reference, Functional Constraint, type, quality and timestamp. Compare with SCL and an independent plant indication.
Reads work, changes do not arrive
The next problem is Reporting coverage, ownership, trigger options or delivery—not basic MMS discovery.
Real application evidence
Keep the model and the live observation in the same IED context.
01Add the intended endpoint
Start from the approved IED identity and IP address without requiring a usable vendor SCL file for the first read-only discovery.
02Verify the observation
Review the device, full reference, value, quality, timestamp and acquisition source together.
Attributable live server evidence
ARSAS can preserve what endpoint answered, what model it exposed, what object was read and what supporting quality, time and source context accompanied the value.
MMS discovery is not complete interoperability proof.
Association and discovery do not prove Reporting, file service, GOOSE binding, controls, receiving-system acceptance, model correctness or IEC 61850 conformance. Those remain separate service-specific validations.
Can an MMS connection succeed while the data is still unusable?
Yes. A TCP connection or MMS association does not prove that the intended model was discovered or that a value has acceptable quality, timestamp and identity.
Can ARSAS discover an IED without an SCL file?
Yes when the IED permits live MMS discovery. SCL remains useful as configured intent and for integration comparison.
What should I check before moving to Reporting?
Confirm the correct IED identity, complete enough model discovery and at least one trustworthy read with a known object reference and Functional Constraint.
Next lesson
Move from one trustworthy read to continuous change delivery.
Learn how DataSets select signals, how BRCB and URCB deliver updates, how ARSAS validates exact coverage and why visible polling fallback is better than a hidden gap.
Verified stable release · ARSAS 1.6.33
Download the release-grade IEC 61850 workstation for Windows.
The current stable build includes Rev.3 IO List FAT import, an executive AS TESTED evidence report, a loaded Engineering/FAT workspace session, and direct receive-only GOOSE plus bounded SMV capture from each IED card.
Use the installer for a normal workstation, choose the portable single EXE for an approved no-install deployment, and verify the published SHA-256 before use.
What’s new, engineering boundaries and signing status →