SIPROTEC 1 Communication Module 2 DNP3 IP 3 4 5 6 · 2016. 11. 21. · SIPROTEC, Communication...

C53000-L2040-C354-1

SIPROTECCommunication ModuleDNP3 IP

Communication Profile

com_dnpip_profile_us.book Page 1 Thursday, February 16, 2012 8:51 AM

Preface

Contents

Characteristic of the DNP3 IP Module 1Configuration in DIGSI 4 2Scaling and Thresholds for Transmission 3Time Synchronization 4DNP3 IP Diagnosis for EN100-Module 5Technical Data 6Index


NOTEFor your own safety, please observe the warnings and safety instructions contained in this document.

Disclaimer of Liability

This document has been subjected to rigorous technical review before being published. It is revised at regular intervals, and any modifications and amendments are included in the subsequent issues. The content of this document has been compiled for information purposes only. Although Siemens AG has made best efforts to keep the document as precise and up-to-date as possible, Siemens AG shall not assume any liability for defects and damage which result through use of the information contained herein.

This content does not form part of a contract or of business relations; nor does it change these. All obligations of Siemens AG are stated in the relevant contractual agreements.

Siemens AG reserves the right to revise this document from time to time.

Document Release: C53000-L2040-C354-1.00Edition: 02.2012Product version: V1.00

Copyright

Copyright © Siemens AG 2012. All rights reserved. The disclosure, duplication, distribution and editing of this document, or utilization and communication of the content are not permitted, unless authorized in writing. All rights, including rights created by patent grant or registration of a utility model or a design, are reserved.

Registered Trademarks

SIMATIC®, SIMATIC NET®, SIPROTEC®, DIGSI®, SICAM®, SIMEAS®, SINAUT® , OSCOP®, and DAKON® are registered trademarks of SIEMENS AG. An unauthorized use is illegal.

All other designations in this document can be trademarks whose use by third parties for their own purposes can infringe the rights of the owner.


Preface

Purpose of this manual

This manual describes the communication profile of the SIPROTEC Communication Module with DNP3 IP.

Target group

Protection engineers, commissioning engineers, persons who are involved in setting, testing and service of protection, automation, and control devices, as well as operation personnel in electrical plants and power sta-tions.

Scope of validity of this manual

This manual is valid for the SIPROTEC Communication Module with DNP3 IP.

Further support

Should further information be desired or should particular problems arise which are not covered sufficiently for the purchaser's purpose, the matter should be referred to the local Siemens representative.

Hotline

Our Customer Support Center provides around-the-clock support.

Phone: +49 (180) 524-7000Fax: +49 (180) 524-2471Internet: http://www.siprotec.come-mail: [email protected]

Training courses

If you are interested in our current training program, please contact our training center:

Siemens AGSiemens Power Academy TD

Humboldtstr. 59

D-90459 NurembergGermany

Phone: +49 (911) 433-7415Fax: +49 (911) 433-7929e-mail: [email protected]: www.siemens.com/energy/power-academy

3SIPROTEC, Communication Module, Communication ProfileC53000-L2040-C354-1, Edition 02.2012

Preface


Notes On Safety

This manual does not constitute a complete catalog of all safety measures required for operating the equipment (module, device) in question, because special operating conditions may require additional measures. However, it does contain notes that must be adhered to for your own personal safety and to avoid damage to property. These notes are highlighted with a warning triangle and different keywords indicating different degrees of dan-ger.

DANGERDanger means that death or severe injury will occur if the appropriate safety measures are not taken.

✧ Follow all advice instructions to prevent death or severe injury.

WARNINGWarning means that death or severe injury can occur if the appropriate safety measures are not taken.

✧ Follow all advice instructions to prevent death or severe injury.

CAUTIONCaution means that minor or moderate injury can occur if the appropriate safety measures are not taken.

✧ Follow all advice instructions to prevent minor injury.

NOTICENotice means that damage to property can occur if the appropriate safety measures are not taken.

✧ Follow all advice instructions to prevent damage to property.

NOTEis important information about the product, the handling of the product, or the part of the documentation in ques-tion to which special attention must be paid.

4 SIPROTEC, Communication Module, Communication ProfileC53000-L2040-C354-1, Edition 02.2012

Preface


Qualified Personnel

Commissioning and operation of the equipment (module, device) described in this manual must be performed by qualified personnel only. As used in the safety notes contained in this manual, qualified personnel are those persons who are authorized to commission, release, ground and tag devices, systems, and electrical circuits in accordance with safety standards.

Use as Prescribed

The equipment (device, module) must not be used for any other purposes than those described in the Catalog and the Technical Description. If it is used together with third-party devices and components, these must be recommended or approved by Siemens.

Correct and safe operation of the product requires adequate transportation, storage, installation, and mounting as well as appropriate use and maintenance.

During the operation of electrical equipment, it is unavoidable that certain parts of this equipment will carry dan-gerous voltages. Severe injury or damage to property can occur if the appropriate measures are not taken:

• Before making any connections at all, ground the equipment at the PE terminal.

• Hazardous voltages can be present on all switching components connected to the power supply.

• Even after the supply voltage has been disconnected, hazardous voltages can still be present in the equip-ment (capacitor storage).

• Equipment with current transformer circuits must not be operated while open.

• The limit values indicated in the manual or the operating instructions must not be exceeded; this also refers to testing and commissioning


Preface




Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1 Characteristic of the DNP3 IP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.2 Identification of Module and Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.3 Supported DNP3 IP Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.4 Table of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.5 DNP3 IP Networking Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1.6 Buffered Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

1.7 File Transfer/Reading of Fault Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1.8 Further Ethernet Services and Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

1.8.1 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

1.8.2 DNP3 IP with IEC 61850 and GOOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2 Configuration in DIGSI 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.1 Inserting and Adjusting of a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.2 Setting the Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.3 Customization of the Allocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3 Scaling and Thresholds for Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.1 Measured Value Scaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2 Measured Value Threshold Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.3 Counter Value Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4 Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.2 Time Synchronization with DNP3 IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5 DNP3 IP Diagnosis for EN100-Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5.1 HTML Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.2 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.3 DNP3 IP Error Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

6 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

6.1 Technical Data of EN100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63


Contents




1 Characteristic of the DNP3 IP Module

1.1 General 10

1.2 Identification of Module and Firmware 12

1.3 Supported DNP3 IP Object Types 13

1.4 Table of Parameters 15

1.5 DNP3 IP Networking Parameters 17

1.6 Buffered Events 18

1.7 File Transfer/Reading of Fault Records 19

1.8 Further Ethernet Services and Protocols 23



1.1 General


1.1 GeneralWith the EN100 module firmware DNP3 IP from version V1.00, the Ethernet-based DNP3 IP protocol is imple-mented in addition to other transmission protocols (e.g. IEC 61850 and GOOSE, see chapter 1.7) in the 100 Mbit Ethernet module EN100.

The required settings are made using the DIGSI 4 parameterization software from version 4.85.

