---
title: "Checks in Problems"
---

# Checks in Problems

The 24 semantic rules the module runs on every SCL file of the workspace: references that must resolve, unique names, address clashes and the written form of addresses.

**State:** verified on the 292 public SCL files: each of the 448 findings in 87 files was read in its file and is a defect of the file, with no false finding. These are the Editor's checks, not a vendor tool's acceptance.

## What is checked

The **Problems** panel shows the faults of every SCL file in the workspace, with the source **IEC 61850 check**, on the start tag of the element they belong to. Each rule has a stable id, which is the code of the Problems entry. 24 rules cover:

- **References that must resolve:** the IED and access point a subnetwork connects; GOOSE and Sampled Values addresses to their control blocks; control blocks to their data sets; data set members; inputs to their IEDs, logical nodes and control blocks; logical nodes and templates to their types.
- **Names that must be unique.**
- **Address clashes on a subnetwork:** an IP address or a GOOSE address used twice.
- **The written form of addresses**, as warnings: IP, IP-SUBNET and IP-GATEWAY as four decimal numbers from 0 to 255; MAC-Address as six hexadecimal pairs with hyphens; APPID as four hexadecimal digits; VLAN-ID as three; VLAN-PRIORITY as 0 to 7.

A file that cannot be read is one error at the place of the problem.

A `.cid` or `.iid` file with one IED is checked as a CID: the references it makes to IEDs it does not carry are set apart rather than marked unresolved. Every other file gets every rule.

## Use the checks

1. Open the station folder. Problems fills for every SCL file; the status bar counts the errors and warnings.
2. Click an entry to open the file at the element.
3. Fix the file and save. Findings follow the file on disk; a file that is gone is cleared.

**Try it:** in an SCD with no findings, change `<P type="APPID">0001</P>` to `<P type="APPID">1</P>` and save. A warning appears on that line about the APPID.

## Examples from the public files

- A PCM600 SCD of 9 IEDs has three relays on one IP address; it is found.
- libiec61850 example files write `VLAN-ID` as `1`; it is flagged.
- No finding on the 21 PCM600 CIDs or the Siemens IEC 61850 System Configurator 7.20.50 SCD.

The IEC schema's keys and keyrefs confirmed the findings where they can say (logical node types, repeated templates); the others were confirmed against the rule of IEC 61850-6.

## Limits

- Problems come from the file on disk, so text not yet saved is not checked.
- A rule cannot be suppressed.
- There are no edition-specific rules.

## Not verified

- The rules follow IEC 61850-6 as understood here and are not yet checked against the standard's text, RiseClipse or any vendor tool.
- The false positive rate on DIGSI 5, SEL and Helinks files is unknown: the public files come from few vendor tools.
- Windows.

If the checks disagree with your configurator's own check on a file, follow your configurator and report the file and tool version.
