com.tom web-plc getting started extension: … of the integration into the web-plc is to expose...

com.tom WEB-PLC Getting Started V0.1 – Extension IEC 61850 and IEC 60870-5-104

Copyright © 2014 Beck IPC GmbH / NettedAutomation GmbH 2014-03-24 of 31

com.tom WEB-PLC Getting Started

Extension:

Integration of IEC 61850 and IEC 60870-5-104



TABLE OF CONTENTS

1 INTRODUCTION .................................................................................................. 3

2 SCOPE ................................................................................................................. 3

3 TOPOLOGY FOR EXAMPLES WITH IEC 60870-5-104 AND IEC 61850 ............ 4

3.1 TOPOLOGY OF THE VARIOUS EXAMPLE APPLICATIONS ............................................................. 4

4 EXTENSIONS FOR IEC 60870-5-104 .................................................................. 5

4.1 TOPOLOGY OF THE APPLICATION ........................................................................................... 5

4.2 GETTING STARTED ............................................................................................................... 5

4.3 SETTINGS FOR IEC 60870-5-104 ......................................................................................... 6

5 EXTENSIONS FOR IEC 61850 .......................................................................... 12

5.1 TOPOLOGY OF THE APPLICATION ......................................................................................... 12

5.2 GETTING STARTED ............................................................................................................. 12

5.3 SETTINGS FOR IEC 61850 ................................................................................................. 13

6 EXTENSIONS FOR IEC 61850 TO IEC 60870-5-104 GATEWAY ..................... 21

6.1 TOPOLOGY OF THE APPLICATION ......................................................................................... 21

6.2 GETTING STARTED ............................................................................................................. 21

6.3 SETTINGS FOR IEC 61850 ................................................................................................. 22

7 USING EXAMPLES TO EASY START ............................................................... 26

7.1 ICD, CID AND CUP FILES PROVIDED ................................................................................... 26

7.2 USE OF ICD, CID, AND CUP FILES ..................................................................................... 26

7.3 ICD AND CID FILES PROVIDED ............................................................................................ 27

8 WHERE TO GET FURTHER INFORMATION .................................................... 30

8.1 GETTING STARTED ............................................................................................................. 30

8.2 WEB-PLC HELP SYSTEM ................................................................................................... 30

8.3 UPDATES, TOOLS, DOCUMENTATION .................................................................................... 30

8.4 SUPPORT ........................................................................................................................... 30



1 Introduction This document will help you get started with WEB-PLC using signals exchanged by protocols like IEC 61850 and IEC 60870-5-104. The standard series IEC 61850 (Communication networks and systems for power utility automation) comprises mainly: Information Models (Logical Nodes and DataObjects), Configuration of a System, the Information and Communication used, and the Communication protocols. The standard series IEC 61400-25 (Communication networks and systems for power utility automation) is a extension IEC 61850. The WEB-PLC supports both standards with the MMS mapping. The WEB-PLC implements IEC 61850 Clients, Server, Publisher and Subscriber. The main purpose of the integration into the WEB-PLC is to expose information to be exchanged with other devices as input or output objects that can be used in the WEB-PLC Editor to receive and/or send data. The IEC 61850 inputs and outputs are automatically configured by an interpretation of the corresponding SCL files for the server and/or the client role. Notes:

1) The general application of the WEB-PLC needs to be understood before using the standards IEC 61850 and IEC 60870-5-104 integrated into the WEB-PLC (see “WEB-PLC Getting started document).

2) The application of the IEC 61850 requires a good understanding of the core standards of the IEC 61850 series.

3) In particular the understanding and use of the ICD and CID files for the client and server roles is a prerequisite of the integration of IEC 61850.

4) It is highly recommended to read the documents "com.tom WEB-PLC Getting Started with IEC 61850 and IEC 60870-5-104" and "The Beautiful Simplicity of the Integration of Modbus, DNP3, IEC 60870-5-104, and IEC 61850 into a powerful WEB-PLC operating on an Embedded Controller". You may also watch a video on the basics, the link could be found here: http://blog.iec61850.com/2014/03/iec-61850-at-hannover-messe-2014.html

5) It is recommended to start with the creation of a server role. Use the provided (original) example icd file. Any other icd file used need to be compliant to the SCL schema of IEC 61850-6 Ed1.