Detailed information on the EN100 module and the IEC 61850 engineering is given in the manuals:

• German edition: Handbuch Ethernetmodul EN100, Bestellnr. C53000-G1100-C167-x

• US-english edition: Manual Ethernet Module EN100, order no. C53000-G1140-C167-x

Abbreviations are used in the following text:

• for 100-MBit Ethernet module EN100: EN100

• for DNP3 IP over the internet protocol suite: DNP3 IP

Application

Figure 1-1 shows an application example of the SIPROTEC devices with DNP3 IP and GOOSE in an installa-tion where DNP3 IP is used for communication to a substation controller and GOOSE for inter-device data ex-change.

Fig. 1-1 Application Communication

NOTERefer to your device manual to find out whether the device you are using supports the DNP3 IP protocol.

NOTEFor the configuration of DNP3 IP a DIGSI 4 packet is required with IEC 61850 station configurator.

SIPROTEC Device 1

EN100 Module(DNP3 IP Outstation

and GOOSE)RJ4

5

SIPROTEC Device 2

RJ4

5

Ethernet Switch RJ4

5R

J45

RJ4

5

Substation Controller

DNP3 IP Master RJ4

5

DNP3 IP

GOOSE

RJ4

5

...

SIPROTEC Device n

RJ4

5

GOOSE


and GOOSE)


and GOOSE)



1.1 General


Documents for DNP3 IP

All relevant information on DNP3 IP is contained in the following documents:

• DNP3Spec-V1-Introduction-20071215.pdf

• DNP3Spec-V2-Part1-ApplicationLayer- 20090315.pdf

• DNP3Spec-V2-Part2-ApplicationLayer- 20090315.pdf

• DNP3Spec-V2-Part3-ApplicationLayer-20071215.pdf

• DNP3Spec-V2-Sup1-SecureAuthentication-20100317.pdf

• DNP3Spec-V3-TransportFunction-20070203.pdf

• DNP3Spec-V4-DataLinkLayer-20070203.pdf

• DNP3Spec-V5-LayerIndependent-20071215.pdf

• DNP3Spec-V6-Part1-ObjectLibraryBasics-20071215.pdf

• DNP3Spec-V6-Part2-Objects-20090315.pdf

• DNP3Spec-V6-Part3-ParsingCodes-20090420.pdf

• DNP3Spec-V7-IPNetworking-20070711.pdf

• DNP3Spec-V8-Apdx1-DeviceProfile-20100223.pdf

• DNP3Spec-V8-Interoperability-20090611.pdf

For more information, go to http://www.dnp.org.

Bus Mapping Documents

You can download the bus mapping document for each device type at the following address:

http://siemens.siprotec.de/download_neu/index_e.htm

The bus mapping documents describe the data objects available via DNP3 IP.

Example: Manual SIPROTEC Feeder Automation Controller 7SC80, order number C53000-L2040-C353

Accessories

Table 1-1Ethernet Patch Cable (double shielded (SFPT), LAN connector plugs on both sides)

Cable Length Order No.

0.5 m 7KE6000-8G-D00-0AA5

1.0 m 7KE6000-8G-D00-1AA0

2.0 m 7KE6000-8G-D00-2AA0

3.0 m 7KE6000-8G-D00-3AA0

5.0 m 7KE6000-8G-D00-5AA0

10.0 m 7KE6000-8G-D01-0AA0

15.0 m 7KE6000-8G-D01-5AA0

20.0 m 7KE6000-8G-D02-0AA0



1.2 Identification of Module and Firmware


1.2 Identification of Module and Firmware

Modulinfo Menu

Available on HMI display or via WebMonitor:

✧ Select Enter → Test/Diagnosis → Modulinfo → Port B (or Port F in 7SC80)

shows e.g. module type, communication protocol, network settings

Fig. 1-2 Modulinfo

Modul type:• EN100 - EN100 module with electrical Ethernet interface

• EN100_O - EN100 module with fiber-optical Ethernet interface

Communication protocol:• IEC61850 - IEC 61850/GOOSE

• DNP3 IP - DNP3 IP with IEC61850/GOOSE option (see chapter 1.8.2)

MLFB/Version Menu

Available on HMI display or via WebMonitor:

✧ Select Enter → Settings → Setup/Extras → MLFB/Version, then scroll down twice

shows the version number of the firmware on EN100 module

Fig. 1-3 MLFB/Version (Note: Modul F in 7SC80)

HTML page of the EN100 module

Refer to chapter 5.1.

• If DNP3 IP firmware is loaded then the menu DNP IP is available in the navigation pane.

• The firmware version is shown on the button of the homepage.

NOTEAlways the firmware identifcation IEC61850 is shown here, also when DNP3 IP firmware is loaded.



1.3 Supported DNP3 IP Object Types


1.3 Supported DNP3 IP Object TypesThe DNP3 IP interface of the SIPROTEC device supports the following object types:

Table 1-2 Supported DNP3 IP Object Types

ObjectNumber

VariationNumber

Object Description

01 2 Binary Input with Status Object 01, variation 2 describe the state of a digital input channel or internal software informa-tion.They are also used during a general interroga-tion.

02 2 Binary Input Change with Time

Object 02, variation 2 describe the changes of a digital input channel or of internal software infor-mation with the associated change time. The binary input changes are used for spontaneous process events.

10 2 Binary Output with Status Object 10, variation 2 describe the status of a binary output channel.They are also used during a general interroga-tion.The control relay output block (see object 12) controls the binary output channels.

12 1 Control Relay Output Block Object 12, variation 1 are used for commands for the process or for setting up internal functions.

20 1 32-bit Binary Counter(with flag)

Object 20, variation 1 describe the state of metered values and pulse counters.They are also used during a general interroga-tion.

22 1 32-bit Counter ChangeEvent without Time

Object 22, variation 1 describe the change of metered values and pulse counters.

30 1 32-bit Analog Input(used for 32-bit statistic values)

Object 30, variation 1 describe the state of statis-tic values, DIGSI 4 data type VI (Value Indica-tion).They are also used during a general interroga-tion.

30 2 16-bit Analog Input(used for measured values)

Object 30, variation 2 describe the state of mea-sured values, DIGSI 4 data type MV, and min/max values, DIGSI 4 data type MVT (Measured Value with Time).They are also used during a general interroga-tion.

32 1 32-bit Analog ChangeEvent without Time

Object 32, variation 1 describe the change of sta-tistic values, DIGSI 4 data type VI (Value Indica-tion).



1.3 Supported DNP3 IP Object Types


32 2 16-bit Analog ChangeEvent without Time

Object 32, variation 2 describe the change of measured values, DIGSI 4 data type MV, and min/max values, DIGSI 4 data type MVT (Mea-sured Value with Time).

50 1 Time and Date Write function:The time and date object are used for time syn-chronization.

Read function:Read the system time of the device.Date and time are displayed in milliseconds from January 1, 1970-01-01 00:00:00.000 UTC.

