Configuration Tool for COM581 - library.e.abb.com · PDF fileDNP3 Master Measurement .....30 1 . ABB Switzerland Ltd 1KHA005021-UEN Extension ... Command Authority overview.....42

p

1KHA005021-UENAdditional for

1MRB520184-Uen

Edition August 2006

CAP581 Configuration Tool for COM581 Extension for Version 6.2 Software Manual

© 2006 ABB Switzerland Ltd

Baden/Switzerland

1st Edition

Applies for software version V6.2 All rights with respect to this document, including applications for patent and registration of other industrial property rights, are reserved. Unauthorized use, in particular reproduction or making available to third parties without our explicit consent in writing, is prohibited. The use is only allowed for the purpose laid down in the contract. This document has been carefully prepared and reviewed. Should in spite of this the reader find an error, he is requested to inform us at his earliest convenience. The data contained herein purport solely to describe the product and are not a warranty of performance or characteristic. It is with the best interest of our customers in mind that we constantly strive to improve our products and keep them abreast of advances in technology. This may, however, lead to discrep-ancies between a product and its “Technical Description” or “Software Manual”.

1KHA005021-UEN Extension for CAP581 V6.20 ABB Switzerland Ltd

Table of Contents

1. PURPOSE .................................................................................. 4

2. ABREVIATIONS ......................................................................... 4

3. CAP581 VERSION 6.20 EXTENSION – OVERVIEW................. 4 3.1. General changes and deviation to the manual CAP581 ............. 4 3.2. Two protocols on one CPU ......................................................... 5 3.2.1. Port configuration........................................................................ 7 3.2.1.1. IMP CPU (Master) ...................................................................... 7 3.2.1.2. CIM CPU (Slave) ........................................................................ 8 3.2.2. Configuration example ................................................................ 8 3.3. Excel configuration changes ....................................................... 9 3.3.1. New flags added ......................................................................... 9 3.3.2. Security in Excel ......................................................................... 9 3.4. DNP Master .............................................................................. 10 3.4.1. Serial line properties ................................................................. 10 3.4.1.1. Specific properties .................................................................... 10 3.4.2. Application properties ............................................................... 11 3.4.2.1. Specific properties .................................................................... 12 3.4.2.2. Communication properties ........................................................ 13 3.4.2.3. Counter properties .................................................................... 15 3.4.2.4. Spares properties ..................................................................... 16 3.4.3. DNP RTU Configuration............................................................ 17 3.4.4. DNP RTU Configuration properties........................................... 17 3.4.4.1. Address..................................................................................... 17 3.4.4.2. Analog properties...................................................................... 18 3.4.4.3. Binary properties....................................................................... 19 3.4.4.4. Measurement properties ........................................................... 20 3.4.4.5. Event properties........................................................................ 21 3.4.5. Data point configuration ............................................................ 22 3.4.5.1. Structure object for DNP3 Master data point ............................ 22 3.4.5.2. Insert new object....................................................................... 23 3.4.5.3. Delete object............................................................................. 24 3.4.5.4. Remove Link............................................................................. 24 3.4.6. DNP30 Master integrated iotals ................................................ 24 3.4.6.1. Address properties.................................................................... 24 3.4.6.2. Spare properties ....................................................................... 25 3.4.6.3. Cnt Spare properties................................................................. 26 3.4.7. DNP30 Master indications ........................................................ 26 3.4.7.1. Specific properties .................................................................... 27 3.4.7.2. Address properties.................................................................... 28 3.4.7.3. Spare properties ....................................................................... 29 3.4.7.4. IndSpare properties .................................................................. 29 3.4.8. DNP3 Master Measurement ..................................................... 30

1

ABB Switzerland Ltd 1KHA005021-UEN Extension for CAP581 V6.20

3.4.8.1. Address..................................................................................... 30 3.4.8.2. Spare properties ....................................................................... 31 3.4.8.3. Measurand Spare properties .................................................... 31 3.4.9. DNP3 Master Step Position Information ................................... 32 3.4.10. DNP3 Master Sequence of Events ........................................... 32 3.4.11. DNP3 Master System Diagnosis............................................... 32 3.4.12. DNP3 Master System Control................................................... 32 3.4.13. DNP3 Master Transparent Data ............................................... 32 3.4.14. DNP3 Master Maintenance Information .................................... 32 3.4.15. DNP3 Master Command........................................................... 32 3.4.15.1. Specific properties .................................................................... 33 3.4.15.2. Address properties.................................................................... 34 3.4.15.3. Spare properties ....................................................................... 35 3.4.15.4. Command Spare properties...................................................... 35 3.4.15.5. DNP3 Master Command Transparent Data .............................. 36 3.5. Redundant gateway with redundant lines ................................. 36 3.5.1. System overview....................................................................... 36 3.5.2. Redundancy types .................................................................... 37 3.5.2.1. Gateway redundancy type 1 ..................................................... 37 3.5.2.2. Gateway redundancy type 2 ..................................................... 38 3.5.2.3. Gateway redundancy type 3 ..................................................... 38 3.5.2.4. Gateway redundancy type 5 - 10 .............................................. 38 3.5.2.5. Gateway redundancy type 4 ..................................................... 38 3.5.3. Restrictions ............................................................................... 39 3.6. Redundant gateway configuration ............................................ 40 3.6.1. COM581 Redundancy properties ............................................. 40 3.7. Redundancy minor error ........................................................... 41 3.8. Command Authority Handling (CA)........................................... 42 3.8.1. CA for IEC 61850 (per IED) ...................................................... 42 3.8.1.1. Command Authority overview ................................................... 42 3.8.1.2. Requirements in SCD file for CA .............................................. 43 3.8.2. CA for LON (per COM581) ....................................................... 45 3.8.2.1. Command Authority overview: .................................................. 45 3.8.2.2. Command Authority configuration............................................. 46 3.8.2.3. COM581 with two LON cards ................................................... 47 3.8.2.4. LON card (first): subnet: 1, node: 110....................................... 47 3.8.2.5. LON card(second): subnet: 2, node: 111 .................................. 48 3.8.2.6. COM581 with three LON cards................................................. 48 3.9. Redundant serial line within one COM581................................ 52 3.9.1. Requirement for IEC101 protocol ............................................. 52 3.9.1.1. Specific serial line properties .................................................... 53 3.10. Redundant serial line with two COM581’s ................................ 53 3.10.1. General description................................................................... 53 3.10.2. Line properties .......................................................................... 54 3.10.2.1. Spare properties ....................................................................... 54 3.10.2.2. Queue specific properties ......................................................... 55

2


3.11. Double Command Blocking ...................................................... 56 3.11.1. General functionality ................................................................. 56 3.11.2. Double command blocking overview......................................... 57 3.11.3. Detailed description for the host ............................................... 57 3.11.3.1. COM581 configuration .............................................................. 58 3.11.3.1.1. Command blocking properties .................................................. 58 3.12. LON supervision ....................................................................... 59 3.12.1. LON device supervision ............................................................ 59 3.12.2. LSG supervision ....................................................................... 59 3.12.3. COM581 ↔ supervision............................................................ 60 3.13. PSF examples .......................................................................... 61 3.13.1. Limitations................................................................................. 61 3.13.2. AND function............................................................................. 61 3.13.3. OR function............................................................................... 62 3.13.4. Not function............................................................................... 62 3.13.5. Convert function........................................................................ 62 3.13.6. Dispatch function ...................................................................... 63 3.13.7. Pulse function ........................................................................... 63 3.13.8. Scale function ........................................................................... 64 3.13.9. Add function.............................................................................. 64 3.13.10. Geometric_Add function ........................................................... 64 3.13.11. Complex_Add function.............................................................. 65 3.13.12. Using internal inputs/outputs..................................................... 65 3.13.13. Diagnostic supervision .............................................................. 65 3.13.14. SON supervision....................................................................... 66 3.14. Added spare attributes in IEC101 ............................................. 66 3.14.1. Fixes ......................................................................................... 66 3.14.2. Spare properties ....................................................................... 66 3.15. Protocols limitation.................................................................... 68 3.15.1. Protocol tables .......................................................................... 68 3.15.2. Additional relevant tables.......................................................... 68