6) It is recommended to use two com.tom with the two SCL files provided: the (original!) example used for the server running on one com.tom and the example provided for the client running on the second com.tom.

2 Scope Currently the WEB-PLC software with integrated IEC 61850 and IEC 60870-5-104 is known to run on the following devices:

• com.tom BASIC 3.1 • com.tom BASIC 5.1 • com.tom M-BUS 1.1 • com.tom M-BUS 2.1 • com.tom M-BUS 3.1 • com.tom M-BUS 4.1 • com.tom M-BUS 6.1 • com.tom RADIO 2.1 • com.tom RADIO 7.1 • com.tom RADIO-UMTS 2.1



3 Topology for examples with IEC 60870-5-104 and IEC 61850

3.1 Topology of the various example applications The following examples use the depicted topology of two (2) com.tom devices as shown in the next figure:

Note that the IP addresses are as shown on the right side of the figure. The icd/cid files need to be configured with these addresses! The example are:

1) Using IEC 60870-5-104 2) Using IEC 61850 3) Using IEC 61850 to IEC 60870-5-104 Gateway

It is highly recommended to use these two com.tom to build the gateways. The corresponding icd/cid files and the two “.cup” files can be downloaded by the link provided in clause 7:



4 Extensions for IEC 60870-5-104

4.1 Topology of the application The topology uses a single com.tom to exchange the process information with the IEC 60870-5-104 server (controlled station):

The signals from the process are polled by the com.tom via Modbus polling from the Janitza UMG 604.

4.2 Getting Started The standard IEC 60870-5-104 (Telecontrol equipment and systems - Part 5-104: Transmission protocols - Network access for IEC 60870-5-101 using standard transport profiles) provides exchange of a wide range of messages for remote monitoring and control of processes. The messages carry mainly status information, measurements, counter values, configuration values and control information. Most of the steps explained in the above clauses are applicable as well for this extension. The signals exchanged with IEC 60870-5-104 are shown in the lists of Inputs and Outputs. They can be applied as shown before. The IEC 60870-5-104 connectivity is shown under the tap “IEC 60870-5-104 Server”:



Specific events on IEC 60870-5-104 will be listed here. Note: The Interoperability list for the IEC 60870-5-104 Server (controlled station) can be found here: http://com-tom.de/download/other/Functionality_IEC60870-5-104_V02.pdf

4.3 Settings for IEC 60870-5-104 The settings shown in the following figure are defined in the standard. The values have to be chosen according to the needs of an application.

http://com-tom.de/download/other/Functionality_IEC60870-5-104_V02.pdf



Maximum number of outstanding I format APDUs k and latest acknowledge APDUs (w)

Parameter Default value Remarks K 12 APDUs Maximum difference receive sequence number to send state W 8 APDUs Maximum difference receive sequence number to send state

Definition of time outs

Parameter Default value Remarks T0 30 s Time-out of connection establishment T1 15 s Time-out of send or test APDUs T2 10 s Time-out for acknowledges in case of no data messages T2 < T1 T3 20 s Time-out for sending test frames in case of a long idle state

Maximum range of values for all time-outs: 1 to 255 s, accuracy 1 s. Maximum range of values K: 1 to 32767 (215–1) APDUs, accuracy 1 APD Maximum range of values W: 1 to 32767 APDUs, accuracy 1 APDU (Recommendation: W should not exceed two-thirds of K).



New signals can easily be configured by using the Add button, adding a name, select an appropriate message type, set an information object address, range, interrogation group and cyclic transmission time:

Press OK to add the new Output message to the List:

The new WEB-PLC object is now listed.

The updated list needs to be loaded to the controller (push button OK) and then the WEB-PLC has to be rebooted:



Push Reboot Button:

After Reboot, the signals are available for building applications:



The following object “HELLO” can be used to send a spontaneous message on a change of the “Val”. The message could be received by an IEC 60870-5-104 master (Client, controlling station), e.g., QTester104.

The “HELLO” object is just inserted on the diagram to show the steps. The following diagram depicts a more useful application. The control of a fan heater and exposing the electrical measurements and calculated values are partly communicated with IEC60870-5-104:

Two signals are communicated: The “Direct-Fan-Status” and the “Direct-Fan-Power”:

The names and information object addresses are freely configurable.



The two signals can be received by the QTester104 as shown in the following figure:

The fan heater “5101” is ON. The measured power “5102” is 1.866,3 kW.



5 Extensions for IEC 61850

5.1 Topology of the application The topology uses a single com.tom to exchange the process information with the IEC 61850 server:

The signals from the process are polled by the com.tom via Modbus polling from the Janitza UMG 604. The com.tom plays an IEC 61850 server role. The IEC 60870-5-104.server is running in parallel.

5.2 Getting Started The standard IEC 61850 (Communication networks and systems for power utility automation) provides information models, information and system configuration, information exchange, and communication protocols. Most of the steps explained in the above clauses are applicable as well for this extension. The signals exchanged with IEC 61850 are shown in the lists of Inputs and Outputs. They can be applied as shown before. The IEC 61850 connectivity is shown under the tap “IEC 61850” as shown in the next figure.



Specific events on IEC 60870-5-104 will be listed here. Note: The PICS (Protocol Implementation Conformance Statement) and PIXIT (Protocol Implementation Extra Information for Testing) for the IEC 61850 Client and Server can be found here: http://www.com-tom.de/products.php?device=IEC 61850

5.3 Settings for IEC 61850 The settings of creating WEB-PLC objects like with IEC 60870-5-104 and Modbus is not required with IEC 61850. The Input and Output objects are automatically derived from the corresponding icd file of the com.tom (server). The button "Toggle expert settings" expands or collapses settings which are usually used for advanced users who know what they are doing and want to change the default configuration or diagnose malfunctions. If expert settings are deselected then the values of the Private Elements in the SCL file are hidden. In the expert mode they are visible (for the experts) that are familiar with the SystemCorp PIS10 Stack/API. This Stack/API is used in the com.tom.

http://www.com-tom.de/products.php?device=IEC%2061850.



Setting with expert mode open:



For the start select the Expert settings. The original icd file on the com.tom <<a:\web\upload\iec61850srv.icd>> (accessible by ftp the chip-tool) is used for the first example. You may check in the Expert settings if the Communication role is Server (only!) and the server file path is as shown above.

It is recommended to first produce a copy of the file (using, e.g., ftp of the chip tool) - just in case you need the original file later. The model of that file is shown to the right under "Server". The button "Expand all" opens the complete tree of the model. Note that the tree shows the data attributes with functional constraint FC=(ST, MX, CO, and SP) only. These are used as follows: ST and MX attributes are later exposed as Output objects at the WEB-PLC; CO and SP attributes as Input objects.

The next step is to "decorate" the (server) attributes that are intended to be used at the WEB-PLC. In the open tree or branch select an attribute with a check mark - you will see the check mark in a check box. If you select "stVal" then "q" and "t" will be selected as well.



When all needed attributes are selected click on "OK" below the expert settings area. The WEB-PLC incorporates the Private elements and assigns values for the five Fields. The Private fields are used internally at the API between the Stack and the Application.

The field values are a kind of pointer or binding between the model (a leaf) and the internal application. The values are automatically assigned by the WEB-PLC. They cannot be modified manually. The Names of the WEB-PLC objects derived from the icd file are built by the hierarchical names of the path from the IED name, LD instance, LN instance and DataObjects. After the loading is complete the com.tom needs to be rebooted (third button on top).

The Inputs and Outputs are now generated and listed (open the + Inputs and +Outputs). The names of the objects of the WEB-PLC are derived from the icd file, e.g., "PQSrvLDPQ/MMXU1.TotW.mag". The string "PQSrvLDPQ" is the LD Reference composed of "PQSrv" (IED Name) and "LDPQ" (Logical Device instance) according to IEC 61850-6. This object is an Output at the server's WEB-PLC. Note that the analogue values are scaled with a fixed factor of 10! These Input and Output objects are now available to be used at the WEB-PLC Editor (Diagram). A counter at the WEB-PLC can be connected to the Input "PQSrvLDPQ/MMXU1.TotW.mag" in order to emulate an active Power value.

This diagram increments the MMXU1.TotW.mag.i value every second by the value 1. The diagram needs to be

saved to the controller and



started.