60 1 Class 0 Data With these objects different classes of informa-tion elements can be read:• The class 0 contains all static data.

• The classes 1 to 3 contain groups of events from information elements.

• The data from class 1 has the highest prior-ity, followed by class 2 and class 3.

60 2 Class 1 Data

60 3 Class 2 Data

60 4 Class 3 Data

70 3 File Command Transfer of fault record files.

70 4 File Command Status

70 5 File Transfer

70 6 File Transfer Status

70 7 File Descriptor

80 1 Internal Indications Write the value 0 to index 7 leads to reset of the bit DEVICE_RESTART in the flag byte for all data objects. Writing to index 4 resets the NEED_TIME bit.

Table 1-2 Supported DNP3 IP Object Types (cont.)

ObjectNumber

VariationNumber

Object Description



1.4 Table of Parameters


1.4 Table of ParametersThe following DNP3 IP-specific configuration parameters are available in the SIPROTEC device (i.e. in the DNP3 IP mapping file, see chapter 2).

Table 1-3 DNP3 IP-Specific Parameters

Parameter DefaultSetting

SettingRange

Description

OutstationAddress 1 0 to 65519 DNP3 IP station address of the device

MasterAddress1 100, 101 0 to 65519 DNP3 IP station addresses of the DNP3 IP masters on both TCP con-nectionsMasterAddress2

ValidateMasterAddress 0 0 = no1 = yes

Specify whether or not to validate the source address (master address) in received DNP3 IP frames. If it is dis-abled, a DNP3 IP master only is identified on Ethernet level by its IP address.

ApplConfirmTimeout 5.0 s 0.1 to 3600.0 s(in 100 ms steps)

Specify how long the DNP3 IP out-station will wait for an application layer confirmation from the DNP3 IP master. In combination with Unsol-RetryDelay (see below) this deter-mines how frequently an unsolicited response will be sent.

EnableUnsolResp 0 0 = unsolicited responses are not configured, and can never be enabled by the master

1 = unsolicited responses are configured, and must be specifically enabled by the master after an initial unsolicited response.

Determines whether unsolicited re-sponses are allowed.

UnsolClass1MaxEvents 5 1 to 100 For each class of change events (class 1, class 2, and class 3), this controls a condition under which an unsolicited response will be sent: If the number of events in each class meets or exceeds this value, an un-solicited response will be sent.

UnsolClass2MaxEvents

UnsolClass3MaxEvents



1.4 Table of Parameters


UnsolClass1MaxDelay 5.0 s 0.0 to 3600.0 s(in 100 ms steps)

For each class of change events (class 1, class 2, and class 3), this controls a condition under which an unsolicited response will be sent: If the time after an event meets or exceeds this value, even if just 1 event occurs, an unsolicited re-sponse will be sent.

UnsolClass2MaxDelay

UnsolClass3MaxDelay

UnsolRetryDelay 5.0 s 0.0 to 3600.0 s(in 100 ms steps)

Specifies the time to delay after an unsolicited confirm time-out (see Ap-plConfirmTimeout) before retrying the unsolicited response.

UnsolMaxRetries 3 1 to 65535 Specify the maximum number of un-solicited retries in case of no re-sponse from DNP3 IP master.

SelectTimer 3.0 s 0.1 s to 60.0 s Specifies the maximum amount of time that a select will remain valid before the corresponding operate is received.

Table 1-3 DNP3 IP-Specific Parameters (cont.)

Parameter DefaultSetting

SettingRange

Description

NOTEThe settings above are valid for all TCP connections in the same way; they are not configurable individually per TCP connection or connected DNP3 IP master.

During startup of the Ethernet module it is checked whether all DNP3 IP parameters are configured in their valid ranges given in table 1-4 and table 1-3. If a parameter value is detected outside the valid range, an error log entry is issued on the EN100 module and the parameter is set to its default value (see figure 5-1).



1.5 DNP3 IP Networking Parameters


1.5 DNP3 IP Networking ParametersFor the IP networking services, the following configuration parameters are available in the SIPROTEC device (i.e. in the DNP3 IP mapping file, see chapter 2):

Table 1-4 DNP3 IP Networking Parameters

Parameter Description Range Default Setting

TcpPortNumber1TcpPortNumber2

The TCP ports to listen on.Port numbers must be different.If both port numbers are equal, only one DNP3 IPserver is started, i.e. only one TCP connec-tion is available.

10000 to 65535 2000020001

TcpMasterIpAddr1TcpMasterIpAddr2TcpMasterIpAddr3TcpMasterIpAddr4TcpMasterIpAddr5

List of IP addresses to accept TCP connections from.

All entries = *.*.*.*:accept connection from any TCP client.

At least one entry is not = *.*.*.* andone or more entries = *.*.*.*:entries with *.*.*.* are ignored.

XXX.XXX.XXX.XXXwith XXX = 0 to 255

special value *.*.*.*:see description column

*.*.*.**.*.*.**.*.*.**.*.*.**.*.*.*

ApplKeepAliveTimeout Reload value for the keep-alive timer to monitor the status of an active TCP connection on DNP3 IP appli-cation layer level. The keep-alive timer is restarted whenever a message is received from the master.If the timer times out, the device (DNP3 IP outstation) transmits a Data Link Layer status request which must be responded by the master or the connection is assumed to have broken down and will be closed.

0 = timer is disabled

0.1 s to 3600.0 s in 100 ms steps

20.0 s

EnableDnpTimeSynch Determines whether the device (DNP3 IP outstation) expects and evaluates time synchronization from DNP3 IP master (see chapter 4.2).

0 = device does not expect time synchroni-zation from DNP3 IP master

1 = device expects time synchronization from DNP3 IP master

0 (dis-abled)

DnpTimeSynchMaster Determines in case of two connected DNP3 IP clients which one acts as time master for the time synchroni-zation via DNP3 IP.

If only one client is connected, then this one also is time master.

0 = the client which wasconnected first

1 = client connected to DNP3 IP server 1 (with TcpPortNumber1)

2 = client connected to DNP3 IP server 2 (with TcpPortNumber2)

1

DnpTimeSynchAsUTC Acc. to "Time Synchronization" in DNP3 IP Spec. Vol. 5, the time for DNP3 IP time synchronization shall (since Jan. 1st, 2008) correspond to Universal Coor-dinated Time, UTC.

This setting is used to support DNP3 IP clients which send time synchronization in local time but should normally remain unchanged to default value.

0 = DNP3 IP time syn-chronization with local time

1 = DNP3 IP time syn-chronization with UTC

1



1.6 Buffered Events


1.6 Buffered EventsMaximum number of buffered events (these values are fixed):

Table 1-5 Buffered Events

Event Numbers Note

Binary Input change:DNP3 IP Object 2

100as sequence of events

All changes will be entered in the event list, also multiple events from the same data object. In case of overflow, the internal indication IIN2.3 bit EVENT_BUFFER_OVERFLOW is set and the oldest event is lost. This internal indication remains set and is reported to the DNP3 IP master until there is again storage in the event buffer for at least one event.

