|
| 1 | +The `Communication` section in a SCL file allows to specify the network, its access points as well as the configuration of each of the access points. |
| 2 | + |
| 3 | +It has as children at least one `SubNetwork`. It can be configured through the child element `BitRate`. Each `SubNetwork` can have multiple `ConnectedAP` elements, which are pointers to IEDs `AccessPoint` - attributes `iedName` and `apName`. Each `ConnectedAP` has one `Address` element and that has as many `P` elements as there are settings for this particular access point. A `P` element is structured as followed: |
| 4 | + |
| 5 | +```xml |
| 6 | +<P type="IP">192.168.210.122</P> |
| 7 | +``` |
| 8 | + |
| 9 | +The `type` attribute defines the setting type and the inner text (here 192.168.210.122) of the element defines the setting value. There are various other optional setting types defined and OpenSCD supports to set those: |
| 10 | + |
| 11 | +- IP |
| 12 | +- IP-SUBNET |
| 13 | +- IP-GATEWAY |
| 14 | +- OSI-TSEL |
| 15 | +- OSI-SSEL |
| 16 | +- OSI-PSEL |
| 17 | +- OSI-AP-Title |
| 18 | +- OSI-AP-Invoke |
| 19 | +- OSI-AE-Qualifier |
| 20 | +- OSI-AE-Invoke |
| 21 | +- OSI-NSAP |
| 22 | +- VLAN-ID |
| 23 | +- VLAN-PRIORITY |
| 24 | +- SNTP-Port |
| 25 | +- MMS-Port |
| 26 | +- DNSName |
| 27 | +- UDP-Port |
| 28 | +- TCP-Port |
| 29 | +- C37-118-IP-Port |
| 30 | +- IPv6 |
| 31 | +- IPv6-SUBNET |
| 32 | +- IPv6-GATEWAY |
| 33 | +- IPv6FlowLabel |
| 34 | +- IPv6ClassOfTraffic |
| 35 | +- IPv6-IGMPv3Src |
| 36 | +- IP-IGMPv3Sr |
| 37 | +- IP-ClassOfTraffic |
| 38 | + |
| 39 | +Each is backed up with pattern check against the pattern defined in the schema (2007B4). |
| 40 | + |
| 41 | +A very typical `Communication` section might look like this: |
| 42 | + |
| 43 | +```xml |
| 44 | +<SubNetwork type="8-MMS" name="Stationbus" desc="Subnetwork"> |
| 45 | + <BitRate unit="b/s" multiplier="M">10</BitRate> |
| 46 | + <ConnectedAP iedName="AA1E1Q04MU" apName="AP1"> |
| 47 | + <Address> |
| 48 | + <P type="IP">192.168.210.142</P> |
| 49 | + <P type="IP-SUBNET">255.255.255.0</P> |
| 50 | + <P type="IP-GATEWAY">192.168.210.1</P> |
| 51 | + <P type="OSI-PSEL">00000001</P> |
| 52 | + <P type="OSI-SSEL">0001</P> |
| 53 | + <P type="OSI-TSEL">0001</P> |
| 54 | + <P type="OSI-AP-Title">1,3,9999,23</P> |
| 55 | + <P type="OSI-AE-Qualifier">23</P> |
| 56 | + </Address> |
| 57 | + </ConnectedAP> |
| 58 | + <ConnectedAP iedName="AA1E1Q02BCU" apName="AP1" redProt="prp"> |
| 59 | + <Address> |
| 60 | + <P type="IP">192.168.210.121</P> |
| 61 | + <P type="IP-SUBNET">255.255.255.0</P> |
| 62 | + <P type="IP-GATEWAY">192.168.210.1</P> |
| 63 | + <P type="OSI-PSEL">00000001</P> |
| 64 | + <P type="OSI-SSEL">0001</P> |
| 65 | + <P type="OSI-TSEL">0001</P> |
| 66 | + <P type="OSI-AP-Title">1,3,9999,23</P> |
| 67 | + <P type="OSI-AE-Qualifier">23</P> |
| 68 | + </Address> |
| 69 | + </ConnectedAP> |
| 70 | +</SubNetwork> |
| 71 | +``` |
| 72 | + |
| 73 | +> NOTE: in addition to the namespace `xmlns="http://www.iec.ch/61850/2003/SCL"` SCL files can have `xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"` as well that allows to faster parse a SCL file for communication type configuration. A `P` type element that can look like this: |
| 74 | +
|
| 75 | +```xml |
| 76 | +<P xsi:type="tP_IP" type="IP">192.168.210.122</P> |
| 77 | +``` |
| 78 | + |
| 79 | +In OpenSCD you can configure the |
| 80 | + |
| 81 | +- [SubNetwork](https://github.com/openscd/open-scd/wiki/Subnetwork) |
| 82 | +- [ConnectedAP](https://github.com/openscd/open-scd/wiki/ConnectedAP) |
0 commit comments