Collect four facts.
- The approved IED IP address
- The subnet mask and required gateway or route
- Whether IEC 61850 MMS service is enabled on TCP port 102
- Permission to connect from this engineering workstation
Practical · approximately 15 minutes · read-only first connection
Connect an IEC 61850 IED by IP address without guessing.
This tutorial takes you from network preparation to one trustworthy live value. The goal is not merely a green “Connected” indicator—the goal is to prove which IED answered, what model it exposed and whether the observed data carries usable quality and time context.
Start read-only.
Discovery and live monitoring should be separated from active control. Do not operate a breaker, change RCB configuration or modify the IED unless the procedure, authority and rollback plan explicitly permit it.
Step-by-step
From IP address to one attributable value.
Confirm the target and authority
Record the IED name, IP address, bay or function, expected vendor/model and the approved purpose of the connection. This prevents a successful connection to the wrong device from being treated as success.
Prepare the Windows network interface
Use an address in the approved subnet, or an approved routed path. Avoid changing plant network settings by trial and error. Keep the original adapter configuration so it can be restored.
Separate ping from IEC 61850 service
Ping can prove basic IP reachability, but MMS uses TCP port 102. A device may answer ping while the service is disabled, blocked by a firewall or unavailable to your client.
Open ARSAS and choose General IEC 61850 Testing
Select Add IED, then enter a clear device name, the approved IP address and TCP port 102 unless the project explicitly uses another endpoint.
Connect and wait for live discovery
ARSAS establishes the MMS association and reads the server model. Do not judge success only from the TCP connection; confirm that Logical Devices, Logical Nodes, Data Objects and DataSets are actually discovered.
Read one point correctly
Choose a familiar indication or measurement. Check the IED identity, full IEC reference, current value, quality, device timestamp and acquisition source. Capture diagnostics before changing anything when one field is missing or unexpected.
Successful first connection
You should be able to answer six questions.
Which IED answered? Which object was read? What was the value? Was its quality acceptable? When did the IED say it changed? How did ARSAS obtain the value—direct read, report or polling?
What the result means
Connection, discovery and trustworthy data are three different milestones.
TCP connection
The network path reached a service endpoint. It does not yet prove the intended IED model or permissions.
MMS association and discovery
The server accepted the association and exposed a navigable IEC 61850 model.
Trustworthy observation
A known point returned a plausible value with understandable quality, timestamp and identity.
Repeatable acquisition
Reporting or bounded polling delivers continued observations with visible source and diagnostics.
If it fails
Use the symptom to choose the next check.
No ping
Check cable, VLAN, subnet, route, duplicate IP and the approved network boundary.
Ping works, port 102 fails
Check MMS enablement, firewall, ACL, service endpoint and whether another interface is intended.
Port 102 works, association fails
Capture the exact diagnostic. Check server limits, authentication or access policy, edition behavior and concurrent client restrictions.
Discovery works, data looks wrong
Verify you selected the right object and Functional Constraint. Compare configured SCL intent with the live model and inspect quality.
Should I use ping as the only connection test?
No. Ping checks basic IP reachability. IEC 61850 MMS requires TCP port 102, a successful association and a usable server model.
Can I connect without an SCL file?
Yes when the IED permits live discovery. SCL remains valuable as configured intent and for integration comparison.
What is the safest first data point?
Choose a familiar read-only indication or measurement whose expected state can be independently confirmed. Avoid active controls during the first connection.
Next lesson
Move from one value to continuous change delivery.
After discovery and a trustworthy read, learn how DataSets, BRCB and URCB let the IED send selected changes and how ARSAS keeps the acquisition source visible.
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 →