Counter change:DNP3 IP Object 22

10most recent events

If a data object changes multiple times without the previ-ous event being sent, then a new event will overwrite the value already stored in the event list.

Analog Input change:DNP3 IP Object 32

50most recent events

NOTENote that the Analog Input change includes measured values, DIGSI 4 data type MV, min/max values, DIGSI 4 data type MVT (Measured Value with Time), both as 16-bit Analog Change Events and statistic values, DIGSI 4 data type VI (Value Indication), as 32-Bit Analog Change Events.



1.7 File Transfer/Reading of Fault Records


1.7 File Transfer/Reading of Fault RecordsFault records from the device can be read using the file transfer feature of DNP3 IP (DNP3 IP object number 70 (file identifier), see table 1-2). The fault records are converted on the EN100 module to Comtrade format.

For reading a fault record, the following steps must be executed:

✧ Open the directory file of available fault records which are available using DNP3 IP object 70, variation 3 (open file), e.g.:

✧ The DNP3 IP outstation responds with DNP3 IP object 70, variation 4 (response).

✧ If no fault records are available, the returned file size is zero, otherwise it is different from zero, e.g.:

With this response, a file handle is returned → File(0x44495220).

✧ If the file size returned in the previous response is different from zero, read the directory file using DNP3 IP object 70, var. 5 (read file). If a file size of zero was returned, then immediately close the file.

File read:

NOTEThe DNP3 IP Protocol Test Harness software from Triangle Microworks was used as DNP3 IP test master for the examples.

NOTEThe file name must be “.” or “\” in order to open the directory.





And interpret the response as file information (a read of a directory returns file directory information data):

Close the file using DNP3 IP object 70, var. 4 (close file), e.g.:

Which is confirmed with:

✧ In the DNP3 IP master the file selection after directory read could look like this:

Fig. 1-4 Select File Name on Remote Device to Read

NOTEIt can be seen here that for each fault record two files are available, a *.cfg and a *.dat, as it is usual for Comtrade.





The time of creation matches the fault record creation in the device.

But the file size of the fault record files cannot be determined correctly during directory read from device and is only a rough estimation.

✧ Open, read and close the file(s) of interest, e.g. the file “00210021.cfg”:

Open request and response:

Read request and response:

Close request and response:

The read file now is available in the DNP3 IP master and the next file can be read.

After that, the fault record Comtrade file can be evaluated, e.g. with the “SIGRA 4 – Fault Evaluation Software” from Siemens.

NOTEThe conversion to Comtrade is only executed when the file is opened for reading and then the final file size is known.





NOTEData processing on the EN100 module after an “open File” command requires an amount of time in order to prepare a file for reading or convert it to Comtrade format.

After receiving the “open File” command, the DNP3 IP outstation immediately responds with a Null Response and later, if data processing is finished, sends the response to the “open File” command as a Class 3 event to the DNP3 IP master.

Poll for events after “open File” command is sent or wait for an unsolicited event.

The values in the .dat file are in binary Comtrade format.



1.8 Further Ethernet Services and Protocols


1.8 Further Ethernet Services and ProtocolsThe following additional services and protocols are supported on the EN100 module. With DIGSI 4 this services can be switched ON or OFF. Unused services shall be switched OFF for security reason.

1.8.1 Services• Module homepage (HTTP)

• Firmware upgrade (HTTP)

• DIGSI 4 over EN100

• SNMP V2 (see chapter 5.2)

• IEC 61850 and GOOSE

• SNTP (see chapter 4.2)

For more information, please refer to the following manual:

Ethernet Module EN100 for IEC 61850 with electrical/optical 100 Mbit Interface,Order number C53000-G1140-C167

1.8.2 DNP3 IP with IEC 61850 and GOOSEThe communication DNP3 IP with IEC 61850 and GOOSE is represented in the following figure:

Fig. 1-5 DNP3 IP with IEC 61850 and GOOSE

7SJ80V4.64.xx

DNPiGOOSE

IEC61850

EN100

7SC80/7SJ80

DNP3 IPGOOSE

IEC 61850

EN100

PAS 1 IEC 61850

PAS 2 IEC 61850

PC IEC-Browser

DNP Master 1

DNP Master 2

SNTP

HTTP

7SJ80V4.64.xx

DNPiGOOSE

IEC61850

EN100DNP3 IPGOOSE

IEC 61850

EN100

EthernetGOOSE

GOOSE16 Datasets

7SC80/7SJ80

SNMP V2Client



1.8 Further Ethernet Services and Protocols




2 Configuration in DIGSI 4

2.1 Inserting and Adjusting of a New Project 26

2.2 Setting the Interfaces 31

2.3 Customization of the Allocations 33



2.1 Inserting and Adjusting of a New Project



✧ Open DIGSI Manager.

✧ Click File → New...The New Project dialog opens.

Fig. 2-1 Dialog New Project

✧ Enter a name for the new project (7SC80_XX in the example) and select the storage location (path). Next click OK.

Fig. 2-2 DIGSI Manager with a New Project

NOTEIn order to configuration the DNP3 IP protocol, the device functions must have been parameterized correctly. For detailed information in this context, please see chapter 1.1 (Prerequisites at DIGSI 4) and refer to theDIGSI 4 manual.

NOTEThe following configuration is shown for the 7SC80. Other relays, e.g. 7SJ80, are to be set in the same way.





✧ Right-click Folder and open the Device Catalog via Insert New Object → SIPROTEC device.

Fig. 2-3 DIGSI Manager with an Object Selected

✧ Select the desired device in the Device Catalog (7SC feeder automation/7SC802/V4.0 in the example) and copy the object into the Folder of the DIGSI Manager window via Drag&Drop.

Fig. 2-4 Device Catalog

The MLFB tab of Properties - SIPROTEC device dialog opens (see figure 2-5).





✧ Configure the order number (MLFB) of your device in the Properties - SIPROTEC device dialog and press the OK button.

Fig. 2-5 Configuring the Order Number (MLFB)

✧ If you have retrofitted the device or if you want to install the DNP3 IP protocol afterwards, you have to activate the DNP3 IP protocol on the tab Communication modules → List item 11. Port F (Communication Interface) → Selection L:.. → Additional Information dialog.

Fig. 2-6 Activating the DNP3 IP Protocol

✧ Click the OK button.





✧ Right-click Folder and insert an IEC61850 station via Insert New Object → IEC61850 station.

An IEC61850 station is inserted in DIGSI Manager.

Fig. 2-7 Inserting an IEC61850 Station

✧ In DIGSI Manager, right-click IEC61850 station and select the Object properties… menu item.

✧ Select a device from the Available IEC61850 devices in the Properties - IEC61850 station dialog → Communicator tab and click Add.

The selected device is moved from the Available IEC61850 devices window into the IEC61850 station communicator window.

Fig. 2-8 Selection in the Communicator