4. REFERENCED DOCUMENT ................................................... 69

5. REVISION HISTORY................................................................ 69

3


1. PURPOSE

This document will describe various extentions which have been implemented for COM581 in Release 6.10 and 6.20.

This is an add-on document to the existing software manual CAP581 [1].

For the next release this extention will be integrated in the official manual CAP581 [1]

2. ABREVIATIONS

LD logical device LN logical node SCD station configuration file

3. CAP581 VERSION 6.20 EXTENSION – OVERVIEW

3.1. General changes and deviation to the manual CAP581

1. Replace ISG & ISP by CIM

2. Delete optical line 12 (only line 11 is available) see Table 8.16.

3. Section 7.1.3: replace max 6 boards with max 9 boards

4. Section 7.1.3, Table 7.4 add DNP Master protocol: delete MVB, ACP, and Type2, TG809.

5. Section 7.1.3, Table 7.4: add 61850 protocol.

6. Whole document: delete MVB, Type2 and TG809.

7. Section 8.1.8.1: replace the MVB time management description by LON time management.

8. Section 7.2.2.3.3: delete address calculation for RP670.

9. Sectionp 7.2.2.3.4: delete address calculation for TG809.

10. Section 8.6: Add, can also handle unsolicited messages.

11. Page 8.26: replace CPU03 by CIM and port 3,4 by 13,14

12. Delete Section 8.8 with ACP.

13. Section 8.1.7, Queue default: Queue3 = should be keep the Newest

14. Add in Table 8.32: Convert – 169 Meas II to 11 variant 0,16

4


15. Add in Table 8.33: PSF variant 16 Measurand value not shifted by 3 bit.

3.2. Two protocols on one CPU

Since release 6.20 it is possible to run two protocols on the same CPU. But it is not possible to select two protocols of the same type on the same CPU.

IEC

6185

0

IEC

6185

0

LON

IEC

6087

0-5-

103

IEC

6087

0-5-

101

IEC

6087

0-5-

101

IEC

6087

0-5-

104

DN

P 3

.0 S

lave

DN

P 3

.0 M

aste

r

IEC

6185

0

IEC

6185

0

LON

IEC

6087

0-5-

103

IEC

6087

0-5-

101

IEC

6087

0-5-

101

IEC

6087

0-5-

104

DN

P 3

.0 S

lave

DN

P 3

.0 M

aste

r

IEC

6185

0IE

C61

850

IEC

6185

0

LON

LON

IEC

6087

0-5-

103

IEC

6087

0-5-

101

IEC

6087

0-5-

101

IEC

6087

0-5-

104

DN

P 3

.0 S

lave

DN

P 3

.0 M

aste

r

Fig. 3.1 Two protocols on one CPU

Two serials, one optical and one Ethernet interfaces can be selected on the 500CIM06 CPU card.

5


Internal via Backplane

Up to 4 serial line to star coupler to connect up to 40 IEC60870-5-103 devices

2 electrical serial Interfaces for communication to NCC’s / IEC60870-5-103

LAN_1: Electrical & Optical Interface for Ethernet

communication

Optical Interfaces for LON / IEC60870-5-103 communication to IED’s

LAN_2: not used

CPU

event logger

Internal via Backplane




communication


LAN_2: not used

CPU

event logger




communication


LAN_2: not used

CPU

event logger

Fig. 3.2 Two serials, one optical, one Ethernet line

The following table shows the possible combinations for 2 protocols on the same CPU card for the release 6.20:

Yes = only one firmware file is used for both protocols

Single = a specific firmware is used for IEC 61850, RP571/71

LON

IEC

6185

0

IEC

6087

0-5-

103

IEC

6087

0-5-

101

IEC

6087

0-5-

104

DN

P 3.

0 Sl

ave

DN

P 3.

0 M

aste

r

RP5

70/5

71

TG80

9

LON no Single yes yes yes yes yes Single noIEC61850 Single no Single yes Single Single Single Single noIEC60870-5-103 yes Single no yes yes yes yes Single noIEC60870-5-101 yes yes yes yes yes yes yes Single noIEC60870-5-104 yes Single yes yes no yes yes Single noDNP 3.0 Slave yes Single yes yes yes no yes Single noDNP 3.0 Master yes Single yes yes yes yes no Single noRP570/571 Single Single Single Single Single Single Single no noTG809 no no no no no no no no no

First Protocol

Seco

nd P

roto

col

Fig. 3.3 Protocol combination on one CPU

6


3.2.1. Port configuration

The following tables show the CAP tool port configuration for the selected protocols.

• Port 3 = First RS232 serial line from the front CPU

• Port 4 = Second RS232 serial line from the front CPU

• Port 11 = Optical line from the front CPU

• Port 1,2,13,14,5,6,7,8 = Start coupler port numbers

NOTE: When using LON on port 11 for IMP or CIM boards, port 3 is not available.

3.2.1.1. IMP CPU (Master)

For the IEC103 protocol configuration:

Means we can configure two IEC103 protocols on the same CPU. Means we can configure four IEC103 protocols on the same CPU.

Fig. 3.4 IMP Protocol configuration

7


3.2.1.2. CIM CPU (Slave)

Means we can configure four IEC103 protocols.

Fig. 3.5 CIM Protocol configuration

The star coupler configuration is defined in the manual for the COM581 [1]

3.2.2. Configuration example

Fig. 3.6 Configuration example

8


3.3. Excel configuration changes

3.3.1. New flags added

New functionalities were added for the flags in the Excel sheet used for signal configuration export and import.

3.3.2. Security in Excel

With the new release for Excel 2003 the Visual Basic security should be enabled:

NOTE: Select in the menu bar “Tools\Macros\Security\Trusted Publishers” and enable “Trust access to Visual Basic Project”.

9


3.4. DNP Master

Only one DNP Master can be configured on each CPU in addition to another protocol.

3.4.1. Serial line properties

3.4.1.1. Specific properties

Fig. 3.7 DNP Master serial line properties

10


• Port Number Range: 1 - 21 Default: 3 Description: Determines the serial output on the front

CPU as follows: Port 3 = Serial line 1 Port 4 = Serial line 2

• Baud Rate:

Range: 50 - 64000 Default: 9600 Description: Determines the communication standard

parameters. • Parity – Format Class:

Range: according to type Default: according to type Description: Are DNP3.0 standard communication para-

meters and should not be changed.

• Time Distribution Mode: Range: Relative time, absolute time Default: Absolute time Description: Not used

NOTE: Only following parameters are used: • Port umber

• Baud rate

3.4.2. Application properties

11



Fig. 3.8 DNP Master application properties

• Application Id Range: 1 - 200 Default: Allocate while adding object Description: Unique identification of the application within

the COM581 system. Allocated in ascending order in increment of one and can then be reset.

