Home / Tools / IEC 61850 SCL viewer
IEC 61850 SCL viewer
Open the substation SCD or the CID of an IED and see who publishes and who subscribes to each GOOSE and sampled value stream, with their addresses, datasets and a consistency review. The file never leaves your computer.
IEC 61850-6SCL language, 2007B4 schemaIEC 61850-8-1GOOSEIEC 61850-9-2sampled values
Results
—
—
—
—
—
—
Want an engineer to review this case? Our team reviews your data and results and quotes the study or the settings work you need.
Charts
- Subscription by ExtRef (number of inputs)
- Only in the IEDName list
- Input with a problem
Calculation and details
File review
What it means
GOOSE and SV plan
| Type | Publisher / control block | Dataset | goID / smvID | Destination MAC | APPID | VLAN | Prio. | Subscribers | Review |
|---|
Control blocks: dataset and subscribers
Communication
IEDs, logical devices and logical nodes
Substation
Header and history
What it is for
To review an IEC 61850 configuration file without opening the manufacturer's engineering tool: see which IEDs there are, on which subnetwork and with which IP, what each one publishes by GOOSE or sampled values, with which MAC, APPID and VLAN, and which IED receives each message. Use it to prepare GOOSE tests, review the SCD delivered by an integrator or find why a signal does not arrive.
The sample SCD is synthetic, created by our team: a 115 kV line bay with a protective relay that publishes a trip GOOSE to the breaker merging unit, and a merging unit that publishes 4 currents and 4 voltages as sampled values to the relay. It validates against the SCL 2007B4 schema. You can download the .scd to try other programs.
How it is calculated
IEC 61850-6SCL 2007B4 schema
Reading the file. The XML is parsed with the element and attribute names of the SCL schema: Header, Communication (SubNetwork, ConnectedAP, GSE, SMV and their P parameters), IED (AccessPoint, Server, LDevice, LN0, LN, DOI, DataSet, FCDA, GSEControl, SampledValueControl, Inputs and ExtRef) and Substation (VoltageLevel, Bay, ConductingEquipment and LNode). The type templates (DataTypeTemplates) are not read.
VLAN = hexadecimal value of VLAN-ID (00A → 10)In SCL the VLAN-ID is written with three hexadecimal digits and the APPID with four; the MAC, with six octets separated by hyphens.
Who subscribes to each message
ExtRef (iedName, ldInst, prefix, lnClass, lnInst, doName, daName) ⊂ FCDA of the block datasetEach ExtRef of a subscribing IED is looked up in the publishing IED. If it has srcCBName (edition 2), it goes straight to that block and checks that the data is in its dataset. If not (edition 1), it searches for the GSEControl or SampledValueControl whose dataset contains the data: the logical device and logical node match, and the ExtRef data is inside the dataset member or contains it. A serviceType of Report or Poll is taken as an MMS read, not as GOOSE.
IEC 61850-8-1GOOSE and SVIEC 61850-9-2
Addresses. The address plan goes through the same rules as the GOOSE and SV address checker: MAC block 01-0C-CD-01 for GOOSE and 01-0C-CD-04 for SV, GOOSE APPID between 0x0000 and 0x3FFF and SV between 0x4000 and 0x7FFF, VLAN, priority and duplicates. It also checks that each access point IP is unique and that those on the same subnetwork are on the same IP network according to their mask.
Estimated size of a GOOSE
bytes ≈ 8 + PDU header (gocbRef, datSet, goID, counters) + Σ membersGOOSE travels in a single Ethernet frame and is not fragmented, so the PDU has to fit in the 1500-byte payload. Without the data types, each basic attribute is counted as 7 bytes (an encoded FLOAT32), quality q as 5, timestamp t as 10 and a whole data object as 24 (stVal, q and t). It is an upper estimate: the exact value comes from the manufacturer's tool.
Limits of the calculation
- It is a viewer and a consistency review, not a validation against the XSD schema or the capabilities of each IED.
- Without DataTypeTemplates it does not check that each data object or attribute exists in its type: dataset members and ExtRefs are resolved down to the logical node.
- In a CID or ICD it is normal for ExtRefs to point to IEDs that are not in the file: they are flagged as warnings for you to check in the SCD.
- ReportControl, LogControl and settings are not read. Substation functions and subfunctions are shown only if they sit inside a voltage level, bay or equipment.
- A very large SCD, tens of megabytes, can take a while to open on a phone.
Frequently asked questions
How do I open an SCD or CID file without the manufacturer's software?
Open this page, tap “Open SCL file” and choose the .scd, .cid, .icd, .iid or .ssd. The viewer reads the XML in your browser and shows the IEDs, the communication section, GOOSE and sampled values with their datasets and subscribers, and the substation if the file includes it. Nothing needs to be installed.
How do I find who subscribes to a GOOSE in an SCD file?
Subscribers are not in the GOOSE control block but in each receiving IED: they are the ExtRefs of its Inputs section. The viewer goes through every ExtRef, matches it against the datasets of each GSEControl and SampledValueControl and builds the publisher → subscriber matrix. The IEDName list of the block only says who it is intended for and may not match.
Is it safe to open my substation SCD here?
Yes. The file is read with FileReader and parsed with DOMParser inside your browser: the page does not send it to any server or store it. It is gone when you close or reload the page. The CSV you download is also generated on your computer.
We configure your IEC 61850 system
We engineer the SCD, assign addresses and VLANs, configure GOOSE, sampled values and reports in the IEDs and test each signal between publisher and subscriber. Remotely worldwide, or on site in Colombia and elsewhere on request.