✧ Double-click the SIPROTEC device in DIGSI Manager.

The Open device dialog opens.

✧ Activate the option Offline in the Connection type section and confirm with OK.

Fig. 2-9 Opening the SIPROTEC Device

After initialization the following window opens:

Fig. 2-10 Select Functions



2.2 Setting the Interfaces


2.2 Setting the Interfaces✧ Double-click the function Settings.

The following windows opens.

Fig. 2-11 Settings

✧ Double-click the function Interfaces.

The Interface Settings dialog opens.

✧ Select the Additional protocols at device tab.

Fig. 2-12 Mapping File Selection an Bus Specific Parameters



2.2 Setting the Interfaces


List Box Mapping File

If no mapping file is currently assigned to the SIPROTEC device then the following entries are available in the list box “Mapping file”:

The following entries can be selected at an already existing mapping file assignment:

If the mapping file assignment was changed for a SIPROTEC device, then this is in general connected with a change of the routing of the SIPROTEC objects to the system interface.

Please, check after choice of a new mapping file the allocations to column Destination or Source in the DIGSI configuration matrix.

To activate and change the protocol DNP3 IP, proceed as follows:

✧ Activate the mapping file DNP3 IP standard mapping 3-1 in the list box Mapping file.

✧ If necessary, change the entries in the Module-specific settings dialog according to your device configuration.


Table 2-1 Selection without Modul-specific Settings

Selection Meaning

<none> No mapping file is assigned to the device.

DNP3 IP standard mapping 3-1 toDNP3 IP standard mapping 3-n

Selection of a mapping file 3-1 to 3-n (n = device type dependent number of standard mappings).

Table 2-2 Selection with Modul-specific Settings

Selection Meaning

<none> No mapping file is assigned to the device.

<see modul-specific settings> This selection indicates the currently to the device assigned mapping file with the changes of bus specific parameters already carried out in the edit area “Module-specific settings”.Number and version of the mapping file have to betaken from the first line in the edit area "Module-specific settings".

DNP3 IP standard mapping 3-1 toDNP3 IP standard mapping 3-n

New) Selection of a mapping file 3-1 to 3-n(n = device type dependent number of standardmappings). All bus specific parameters are reset todefault values.

NOTEThe mapping file is factory-set, but you can adapt it to your device configuration.

NOTEPlease, edit only the numbers in the rows which do not start with “//” and note the semicolons at the end of the line.

Editing anything else in the Module-specific settings may cause an error when closing the Interface Settings dialog.



2.3 Customization of the Allocations


2.3 Customization of the Allocations✧ Double-click the function Masking I/O (Configuration Matrix) in the dialog Settings acc. to figure 2-11.

The windows Setting Masking I/O opens:

Fig. 2-13 DIGSI 4 Configuration Matrix with Columns for System Interface Routing

✧ Move the cursor in the columns Source and Destination over port F and determine the column assigned to DNP3 IP (marked in red in figure 2-13).

The used protocol is displayed (text in a yellow box) if you stop for a short while on the letter F.

✧ If necessary, adapt the default routing in the configuration matrix to your SIPROTEC device/installation as follows. If you do not want to change anything in the DIGSI routing matrix, continue with the section Time Synchronization.

✧ If you want to delete all default routings to set new default routings, right-click the corresponding port F or the system interface S in Source or Destination. Then, click the query Delete configurations at Port F or Delete configurations at System Interface.

A dialog appears with the information that a deletion is not possible or with the confirmation about how

Sourcesystem interface system interface

DestinationInformationtype

Port FDNP3 IP

system interface

Port FDNP3 IP

system interface

NOTEAnother port instead of port F can be displayed as Source and Destination of the system interface, for exam-ple, port B for SIPROTEC 4 devices.

NOTEIf you do not want to display all columns and rows in the configuration matrix for the setting of the system in-terface or for your information, you can minimize these columns and rows by double-clicking the corresponding button. If you want to enter values to the minimized columns, you can maximize these columns again by dou-ble-clicking the corresponding button.





many entries can be deleted or cannot be deleted. Confirm this information with OK:

Fig. 2-14 Indications for Delete

The identification whether an information is routed on system interface (DNP3 IP) is shown in the columns Source and Destination, port F, system interface S in the DIGSI configuration matrix.

A cross ('X') in this column indicates the associated information as "routed on system interface"(see figure 2-13).

Source System Interface

The SIPROTEC object can be controlled via DNP3 IP. This is possible for the following information types (col-umn Type in configuration matrix):

• IntSP Internal single-point indication (tagging)

• IntDP Internal double-point indication (tagging)

• SC/DC Single control/Double control without feedback from process

• SF/DF Single control/Double control with feedback from process

Destination System Interface

The value of the SIPROTEC object is transmitted to the DNP3 IP master. This is possible for the following in-formation types:

• SP Single-point indication

• DP Double-point indication

• Out Output annunciation

• IntSP Internal single-point indication (tagging)

• IntDP Internal double-point indication (tagging)

• MV Measured value

• MVMV Power meter (metered measurand, source is a measured value)

• PMV Pulse (metered measurand, source is a pulsed binary input)





To add or remove an information to Source or Destination of system interface set/reset the cross ('X') in the associated column of the DIGSI configuration matrix (pop-up menu when pressing the right mouse button).

Fig. 2-15 Pop-up Menu in Column Destination F/S

Fig. 2-16 Error Message

NOTE• The maximum number of routable objects of an information type varies according to the chosen mapping

file. If e.g. a measured value not routed in the mapping file per default shall be transferred via DNP3 IP, then first a measured value already routed has to be removed from system interface so that the position gets available in the DNP3 IP message.

• An error message (see figure 2-16) is shown if all routing possibilities of an information type are occupied and if it is nevertheless tried to route an information of this type.





Adding an Allocation

Adding an allocation requires (in addition to the identification in the system interface column of the DIGSI con-figuration matrix) the selection of the position of the information in the DNP3 IP message as well as the defini-tion of scaling values for measured values (scaling of measured values see chapter 3).

Therefore after adding the allocation, the Object properties dialog window which is used to define the mes-sage position of the information is opened automatically (property sheets for source: Protocol info - Source F; property sheets for destination: Protocol info - Destination F and Measured value - Destination F).

Fig. 2-17 Definition of the Position of an Information in the DNP3 IP Message

NOTE• The information type of double commands for routing as Source system interface depends on the infor-

mation type of the associated checkback indication.

Only double commands with a double-point indication as checkback indication can be routed to the positions in the DNP3 IP message which are reserved for double commands according to the bus mapping.

Double commands with a single-point indication as checkback indication or without checkback indication are treated via DNP3 IP like single commands and must be routed to the positions reserved for single commands.

• Commands without checkback indication can not be routed to Destination of system interface. Reading the state of these command types is not possible via DNP3 IP.





Change of an Existing Allocation