• Master Address Range: 0 - 65535 Default: Allocate while adding object Description: Define the DNP Master address

12


3.4.2.2. Communication properties

Fig. 3.9 DNP Master communication properties

• Application Fragment Fill Timeout Range: 2 - 255 Default: 3 Description: Application fragment timeout. This is the

maximum reservation time for the currently active application fragment. (Time to fill up the active application fragment)

• Application Fragment Free Timeout Range: 2 - 255 Default: 10 Description: Maximum waiting time to get all fragments

free. This is the maximum time in seconds where no request is possible. After the timeout expires, a new request is enabled.

• Gap Supervision Time Range: 0 - 500 Default: 10 Description: Maximum gap between received characters

in 1-bit steps.

• Link Frame Timeout Range: 0 – 30.000 Default: 200

13


Description: Incoming link frame supervision. Maximum supervision time for next expected link frame in milliseconds.

• Number of Retries Range: 1 – 12 Default: 1000 Description: Determines how often a telegram is repeated

in the event of communication failure. Should the latter be detected, the last telegram sent to a station is repeated as many times as specified (Number of Retries). At the same time, communication with the station at the link level is discontinued. Declared not reachable and reinitialized by the next cycle.

• RTU Clock Synch Cycle Time Range: 5 – 3600 Default: 900 Description: Determines the period of the time synchro-

nizing cycle for all stations (broadcast).

• RTU Offline Supervision Cycle Time Range: 0 – 300 Default: 30 Description: Determines the off-line cycle period for trying

to restart an RTU in seconds.

• RTU Alive Supervision Cycle Time Range: 0 – 300 Default: 30 Description: Determines the test cycle period for choking

if an RTU is still alive in seconds.

• Transmit Delay Time Range: 0 – 200 Default: 0 Description: This function (FC=23) is used to calculate

the communication delay for a particular outstation. It is generally used in the time synchronization process for the outstations (see DNP Application Layer Document

14


section 6. Time synchronization for a de-tailed description of the process).

The outstation responds with the time delay fine object. This object states the number of milliseconds elapsed between the outstation receiving the first bit of the first byte of the request and the time of transmission of the first bit of the first byte of the response.

3.4.2.3. Counter properties

Fig. 3.10 DNP Master counter properties

• Counter Freeze and Clear Range: Yes, No Default: No Description: This function code is used to copy the

specified data to a freeze buffer like the freeze immediate function code but then the outstation clears ( to 0 ) the specified data objects. Typically, this function code is used to freeze counters or accumulators and then reset them to 0.

• Counter Freeze Cycle Time Range: 0 – 86400 Default: 0

15


Description: Determines the period of periodical counter freeze command in seconds.

• Counter Freeze Offset to Midnight Range: 0 – 86400 Default: 0 Description: Determines the offset from midnight of the

counter freeze command in seconds.

• Counter Reading Cycle Time Range: 0 – 86400 Default: 0 Description: Determines the period of the periodical

counter read command in seconds.

• Counter Reading Offset to Midnight Range: 0 – 86400 Default: 0 Description: Determines the offset from midnight of the

counter read command in seconds.

3.4.2.4. Spares properties

Fig. 3.11 DNP Master spare properties

In this release, V6.20, the spare attributes are not used.

16


3.4.3. DNP RTU Configuration

Use the DNP30 RTU configuration properties “insert new object” in order to add an RTU in the DNP Master polling list (max 100 RTU’s).

The RTU Port numbers determine the serial output on the front as follows: Port 3 = Serial 1 Port 4 = Serial 2

3.4.4. DNP RTU Configuration properties

3.4.4.1. Address

Fig. 3.12 DNP Master RTU Configuration properties

• Slave Address Range: 0 - 65535 Default: 0 Description: Defines the DNP RTU Slave address on the

polling list.

17


3.4.4.2. Analog properties

Fig. 3.13 DNP Master Analog properties

• Analog Input Change Event Reading Range: Yes, No Default: No Description: If Yes, request a Read Object 32 Var 0

(Analog Change Event) for that RTU on the polling list. If No, read static object is applied.

• Analog Input Object Reading Number Range: 0 - 255 Default: 16 Description: Defines how many analog input change

objects are requested per cycle.

• Analog Input Reading Cycle Time Range: 0 - 3600 Default: 0 Description: Requests analog input change for that object

specified according to the defined cycle time in seconds. Value 0 means no cyclic acquisition is performed.

18


3.4.4.3. Binary properties

Fig. 3.14 DNP Master - Binary properties

• Binary Input Change Variation Range: Disable, All, without time, With time, With

relative time Default: Disable Description: If YES, it performs a read of object 1 or

object 2 Var 0 for that RTU on the polling list, depending on the above selection.

• Binary Input Object Reading Number Range: 0 - 255 Default: 16 Description: Defines how many binary input change

objects are requested per cycle.

• Binary Input Reading Cycle Time Range: 0 - 3600 Default: 0 Description: Requests binary input change for that object

specified according to the defined cycle time.

19


3.4.4.4. Measurement properties

Fig. 3.15 DNP Master Measurement properties

• Enable Measurement Delay Range: Yes - No Default: No Description: Activates the transmission line delay

calculation.

• No of Event per Polling Range: 1 - 255 Default: 10 Description: The server is expected to report a maximum

of 10 events in one telegram.

• Send Test Link Timeout Range: 0 - 3600 Default: 120 Description: Sends a test link according to the time period

configured, in order to test the link layer. This function is only perfumed, if no other activity is ongoing during the supervision time.

20


3.4.4.5. Event properties

Fig. 3.16 DNP Master - Event properties

• Class 0 Reading Cycle Time Range: 0 - 3600 Default: 60 Description: Class 0 is reserved for static data objects

(static data reflects the current value of data in the outstation). Makes a general interrogation of the data base for binary and measurand points.

• Enable Unsolicited Message Class 1 Range: Yes, No Default: No Description: Process unsolicited message from the server

for class 1. The server is behaving in balanced mode.

• Enable Unsolicited Message Class 2 Range: Yes, No Default: No Description: Process unsolicited message from the server

for class 2. The server is behaving in balanced mode.

• Enable Unsolicited Message Class 3 Range: Yes, No Default: No

21


Description: Process unsolicited message from the server for class 3. The server is behaving in balanced mode.

• Number of Events Per Polling Range: 1 - 255 Default: 10 Description: A maximum of 10 events should be reported

by the server in one telegram.

3.4.5. Data point configuration

Unlinked data point

Fig. 3.17 Unlinked DNP3.0 source data point

Linked data point

Fig. 3.18 Linked DNP3.0 source data point

3.4.5.1. Structure object for DNP3 Master data point

Fig. 3.19 DNP structure objects for DNP3.0 data points

22


3.4.5.2. Insert new object

• Sink Data points Command

DNP30 Sink Command Structuring Node

Transparent Data

DNP30 Sink Transparent Data Structuring Node

• Source Data points Integrated Totals

DNP30 Source Binary Counter DNP30 Source Frozen Counter Structuring Node

Indication

DNP30 Source Binary Input Structuring Node

Measurand Value

DNP30 Source Analog Input DNP30 Source Binary Coded Decimal DNP30 Source Floated Point DNP30 Source Frozen Analog Input Structuring Node

Step Position Information

DNP30 Source Analog Input DNP30 Source Binary Coded Decimal DNP30 Source Floated Point DNP30 Source Frozen Analog Input Structuring Node

Sequence of Events


System Diagnosis


System Control


23