In order to communicate with the server any standard conformant IEC 61850 client can be used. For example use the IEDScout from http://www.omicron.at. The IEDScout runs in demo mode - good enough for a first test. If the com.tom also supports an IEC 60870-5-104 Server (controlled station) then the Output objects of the 104 server can be connected with the Input objects of the IEC 61850 Server; and vice versa (to build gateways – see next clause). Using other icd files to generate servers requires to generate the icd file of the server with care:

1. The length of the reference in the server "LD/LN.DO. ..." must be less or equal 64 characters.

2. The maximal number of generated WEB-PLC objects from an icd file is 32. A branch of "stVal, q, t" generates one (1) WEB-PLC object.

The following diagram shows a simple application that could be used to control (on/off) the fan heater through Output 1 of the WEB-PLC.

Output 0 of the com.tom is connected to a relay that switches the fan heater on and off:



The Debug flags in the expert settings are defined as follows: Communication role Server, Client or both (start with selecting a server!) Client SCL file path Location of the file Server SCL file path Location of the file Debug flags DEBUG_READ_CALLBACK = 1,

DEBUG_WRITE_CALLBACK = 2, DEBUG_SELECT_CALLBACK = 4, DEBUG_OPERATE_CALLBACK = 8, DEBUG_CANCEL_CALLBACK = 16, DEBUG_UPDATE_CALLBACK = 32, DEBUG_RESOLVE = 64, DEBUG_POLL = 128, DEBUG_MMS_WRITE = 256, NO_MMS_WRITE = 512 Use one or more: 3 = READ/WRITE-Callback