If an information already routed on system interface shall get another (empty) position in the DNP3 IP message, then the Object properties dialog (see figure 2-17) has to be selected (Properties ... in the pop-up menu when pressing the right mouse button in one of the columns Display text, Long text or Type of the DIGSI configu-ration matrix in the row which is associated to the information).

Fig. 2-18 Change of an Existing Allocation

Depending on the information type the following parameters are to select in the property sheetProtocol info - Source F, Protocol info - Destination F or Measured value - Destination F of the Object properties dialog:

Table 2-3 Protocol Info Source

Parameter Comments Info Types

Point index The index indicates the position in the DNP3 IP point list of Binary Outputs.

IntSP, IntDP, SC/DC, SF/DF

Flags Command properties (Latch ON/OFF, ... - depending on the object info type)

Table 2-4 Protocol Info Destination

Parameter Comments Info Types

Point index The index indicates the position in the DNP3 IP point list of Binary Inputs, Analog Inputs or Counters (depending on the object info type).

SP, DP, Out, IntSP,IntDP, MV, MVMV,PMV

DNP3 IP class Class of the DNP3 IP information object.





Measurement Conversion

Before transmission of a measured value via DNP3 IP a measurement conversion (scaling) must be executed in the SIPROTEC device.

Scaling

Scaling of a measured value to the format for the transmission via DNP3 IP means the definition of:

• Type

• Scaling factor

• Zero offset

Type

Decision, whether the measured value is transmitted as percentage value or whether a conversion shall take place into primary or secondary value before (depending on the measured value not all of these three possibil-ities are available, e.g. no secondary values for power values).

Threshold value

Changes of measured values are transmitted using DNP3 IP object 32 (Analog Change Event) only if the ac-cumulated change differences of the 16-bit analog input exceed the threshold value.

Scaling factor

The measured value in the SIPROTEC device (floating-point format) is multiplied by the scaling factor before transformation to an integer value. With that it is possible to transfer fractional digits by multiplication by a mul-tiple of 10 in the integer value.

Zero offset

The Zero offset is added to the result of the multiplication of the measured value in the SIPROTEC device (float-ing-point format) by the scaling factor.

The measured value in the integer format for transmission via DNP3 IP is calculated summarizing according to the following formula:

Measured valueInteger = Measured valueFloat * Scaling factor + Zero offset

in which "Measured valueFloat" is a percentage value or, if necessary, changed into primary value or second-ary value before (according to the definition of type).





Time Synchronization

✧ If the device requires time synchronization with NTP or DNP3 IP, double-click Time Synchronization.

The Time Synchronization & Time Format dialog opens.

✧ Select Ethernet NTP as the source in the field Source of time synchronization and set the desired parameters.

Fig. 2-19 Setting the Time Synchronization

✧ Confirm with OK.

✧ Close the SIPROTEC device and confirm that you want to save the modified data.

✧ Close the Report window.

✧ Double-click IEC61850 station in DIGSI Manager.

The DIGSI system configurator opens with the IEC61850 station application and Subnet1.

Fig. 2-20 DIGSI System Configurator - Subnet





✧ If necessary, change the name for Subnet1 in the Properties window (right window) and the parameters (e.g. IP start address, Subnet mask, Standard gateway).

✧ Click the SIPROTEC device and change its parameters in the Properties window (right window) (e.g. IP address, Subnet mask, Standard gateway).

Fig. 2-21 DIGSI System Configurator - SIPROTEC Device

✧ Close the DIGSI system configurator and confirm saving the IEC61850 station settings with OK.

✧ The following steps only have to be carried out if time synchronization via NTP or DNP3 IP is required; in case of time synchronization via NTP with a second, redundant NTP server these steps have to be carried out for two NTP servers:

− Right-click Folder and open the Import device dialog via Insert New Object → Other IEC61850 communicator.

− Search for the file sntp.icd in the DIGSI 4 folder and click OK.(Example (x = hard drive directory): x:\DIGSI4\Utilities\IEC61850\ICD\sntp.icd)

TEMPLATE is inserted in the DIGSI Manager window.

− Rename TEMPLATE to NTP Server.− In DIGSI Manager, right-click IEC61850 station and select the menu item Object properties...− Select a device from the Available IEC61850 devices in the Properties - IEC61850 station dialog

→ Communicator tab and click Add.The selected device is moved from the Available IEC61850 devices window into the IEC61850 station communicator window and click OK.

− Double-click on IEC61850 station in DIGSI Manager.The DIGSI system configurator opens with the IEC61850 station application.





− Drag & Drop the NTP server entered under New devices (1) into the Subnet1 folder.

Fig. 2-22 Integrating the NTP Server in Subnet1

− Click on NTP server and enter the IP address under Parameter in the Properties window (right window). If necessary, change subsequently the Subnet mask and the Standard gateway.

− Close the DIGSI system configurator and confirm saving the IEC 61850 station settings with OK.

Parameterizing the Device Functions

✧ Open the SIPROTEC device from the DIGSI 4 user interface.

✧ Enter all desired settings (see figure 2-11).

✧ Save the parameter set and subsequently close the device on the DIGSI 4 user interface.

Update the Parameter Sets of IEC 61850

✧ In DIGSI Manager, right-click IEC61850 station and select the menu item Object properties...

✧ In the Properties - IEC61850 station dialog box select the Update tab and update the parameter set using the Update all parameter sets button.

✧ Close the Report window and the Properties - IEC61850 station dialog box.

NOTEThese settings, e.g. protection settings, CFC charts and routing to binary inputs/outputs or LEDs, are described in the DIGSI 4 manual.

NOTETo activate the modified parameters, you have to update the parameter set after each time you have changed the settings in DIGSI Manager.





Initializing the SIPROTEC Device

✧ Right-click the SIPROTEC device in DIGSI Manager.

✧ Click Initialize device.... in the menu that opens.

✧ Adapt again the device settings in DIGSI 4 or the DNP3 IP settings in the mapping file if necessary.

✧ To transmit the device settings modified in DIGSI Manager to the SIPROTEC device, right-click the SIPROTEC device.

✧ Click DIGSI -> Device... in the menu that opens.

✧ Select the Connection type and the device in the Transfer the parameter set dialog.

NOTEThe SIPROTEC device only has to be initialized once when a new device has been added.



3 Scaling and Thresholds for Transmission

3.1 Measured Value Scaling 44

3.2 Measured Value Threshold Processing 46

3.3 Counter Value Scaling 47



3.1 Measured Value Scaling


3.1 Measured Value ScalingDepending on the rated values of the primary equipment of the installation (Vrated, Irated), the scaling of the measured values has to be adapted in order to ensure a correct transmission of these values in integer format (±32767) including implicit fractional digits.

Example with rated current: 120 A

Primary current values in SIPROTEC are then displayed in A.

For transmission with implicit one fractional digit a scaling factor of 10 must be used:

120 A then is transmitted as: 120 * 10 = 1200

Example with rated current: 1500 A

Primary current values in SIPROTEC are then displayed in kA.