Transparent Data DNP30 Source Transparent Data Structuring Node

Maintenance Information

DNP30 Source Transparent Data Structuring Node

3.4.5.3. Delete object

Yes, All signals that are added can be deleted.

3.4.5.4. Remove Link

This operation is only possible in the signal tree window.

3.4.6. DNP30 Master integrated iotals

Fig. 3.20 Linked DNP Master Source Binary Counter

3.4.6.1. Address properties

Fig. 3.21 DNP Master Address properties

24


• Slave Address Range: 0 – 65535 Default: 0 Description: Corresponds to the station address of the

DNP30 application. • Object Address

Range: 0 - 65535 Default: Allocated while adding object, (starting at 0). Description: Defines the DNP30 object address, also

referred to a DNP30 point. An object address must be unique in the address range of a data type.

• Data Type Range: DNP30 Binary Counter, DNP30 Frozen

Counter Default: Assign during configuration Description: Defines the type of counter.

3.4.6.2. Spare properties

Fig. 3.22 DNP Master Frozen Counter -Spare properties

• Spare_1 – Spare_4 Range: String Default: Type dependant Description: Not used

25


3.4.6.3. Cnt Spare properties

Fig. 3.23 DNP Master Frozen Counter Cnt Spare properties

• CntSpare_1 – CntSpare_4 Range: String Default: Type dependant Description: Not used

3.4.7. DNP30 Master indications

Fig. 3.24 DNP Master Linked DNP3.0 Source Binary Input

26



Fig. 3.25 DNP Master Indications properties

• Indication Type Range: Single, Double, Counter Freeze, SON.

Single 1-bit process information Double 2-bits process information Counter Freeze Not used SON Used for system diagnosis information, e.g. to report the state of an RTU connected to the DNP3 Master.

Default: Single. Description: The status of a single indication is described

by a bit corresponding to the positions ON or OFF. The status of a double indication is described by two bits corresponding to the positions ON or OFF and two intermediate positions. DNP30 binary input objects can be configured as double induction type because some sink applications might require this.

• Sequential Event Recording Range: None Zero to One, One to Zero, Both. Default: Both. Description: Determine which kind of change of state

positive, negative-going edge, initiates trans-mission of an event,

27



Fig. 3.26 DNP Master Binary Input - Address properties

• Slave Address Range: 0 – 65535 Default: 0 Description: Correspond to the station address of the

DNP30 application.

• Object Address Range: 0 - 65535 Default: Allocated while adding object, (starting at 0). Description: Defines the DNP30 object address, also

referred to as DNP30 point. An object address must be unique in the address range of a data type.

• Data Type Range: DNP30 Binary Input, Default: Assign during configuration Description: Defines the type of input.

28



Fig. 3.27 DNP Master Binary Input - Spare properties


3.4.7.4. IndSpare properties

Fig. 3.28 DNP Master - Ind Spare properties

• IndSpare_1 – IndSpare_4 Range: String Default: Type dependant Description: Not used

29


3.4.8. DNP3 Master Measurement

3.4.8.1. Address

Fig. 3.29 DNP Master Analog Input - Address properties


DNP30 application.



• Data Type Range: DNP30 Analog Input, Default: Assign during configuration Description: Defines the type of input.

30



Fig. 3.30 DNP Master Analog Input - Spare properties


3.4.8.3. Measurand Spare properties

Fig. 3.31 DNP Master - Measurand Spare properties

• MeaSpare_1 – MeaSpare_4 Range: String Default: Type dependant Description: Not used

31


3.4.9. DNP3 Master Step Position Information

Not supported.

3.4.10. DNP3 Master Sequence of Events

Not supported.

3.4.11. DNP3 Master System Diagnosis

Not supported.

3.4.12. DNP3 Master System Control

Not supported.

3.4.13. DNP3 Master Transparent Data

Not supported.

3.4.14. DNP3 Master Maintenance Information

Not supported.

3.4.15. DNP3 Master Command

Fig. 3.32 Linked DNP3.0 Sink Command Objects

32



Fig. 3.33 DNP Master Command properties

• Associated DNP30 Input Signal Range: 0 – 65535 Default: 0 Description: A command address can be linked to a

signal address so that the status of the DNP30 command object can be updated together with the associated signal object. The permitted signal types are DNP30 process signals and SON signal.

• Control Code Range: Persistent Output, Pulse Output, Trip/Close Default: Persistent Output Description: The command code is defined during data

point configuration.

• Length On Pulse Range: 0 – 65535 Default: 0 Description: The on-time field specifies the amount of

time the digital output is to be turned on in milliseconds.

• Length Off Pulse: Range: 0 – 65535

33


Default: 0 Description: The off-time field specifies the amount of

time the digital output is to be turned off in milliseconds.


Fig. 3.34 DNP Master Command Address properties


DNP30 application.



• Data Type Range: DNP30 Command, Default: Assign during configuration Description: Defines the data type.

34



Fig. 3.35 DNP Master Address Command Spare properties


3.4.15.4. Command Spare properties

Fig. 3.36 DNP Master Address CmdSpare Command properties

35


• CmdSpare_1 – CmdSpare_4 Range: String Default: Type dependant Description: Not used

3.4.15.5. DNP3 Master Command Transparent Data

Not supported.

3.5. Redundant gateway with redundant lines

3.5.1. System overview

PSM

17 * REC316

60 * REF545

Main Data Exchange for COM581 redundancy

Direct optical connection

Optional Data Exchange for COM581 redundancy

Line Splitter Line Splitter

IEC101 IEC101

PSM

17 * REC316

60 * REF545

Main Data Exchange for COM581 redundancy

Direct optical connection

Optional Data Exchange for COM581 redundancy

Line Splitter Line Splitter

IEC101 IEC101

Fig. 3.37 Redundant gateway with redundant lines

The following general requirements should be fulfilled for redundant COM581:

• At startup of both COM581 at the same time only one of them must come online. In standby-state the state of the other must be checked, if it is also online it will wait for a random number of seconds to come online (see Fig. 3.37).

36


• The standby COM581 is not allowed to send anything to the master.

• If any major problem arises in the online COM581 a switchover to the other COM581 will take place.

• A switchover will not exceed a time of one minute (time from appearance of the fault until the end of switchover).

• All states related to the switchover must be sent to the NCC and the local MMI.

The two COM581’s must have a connection between each other. This could be done by:

Serial 1, Serial 2, optical; LAN connection is not supported at the moment.

The connection is done between the master-CPU (IMP) of the two COM581.

Additionally there could be a connection between the slave-cards of the two COM581 for additional security according to the COM581 redundancy configuration.

Supervision:

COM581 reports the following supervision signals to Microscada and if required also to NCC:

• IEC101 line status (ONLINE, BACKUP, STANDBY).

− ONLINE means master is sending cyclically class2 requests,

− BACKUP means master is sending cyclically reset link requests to check the communication line.

− STANDBY means COM581 is not sending any answer

3.5.2. Redundancy types

3.5.2.1. Gateway redundancy type 1

The redundace type 1 is a simple redundance where the COM581 (hot) will switch from hot to standby in case of a power failure or major error or HW defect from the standby COM581.

37


PS

M

Line Splitter C Line Splitter D

IEC101 Line C IEC101 Line D

L11 L12 L21 L22

N11 N12 N22N21COM581 A COM581 B

Switch over by COM581

PS

M


IEC101 Line C IEC101 Line D

L11 L12 L21 L22

N11 N12 N22N21COM581 A COM581 B


IEC101 Online - active