Poll connection status [s] Check if connection is still open (in seconds Poll data objects [s]: Poll all data (in case com.tom plays client role) (in seconds) … selecting “1” (Read Callback at SystemCorp PIS10 API):

The read of the MMXU1.PhsV.PhsA is shown in the list of the Event Log:



The corresponding MMS read message is shown with the Wireshark:

… and the MMS read response message:



The analysis of the MMS messages with Wireshark is only required for diagnosis in case of technical issues. Sometimes it may be helpful to provide a trace of the messages to do trouble shooting.



6 Extensions for IEC 61850 to IEC 60870-5-104 Gateway

6.1 Topology of the application The topology uses two com.tom devices. The first is used to exchange the process information with the IEC 61850 server (IEC 61850 PQ Server). The second provides a gateway function between the underlying IEC 61850 Server and IEC 60870-5-104 (104 GW) OR IEC 61850 (GW, Proxy Server).

The signals from the process are polled by the com.tom via Modbus polling from the Janitza UMG 604.

6.2 Getting Started Most of the steps explained in the above clauses are applicable as well for this extension. The signals exchanged with IEC 61850 are shown in the lists of Inputs and Outputs. They can be applied as shown before. The specific add-on is that the Gateway approach requires a second device for implementing the Gateway. Note: In the case of a single com.tom, (the lower com.tom) we can build also some Gateway functionality. The com.tom is a Gateway between:

1. Modbus (client or master) and IEC 60870-5-104 (Server or controlled station), 2. Modbus (client or master) and IEC 61850 (Server), and 3. IEC 60870-5-104 (Server or controlled station) and IEC 61850 (Server)



6.3 Settings for IEC 61850 The only difference compared to the last clause is this: The com.tom implementing the gateway between an IEC 61850 PQ client and the 104 GW Server or IEC61850 GW (Proxy) Server is this: the IEC 61850 client needs a cid file that includes the IED section of the icd file used for the underlying IEC 61850 Server in the PQ Server. And it needs an icd file for the IEC 61850 Server (if a server is implemented as well). The settings of creating WEB-PLC objects like with IEC 60870-5-104 and Modbus is not required with IEC 61850. The Input and Output objects (for the client and the server roles) are automatically derived from the corresponding cid/icd files of the com.tom (server). The button "Toggle expert settings" expands or collapses settings which are usually used for advanced users who know what they are doing and want to change the default configuration or diagnose malfunctions. If expert settings are deselected then the values of the Private Elements in the SCL file are hidden. In the expert mode they are visible (for the experts) that are familiar with the SystemCorp PIS10 Stack/API. This Stack/API is used in the com.tom. Getting started with a first Client (in one com.tom) and a Server (in another com.tom) Note: The IEC Server with the original icd file of the above server example is used as the underlying device (com.tom). The second com.tom is playing the role as an IEC 61850 Client. The (original) icd file located at the second com.tom <<a:\web\upload\iec61850srv.icd>> is used by the client to automatically connect with the server, enable control blocks and receive report messages according to the configuration in the server icd file. This icd file is actually an cid file: it consits of the client information (mainly the client IP Address) AND the IED Section of the server device (underlying com.tom). For details on the cid files for clients see the standard part IEC 61850-6. The following figure depicts the icd file of the PQ Server and the cid file of the GW. The IEC element of the PQ Server is “copied” into the cid of the GW.

The GW knows by the information about the PQ Server which DataSets and Report Control Blocks are configured. The IEC 61850 client automatically connects to the PQ Server and enables all Report Control Blocks (without human intervention).



For the start select the Expert settings. The original icd file of the underlying server com.tom <<a:\web\upload\iec61850srv.icd>> is used for server as done above. You may check in the Expert settings if the Communication role is Server AND Client (!) and both file paths are shown.

The “decoration” of the model with the five Private fields is done in the same way as above described. The result is a list of Input and Output objects of the WEB-PLC as shown in the next figure. The client can communicate to two (2) servers: PQSrv and DK61.



It is recommended to first produce a copy of the client and server files (using, e.g., ftp of the chip tool) - just in case you need the original file later. The model of the client file is shown at the left under "Client". The button "Expand all" opens the complete tree of the model. Note that the tree shows the data attributes with functional constraint FC=(ST, MX, CO, and SP) only. The server from the underlying server is shown on the right. The tree shows the following: ST and MX attributes are later exposed as Input objects at the WEB-PLC; CO and SP attributes as Output objects. Note that the inputs at the server become outputs at the client !! A status value (FC=ST) is seen by the WEB-PLC of the client com.tom (this is the second decive) as an Input - coming from an underlying device (which has the IEC 61850 server). The next step is to "decorate" the (client) attributes that are intended to be used at the WEB-PLC. In the open tree or branch select an attribute with a check mark - you will see the check mark in a check box. If you select "stVal" then "q" and "t" will be selected as well. When all needed attributes are selected click on "OK" below the expert settings area. The WEB-PLC incorporates the Private elements and assigns values for the five Fields. The Private fields are used internally at the API between the Stack and the client Application. After the loading is complete the com.tom needs to be rebooted (third button on top). The Inputs and Outputs are now generated and listed (open the + Inputs and +Outputs). The names of the objects of the WEB-PLC are derived from the icd file, e.g., "PQSrvLDPQ/MMXU1.TotW.mag". The string "PQSrvLDPQ" is the LD Reference composed of "PQSrv" (IED Name) and "LDPQ" (Logical Device instance) according to IEC 61850-6. This object is an Input at the client's WEB-PLC. Note that the analogue values are scaled with a fixed factor of 10! These Input and Output objects are now available to be used at the WEB-PLC Editor (Diagram). Example application:



If this second com.tom (with the client role) also supports an IEC 60870-5-104 Server (controlled station) then the Output objects of the 104 server can be connected with the Input objects of the IEC 61850 Client; and vice versa.An IEC 61850 Server is also included in the above example. Using other IEC 61850 server devices require to handle the icd file of the server to build the cid file of the client of the second com.tom!

1. The length of the reference in the server "LD/LN.DO. ..." must be less or equal 64 characters.

2. The maximal number of generated WEB-PLC objects from an icd file is 32. A branch

of "stVal, q, t" generates one object.

3. DataSets with analogue members have to be FCDAs (e.g., ...mag.i, FC=MX) - in this beta version of using the PIS10 as a client.



7 Using examples to easy start

7.1 ICD, CID and CUP files provided All documents referred to in this clause can be downloaded from the following website at http://www.com-tom.de/products.php?device=IEC 61850

7.2 Use of ICD, CID, and CUP files The following figure shows the use of the three scl files for the examples. Note: It is highly recommended to start with the examples provided before any modification of the scl files or the diagrams (logic) is implemented. The two devices are as follows:

The PQ Server (Address .51) and the GW (Address .31) are visible and accessible with the Chiptool.




The corresponding files for the examples are:

1. CUP192.168.178.31 CUP192-168-178-31.cup 2. CUP192.168.178.51 CUP192-168-178-51.cup 3. CID192.168.178.31-Client (1) iec61850cli.icd 4. CID192.168.178.31-Server (2) iec61850srv.icd 5. CID192.168.178.51-Server (3) iec61850srv.icd

The file names for the SCL files are shown after the Use the file names when files are uploaded to the device or cup files are used for the update: Note: the IP addresses may be changed to match the subnet in which they are used. Make sure that the corresponding scl files apply the modified addresses!

7.3 ICD and CID files provided All five documents referred to in this clause can be downloaded from the following link: <<icd-cid-cup_61850_2014-03-24.zip>> available at the following page (Download): http://www.com-tom.de/products.php?device=IEC 61850

The first example that uses only the PQ Server (.51) needs only the following two files CUP192.168.178.51 CUP192-168-178-51.cup CID192.168.178.51-Server (3) iec61850srv.icd




Saved Files:

The scl files (1), (2), and (3) used are depicted in the following figure:



The two cup files are for the corresponding devices with the addresses (.31) and (.51). After updating the com.tom with the corresponding cup files the diagrams and signals should be visible: 1. com.tom Gateway Server (192.168.178.31) 2. com.tom PQ Server (192.168.178.51)

Both diagrams are further discussed in the above clauses.



8 Where to get further information

8.1 Getting Started All software referred to in this document can be downloaded from the Getting Started website at http://www.beck-ipc.com/gettingstarted.

8.2 WEB-PLC help system The WEB-PLC features a help system, which you can open by clicking on the help icon. The help system provides more detailed information on the editor, the settings and the various I/O bus systems.

8.3 Updates, tools, documentation Regularly check out the com.beck website at http://www.beck-ipc.com/combeck for

• Firmware updates • Useful tools • Further documentation

8.4 Support If you need support please… 1. Check our support website at http://www.beck-ipc.com/support. 2. Visit our forum at http://forum.beck-ipc.com . Here you will find a lot of answers to

customer problems and you can also add your own ideas and questions. 3. Contact our support at [email protected]. Of course you may also contact us by

phone. But please use email if possible. This not only reduces the time you spend on the phone, it also allows us to easily manage the questions and identify problem areas.

http://www.beck-ipc.com/gettingstarted

http://www.beck-ipc.com/combeck

http://www.beck-ipc.com/support

http://forum.beck-ipc.com/

mailto:[email protected]



Copyright © 2000-2011 BECK IPC GmbH All rights reserved

No part of this document may be copied or reproduced in any

form or by any means without the prior written consent of

BECK IPC GmbH. The information in this document is subject

to change without notice. Devices sold by BECK IPC GmbH

are covered by warranty and patent indemnification

provisions appearing in BECK IPC GmbH Terms and

Conditions of Sale only.

BECK IPC GmbH MAKES NO WARRANTY, EXPRESS,

STATUTORY, IMPLIED OR BY DESCRIPTION,

REGARDING THE INFORMATION SET FORTH HEREIN OR

REGARDING THE FREEDOM OF THE DESCRIBED

DEVICES FROM INTELLECTUAL PROPERTY

INFRINGEMENT. BECK IPC GmbH MAKES NO

WARRANTY OF MERCHANTABILITY OR FITNESS FOR

ANY PURPOSE.

BECK IPC GmbH shall not be responsible for any errors that

may appear in this document. BECK IPC GmbH makes no

commitment to update or keep current the information

contained in this document.

Life critical applications - BECK products are not authorized

for use as critical components in life support devices or

systems unless a specific written agreement pertaining to

such intended use is executed between the customer and

BECK prior to use. Life support devices or systems are those

which are intended for surgical implantation into the body, or

which sustain life, and whose failure to perform, when

properly used in accordance with instructions for use provided

in the labelling, can be reasonably expected to result in

significant injury to the user. BECK IPC GmbH customers

using or selling these products for use in such applications do

so at their own risk and agree to fully indemnify BECK IPC

GmbH for any damages resulting from such application.

Right to make changes - Beck IPC GmbH reserves the right

to make changes without notice in the products, including

software, described or contained herein in order to improve

design and/or performance. Beck IPC GmbH assumes no

responsibility or liability for the use of any of these products.

com.tom web-plc getting started extension: … of the integration into the web-plc is to expose...

Documents