For transmission with implicit 3 fractional digit a scaling factor of 1000 must be used:

1.5 kA then is transmitted as: 1.5 * 1000 = 1500

In addition to the scaling factor it has to be determined whether the measured value shall be transmitted as primary value, secondary value or percentage value (i.e. the measured value type).

For the scaling of a measured value, a scaling index in the conversion table has to be selected which is a com-bination of scaling value, threshold value and measured value type as shown in the following table with the default entries:

NOTEBy default, only primary values are used with DNP3 IP.

Table 3-1 Conversion Table for Measured Values with Default Entries

Scaling Index Scaling Factor Measured Value Type

Threshold Value (in%)

By Default Used for

0 10 Primary value 5 AC currents

1 100 Primary value 3 AC voltages

2 100 Primary value 10 Power

3 1000 Primary value 5 Power factor

4 100 Primary value 0.1 Frequency

5 10 Primary value 2 DC voltages

6 10 Primary value 2 Temperatures

7 100 Primary value 10 -



3.1 Measured Value Scaling


The scaling index also determines the threshold value for measured values.

Threshold value: Changes of measured values are transmitted using DNP3 IP object 32 (Analog Change Event) only if the accumulated change differences of the 16-bit Analog Input exceed the threshold value.

8 100 Percentage value 10 -

9 100 Percentage value 10 -

10 10 Secondary value 10 -

11 100 Secondary value 10 -

Table 3-1 Conversion Table for Measured Values with Default Entries (cont.)

Scaling Index Scaling Factor Measured Value Type

Threshold Value (in%)

By Default Used for



3.2 Measured Value Threshold Processing


3.2 Measured Value Threshold ProcessingThreshold processing is executed based on a combined fixed and integrated threshold method and based on relative thresholds related to the last transmitted value.

Relative thresholds related to the last transmitted valueThe threshold values are given in percent.

The absolute size of the threshold value in units of the measured value depends on the value last transmitted to the DNP3 IP master and is smaller for smaller values than for larger values.

Example for Configured Threshold Value: 10 %

Last transmitted value: 100 V

Current threshold in units: 10 V

If the last transmitted value was zero, a measured value change is transmitted immediately.

Fixed and integrated threshold methodFixed part

A measured value is immediately transmitted as Analog Input change event if the difference between the current value compared with the last transmitted value is larger than the configured threshold value (in positive or negative direction).

Integrated part

Change differences of the current value compared with the last transmitted value are summarized all 500 ms (without observing the sign of the change, only the change amount is summarized).

If this sum of differences exceeds a certain value (depending on the configured threshold value), the current value is also transmitted as Analog Input change event.

The following is valid as a reference:

− A change of a measured value to the amount of the threshold value is transmitted after 5 s.− A change of a measured value to half the amount of the threshold value is transmitted after 10 s.

NOTEThis is independent if the last value has been transmitted by a change event or by a value request from the DNP3 IP master, e.g. for General Interrogation.

NOTEUse an appropriate scaling of the measured value in order to avoid transmission of unnecessary changes around zero.



3.3 Counter Value Scaling



Scaling

The scaling of the metered measurands, which are derived from measured values, refers to:

60 000 impulses per hour for V = Vprim and I = Iprim

Vprim = Full Scale Voltage

(parameter address = 1101)

Iprim = Full Scale Current

(parameter address = 1102)

Example

The following is configured in the parameter set:

Iprim = 1000 A and Vprim = 400.0 kV

60 000 impulses correspond so that:

1 h * 1000 A * 400 kV * = 692.82 MWh

NOTE• The type of the update (cyclic, with or without deletion) and the update interval must be programmed for

the metered measurands with the parametrization software DIGSI 4.

• The scaling of the metered measurands at binary inputs Wp(puls) and Wq(puls) depends on the externally connected pulse generator.







4 Time Synchronization

4.1 General 50

4.2 Time Synchronization with DNP3 IP 50



4.1 General


4.1 GeneralDuring operation, SIPROTEC devices need the date and time for all time-relevant processes. The time syn-chronization is required to guarantee a uniform time basis for the communication with other devices and time stamping of the process data.

Chapter 2 describes the configuration of the time synchronization with DNP3 IP.

4.2 Time Synchronization with DNP3 IPDNP3 IP offers an own time synchronization from the DNP3 IP master to the DNP3 IP outstations using object number 50 var 1, see table 1-2.

During configuration of the SIPROTEC device in DIGSI 4, set the time synchronization parameters for time syn-chronization via DNP3 IP in same manner as for NTP (see figure 2-19):

• Source of time synchronization: Ethernet NTP

• Further time synchronization parameters (e.g. fault indication after): as required

The following DNP3 IP-specific parameters are relevant for time synchronization via DNP3 IP:

If DNP3 IP time synchronization is enabled, the DNP3 IP master shall perform time synchronization to the out-station periodically every 55 s to 61 s, because the time control algorithm in the SIPROTEC devices is based on a cyclical synchronization within this time period.

The accuracy of the time synchronization via DNP3 IP protocol is 5 ms when time telegrams are being received continuously in the interval stated above.

Additionally, the internal indication IIN1.4 bit NEED_TIME is set in a telegram to the DNP3 IP master if the de-vice needs time synchronization (is set all 60 s if no time synchronization message is received).

If two DNP3 IP clients are connected to the device, the parameter DnpTimeSynchMaster determines which client acts as time master. Time synchronization messages from the client which is not the time master are re-jected. The IIN1.4 bit NEED_TIME is only set in telegrams to the DNP3 IP client which is the time master.

Table 4-1 DNP3 IP-specific Parameters

Parameter Description

EnableDnpTimeSynch Determines whether the device (DNP3 IP outstation) expects and evaluates time synchronization from DNP3 IP master.

DnpTimeSynchMaster Determines in case of two connected DNP3 IP clients which one acts as time master for the time synchronization via DNP3 IP.If only one client is connected, this one is also the time master.

DnpTimeSynchAsUTC Acc. to "Time Synchronization" in DNP3 IP Spec. Vol. 5, the time for DNP3 IP time synchronization shall (since Jan. 1st, 2008) correspond to Universal Time Coordinated, UTC.This setting is used to support DNP3 IP clients which send time synchronization in local time but should normally remain unchanged to default value.

NOTEFor time synchronization with NTP or DNP3 IP, at least one NTP server must be configured in the IEC 61850 System Configurator (see figure 2-22)



4.2 Time Synchronization with DNP3 IP


The DNP3 IP-specific parameter EnableDNPTimeSynch determines whether NTP or DNP3 IP is used for time synchronization:

DNP3 IP time objects contain the number of milliseconds from the DNP3 IP time epoch, which is defined as 1970-01-01 00:00:00.000 UTC. Before transmitting internally from the EN100 to the SIPROTEC device, the local time correction factor that is configured for NTP time synchronization (and which contains the time zone and daylight saving time factors, see figure 2-19) is added; only if DnpTimeSynchAsUTC parameter is set to 1 (default).