IEC101 Online - backup

IEC101 Stand by - idle

COM581 Online

COM581 Stand by

Error / Fault




COM581 Online

COM581 Stand by

Error / Fault

Fig. 3.38 Redundant Type 1

Status COM581 A Status COM581 B Action

Power-fail on COM581 A COM581 B running Switchover to COM581 B

Major-Error on COM581 A COM581 B ok Switchover to COM581 B

HW defect on COM581 A COM581 B running Switchover to COM581 B • Conditions with “minor error” < 20 sec


Reserved for future implementation



3.5.2.4. Gateway redundancy type 5 - 10



The redundace type 4 is a specific redundance made for the DEWA project where the COM581 (hot) will switch from hot to

38


standby depending on the NCC and IEC61850 line status failure (see table below).

COM581 B

PSM


IEC101 Line CRoute A

L11 L12 L21 L22

N11 N12 N22N21COM581 A


SCC A

SCC B

ECC A

ECC B

IEC101 Line DRoute B

COM581 B

PSM


IEC101 Line CRoute A

L11 L12 L21 L22

N11 N12 N22N21COM581 A


SCC A

SCC B

SCC A

SCC B

ECC A

ECC B

ECC A

ECC B

IEC101 Line DRoute B




COM581 Online

COM581 Stand by

Error / Fault




COM581 Online

COM581 Stand by

Error / Fault

Status 1 Status 2 Action

N11 error and N21 ok N12 ok and N22 error No Switchover to COM581 B

N11 error and N21 ok N12 ok and N22 ok L21 or L22 ok Switchover to COM581 B

N11 error and N21 ok N12 ok and N22 ok L21 or L22 error No Switchover to COM581 B

N11 error and N21 error N12 ok and N22 error No Switchover to COM581 B

Fig. 3.39 Redundant type 4

• Switch over time < 120 sec

• Master supervision time > 120 sec

• COM581 has to be ready (COM581 B → L21) before IEC101 ECC Master will switch over to Line D

3.5.3. Restrictions

• Serial Line 1 and optical Line 11 (LON/IEC103) can‘t be used at the same time on either IMP or CIM CPU.

• Event handling by switch over (stand by → hot) Make sure to enable the flash queues with keep newest.

39


• Ethernet connection can not be used for the redundancy data exchange

3.6. Redundant gateway configuration

3.6.1. COM581 Redundancy properties

Fig. 3.40 Redundant gateway configuration

• Redundancy Type Range: Not Redundant, Redundancy I –

Redundancy X Default: Not Redundant Description: Define the Type of Redundancy to be

configured Redundancy types II, III, V, VI, VII, VIII, IX, X → reserved for future implementation

• Redundancy Connection 1 Range: CPU1 Serial 1, CPU1 Serial 2 el., CPU1

Serial 2 opt. Default: CPU1 Serial 1 Description: Defines the redundancy channel on the IMP

CPU to be configured. The first connection is done between the master IMP-cards of the two COM581’s.

40


• Redundancy Connection 2 Range: None, CPU1 Serial 1, CPU1 Serial 2 el.,

CPU1 Serial 2 opt, CPU2 Serial 1, CPU2 Serial 2, CPU2 optical, CPU3 Serial 1, CPU3 Serial 2, CPU3 optical, CPU4 Serial 1, CPU4 Serial 2, CPU4 optical, CPU5 Serial 1, CPU5 Serial 2, CPU5 optical, CPU6 Serial 1, CPU6 Serial 2, CPU6 optical, CPU7 Serial 1, CPU7 Serial 2, CPU7 optical, CPU8 Serial 1, CPU8 Serial 2, CPU8 optical, CPU9 Serial 1, CPU9 Serial 2, CPU9 optical

Default: None Description: Define the second Redundancy channel

between the CIM-cards of the two COM581’s to be configured for additional security.

• When using the serial interface make sure you are using a

cross cable, see picture in manual COM581[2]

3.7. Redundancy minor error

Minor error will be stored in the LMI queue.

The first IEC101 line means the line connected to the first serial interface on the board (L11 or L21).

The second IEC101 line means the line connected to the second serial interface on the board (L12 or L22).

Error No. Designation Significance

41 First IEC101 line failed First IEC101 line was active, backup or idle and failed.

43 Second IEC101 line failed Second IEC101 line was active, backup or idle and failed.

81 First IEC101 line failed First IEC101 line was active and failed.

83 Second IEC101 line failed Second IEC101 line was active and failed.

91 First IEC101 line failed First IEC101 line was backup and failed.

93 Second IEC101 line failed Second IEC101 line was backup and failed.

101 First IEC101 line failed First IEC101 line was idle and failed.

103 Second IEC101 line failed Second IEC101 line was idle and failed.

Fig. 3.41 Redundant minor error

41


3.8. Command Authority Handling (CA)

3.8.1. CA for IEC 61850 (per IED)

3.8.1.1. Command Authority overview

The Command Authority is controlled in COM581. It can be tested with any NCC protocol.

The MicroScada client by sending double commands changes the filtering of NCC commands in COM581.

The COM581 will send actual authority status of every bay respective the station back to MicroScada.

In a distribute system architecture with MicroScada Pro and COM581 it is necessary to deal with the Command Authority. Either the commands could be sent from the NCC or locally from the station PC (MicroScada Pro).

Fig. 3.42 Command Authority

This Command Authority handling can be configured in two modes:

• Command Authority Handling generally per gateway • Command Authority Handling individually per Bay/IED

Command Authority configuration:

Generally: In CAP no configuration is needed for authority, it will be handled in communication stack. SCD File (and CCF File)

42


must contain specific logical node and data objects, which are described here.

3.8.1.2. Requirements in SCD file for CA

Fig. 3.43 IEC61850 structure of COM581

• The picture above describes the IEC61850 structure of COM581 (AA1TH1).

• For each subnet there must exist two LD with names LDx, LDxSUPERV (in case of two subnets x=1,2)

• LNs which are describing special functionality must be inserted in LD with name containing “SUPERV”, see example: LD1SUPERV, LD2SUPERV.

• For Command Authorithy handling GGIO with prefix “AUTH” is needed.

• In case of handling the Command Authority individually per IED, this GGIO must contain “SPCSOx” data objects for every IED, d-Attribut must contain according IED name, see the following example, e.g. AA1A1, AA1A2:

43


Fig. 3.44 SCD except for Command Authority (1)

• In case of handling the Command Authority generally per gateway, this GGIO must contain “SPCSO” data object to be used to control authority for the whole station.

• The GGIO must contain data object "AuthWac" for station level client supervision (cyclic alive command), which must be sent every 20 seconds, otherwise COM581 will switch to authority=NCC for the whole station.

• The actual authority of the IED respective the whole station is according IEC61850 standard described in LLN0:

Fig. 3.45 SCD excerpt for command authority (2)

• The data objects “Locx” must be sent back to IEC61850 client of MicroScada PC (AA1OPC1, AA1OPC3) to have the same status like in COM581. Additionally the COM581 itself has to be configured as client, if the authority signals should be sent to NCC (only data in datasets will be recognized during SCD import into excel):

44


Fig. 3.46 SCD excerpt for Command Authority (3)

• The “SPCSOx” and “AuthWac” data objects should not be imported to CAP, have to be marked as "unused" before export. Only “Locx” data objects must be configured if they should be sent to NCC.

3.8.2. CA for LON (per COM581)

3.8.2.1. Command Authority overview:

By changing Local / Remote flag the commands from NCC can be disabled / enabled. Default value for the flag is remote. Setting it to local must be done periodically. If not after 1 minute the flag changes automatically to remote. The flag value change can be initiated only by a command coming over LON.

45


Fig. 3.47 CA for LON

The Command Authority in LON waits for the unconfigured command data point coming over LON with unit address equal to own LON node and the object address 65521. When the LON application address is subnet 1 node 110 then the address for unconfigured CA command is 110.65521. When for instance command 110.65521 comes the Command Authority implementation checks for commands with addresses 110.65522…110.65524 to send the CA command to another LON applications on another cards.

The change of L/R flag is signalized by a double point indication with time tag with unit address same as the command that caused the change and object address 65530.

3.8.2.2. Command Authority configuration

See Fig. 3.43 for an example how to configure Command Authority with two LON applications (cards).

46


Fig. 3.48 Command Authority configuration

3.8.2.3. COM581 with two LON cards

MS stands for Micro Scada. L/R flag is local/remote flag. Value local means that NCC commands are refused by LON protocol and sent back with negative response.

3.8.2.4. LON card (first): subnet: 1, node: 110

CA configuration:

1. Unconfigured double command from MS address 110.65521 is used as a CA command to change the L/R flag.

2. Command 110.65522 to send the CA command from the first LON card to the second LON card.

3. Command 113.65522 to receive the CA command from the second LON card at the first LON card.

47


4. Indication 110.65530 indicates the change of L/R flag on the first LON card after the CA command 110.65521 from MS was received.

5. Indication 113.65530 indicates the change of L/R flag on the first card after the CA command from second LON card was received.

3.8.2.5. LON card (second): subnet: 2, node: 111

CA configuration:

6. Unconfigured double command from MS address 111.65521 is used as a CA command to change the L/R flag.

7. Command 111.65522 to send the CA command from the second LON card to the first LON card.

8. Command 112.65522 to receive the CA command from the first LON card at the second LON card.

9. Indication 111.65530 indicates the change of L/R flag on the second LON card after the CA command 111.65521 from MS was received.

10. Indication 112.65530 indicates the change of L/R flag on the second card after the CA command from first LON card was received.

This configuration enables changes of L/R flag on both LON cards by an uncofigured CA double command sent from MS to one of the LON cards. The only problem appears at the startup. Only the first (master) LON card knows when the system comes to ready state and initializes L/R flags and indication data points. That is why the indications 113.65530 and 111.65530 can be in an unknown state after the startup until they will be activated by sending a CA command from MS to the second LON card. For CA units values LON application node .. LON application node + 4 can be used, for example for the first LON card units 110 .. 114 can be used, for the second LON card units 111 .. 115 can be used.

3.8.2.6. COM581 with three LON cards

The situation is similar to the example with two LON cards. In this case three LON applications are configured with LON node addresses 110, 111 and 112. That means for first LON application addresses from range 110 .. 114.65522 .. 65525 can be used, for second LON application addresses from range 111 .. 115.65522 .. 65525 can be used and for first LON application addresses from range 112 .. 116.65522 .. 65525 can be used.

48


Every LON applications is able to send the CA command to two another LON applications and to accept CA command from these applications. Special attention shall be paid to sink unit addresses that must fulfil the constraint for unit address on the sink application not on the source. An example how to configure command authority for three LON applications is on the Pic 3. Double indications are used to signalize the change of the L/R flag. When CA command comes an indication is sent with the same unit address, as the command has, and with the object address 65530. For instance when third LON application receives a CA command from the first LON application with address 115.65522 indication with address 115.65530 is sent. When the third LON application receives CA command over LON bus from Microscada with address 112.65521 the indication with address 112.65530 is sent.

49


Fig. 3.49 Command authority with three LON cards

Same LON node address for several LON segments

Two LON applications running on different boards can have same LON node address but then their LON addresses must differ in subnet address. For instance first LON application with Id 2 can have LON address subnet 1, node 125 and second LON application with Id 3 can have LON address subnet 2, node 125.

50


Fig. 3.50 Two LON applications with same LON node address

IMPORTANT: Never configure a LON node for Command Authority!

Capture example

Commands sent from MS:

LONSIM: y = 1.110, s = 110

110.65521:

51


06 00 6E 01 2E 01 FF F1 00 00 01(1 – local, 2 - remote) 00

LONSIM: y = 2.111, s = 111

111.65521:

06 00 6F 01 2E 01 FF F1 00 00 01(1 – local, 2 - remote) 00

3.9. Redundant serial line within one COM581

Fig. 3.51 Redundant serial line

• In order to add a redundant line select with the right mouse the IEC101 application under port 3, and then link it to the redundant serial port 4 according to Fig. 3.46.

A line switchover should take place if anything fails in the hot line and the standby line is healthy. Redundant line switching is always controlled by the master.

3.9.1. Requirement for IEC101 protocol

• Both lines are communicating, one line is polled, the other is checked with “Request link status” telegrams.

• The actual line switchover is done by a “reset of link” message.

• No events will be lost during line switchover.

• No events should be sent more than once, during a line switchover.

• The lines must answer immediately to a request from the master (that means the switchover-time depends on the master).

• The redundant line is able to run with different line parameters (e.g. speed).

• A line is considered as ok if any legal telegram is received.

52


3.9.1.1. Specific serial line properties

For both IEC101 Serial Lines

Fig. 3.52 Specific serial line properties

• Redundancy Serial Range: Yes, No Default: No Description: Define whether the line redundancy is

enabled or not.

3.10. Redundant serial line with two COM581’s

3.10.1. General description

We have 2 COM581’s in a redundant configuration. On each COM581 we have 2 connections either with IEC60870-5-101 or IEC60870-5-104 to 2 different NCC’s.

Each NCC will select only one communication line; the other communication line will not be used and is on standby mode (not communication on that line).

For the Hot-Standby switch over the standby gateway will delete (each 10 seconds ==> time is configurable from Spare 4) the existing events. Then after a switch over there are only few remaining events in the buffer which will be sent to the NCC. These few events could be duplicated on the NCC.

53


IEC101 IEC101

IEC61850

IEC104 IEC104

NCC2NCC1

Fig. 3.53 Redundant serial line with 2 COM581’s

3.10.2. Line properties


Fig. 3.54 Linked line properties

Set Spare attribute “4” for IEC101 or (and) IEC104 line.

Fig. 3.55 Line properties

• Spare_4 Range: 0 - 65535 Default: 0 Description: Time_Supervision_for_Flushing_Queues

Use spare attribute for configuring the time (sec), when to delete the events in the queue after line switch over. After the line switch

54


over, only the events stored in the queue during the configured time will be sent to the Host. 0 = No time supervision

3.10.2.2. Queue specific properties

Fig. 3.56 Queue Specific properties

• Queue Size: See Section 8.1.6 [1]

• 1 Queue Overflow Range: Keep the Newest, Keep the Oldest, Keep the

Oldest and then the Newest. Default: Keep the Newest Description: Time_Supervision_For_Flush_Queues


Oldest and then the Newest. Default: Keep the Oldest or Keep the Newest Description: Time_Supervision_For_Flush_Queues


Oldest and then the Newest.

55


Default: Keep the Oldest or Keep the Newest Description: Time_Supervision_For_Flush_Queues

The size of the local application queues (not the internal COM581 queues) is 50 entries for each data type.