Table 4-2 Time Synchronization Sources

Source Time Synchronization

Selection in DIGSI 4

NTP Server isConfigured in

Station Configurator

SettingEnableDNPTimeSynch

Result

Ethernet NTP Yes = 0: NTP is used Device is synchronized from NTP (no time requests with IIN1.4 to a DNP3 IP master and time telegrams from DNP3 IP master are reject-ed)

= 1: DNP3 IP is used Device is synchronized from DNP3 IP

Ethernet NTP No Not relevant No time synchronization(no time requests with IIN1.4 to a DNP master and time telegrams from DNP3 IP master are rejected)

Other thanEthernet NTP(e.g. IRIG B, GPS)

Not relevant Device is synchronized from the selected source (no time requests with IIN1.4 to a DNP3 IP master and time telegrams from DNP3 IP master are rejected)



4.2 Time Synchronization with DNP3 IP




5 DNP3 IP Diagnosis for EN100-Module

5.1 HTML Page 54

5.2 SNMP 57

5.3 DNP3 IP Error Indication 58



5.1 HTML Page


5.1 HTML PageEN100 has a homepage which you can open by entering the IP address of the device.

To open the HTML page, proceed as follows:

✧ Enter the IP address of the device in the browser according to the following rule:

http://IP address/home

Example: http://172.16.52.53/home

The EN100 homepage opens.

Fig. 5-1 EN100 Homepage

✧ In the navigation pane (menu on the left), click the entry DNP IP.

The DNP3 IP diagnosis page opens.

Fig. 5-2 DNP3 IP Diagnosis HTML Page



5.1 HTML Page


This page offers statistic data that are useful for communication diagnosis (e.g. telegram and error counters as well as the IP of the connected DNP3 IP master). Additionally, the main protocol-specific settings made during DNP3 IP configuration in the mapping file are shown and give an overview with which parameters DNP3 IP is running on the module.

The parameters displayed on the diagnosis page correspond to the DNP3 IP-specific parameters(see table 1-3) and the DNP3 IP networking parameters (see table 1-4).

Additional Remarks to Links

Clear statistics (link) Pressing this link resets all statistic values (telegram and error counters) to zero.

Update statistics (link) The HTML page is not updated automatically. Press this link to up-date the statistic values (all values will then be read again from the EN100 module)

Additional Remarks to Statistics and Parameters

Connected It is shown whether a DNP client is connected to this DNP server - “yes” or “no”- and additionally if time synchronization via DNP3 IP is executed, the text “Time synch.” shows which client acts as time master.

DNP Client IP address:Port IP address and TCP port number of the client which is currently con-nected to the server or was connected last to the server.

Enable DNP time synchronization The value “(yes)” is shown if on the one hand the parameterEnableDnpTimeSynch is set to 1, but on the other hand no NTP server is configured in the DIGSI system configurator.

- no: Enable DNP time synchronization = no

- yes: Enable DNP time synchronization = yes and NTP server is configured

- (yes): Enable DNP time synchronization = yes but no NTP server is configured



5.1 HTML Page


Fig. 5-3 EN100 Module - Connection/Security Log

NOTEThe entry Connection / Security log in the navigation pane (see figure 5-1) is also relevant for DNP3 IP.

The following events are entered:

• Establishing a new connection with a client (DNP3 IP master)

• Closing a connection

• Rejecting a connection (unknown IP address or server already connected)



5.2 SNMP


5.2 SNMPAll statistic data shown in the DNP3 IP diagnosis HTML page (see figure 5-2) are also available via SNMP. A special MIB file with the name “SipDnp.mib” exists for this purpose and is delivered together with the other MIB files for the EN100 module. The “SipDnp.mib” is contained in the “IEC61850 SNMP MIB V1.XX”.

MIB files package for SIPROTEC devices with EN100 can be downloaded from:

http://siemens.siprotec.de/download_neu/index_e.htm → All Documents for Communication → IEC 61850 - General information and descriptions → Tools and MIB-Files



5.3 DNP3 IP Error Indication



Display in DIGSI 4

For the DNP3 IP error indication the SysIntErr (Error System Interface) indication in the device is used. In the DIGSI Configuration Matrix this indication is available in the Protocol group.

Fig. 5-4 DNP3 IP Error Indication - Group Protocol in DIGSI 4

The following table shows the values and causes of the DNP3 IP error indication:

Table 5-1 Indication SysIntErr in DIGSI 4

Indication After Startup/Restart

Change ON to OFF Change OFF to ON

SysIntErr ON Changes to OFF when a client is connected to at least one of the DNP3 IP servers 1 or 2 with its configured TCP port num-bers.

Changes to ON when no clientsare connected to the DNP3 IP servers 1 or 2 any more.Refer to the ApplKeepAliveTimeout parameter in chapter 1.5 for connec-tion supervision to the DNP3 IP client.





Display in DIGSI 4 for EN100

Further general EN100 indications show the startup state of the EN100 module as well as Ethernet link status information:

Fig. 5-5 DNP3 IP Error Indication - EN100

Table 5-2 Indication SysIntErr from EN100

Indication After Startup/Restart

Change ON to OFF Change OFF to ON

Failure Modul ON Module is ready, startup se-quence via DPR successfully processed

Device or module reset/restart

Fail Ch1 ON Ethernet link on Ch1/Ch2 is es-tablished

Ethernet link on Ch1/Ch2 is lost

Fail Ch2 ON







6 Technical Data

6.1 Technical Data of EN100 62


6 Technical Data

6.1 Technical Data of EN100


6.1 Technical Data of EN100The following manuals contain a detailed list of the technical data of the EN100:

• German edition: Handbuch Ethernetmodul EN100, Bestellnr. C53000-G1100-C167-x

• US-english edition: Manual Ethernet Module EN100, order no. C53000-G1140-C167-x

Since EN100 modules are installed in SIPROTECT 4 devices, both the technical data of the EN100 and the technical data of the SIPROTEC 4 device used apply.



Index

AAdjusting the DNP3 IP parameters and the mapping 41Application 10

BBuffered Events 18Bus Mapping Documents 11

CCounter Value Scaling 47

DDNP3 IP Diagnosis for EN100-Module 53DNP3 IP Object Types 13DNP3 IP with IEC 61850 and GOOSE 23DNP3 Networking Parameters 17Documents for DNP3 11

EEthernet Services and Protocols 23

FFile Transfer 19File Transfer/Reading of Fault Records 19

HHTML Page 54

IInitializing the SIPROTEC 4 device 42

MMeasured Value Scaling 44Measured Value Threshold Processing 46

PParagraph formats 62Parameterization 25Parameterizing the device functions 41Parameters 15

RReading of Fault Records 19

SScaling for Transmission 43SNMP 57

TThresholds for Transmission 43Time Synchronization 49Time Synchronization with DNP3 IP 50

UUpdate the Parameter Sets of IEC 61850 41


Index



Date post:	08-Mar-2021
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times