NOTE: Only the local application queues are flushed after a switchover, not the COM81 internal queues which may contain queued events. Therefore, it is advisable to always use the “Keep Newest” strategy, where events may be lost if the NCC communication is lost for some time (IEC101 application is configurable with “Timeout for Keeping Inormation”).

3.11. Double Command Blocking

3.11.1. General functionality

• Used with IEC61850 protocol only.

• Station-wide: only one single selection allowed in the whole station, independant of the issuer (SCS or NCC).

• Based on each switching object stSeld report

• Completely independant from the COM581 status

• If any stSeld is active further switching commands must be inhibited (logical OR)

• No influence to other than switching commands (transformer commands, trip reset commands)

• Commands issued in LOCAL operation mode do not activate stSeld, but Authority LOCAL is indicated.

Fig. 3.57 Double CMD Blocking

56


3.11.2. Double command blocking overview

PS

M

17 * REC316

60 * REF???

MicroScada

IED A

Commando to “IED A”

stSeld “IED A”

stSeld “IED A”


Commando to “IED A” LOCAL

stSeld “IED A”

PS

M

17 * REC316

60 * REF???

MicroScada

IED A


stSeld “IED A”

stSeld “IED A”


Commando to “IED A” LOCAL

stSeld “IED A”

3.11.3. Detailed description for the host

The StSeld indication of switching object will be reported by the server to MicroScada. The idea is, that when the first stSeld is reported, a command procedure which is connected to every IX=20, will set manual process object to 1.

In according picture function for switching object the status of this process object will be analyzed and depending on status the buttons of switching dialog will be set to insensitive.

The manual process object will be generated independent of IET using command procedure AFTER_DB_IMPORT which should be carried out once after every import of process database loadfiles.

There are two more tasks of that command procedure: set eventchannel for stSeld, set correct OI for authority commands. It is recommend carried out the three task independently.

57


3.11.3.1. COM581 configuration

3.11.3.1.1. Command blocking properties

Fig. 3.58 Double CMD blocking properties

• Double CMD Blocking Range: Yes - No Default: No Description: Double CMD blocking is a feature of

IEC61850 Client Application to prevent NCC protocol applications (e.g. IEC104) to force different commands (over IEC61850 to IEC61850 IEDs) at the same time or the same command from different NCCs at the same time. The function works as follows: All IEC61850 client applications (on different CPUs) are checking for active stSeld signals on the IEC61850 Bus. If there is an active stSeld, only the corresponding command is possible to be used and all others commands are blocked.

• CMD Blocking Timeout Range: 1 – 65535 (sec) Default: 30

58


Description: This timeout is used to reset the double command blocking on failure (e.g. stSeld does not fall back to false after certain time). It should be bigger than maximum time of an active stSeld returnd by an IED.

3.12. LON supervision

LON supervision guidelines:

3.12.1. LON device supervision

For each IED connected to the LON COM581 opens a LON session. The LON sessions are controlled by COM581. Therefor each IED must set one data point to “0” if the bay unit is OK. If the bay unit fails or the optical fiber is interrupted, COM581 sets the status of this IED to “minor error”. In case of an IED failure the COM581 sets the configured data point to “1”. At the same time all data points are set to “invalid” excepted the SON signal. It stays even in case of failure on “valid”, bur COM581sets it to “1”.

Therefor one data point of type SON must be configured in COM581 for each bay unit and the bay unit must overwrite this data point with “0”.

3.12.2. LSG supervision

LSG

COM581

SPA

SPA

LON

Fig. 3.59 LSG supervision

The COM581 will supervise the status of LSG by sending the diagnostic message QUERY_STATUS every minute. If a LSG does not respond to the message, communication to all units belonging to that LSG is regarded as lost. If a NV_Poll to a LSG

59


fails after 3 attempts, the corresponding data point is marked as invalid in the process image.

If a SPA poll to a SPA unit fails (no SPA response) after 3 attempts, communication to that unit is regarded as lost. All data points from that unit are marked as invalid in the process image and passed to IAL

If LSG sends SPA event E51 (event buffer overflow), an interrogation of all SPA data points belonging to that LSG is performed.

If LSG sends SPA event E53 (no connection to slave), communication to the unit identified by the SPA node address is regarded as lost. All data points from that unit are marked as invalid in the process image and passed to IAL

For the supervision, a SON data point can be configured for each SPA node (NV SON Signal). This signal is set to NOT_READY when the COM581 detects loss of connection to a SPA device. When the connection is valid again, the NV data point is not interrogated form SPA unit, but it is set to READY.

3.12.3. COM581 ↔ supervision

COM581_A COM581_B.

LON

SON1.25

SON1.124

Subnet 1Node Id = 124

DIA Object Address = 4

Subnet 1Node Id = 125

DIA Object Address = 4

Fig. 3.60 COM581 Supervision

It works like hte LON device supervision. One advantage is, that the COM581 writes its data point to the LON. So only at the sescon COM581 the data point for the COM581 being supervised has to be installed.

COM581 sends its data point:

Put in the own address for Subnet and Node ID.

In this example ii is Node Id 125 and Object Address 4.

60


Fig. 3.61 LSG Supervision Configuration

COM581 supervises the redundant COM581

Now the redundant COM581 should be supervised. Therefor the LON signal must - as for a bay unit – be read and send to the desired NCC Link.

Fig. 3.62 COM581 supervision link

3.13. PSF examples

3.13.1. Limitations

• No PSF on IMP CPU

• Only one PSF application running on each CIM CPU

3.13.2. AND function

Example for SI Type 140

• Four inputs from LON

• One output to IEC101, IEC104

61


Fig. 3.63 PSF AND function

3.13.3. OR function

Example for Single point Type 140 with time tag

• Input from LON

• Output to DNP3.0

Fig. 3.64 PSF OR function

3.13.4. Not function

Example for single point Type 140 with time tag with OR function and internal inputs

• Input from LON

• Output to DNP3.0

Fig. 3.65 PSF Not function

3.13.5. Convert function

Example for Status of Node (SON)

• Input as SON

• Output to IEC101 as SPI

62


Fig. 3.66 PSF Convert function

Example for IEC103 message with relative time

• Input as IEC103 Type 162

• Output to DNP3.0 as SPI

Fig. 3.67 PSF Convert with IEC103 Function

3.13.6. Dispatch function Example for Single point Type 140 with time tag with internal inputs

• Input from IEC101 NCC1, IEC101 NCC2

• Output to 6 x LON Command

Fig. 3.68 PSF Dispatch Function

3.13.7. Pulse function

Example for Single point Type 140 with time tag

• Input from LON

• Output to IEC101, IEC104

Fig. 3.69 PSF Pulse Function

63


3.13.8. Scale function

Example for measurand 16 bit Type 11 scaled to 2

• Input from LON

• Output to IEC101

Fig. 3.70 PSF Scale Function

3.13.9. Add function

Example for measurand 16 bit Type 11 scaled to 2

• Input from LON

• Output to IEC101, IEC104

Fig. 3.71 PSF Add function

3.13.10. Geometric_Add function

Example for measurand 16 bit Type 11

• Two Inputs from LON

• One Output to IEC101, RP570, ACP, IEC104

Fig. 3.72 PSF Geometric_Add function

64


3.13.11. Complex_Add function

Example for measurand 16 bit Type 11 with Scaled functions

• Inputs from LON

• One Output to DNP3.0

Fig. 3.73 PSF Complex_Add function

3.13.12. Using internal inputs/outputs

See example above.

3.13.13. Diagnostic supervision

Fig. 3.74 PSF Diagnostic supervision

65


3.13.14. SON supervision

3.14. Added spare attributes in IEC101

3.14.1. Fixes

• Disable Spare_1 attribute on IEC101 application object (used for set time synchronization behavior).

→ All spares are defined for IEC101 balanced and unbalanced mode unless stated otherwise.

3.14.2. Spare properties

Fig. 3.75 IEC101 Spare properties

• Spare_1 Range: Read Only Default: 0 Description: Not used

• Spare_2 Range: 0 - 255 Default: 0

66


Description: OAD_Originator Address in Command information telegram sent to LON or IEC61850 server.

• Spare_3 Range: 0 = FALSE, 1= TRUE Default: 0 Description: Force_Time Synch_Positive_Ack for IEC101

protocol. When the NCC is sending a telegram type 103 time Synch, the COM581 responds with a positive answer if the Spare attribute is set to 1 although it cannot be synchronized from the IEC101 Master.

• Spare_4 Range: 0 - 65535 Default: 0 = No Time supervision Description: Time_Supervision_for_Flushing_Queues

Using spare attribute for configuring the time (sec) when to delete the events in the queue after Line switch over. After the line switch over, only the events stored in the queue during the configured time will be sent to the Host. Applies only to the local application queues, which hve 50 entries for each ta-type.

• Spare_5 Range: 0 = FALSE, 1= TRUE Default: 0 Description: Measurands Time Tags are suppressed if

the attribute is set to 1.

• Spare_6 Range: 0 – 65535 (sec) Default: 0 Description: Cycle Time for sending Time Telegrams for

IEC101 Balanced mode. If set to ≠ 0, the COM581 connected to the Host should sent with a periodicity according to the Spare parameter (sec) a synchronization telegram. This telegram ASDU103 acc. to Section 7.3.4.4 of IEC870-5-101 with the field "time-stamp" related to "information object" 7

67


octets, specifying date/hour (field month...year) to permit a synchronizationof the Host without ambiguity. In case of communication failure between the COM581 and the SAS, the telegrams ASDU 103 will be stored in a "buffer", then after re-establishing the communication will sent all telegrams to the host to have the time reference. The telegram should be sent with a COT type 3 ("spontaneous"). With the re-establish of the communication (after a communication failure or re-initialising of the system) the ASDU should be sent with a COT of type 20 (GI).

3.15. Protocols limitation

The following lists give an overview on how many applications can be configured per COM581.

3.15.1. Protocol tables

LON 9

IEC101S 4

IEC103M 8

IEC104 4

IEC61850 4

DNP30S 4

DNP30M 9

RP570S 3

TG809S - (only on request)

ACP 4 (not supported from Ver 6.0)

3.15.2. Additional relevant tables

Serial_Line 10

Modem 10

Ethernet_Line 5

ICC_Application 20

68


(ICC_DIA_Data point) 50

Max Queue 240/12 max No. of Applications = 10

NOTE: In total, all configured protocols cannot exceed more than 10 per COM581.

4. REFERENCED DOCUMENT

[1] Operating Instruction for CAP581 1MRB520184- Uen, Edition July 2005

[2] Software Manual for COM581 1MRB520267-Uen, Edition April 2006

5. REVISION HISTORY

Version Chapter Changes Person Date

1.00 Original J. Servoz 02-08-2006

1.01 1.11 1.5

Added-Limitation Added CA for 61850.

J. Servoz 06-08-2006

1.02 2.7 2.10

Command Authority Double command blocking

J. Servoz 15-08-2006

1.03 All Minor changes after review J. Servoz 17-08-2006

69

Notification Form for Errors in this Document Dear User,

We constantly endeavour to improve the quality of our technical publications and would like to hear your suggestions and comments. Would you therefore please fill in this questionnaire and return it to the address given below. ABB Switzerland Ltd Power Systems Betreuung Dokumentation, PS-BD Bruggerstrasse 72 CH-5401 Baden Telefax +41 58 585 35 82

Concerns publication: 1KHA005021-UEN (Additional to 1MRB520184-Uen-CAP581 Extension for V6.2)

Have you discovered any mistakes in this publication? If so, please note here the pages, sections etc. Do you find the publication readily understandable and logically structured? Can you make any suggestions to improve it? Is the information sufficient for the purpose of the publication? If not, what is missing and where should it be included? Name: Date: Company: Postal code: Town: Country:

Notification Form for Equipment Faults and Problems Dear User,

Should you be obliged to call on our repair service, please attach a note to the unit describing the fault as precisely as possible. This will help us to carry out the repair swiftly and reliably, which after all is to your own advantage. Please attach a completed form to every unit and forward them to the address below. Place of delivery Baden/Switzerland: ABB Switzerland Ltd Power Systems Repair Center Warenannahme PT-EG Bruggerstrasse 72 CH-5401 Baden

Equipment data: Unit type:

Serial No.: ……….....................................

In operation since:

Reason for return: (tick where applicable)

Overfunction

No function

Outside tolerance

Abnormal operating temperature

Sporadic error

Unit for checking

Remarks/Description of fault:

Customer: Date: Address: Please contact: Phone: Fax:

Notification Form for Software Errors and Problems Dear User,

As we all know from practice, software does not always function as expected for all applications. A precise description of the problem and your observations will help us to improve and maintain the software. Please complete this form and send it together with any supporting information or documents to the address below. ABB Power Technologies AB Substation Automation Product Support, Supportline SE-721 59 Västerås Sweden Telefax +46 21 14 69 18 E-mail: [email protected] Unit/ COM581 SW Version: System: HMI SW Version: other: SW Version:

Problem: Program error (unit/system) Program error (HMI /PC) Error in manual Suggestion for improvement other:

Can the error be reproduced at will? yes no

Particulars of hardware and software (unit/system configuration including jumper positions, type of PC etc.): Problem located? yes no Suggested changes enclosed? yes no

The following are enclosed (floppy/CD with settings etc.):

Floppy/CD Unit/system settings, file name: other:

Description of problem: Customer: Date: Address: Please contact: Phone: Fax:

mailto:[email protected]

DESCRIPTION OF PROBLEM: (continuation) ___________________________________________________________________ACTION (internal use of ABB Sweden only)

Received by: Date: Answered by: Date:

Problem solved? yes no

Week: Name: Position: Consequence:

IMPORTANT NOTICE! Experience has shown that reliable operation of our products is assured, providing the information and recommendations con-tained in these Operating Instructions are adhered to. It is scarcely possible for the instructions to cover every eventu-ality that can occur when using technical devices and systems. We would therefore request the user to notify us directly or our agent of any unusual observations or instances, in which these instructions provide no or insufficient information. In addition to these instructions, any applicable local regulations and safety procedures must always be strictly observed both when connecting up and commissioning this equipment. Any work such as insertion or removal of soldered jumpers or setting resistors, which may be necessary, may only be per-formed by appropriately qualified personnel. We expressly accept no responsibility for any direct damage, which may result from incorrect operation of this equipment, even if no reference is made to the particular situation in the Operating Instructions.

ABB Switzerland Ltd Power Systems Bruggerstrasse 72 CH-5400 Baden / Switzerland Phone +41 58 585 77 44 Fax +41 58 585 55 77 E-mail [email protected] www.abb.com/substationautomation

Printed in Switzerland (0608-0000-0)

www.abb.com/substationautomation

Documents

Configuration Tool for COM581 - library.e.abb.com · PDF fileDNP3 Master Measurement .....30 1 . ABB Switzerland Ltd 1KHA005021-UEN Extension ... Command Authority overview.....42