______________________________________________________________________________ Preface, Table of Contents ______________________________________________________________________________ Protocol Element 1 2 3 4 5 6 7 8 9 ______________________________________________________________________________ ACP 1703 • Ax 1703 Architecture and Data Flow ______________________________________________________________________________ Point-to-Point Traffic (BPP) ______________________________________________________________________________ Common Functions Multi-Point Traffic (UMP) ______________________________________________________________________________ Interfacing of Protective Devices (103) ______________________________________________________________________________ Protocol Elements SICAM 1703 Field Bus (SFB) ______________________________________________________________________________ Dial-Up Traffic (DIA) ______________________________________________________________________________ LAN Communication (104) ______________________________________________________________________________ LAN Communication (61850) ______________________________________________________________________________ Appendix ______________________________________________________________________________ Literature ______________________________________________________________________________ DC0-023-2.01 Hint Please observe Notes and Warnings for your own safety in the Preface. Disclaimer of Liability Although we have carefully checked the contents of this publication for conformity with the hardware and software described, we cannot guarantee complete conformity since errors cannot be excluded. Dennoch können Abweichungen nicht ausgeschlossen werden, so dass wir für die vollständige Übereinstimmung keine Gewähr übernehmen. The information provided in this manual is checked at regular intervals and any corrections that might become necessary are included in the next releases. Any suggestions for improvement are welcome. Copyright Copyright © Siemens AG 2007 The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Subject to change without prior notice. Identification Version.Revision Release date GF PRE ACP.201 2.01 03.08.2007 Siemens Aktiengesellschaft Bestellnr.: DC0-023-2.01 Preface This document is applicable to the following product(s): • Ax 1703 • ACP 1703 Purpose of this manual This handbook describes the function and method of operation of the protocol elements acc. to IEC 60870-5-101/103/104, that are supported on the ACP 1703 platforms. It is intended for users of the target group stated below and essentially consists of • Functional descriptions • Descriptions of interfaces to the process and other system elements • Principle wiring diagrams, and examples Target Group The document you are reading right now is addressed to users, who are in charge of the following engineering tasks: • Conceptual activities, as for example design and configuration • System parameterization and system diagnostic, using the designated engineering tools • Technical system maintenance Notes on Safety This manual does not constitute a complete catalog of all safety measures required for operating the equipment (module, device) in question because special operating conditions might require additional measures. However, it does contain notes that must be adhered to for your own personal safety and to avoid damage to property. These notes are highlighted with a warning triangle and different keywords indicating different degrees of danger. Danger means that death, serious bodily injury or considerable property damage will occur, if the appropriate precautionary measures are not carried out. Warning means that death, serious bodily injury or considerable property damage can occur, if the appropriate precautionary measures are not carried out. Caution means that minor bodily injury or property damage could occur, if the appropriate precautionary measures are not carried out. Hint is important information about the product, the handling of the product or the respective part of the documentation, to which special attention is to be given. Qualified Personnel Commissioning and operation of the equipment (module, device) described in this manual must be performed by qualified personnel only. As used in the safety notes contained in this manual, qualified personnel are those persons who are authorized to commission, release, ground, and tag devices, systems, and electrical circuits in accordance with safety standards. Use as Prescribed The equipment (device, module) must not be used for any other purposes than those described in the Catalog and the Technical Description. If it is used together with third-party devices and components, these must be recommended or approved by Siemens. Correct and safe operation of the product requires adequate transportation, storage, installation, and mounting as well as appropriate use and maintenance. During operation of electrical equipment, it is unavoidable that certain parts of this equipment will carry dangerous voltages. Severe injury or damage to property can occur if the appropriate measures are not taken: • Before making any connections at all, ground the equipment at the PE terminal. • Hazardous voltages can be present on all switching components connected to the power supply. • Even after the supply voltage has been disconnected, hazardous voltages can still be present in the equipment (capacitor storage). • Equipment with current transformer circuits must not be operated while open. • The limit values indicated in the manual or the operating instructions must not be exceeded; that also applies to testing and commissioning. ii DC0-023-2.01 Functions Protocol Elements Typographic and character conventions In this document, reference is often made to important information, notifications and limitations. For clarification, the following conventions are thereby adhered to. Note: Is an important note concerning characteristic or application of the described function Attention: Provides information and explanations, the non-observance of which can lead to faulty behavior of the system. technical term or phrase This syntax, for the purpose of easier readability, identifies a term (also consisting of several words) or a phrase. <parameter group> | <parameter> This syntax identifies a system-technical parameter; for example: Parameter Name Names of parameters are represented in this font, for example IES_pickup value. Common settings | baud rate receiving direction They can also contain the path of the OPM II Tree, which leads to the parameter, for example: Plant-side Settings | Residual Current Measurement | IE_sensitive. Several fundamental terms Spontaneous Information Object A spontaneous information object is an object, which with change is transmitted spontaneously in a message, and is used for the exchange of a process signal or a derived information (including Status) between the system elements of the particular automation unit, another automation unit or a control system. A spontaneous information object is always transmitted individually and normally has a time stamp, in order to be able to establish a chronologically consistent interrelationship later. Message Functions Protocol Elements A message is used for the spontaneous transmission of processand system information. A message contains a spontaneous information object, the address for the unambiguous identification of the information, type identification and additional information necessary for the transmission (e.g. length of the message) DC0-023-2.01 iii iv DC0-023-2.01 Functions Protocol Elements Contents Contents 1. Protocol Element............................................................................................................ 1-1 2. Architecture and Data Flow........................................................................................... 2-1 2.1. 2.1.1. Protocols according to IEC 60870-5-101/103 ............................................. 2-1 2.1.2. Protocols according to IEC 60870-5-104..................................................... 2-3 2.1.3. Protocols according to IEC 61850 ............................................................... 2-4 2.2. 3. Protocol Structure ............................................................................................. 2-1 Data Flow of Process Information..................................................................... 2-5 Point-to-Point Traffic (BPP)........................................................................................... 3-1 3.1. 3.1.1. 3.1.1.1. Communication according to IEC 60870-5-101................................................ 3-4 Data Transmission Procedure ..................................................................... 3-4 Acknowledgement Procedure................................................................. 3-4 3.1.2. Station Initialization...................................................................................... 3-6 3.1.3. Acquisition of Events (transmission of data ready to be sent)..................... 3-6 3.1.4. General Interrogation, Outstation Interrogation ........................................... 3-6 3.1.5. Clock Synchronization ................................................................................. 3-7 3.1.6. Command Transmission.............................................................................. 3-8 3.1.6.1. Control Location ..................................................................................... 3-8 3.1.6.2. Control Location Check .......................................................................... 3-8 3.1.6.3. Set Control Location ............................................................................... 3-9 3.1.7. Transmission of Integrated Totals ............................................................. 3-10 3.1.8. File Transfer............................................................................................... 3-10 3.1.9. Acquisition of Transmission Delay............................................................. 3-10 3.2. Optimized Parameters for selected Transmission Facilities........................... 3-11 3.3. Function for the Support of Redundant Communication Routes.................... 3-15 3.3.1. Redundancy Mode "1703-Redundancy" ................................................... 3-15 3.3.2. Redundancy Mode "Norwegian User Conventions (NUC)"....................... 3-16 3.3.3. Deactivating the Interface .......................................................................... 3-17 3.4. Message Conversion ...................................................................................... 3-18 3.4.1. Blocking ..................................................................................................... 3-18 3.4.2. Special Functions ...................................................................................... 3-19 3.4.2.1. Daylight-Saving Time Bit = 0 for all Messages in Transmit Direction .. 3-19 3.4.2.2. Weekday = 0 for all Messages in Transmit Direction ........................... 3-19 3.4.2.3. Originator Address = 0 for all Messages in Transmit Direction ............ 3-19 3.4.2.4. Convert General Interrogation Command in Receive Direction to BROADCAST 3.4.2.5. Emulate ACTCON+ for Clock Synchronization Command .................. 3-20 3.4.2.6. Emulate ACTCON+/- for Commands ................................................... 3-21 3.4.2.7. Emulate ACTCON+ for Commands ..................................................... 3-22 Functions Protocol Elements DC0-023-2.01 v 3-20 Contents 4. 3.4.2.8. Emulate ACTCON, ACTTERM for Commands with Control Messages3-23 3.4.2.9. Compatibility TCS100 ...........................................................................3-24 3.4.2.10. Settings for Project DBAG / PSI ...........................................................3-24 3.5. Transparent Mode (Tunneling, Container Mode)............................................3-26 3.6. Protocol Element Control and Return Information ..........................................3-29 3.6.1. Protocol Element Control ...........................................................................3-30 3.6.2. Protocol Element Return Information.........................................................3-32 Multi-Point Traffic (UMP)................................................................................................4-1 4.1. 4.1.1. Data Acquisition by Polling (Station Interrogation) ......................................4-4 4.1.1.1. Continuous Interrogation of a Remote Terminal Unit .............................4-7 4.1.1.2. Acknowledgement Procedure.................................................................4-7 4.1.1.3. Failure Monitoring in the Master Station .................................................4-8 4.1.1.4. Failure Monitoring in the Remote Terminal Unit .....................................4-9 4.1.2. Station Initialization ......................................................................................4-9 4.1.3. Acquisition of Events (transmission of data ready to be sent)...................4-10 4.1.3.1. Message from the Remote Terminal Unit to the Master Station ..........4-10 4.1.4. General Interrogation, Outstation Interrogation .........................................4-10 4.1.5. Clock Synchronization ...............................................................................4-11 4.1.6. Command Transmission ............................................................................4-12 4.1.6.1. Message from the Master Station selectively to a Remote Terminal Unit4-12 4.1.6.2. Control Location....................................................................................4-13 4.1.6.3. Control Location Check.........................................................................4-13 4.1.6.4. Set Control Location .............................................................................4-14 4.1.6.5. Message from the Master Station to all Remote Terminal Units (unacknowledged) 4-14 4.1.7. Transmission of Integrated Totals..............................................................4-15 4.1.8. Acquisition of Transmission Delay .............................................................4-15 4.2. Optimized Parameters for selected Transmission Facilities ...........................4-16 4.3. Co-ordination of Several Masters ...................................................................4-22 4.4. Standby Transmission Line over the Public Telephone Network (PSTN) ......4-24 4.5. Data Transmission using Time Slot Radio......................................................4-27 4.6. Data Transmission in Relay Operation “Multi-Point Traffic with Routing”.......4-28 4.6.1. Main and Standby Transmission Line........................................................4-34 4.6.2. Routing Method..........................................................................................4-35 4.6.2.1. Non-optimized Routing Method ............................................................4-36 4.6.2.2. Optimized Routing Method ...................................................................4-37 4.7. Function for the Support of Redundant Communication Routes ....................4-38 4.7.1. Redundancy Mode "1703-Redundancy"....................................................4-38 4.7.2. Redundancy Mode "Norwegian User Conventions (NUC)" .......................4-39 4.8. vi Communication according to IEC 60870-5-101 ................................................4-4 Message Conversion ......................................................................................4-41 4.8.1. Blocking......................................................................................................4-41 4.8.2. Class 1, 2 Data...........................................................................................4-42 4.8.3. Special Functions.......................................................................................4-43 DC0-023-2.01 Functions Protocol Elements Contents 5. 4.8.3.1. Daylight-Saving Time Bit = 0 for all Messages in Transmit Direction .. 4-43 4.8.3.2. Weekday = 0 for all Messages in Transmit Direction ........................... 4-43 4.8.3.3. Originator Address = 0 for all Messages in Transmit Direction ............ 4-43 4.8.3.4. Send GI-Data as Class 1...................................................................... 4-44 4.8.3.5. Timeout Monitoring for GI-Data ............................................................ 4-44 4.8.3.6. Convert General Interrogation Command to BROADCAST in Receive Direction 4.8.3.7. Emulate ACTCON+ for Clock Synchronization Command .................. 4-44 4.8.3.8. Emulate ACTCON+/- for Commands ................................................... 4-45 4.8.3.9. Emulate ACTCON+ for Commands ..................................................... 4-46 4.8.3.10. Message Synchronization .................................................................... 4-46 4.9. Transparent Mode (Tunneling) ....................................................................... 4-47 4.10. Protocol Element Control and Return Information.......................................... 4-50 4.10.1. Protocol Element Control........................................................................... 4-51 4.10.2. Protocol Element Return Information ........................................................ 4-53 4-44 Interfacing of Protective Devices (103) ........................................................................ 5-1 5.1. 5.1.1. Communication according to IEC 60870-5-103................................................ 5-4 Data Acquisition by Polling (Station Interrogation) ...................................... 5-4 5.1.1.1. Continuous Interrogation of a Remote Terminal Unit ............................. 5-7 5.1.1.2. Acknowledgement Procedure................................................................. 5-7 5.1.1.3. Failure Monitoring in the Master Station................................................. 5-8 5.1.1.4. Failure Monitoring in the Remote Terminal Unit..................................... 5-8 5.1.2. Station Initialization...................................................................................... 5-9 5.1.3. Acquisition of Events (transmission of data ready to be sent)................... 5-11 5.1.3.1. Message from the Remote Terminal Unit to the Master Station .......... 5-11 5.1.3.2. Test Mode............................................................................................. 5-11 5.1.4. General Interrogation, Outstation Interrogation ......................................... 5-12 5.1.5. Clock Synchronization ............................................................................... 5-13 5.1.6. Command Transmission............................................................................ 5-14 5.1.6.1. Message from the Master Station selectively to a Remote Terminal Unit5-14 5.1.6.2. Control Location ................................................................................... 5-15 5.1.6.3. Control Location Check ........................................................................ 5-15 5.1.6.4. Set Control Location ............................................................................. 5-16 5.1.6.5. Message from the Master Station to all Remote Terminal Units (unacknowledged) 5-16 5.1.7. Transmission of Integrated Totals ............................................................. 5-17 5.1.8. File Transfer............................................................................................... 5-18 5.1.8.1. 5.1.8.2. Transfer of Disturbance Records to SICAM DISTO ............................. 5-19 Transfer of Disturbance Records to IEC 60870-5-101/104 Systems ... 5-22 5.2. Transfer of Parameters for Reyrolle Protection Equipment............................ 5-23 5.3. Optimized Parameters for selected Transmission Facilities........................... 5-28 5.4. Function for the Support of Redundant Communication Routes.................... 5-33 5.4.1. Redundancy Mode "1703-Redundancy" ................................................... 5-33 5.4.2. Deactivating the Interface .......................................................................... 5-34 5.5. Message Conversion ...................................................................................... 5-35 Functions Protocol Elements DC0-023-2.01 vii Contents 5.5.1. Message Conversion IEC 60870-5-101 IEC 60870-5-103 ...................5-36 5.5.2. Message Conversion IEC 60870-5-101 IEC 60870-5-101 ...................5-55 5.5.3. Message Conversion IEC 60870-5-101 IEC 60870-5-103 (101)..........5-56 5.5.4. Blocking......................................................................................................5-57 5.5.5. Class 1, 2 Data...........................................................................................5-57 5.5.6. Special Functions.......................................................................................5-58 5.5.6.1. Send Short-Circuit Location Values with GI..........................................5-58 5.5.6.2. Resetting the Short-Circuit Location Values .........................................5-58 5.5.6.2.1. Reset the Short-Circuit Location Values with Command ................5-59 5.5.6.2.2. Reset Short-Circuit Location Values automatically .........................5-59 5.5.6.3. Signaling / Measured Value Disabling ..................................................5-60 5.5.6.4. Technological Adaptation for Measured Values ...................................5-60 5.5.6.5. Measured Value Change Monitoring ....................................................5-62 5.5.6.6. Monitoring Intermediate and Faulty Positions of Double-Point Information5-64 5.5.6.7. Transfer of the Information "Blocked Activation/Tripping of the Protection"5-65 5.5.6.8. Transmit Non-Updated Process Images...............................................5-67 5.6. 6. 5.6.1. Protocol Element Control ...........................................................................5-69 5.6.2. Protocol Element Return Information.........................................................5-72 SICAM 1703 Field Bus (SFB) .........................................................................................6-1 6.1. 6.1.1. Communication .................................................................................................6-3 Data Acquisition by Polling (Station Interrogation) ......................................6-3 6.1.1.1. Continuous Interrogation of a Remote Terminal Unit .............................6-5 6.1.1.2. Acknowledgement Procedure.................................................................6-5 6.1.1.3. Failure Monitoring in the Master Station .................................................6-6 6.1.1.4. Failure Monitoring in the Remote Terminal Unit .....................................6-6 6.1.2. Station Initialization ......................................................................................6-7 6.1.3. Acquisition of Events (transmission of data ready to be sent).....................6-7 6.1.3.1. Message from the Remote Terminal Unit to the Master Station ............6-7 6.1.4. General Interrogation, Outstation Interrogation ...........................................6-8 6.1.5. Clock Synchronization .................................................................................6-8 6.1.6. Command Transmission ..............................................................................6-9 6.1.6.1. Message from the Master Station selectively to a Remote Terminal Unit6-9 6.1.6.2. Message from the Master Station to all Remote Terminal Units (unacknowledged) 6-9 6.1.7. Transmission of Integrated Totals................................................................6-9 6.2. Optimized Parameters for selected Transmission Facilities ...........................6-10 6.3. Function for the Support of Redundant Communication Routes ....................6-14 6.3.1. 6.4. Redundancy Mode "1703-Redundancy"....................................................6-14 Message Conversion ......................................................................................6-15 6.4.1. Blocking......................................................................................................6-15 6.4.2. Class 1, 2 Data...........................................................................................6-15 6.5. 6.5.1. viii Protocol Element Control and Return Information ..........................................5-68 Protocol Element Control and Return Information ..........................................6-16 Protocol Element Control ...........................................................................6-17 DC0-023-2.01 Functions Protocol Elements Contents 6.5.2. 7. Protocol Element Return Information ........................................................ 6-19 Dial-Up Traffic (DIA) ....................................................................................................... 7-1 7.1. 7.1.1. 7.1.1.1. 7.1.2. Control of Connection Setup and Disconnection.............................................. 7-3 Connection Establishment spontaneously and cyclically, Controlling Station Controlled Station.......................................................................................................... 7-4 Cyclic Connection Setup at a settable Interval (monitoring cycle) ....... 7-12 Connection Setup Control via Modem Commands ................................... 7-14 7.1.2.1. AT-Hayes.............................................................................................. 7-14 7.1.2.2. AT-Hayes (ETSI) .................................................................................. 7-15 7.1.2.3. V.25bis.................................................................................................. 7-15 7.1.2.4. X.20 ...................................................................................................... 7-15 7.1.2.5. X.28 ...................................................................................................... 7-15 7.1.2.6. Arbitrary Main Telephone Number in a Telephone Network (PSTN)... 7-16 7.1.3. Access Control (LOGIN with Password) in the Private Range of IEC 60870-5-101 7.1.4. Disconnection Control in the Private Range of IEC 60870-5-101 ............. 7-20 7.2. 7.2.1. Communication with existing Connection according to IEC 60870-5-101 ..... 7-23 Data Acquisition by Polling (Station Interrogation) .................................... 7-23 7.2.1.1. Continuous Interrogation of a Remote Terminal Unit ........................... 7-25 7.2.1.2. Acknowledgement Procedure............................................................... 7-25 7.2.1.3. Failure Monitoring in the Master Station............................................... 7-26 7.2.1.4. Failure Monitoring in the Remote Terminal Unit................................... 7-26 7.2.2. Station Initialization.................................................................................... 7-27 7.2.3. Acquisition of Events (transmission of data ready to be sent)................... 7-28 7.2.3.1. 7-19 Message from the Remote Terminal Unit to the Master Station .......... 7-28 7.2.4. General Interrogation, Outstation Interrogation ......................................... 7-28 7.2.5. Clock Synchronization ............................................................................... 7-29 7.2.6. Command Transmission............................................................................ 7-30 7.2.6.1. Message from the Master Station selectively to a Remote Terminal Unit7-30 7.2.6.2. Control Location ................................................................................... 7-31 7.2.6.3. Control Location Check ........................................................................ 7-31 7.2.6.4. Set Control Location ............................................................................. 7-32 7.2.6.5. Message from the Master Station to all Remote Terminal Units (unacknowledged) 7-32 7.2.7. Transmission of Integrated Totals ............................................................. 7-33 7.2.8. Acquisition of Transmission Delay............................................................. 7-33 7.3. SMS Messages............................................................................................... 7-34 7.4. Co-ordination of several Masters in "Multi-Master Mode" .............................. 7-35 7.5. Standby Transmission Line(s) over Standby Telephone Number(s).............. 7-36 7.6. Multi-Hierarchical Configurations.................................................................... 7-36 7.7. Standby Transmission Line via Dial-up Traffic ............................................... 7-37 7.8. Optimized Parameters for selected Transmission Facilities........................... 7-39 7.8.1. Permissible combinations for transmission facilities ................................. 7-48 7.8.2. ASCII Mode ............................................................................................... 7-50 7.8.3. CRC Generator Polynomial ....................................................................... 7-51 Functions Protocol Elements DC0-023-2.01 ix Contents 7.9. Toll-Saving Transmission Strategies ..............................................................7-52 7.10. Having a Telephone Set connected in Parallel ...............................................7-52 7.11. Functions for supporting Redundant Communication Routes ........................7-53 7.11.1. 7.12. Blocking......................................................................................................7-54 7.12.2. Class 1, 2 Data...........................................................................................7-54 Protocol Element Control and Return Information ..........................................7-55 7.13.1. Protocol Element Control ...........................................................................7-56 7.13.2. Protocol Element Return Information.........................................................7-60 LAN Communication (104).............................................................................................8-1 8.1. LAN/WAN Communication over Ethernet TCP/IP according to IEC 60870-5-1048-3 8.1.1. Layer Model – General Information about the Protocols used ....................8-3 8.1.2. Definition of the Connections .......................................................................8-4 8.1.2.1. Data Transmission Procedure ..............................................................8-12 8.1.2.2. Acknowledgement Procedure...............................................................8-14 8.1.2.3. Failure Monitoring .................................................................................8-15 8.1.3. Station Initialization ....................................................................................8-16 8.1.4. Acquisition of Events (transmission of data ready to be sent)...................8-16 8.1.5. General Interrogation, Outstation Interrogation .........................................8-16 8.1.6. Clock Synchronization ...............................................................................8-17 8.1.6.1. Clock Synchronization Command.........................................................8-17 8.1.6.2. Clock Synchronization with Network Time Protocol (NTP)...................8-18 8.1.6.2.1. Clock Synchronization with one or several NTP Servers ................8-19 8.1.6.2.2. Clock Synchronization for one or several NTP Clients....................8-21 8.1.7. Command Transmission ............................................................................8-22 8.1.7.1. Command Transfer Monitoring (dwell time monitoring for data in the network) 8.1.7.2. Transmission of Integrated Totals ........................................................8-23 8.2. Function for the Support of Redundant Communication Routes ....................8-24 8.2.1. PSI-Redundancy (Synchronous Connections) ..........................................8-24 8.2.2. 104-Redundancy - Norwegian User Conventions (NUC) ..........................8-27 8.2.2.1. 104-Redundancy with 1 Ethernet Interface ..........................................8-28 8.2.2.2. 104-Redundancy with 2 Ethernet Interfaces [only ACP 1703] .............8-31 8.2.3. 8.3. Redundancy Mode "1703-Redundancy"....................................................8-34 Message Conversion ......................................................................................8-35 8.3.1. Blocking......................................................................................................8-35 8.3.2. Special Functions.......................................................................................8-36 8.3.2.1. Daylight-Saving Time Bit = 0 for all Messages in Transmit Direction...8-36 8.3.2.2. Weekday = 0 for all Messages in Transmit Direction ...........................8-36 8.3.2.3. Originator Address = 0 for all Messages in Transmit Direction ............8-36 8.3.2.4. Settings for Project DBAG / PSI ...........................................................8-37 8.3.2.5. Settings for Project RWE ......................................................................8-39 8.3.2.5.1. x Message Conversion ......................................................................................7-54 7.12.1. 7.13. 8. Redundancy Mode "1703-Redundancy"....................................................7-53 Bit by Bit Marking of the Field ..........................................................8-40 DC0-023-2.01 Functions Protocol Elements 8-22 Contents 8.3.2.5.2. Cyclic Measured Values .................................................................. 8-41 8.3.2.5.3. Address of the Return Information for Selection Command ........... 8-43 8.3.2.5.4. NT-Bit, IV-Bit according to RWE Requirements.............................. 8-44 8.4. 9. Protocol Element Control and Return Information.......................................... 8-45 8.4.1. Protocol Element Control........................................................................... 8-46 8.4.2. Protocol Element Return Information ........................................................ 8-46 8.5. WEB Server .................................................................................................... 8-47 8.6. Coupling of the SICAM TOOLBOX II over LAN/WAN (remote connection) ... 8-49 8.6.1. Remote Connection over external Terminal Server (connection to M-CPU with TIAX00) 49 8.6.2. Remote Connection over integrated Terminal Server (Telnet).................. 8-50 LAN Communication (61850) ........................................................................................ 9-1 9.1. LAN Communication over Ethernet TCP/IP according to IEC 61850............... 9-4 9.1.1. Objects and Data ......................................................................................... 9-9 9.1.2. Definition of the Connections..................................................................... 9-23 9.1.2.1. Data Transmission Procedure .............................................................. 9-26 9.1.2.2. Failure Monitoring ................................................................................. 9-27 9.1.3. Station Initialization.................................................................................... 9-28 9.1.4. Acquisition of Events (transmission of data ready to be sent)................... 9-29 9.1.4.1. 9.1.4.2. Data Transmission Server Client ..................................................... 9-29 Data Transmission Server Server with "GOOSE" [only server] ..... 9-31 9.1.5. General Interrogation, Outstation Interrogation ......................................... 9-35 9.1.6. Clock Synchronization ............................................................................... 9-36 9.1.6.1. Clock Synchronization with Network Time Protocol (NTP) .................. 9-36 9.1.6.1.1. Clock Synchronization with one or several NTP Servers................ 9-37 9.1.6.1.2. Clock Synchronization for one or several NTP Clients ................... 9-38 9.1.7. 9.1.7.1. Command Transmission............................................................................ 9-39 Control Location [Client only]................................................................ 9-43 9.1.7.1.1. Control Location Check ................................................................... 9-43 9.1.7.1.2. Set Control Location ........................................................................ 9-44 9.1.7.2. 9.1.8. Transmission of Integrated Totals ........................................................ 9-45 File Transfer (disturbance records) ........................................................... 9-46 9.1.8.1. Transfer of Disturbance Records to SICAM DISTO ............................. 9-47 9.1.8.2. Transmission of Disturbance Records [SICAM 1703 = Server] ........... 9-48 9.2. Function for the Support of Redundant Communication Routes.................... 9-49 9.2.1. Redundancy Mode "1703-Redundancy" ................................................... 9-49 9.2.2. Server Redundancy ................................................................................... 9-50 9.2.3. GOOSE Redundancy ................................................................................ 9-51 9.3. Protocol Element Control and Return Information.......................................... 9-52 9.3.1. Protocol Element Control........................................................................... 9-53 9.3.2. Protocol Element Return Information ........................................................ 9-54 9.4. 9.4.1. Message Conversion ...................................................................................... 9-55 Special Functions ...................................................................................... 9-64 Functions Protocol Elements DC0-023-2.01 xi 8- Contents xii 9.4.1.1. Conversion of the Time Information......................................................9-64 9.4.1.2. Signaling / Measured Value Disabling [Client only] ..............................9-65 9.4.1.3. Emulation of the Going Binary Information [Client only] .......................9-66 9.4.1.4. Emulation of the Data on Reception of the Attribute Beh.stVal="OFF" [Client only] 9-66 9.4.1.5. Technological Adaptation for Measured Values ...................................9-67 9.4.1.6. Measured Value Change Monitoring ....................................................9-69 9.4.1.7. Monitoring Intermediate and Faulty Positions of Double-Point Information [Client only] 71 9.4.1.8. Logging of the Remote Commands at the Local Control Centre [Server only] 9-72 9.4.1.9. Remote Parameterization/Diagnostic of SICAM 1703 Components via 61850 9-72 9.5. WEB Server.....................................................................................................9-73 9.6. Coupling of the SICAM TOOLBOX II over LAN (remote connection).............9-97 9.6.1. Remote Connection over external Terminal Server (connection to M-CPU with TIAX00) 97 9.6.2. Remote Connection over integrated Terminal Server (Telnet)..................9-98 DC0-023-2.01 Functions Protocol Elements 9- 9- Protocol Element 1. Protocol Element A protocol element is used for the exchange of data - and thereby for the transmission of messages - over a communication interface to other automation units or devices of third-party manufacturers, e.g. control systems. The task of the protocol element is: • the handling of specifical communication protocols with the communication of SICAM 1703 automation units among themselves or with devices of other manufacturers. • the adaption of the internal message formats to the corresponding external message formats. • the adaption of system and adressing concepts of SICAM 1703 and the devices of other manufacturers. Thereby it is distinguished between protocol elements with serial communication or with LAN / WAN communication. Serial communication For serial communication are available as standard protocols: • point-to-point traffic • multi-point traffic, optionally with relay operation • dial-up traffic The standard protocols are based on the interoperable standard to IEC 60870-5-101 Yet, there is still a whole series of other available protocols such as: • counter interfacing according to IEC 61107 • interfacing of protective devices according to IEC 60870-5-103 • Modbus • Profibus DP • DNP 3.0 LAN/WAN communication For the LAN/WAN communication Ethernet TCP/IP according to IEC 60870-5-104 or IEC 61850 is used. Functions Protocol Elements DC0-023-2.01 1-1 Protocol Element 1-2 DC0-023-2.01 Functions Protocol Elements Architecture and Data Flow 2. Architecture and Data Flow 2.1. Protocol Structure 2.1.1. Protocols according to IEC 60870-5-101/103 Protocols according to the standards of the series IEC 60870-5 are based on the three-layer model „Enhanced Performance Architecture“, refer to IEC 60870-5-3, Section 4. This model has been developed especially for telecontrol systems which require particularly short reaction times in combination with low-bandwidth transmission networks. Protocols based on this architecture utilize only three layers of the ISO-OSI-reference model (Layer model for the communication of open systems), namely the bit transmission layer, the link layer and the application layer. The physical layer utilizes ITU-T recommendations for the binary symmetric and memoryless transmission on the required medium, in order to ensure the high data integrity of the block encoding method in the link layer. Functions Protocol Elements DC0-023-2.01 2-1 Architecture and Data Flow The following picture shows the model of the enhanced performance architecture (EPA) and the standard definitions selected for this application-related standard. AP IEC60870-5-101/-103 IEC 60870-5-5 Protocol specific functions 7 IEC 60870-5-3, IEC 60870-5-4 6 5 4 3 Layer 3-6 are not used in the EPA-layer model ! 2 IEC 60870-5-2, IEC 60870-5-1 1 Selectet ITU-T-recommendations Legend: Layer Task Functions, Characteristics, Comments • Transmission protocol for basic telecontrol tasks acc. to IEC 60870-5-101 or Transmission protocol for the information interface of protection equipment acc. to IEC 60870-5-103 • Selected application functions acc. to IEC 60870-5-5 • Protocol-specific functions AP- Application processes 7 – Application layer 2-2 …. IEC 60870-5-101-/103 Application Data format • Selected information elements of the application layer acc. to IEC 60870-5-4 • Selected service data units of the application layer acc. to IEC 60870-5-3 6 – Representation layer • - 5 – Communication control layer • - 4 – Transport layer • - 3 – Network layer • - 2 – Link layer • Selected transmission procedures of the link layer acc. to IEC 60870--5--2 • Selected message formats acc. to IEC 60870-5-1 1 – Bit transmission layer (Physical) • Selected ITU-T recommendations DC0-023-2.01 Functions Protocol Elements Architecture and Data Flow 2.1.2. Protocols according to IEC 60870-5-104 Protocols according to the IEC 60870-5-104 standard are based on the OSI layer model. 7 6 5 IEC 60870-5-5 Application Procedures IEC 60870-5-104 APCI TELNET TCP 4 3 2 HTTP APDU NTP UDP IP ICMP IP Encapsulation ARP Legende: APDU ……….. Application Protocol Data Unit (IEC 60870-5-104) APCI ……...…. Application Protocol Control Information (IEC 60870-5-104) ARP ……...….. Address Resolution Protocol HTTP ….....….. Hyper Text Transfer Protocol ICMP …..…….. Internet Control Message Protocol IP …………….. Internet Protocol NTP ………….. Network Time Protocol TCP …….……. Transmission Control Protocol UDP ……….…. User Datagram Protocol IP Encapsulation RFC 894 1 Ethernet Layer …. IEC 60870-5-104 Task Functions, Characteristics, Comments 7 - Application Application • Transmission handling • Reception handling • Management of up to 100 connections 6 - Presentation Data format • IEC 60870-5-104 APDU's to Ax 1703 / ACP 1703 and compatible systems In the "private range" according to IEC 60870-5-104, Ax 1703 / ACP 1703-specific system messages and some user data are implemented 5 - Session Interface between data format and communication protocol • IEC 60870-5-104 APCI • NTP according to RFC 1305 • TELNET according to RFC 854 4 - Transport 3 - Network Communication protocol • TCP/IP according to RFC 791 and RFC 793 • ICMP according to RFC 792 2 - Data Link 1 - Physical LAN interface • Ethernet 10/100 Mbps according to IEEE 802.3 • Medium and transmission rate can be selected with SICAM TOOLBOX II • Connection technique (on the master control or communication element) RJ45 for copper and MT-RJ connector for FO • ARP according to RFC 826 • IP Encapsulation according to RFC 894 Functions Protocol Elements DC0-023-2.01 2-3 Architecture and Data Flow 2.1.3. Protocols according to IEC 61850 Protocols according to the IEC 61870-5 standard are based on the OSI layer model. Layer 2-4 Task Functions, Characteristics, Comments 7 - Application Application • Transmission handling • Reception handling • Management of multiple connections 6 - Presentation Data format • IEC 61850 ACSI to Ax 1703 / ACP 1703 and compatible systems In the "private range" according to IEC 60870-5-104, Ax 1703 / ACP 1703-specific system messages and some user data are implemented (e.g. transmission of disturbance records to SICAM DISTO) 5 - Session Interface between data format and communication protocol • • • • • 4 - Transport 3 - Network Communication protocol • TCP/IP according to RFC 791 and RFC 793; GOOSE • ICMP according to RFC 792; GOOSE 2 - Data Link 1 - Physical LAN interface • Ethernet 10/100 Mbps according to IEEE 802.3; GOOSE • Medium and transmission rate can be selected with SICAM TOOLBOX II • Connection technique (on the master control or communication element) RJ45 for copper and MT-RJ connector for FO • ARP according to RFC 826 • IP Encapsulation according to RFC 894 GOOSE MMS HTTP TELNET according to RFC 854 NTP according to RFC 1305 DC0-023-2.01 Functions Protocol Elements Architecture and Data Flow 2.2. Data Flow of Process Information Process signals TM Bus Prozess Peripherals IEC60870-5-101/104 Process Input/Output I/O Modul Prozess Peripherals IEC60870-5-101/104 Peripheral element Process Input/Output Peripheral element I/O Modul Ax 1703 PE-Bus Processing of Commands Diagnostic Error messages IEC60870-5-101/104 Communication function Basic system element Internal distribution of messages with process information (Data flow control) Protocol element control Node Bus Open-/ClosedLoop Control Function ZBG Bus Protocol element Protocol element Transmission route Telecontrol Messages with process informations Automation periodical information Functions Protocol Elements DC0-023-2.01 2-5 Architecture and Data Flow 2-6 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) 3. Point-to-Point Traffic (BPP) Point-to-point traffic describes a serial communications protocol with which a master station is connected with a remote terminal unit over a communication link in a point-to-point configuration. Each station has equal access and can spontaneously perform a data transmission. Master Station TF TF Remote station Legende: TF ………..….. Transmission facility (for full duplex transmission route) In point-to-point traffic a "symmetric transmission procedure" is used. That means, that every station can initiate message transmissions. As a result, every station in point-to-point traffic performs both the functions of the primary station as well as the functions of the secondary station. The function to be performed is determined through the initiation of the data transmission. For point-to-point traffic a "full duplex" transmission medium is required. Functions Protocol Elements DC0-023-2.01 3-1 Point-to-Point Traffic (BPP) General Functions Communication with a remote station • Balanced Point-to-Point (point-to-point traffic) according to IEC 60870-5-101 ─ Supported functionality according to − ACP 1703 Interoperability IEC 60870-5-101/104 (DC0-013-1) − Ax 1703 Interoperability IEC 60870-5-101/104 (DA0-046-1) ─ Acquisition of events (transmission of data ready to be sent) ─ General interrogation, outstation interrogation ─ Clock synchronization − Cyclic, at least 1 times per minute ─ Command transmission − Set control location, control location check ─ Transmission of integrated totals ─ Acquisition of transmission delay (for the correction of time synchronisation) • Optimized parameters for selected transmission facilities • Functions for supporting redundant communication routes • Special functions The operating mode of the interface is determined by parameters of the protocol element and optional equipment. Standard Operation Mode Unbalanced interchange circuit V.24/V.28 Parameter and Setting Interface signals on RJ45 connector Asynchronous / Isochronous Asynchronous RXD, TXD, CTS, RTS, DCD, DTR, DSR/+5V, GND V.28 asynchronous Optional Operation Mode Parameter and Setting Balanced interchange circuit X.24/X.27 Asynchronous / Isochronous V.11 isochronous Interface signals on RJ45 connector Isochronous Bit timing internal RXD, TXD, CTS, TXC, DCD, DTR, DSR/+5V, GND Bit timing external RXD, TXD, RTS, RXC, DCD, DTR, DSR/+5V, GND with CM-0829 Balanced interface RS-422 Asynchronous / Isochronous V.11 asynchronous Asynchronous Optical interface (multimode fibre optic) Asynchronous / Isochronous RXD, TXD, CTS, RTS, DCD, DTR, DSR/+5V, GND Asynchronous RXD, TXD, +5V, GND with CM-0827 3-2 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) For the communication with a remote station in point-to-point traffic according to IEC 60870-5-101 the following basic settings are required: • • • Address of the link layer Number of octets for the address of the link layer Station type For this, in the master / remote terminal unit the parameter advanced parameters | IEC 60870-5101 | Address field of the link and the parameter advanced parameters | IEC 60870-5101 | Addres field of the link (number) must be set according to the selected definition. For the communication with a remote station in point-to-point traffic according to IEC 60870-5-101 in addition the setting of the parameter Common settings | Station type is required. Thereby a station is to be assigned either "Station A" or "Station B". Station type "Own Station" Station type "Remote Station" Station A Station B Station B Station A For the coupling of different systems with the IEC 60870-5-101 protocol, the setting of the variable elements of the message is required. These parameters are shown in the Interoperability List. The following table provides an overview of which IEC-parameters are to be parameterized on which system elements. IEC 60870-5-101 Parameter Description System Element bytes link address Number of octets for the address field of the link layer PRE Cause of transmission (COT) Number of octets for cause of transmission BSE Common address of ASDU (CASDU) Number of octets for common address of the ASDU BSE Information object address (IOA) Number of octets for the address of the information object BSE Acknowledgement on IEC 60870-5-2 layer Single character or short message (ACK) PRE Maximum message length Time Stamp Legend: BSE Number of octets for time stamp BSE SSE = Supplementary system element (with serial interfaces, this is always configured with a PRE) PRE = Protocol element BSE = Basic system element Functions Protocol Elements DC0-023-2.01 3-3 Point-to-Point Traffic (BPP) 3.1. Communication according to IEC 60870-5-101 3.1.1. Data Transmission Procedure The transmission of the data from the remote terminal unit to the master station as well as from the master station to the remote terminal unit takes place spontaneously. The prioritization and blocking of the data to be sent takes place on the basic system element (BSE). The data transmission is started after a startup or, with redundancy switchover after successful station initialization. If a remote station (secondary station) can presently not process more data messages (messages), for the data flow control the DFC bit (Data Flow Control) is set in the control field of the message direction secondary station primary station. From this moment the protocol firmware of the primary station sends no more data messages to the remote station, until the remote station resets the DFC-bit. In addition a warning is output by the protocol element of the primary station. The data are stored in the data storage of the communication function on the basic system element (BSE) until these are deleted by the dwell time monitoring or can be transmitted to the remote station. The primary station also monitors whether the secondary station resets the DFC-bit within a time that can be set with the parameter advanced parameters | IEC 60870-5-101 | DFC-monitoring time. The state of the DFC-bit of the secondary station is interrogated by the primary station by means of cyclic messages "REQUEST STATUS OF LINK". The cycle time can be set with the parameter advanced parameters | IEC 60870-5-101 | Polling cycle for stations with "DFC-bit = 1". If the DFC-bit is present for longer than the set monitoring time, the interface is reported as failed. 3.1.1.1. Acknowledgement Procedure All sent data messages must be acknowledged by the other station (secondary station). If, with non-faulty transmission line, the acknowledgement is missing for longer than the expected acknowledgement time, transmitted messages are repeated up to n-times (n can be parameterized). On expiry of the number of retries, the station is flagged as faulty. The required expected acknowledgement time is determined automatically from the set parameters, but if necessary can be extended accordingly with the parameter advanced parameters | monitoring times | expected_ack_time_corr_factor. This is then the case if additional signal propagation delays, delay times or slow processing times of the connected stations must be taken into consideration. The number of retries for data messages is to be set with the parameter Message retries | Retries for data message SEND/CONFIRM or for messages for station initialization with the parameter Message retries |Retries for INIT-messages SEND/CONFIRM. The acknowledgement can be transmitted optionally as single character (E5) or as message with fixed length (ACK). If no additional information is to be transmitted, as standard the single character (E5) is used for acknowledgement, however some third-party systems always expect the acknowledgement as message with fixed length. The message type for the acknowledgement can be selected with the parameter advanced parameters | IEC 60870-5-101 | Acknowledgement IEC 60870-5-2". 3-4 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) Failure Monitoring The monitoring of the interface by the active master / remote terminal unit takes place by means of cyclic transmitted (subject to acknowledgement) messages or by means of a cyclic executed "Test function of the link layer ". The interface monitoring with "Test function of the link layer" can be parameterized with the parameter advanced parameters | interface_monitoring "cycle time". On expiry of the retry number the remote station is reported as failed. No further data are sent to a failed remote station until successful station initialization. The data are stored in the data storage of the communication function on the basic system element (BSE) until these are deleted by the dwell time monitoring or can be transmitted to the re-reachable remote station. Functions Protocol Elements DC0-023-2.01 3-5 Point-to-Point Traffic (BPP) 3.1.2. Station Initialization After startup or redundancy switchover, the operation of the interface is begun after successful station initialization. The initialization of the link layer of the remote terminal unit is performed by the master station with: • • "Request for the status of the link layer (REQUEST STATUS OF LINK) Reset of the remote terminal unit link layer (RESET OF REMOTE LINK) Reset Command Function in the Remote Station REQUEST STATUS OF LINK - "STATUS OF LINK" is transmitted to the remote station RESET of REMOTE LINK - FCB-Bit (Frame Count Bit) is initialized - Acknowledgement for RESET of REMOTE LINK is transmitted to remote station Initialization End If "Send Initialization End" is enabled on the basic system element in the IEC 60870-5-101/104 parameter block, after the station initialization is performed, data are only sent from the protocol element if the "INIT-End" has been received from the basic system element for the corresponding ASDU. "<TI=70> Initialization End" is also transmitted to the remote station. The clock synchronization command or general interrogation command may only be transmitted after "INIT-End". 3.1.3. Acquisition of Events (transmission of data ready to be sent) The transmission of data ready to be sent from the remote terminal unit to the master station as well as from the master station to the remote terminal unit takes place spontaneously. The prioritization and blocking of the data ready to be sent takes place on the basic system element (BSE). The data transmission is started after a startup or, with redundancy switchover after successful station initialization. For further details, refer to chapter "Data Transmission Procedure"! 3.1.4. General Interrogation, Outstation Interrogation The general interrogation (outstation interrogation) function is used to update the master station after the internal station initialization or after the master station has detected a loss of information. The function general interrogation of the master station requests the remote terminal unit to transmit the actual values of all its process variables. 3-6 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) 3.1.5. Clock Synchronization Setting the time The clock synchronization command is sent to the remote station by the protocol element spontaneously with a change of the time and for remote synchronization cyclic 1x per minute. The clock synchronization command is sent between the 20th and 50th second of the running minute. The transmit moment is determined based on the set parameters (baud rate, message length, number of retries) and a possible presently running message transmission, so that the clock synchronization command arrives in the remote station in all cases before the minute change. The clock synchronization command is sent at the transmit moment, exactly synchronized to the internal 10ms cycle. The time in the message corresponds to the absolute time of the 1st bit during the transmission on the line. Messages, which are sent after a startup, but before the SICAM 1703 remote terminal unit has the correct time, contain the relative time from startup (reference day: 1.1.2001) with the flagging of the time stamp as invalid. Remote Synchronization The clock synchronization of the remote station can be performed over the serial communication line – controlled by the master station. The transmission of the clock synchronization command is activated with the parameter advanced parameters | Send clock sychronization command cyclic. The remote synchronization is performed cyclic by the master station 1x per minute. The transmission of the clock synchronization command always takes place with high priority at the end of the running minute (between the 50th and 59 second). The clock synchronization command is sent at the transmit moment, exactly synchronized to the internal 10ms cycle. The time in the message corresponds to the absolute time of the 1st bit during the transmission on the line. The typical accuracy achieved through this is ± 20 ms. If the accuracy of the remote synchronization is insufficient, a local time signal receiver must be used in the remote station. Functions Protocol Elements DC0-023-2.01 3-7 Point-to-Point Traffic (BPP) 3.1.6. Command Transmission Data messages in command direction are always sent spontaneously by the master station to the remote station. The prioritization and blocking of the data to be sent already takes place on the basic system element (BSE). For further details, refer to chapter "Data Transmission Procedure"! 3.1.6.1. Control Location If the function "Control location" is activated, commands from the protocol element of the master station are only then transmitted to the remote terminal unit (remote station) if the command has been sent from an enabled control location (originator address). The setting of the control location itself takes place with a command message in single command format <TI=45> which is converted on the basic system element to a PRE control message (function: set control location) by the protocol control function. A command received with an originator address not enabled as control location is not transmitted from the protocol element of the master station and is discarded. For these commands a negative confirmation of activation (ACTCON-) is sent back immediately by the protocol element to the originator address. 3.1.6.2. Control Location Check The control location check is used to check whether the control location, specified with the originator address in the spontaneous information object "Command", has command authority. The originator address specified in the spontaneous information object "Command" must correspond with the control location previously set. If the originator address in the spontaneous information object "Command" does not match the control locations previously set or if no control location has been preset: • the command is rejected • a negative confirmation of the activation is sent (ACTCON-) The control location check is activated as soon as a PRE control message of the type "Set control location" is entered in the PST detailed routing on the basic system element (BSE) for a protocol element (PRE). After startup of the PRE, the BSE sends a PRE control message "Set control location" to the PRE. As a result the control location check function is activated on the PRE. 3-8 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) 3.1.6.3. Set Control Location The control location is set on the PRE with a PRE-control message (Function = Set control location) either globally for all stations or station-selective. The control location can be set or deleted and is applicable for all commands of a protocol element. On the BSE the control location is set by the spontaneous information object "control location" and is valid for all commands of a protocol element. The assignment of this message takes place in the OPM of the Toolbox II with the category ACP 1703 Systemfunktionen / protocol element control message. For the derivation of the control location, the following values in the spontaneous information object "Command" signify the originator address: Note: Originator Address Control Location 0 default 1 ... 127 remote command 128 ... 255 local command The selection of the control location and the generation of the spontaneous information object "Control location" must be programmed in an application program of the open-/closed-loop control function. With the spontaneous information object "Control location" in "single command" format, up to 256 control locations can be set at the same time. The information object "Control location" is converted on the basic system element (BSE) to a PRE-control message and passed on to the protocol element. Due to an information object "Control location" with the single command state "ON", the originator address is added to the list of enabled control locations (="Control location enabled"). Due to an information object "Control location" with the single command state "OFF", all originator addresses are deleted from the list of enabled control locations (="All control locations not enabled"). No confirmation (ACTCON) and no termination (ACTTERM) of the command initiation is created for the information object "Control location". With each startup of the protocol element, all enabled control locations are reset. The control location(s) is/are to be set with each startup of the system element. Functions Protocol Elements DC0-023-2.01 3-9 Point-to-Point Traffic (BPP) 3.1.7. Transmission of Integrated Totals A counter interrogation command triggered in the system is transmitted acknowledged from the protocol element to the remote station. The functionality implemented in the System SICAM 1703 concerning integrated totals is documented in the document "Common Functions of Peripheral Elements according to IEC 60870-5-101/104". 3.1.8. File Transfer The protocol element sends all message formats received from the basic system element (BSE) that are defined for the transfer of files to the remote station. All message formats received from the remote station for the transfer of files are passed on by the protocol element to the basic system element. The protocol element itself performs no functions for the transfer of files. Messages for the transfer of files are passed on "transparently". Limitation: For the transfer of files the System SICAM 1703 supports only max. 200 data bytes per segment! 3.1.9. Acquisition of Transmission Delay The protocol element supports the function "Acquisition of transmission delay" and the time correction resulting from this with clock synchronization according to IEC 60870-5. With this procedure the transmission delay is determined with <TI=106> and the corrected time loaded in the remote station. The correction of the time in the clock synchronization command is performed in the remote station. The acquisition of the monitoring time is performed cyclic every "2 minutes". The "Correction time for clock synchronization command" is produced from: • Message delay • Transmission delay The clock synchronization command is transmitted cyclic 1x per minute to the remote station. The time in the clock synchronization command corresponds to the absolute moment of the 1st bit during the transmission on the line. See also chapter "Clock Synchronization"! 3-10 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) 3.2. Optimized Parameters for selected Transmission Facilities The protocol element requires a "full duplex" link. For the adaptation to various modems or time requirements of external systems, the following parameters can be set individually: • Common settings | electrical interface • Common settings | asynchron/isochron • Common settings | source for receive-/transmit clock (only for "Isochronous") • Common settings | advanced time settings | pause time (tp), Common settings | advanced time settings | pause time "time base" (tp) • Common settings | advanced time settings | set up time (tv), Common settings | advanced time settings | set up time "time base" (tv) • Common settings | advanced time settings | run-out time (tn), Common settings | advanced time settings | run-out time "time base" (tn) • Common settings | advanced time settings | DCD handling • Common settings | advanced time settings | bounce suppression time (tprell) • Common settings | advanced time settings | disable time (tdis), Common settings | advanced time settings | disable time "time base" (tdis), • Common settings | advanced time settings | stability monitoring time (tstab) • Common settings | advanced time settings | continuous level monitoring time (tcl) • Common settings | advanced time settings | Transmission delay if countinous level (tcldly) • advanced parameters | 5V supply (DSR) • advanced parameters | Configuration for CM-082x [SM2541 only] [only SM0551, SM2551] [only SM0551, SM2551] How the individual time settings are effective during the data transmission is shown on the following page in a Timing Diagram. Parameter "5V Supply (DSR)" [only SM0551, SM2551] If necessary the voltage supply of the transmission facility (only 5V) – insofar as this is sufficient – can take place over the state line DSR. The enabling of the voltage supply is performed with the parameter advanced parameters | 5V supply (DSR). The voltage supply is only switched on the DSR state line instead of the DSR signal with corresponding parameter setting. ATTENTION: Required voltage supply and maximum current consumption of the transmission facility must be observed! Parameter "Configuring for CM082x" [only SM0551, SM2551] If an optical transformer of the type CM082x is used as external transmission facility, then the parameter advanced parameters | Configuration for CM-082x must be set when using a patch plug of the type CM2860. Most transmission facilities support only certain baud rates or combinations of baud rates in transmit/receive direction – these are to be taken from the descriptions for the transmission facility. The transmission rate (baud rate) is to be set depending on the submodule used for communication, separate for transmit/receive direction with the parameter Common settings | baud rate receiving direction and the parameter Common settings | baud rate transmit direction or for transmit/receive direction together with the parameter Common settings | baud rate. In addition, for the adaptation of the protocol to the transmission medium used or to the dynamic behavior of the connected remote station, the following parameters are available: Functions Protocol Elements DC0-023-2.01 3-11 Point-to-Point Traffic (BPP) • advanced parameters | monitoring times | Character monitoring time, advanced parameters | monitoring times | Character monitoring time "time base" • advanced parameters | monitoring times | idle monitoring time, advanced parameters | monitoring times | idle monitoring time "time base" • advanced parameters | monitoring times | expected_ack_time_corr_factor (see Acknowledgement Procedure) The character monitoring time and idle monitoring time is used for message interruption monitoring and message re-synchronization in receive direction. A message interruption is detected if the time between 2 bytes of a message is greater than the set character monitoring time. With message interruption the running reception handling is aborted and the message is discarded. After a detected message interruption a new message is only accepted in receive direction after an idle time on the line (idle time). The protocol element can – insofar as the transmission facility (e.g. VFT-channel) makes this signal available receive-side – evaluate the interface signal DCD and utilize it e.g. for monitoring functions. 3-12 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) Default parameters for transmission facilities Time settings for transmission facility Electrical Interface RTS RS-232 ON tp [ms] tv [ms] tn [Bit] tdis [ms] DCD 0 0 0 0 YES tbs [ms] tstab [ms] tdurati on [sec] tdelay [ms] A_I 0 0 0 0 A T I Z B 5V CM082x 1) 1) NO NO Legend: Electrical interface ............. Parameter "electrical interface" [only SM2541] RTS ................................................ = RTS is switched for the control of the carrier switching of the modem with each message (ON / OFF) tp .................................................... Parameter "Pause time (tp)", Parameter "Pause time_time base (tp)" tv .................................................... Parameter "Set-up time (tv)", Parameter "Set-up time_time base (tv)" tn .................................................... Parameter "Overtravel time (tn)", Parameter "Overtravel time_time base (tn)" tdis ................................................. Parameter "Blocking time (tdis)", Parameter "Blocking time_time base (tdis)" DCD ............................................... Parameter "DCD-evaluation" tbs .............................................. Parameter "Bounce suppression time (tbs)" tstab .............................................. Parameter "Stability monitoring time (tstab)" tduration ............................................ Parameter "Continuous level monitoring time (tduration)" tdelay ...............................................Parameter "Transmit delay at level (tdelay)" A_I .................................................. Parameter "Asynchronous_Isochronous" (A=asynchronous, I=isochronous) T ..................................................... Parameter " Bit timing (only with isochronous)" (I=internal, E=external) Z ..................................................... Parameter "selective RT remote synchronization" (s=selective, B=BROADCAST) 1) CM082x ..................................... Parameter "Configuring for CM082x". Configuring of the interface for optical transformer CM-082x with patch plug CM-2860 [only SM0551, SM2551] 1) 5V ............................................ Parameter "5V Supply (DSR)" [only SM0551, SM2551] Functions Protocol Elements DC0-023-2.01 3-13 Point-to-Point Traffic (BPP) The following picture shows the dynamic behavior (timing) in detail for the data transmission when using transmission facilities with switched carrier. The protocol element requires a full duplex link i.e. both stations (master station and remote terminal unit) can send and receive at the same time. In the following timing the full duplex data transmission is not shown for better clarity. RTS Master station tverz tp tv tn Data transmission tsw TXD tPrell DCD tPrell tverzRTS Data transmission RXD tsignal tsignal tdis t´verzRTS t´verzRTS t´Prell Remote station DCD t´Prell t´signal Data transmission RXD t'dis RTS t'sw tp' t'v Data transmission t'n TXD t'verz tPrell tPrell tstab tstab tdauer Legend: RTS ………….. Request to Send DCD …………. Data Carrier Detect TXD ……...….. Transmit Data RXD ……...….. Receive Data tverzRTS ……….. Processing time of the transmission system Time delay/time difference between activation of transmit part (RTS ) and receiver ready (DCD ) tp ………….….. tv ………….….. tn ………….….. tsw ….....….….. tsignal ….....….. Break time (delay, before transmit part is activated with RTS) Setup time (transmission delay, after transmit part was activated with RTS) Reset time (delayed switch off of the transmit signal level with RTS after message transmission ) Internal processing time Signal propagation delays (dependent from the used transmission facility /transmission path) tPrell …...….….. Protective time after positive/negative DCD-edge (debounce of DCD) tstab …...….….. Stability monitoring time – the new DCD-status is only used for message synchronisation after the expiration of the stability monitoring time tdauer …...….….. Continuous level monitoring time tverz …...….….. Transmission delay – in case of a continuous level a further message transmission will be made at the latest after the transmission delay tdis …….….….. Disable time of the receiver after message receiption (to supress faulty signs during level monitoring) t`x …………….. Corresponding times in the remote stations …………….. DCD valide 3-14 DC0-023-2.01 Functions Protocol Elements tp tv Point-to-Point Traffic (BPP) 3.3. Function for the Support of Redundant Communication Routes To increase the availability both master stations as well as remote terminal units can be designed redundant. In the master station and remote terminal unit, with the parameter advanced parameters | project specific | Redundancy control one can select between the following redundancy controls: • 1703-Redundancy • Norwegian User Conventions (NUC) The switchover of the redundancy state takes place system-internal through redundancy control messages. In the master station and remote terminal unit, in addition a delay for the switchover of the redundancy state from PASSIVE (=STANDBY) to ACTIVE can be set with the parameter Redundancy | Delay time passive=>active. 3.3.1. Redundancy Mode "1703-Redundancy" The redundancy mode "1703-Redundancy" is selected with the parameter advanced parameters | project specific | Redundancy control. In the STANDBY-station, for the synchronization of the FCB-Bit (Frame Count Bit) this is taken from a listened RESET OF REMOTE LINK or from a valid received message with variable block length. The operating mode of the interface with redundancy state "PASSIVE" can be set according to the redundancy configuration with the parameter Redundancy | operation if passive as follows: • • • Transmitter "tristate", listening mode Transmitter "active", listening mode Transmitter "active", normal mode From the redundant, not active master / remote terminal unit, listened messages are passed on to the basic system element (BSE) and forwarded by this in the system with the identifier "passive" in the state. In redundant master / remote terminal units that are not active, a failure of the interface is monitored globally. The failure of the interface is detected by the STANDBY station by monitoring for cyclic message reception. The monitoring time is set with the parameter Redundancy | listening_mode (failure monitoring time). The monitoring time is retriggered with a message received free of errors (except REQUEST STATUS OF LINK and RESET OF REMOTE LINK). On receive timeout (active master / remote terminal unit or transmission facility has failed) the interface is signaled as failed. The failure of the interface is reset in redundant STANDBY stations, if an error-free message (except REQUEST STATUS OF LINK and RESET OF REMOTE LINK) from the respective remote station is "listened" or if no failure monitoring is parameterized. Functions Protocol Elements DC0-023-2.01 3-15 Point-to-Point Traffic (BPP) 3.3.2. Redundancy Mode "Norwegian User Conventions (NUC)" The redundancy mode "Norwegian User Conventions (NUC)" uses 2 communications lines (main/stand-by transmission line) from the master station (Controlling Station) to the remote terminal unit (Controlled Station). Each of these communications lines is fixed activated to a specific interface in the master station and in the remote terminal unit. The data are only transmitted to the active interface. The passive interface is only monitored by the master / remote terminal unit. The redundancy mode "Norwegian User Conventions (NUC)" is selected with the parameter advanced parameters | project specific | Redundancy control. The protocol element only supports the functions of the "Controlled Station"! The operating mode of the interface with redundancy state "PASSIVE" is not to be parameterized for this redundancy mode. The function is defined by the "Norwegian User Conventions (NUC)". Redundancy function according to "Norwegian User Conventions (NUC)" for "balanced-Mode": • After startup of the master station (Controlling Station) and the remote terminal unit (Controlled Station) both stations perform the initialization of the link layer. • After startup of the remote terminal unit (Controlled Station) both interfaces are "PASSIVE". The remote terminal unit (Controlled Station) sends the message "Test function of the link layer" cyclic for monitoring the interfaces on both lines to the master station (Controlling Station). This message is acknowledged by the master station (Controlling Station) with NAK until this switches one of the two interfaces to "ACTIVE". • The activation of an interface is always performed by the master station only – either manually or automatically on failure of one interface. The activation is performed either by a message sent from the master station (Controlling Station) on an interface to the remote station or with the acknowledgement of the message "Test function of the link layer" with ACK. • The master station (Controlling Station) also sends the message "Test function of the link layer" cyclic for monitoring the interfaces on both lines to the remote terminal unit (Controlled Station). The "ACTIVE" interface acknowledges this message with ACK, the passive interface with NAK. • During the switchover from main transmission line-stand-by transmission line, no data loss must occur in the Controlled Station. Transmitted data may only be deleted in the remote terminal unit if these have been explicitly acknowledged by the master station. With switchover, no general interrogation is necessary. The passive line is monitored cyclic with the message "Test function of the link layer". If a station no longer replies, on expiry of the number of retries this is reported as failed. 3-16 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) In the remote terminal unit, for the redundancy mode "Norwegian User Conventions (NUC)" the LOAD-SHAREMode of the communications function must be used on the basic system element. With this mode the basic system element uses 2 fixed assigned interfaces for the transmission of the data from a process image. With the redundancy mode "Norwegian User Conventions (NUC)", data are only transmitted over the active interface to the master station. Through the LOAD-SHARE-Mode a switchover without loss of data is ensured – a doubling of data can occur under certain circumstances. In the remote terminal unit the assignment of the interfaces for main transmission line and stand-by transmission line is defined on a basic system element as follows: Note Interface 1 Main/Standby transmission line Interface 2 Main/Standby transmission line SSE = 128 SSE = 129 Redundant interface pair for NUC-Redundancy SSE = 130 SSE = 131 Redundant interface pair for NUC-Redundancy Legend: SSE = Supplementary system element (with serial interfaces, this is always configured with a PRE) The SICAM 1703 remote terminal unit performs the following functions with redundancy state "PASSIVE": • • • • 3.3.3. No data for emission are requested by the basic system element The "Test function of the link layer" message is send cyclic – with that a failure of the master station or a switchover of the redundancy state is detected. All data in signaling direction are transmitted over the active interface to the master station The interface is always electrically "ACTIVE" (and is not switched to "TRISTATE") Deactivating the Interface When using mobile control systems the interface can be deactivated in order to suppress the interface failure if the control system is not connected. With deactivated interface the transmitter of the interface is switched to "tristate" and the data for emission are fetched from the basic system element and discarded without error message. Received messages are discarded and not passed on to the basic system element. The activation/deactivation of the interface takes place through PRE control messages. After startup of the protocol element the interface is activated by default. With deactivation of the interface a possibly present failure of the interface is reset if no "listening mode (failure monitoring time)" is parameterized. With deactivated interface, no monitoring of the interface takes place! Functions Protocol Elements DC0-023-2.01 3-17 Point-to-Point Traffic (BPP) 3.4. Message Conversion Data in transmit direction are transferred from the basic system element to the protocol element in the SICAM 1703 internal IEC 60870-5-101-/104 format. These are converted by the protocol element to the IEC 60870-5-101 message format on the line and transmitted according to the transmission procedure of the protocol. Data in receive direction are converted by the protocol element from IEC 60870-5-101 format on the transmission line to a SICAM 1703 internal IEC 60870-5-101-/104 format and transferred to the basic system element. 3.4.1. Blocking For the optimum utilization of the transmission paths, for the data transmission with IEC 60870-5-101 protocols the "Blocking" according to IEC 60870-5-101 is implemented. This function is performed on the basic system element (BSE) according to the rules applicable for this. Data to be transmitted are thereby already blocked on the basic system element and passed on to the protocol element for transmission. The blocking for data to be transmitted does not support the maximum possible message length according to IEC 60870-5-101! Received data in blocked format according to IEC 60870-5-101 are passed on from the protocol element to the basic system element in blocked format. On the basic system element the blocked data are split up again into individual information objects by the detailed routing function and passed on as such to the further processing. Received messages with maximum length are transmitted SICAM 1703 internal in 2 blocks to the basic system element (BSE) because of the additionally required transport information. The parameters necessary for the blocking are to be set on the basic system element (BSE) in the IEC 60870-5-101/104 parameter block. 3-18 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) 3.4.2. Special Functions For the coupling to external systems, if necessary the following special functions can be activated for the adaptation of the message conversion: • • • • • • • • • • daylight-saving time bit (SU)=0 for all messages in transmit direction (daylight-saving time bit in the time stamp) Weekday (DOW)=0 for all messages in transmit direction (weekday in the time stamp) Originator address=0 for all messages in transmit direction Convert general interrogation command in receive direction to BROADCAST ACTCON for clock synchronization command Emulate ACTCON+/Emulate ACTCON for commands Emulate ACTCON, ACTTERM for commands with commands Compatibility TCS100 Settings for project DBAG / PSI 3.4.2.1. Daylight-Saving Time Bit = 0 for all Messages in Transmit Direction With function enabled with the parameter advanced parameters | IEC60870-5-101 | time lag | summertime(SU) = 0 for all messages with time stamp in transmit direction the daylight-saving time bit (SU) is always set to 0 by the protocol element. 3.4.2.2. Weekday = 0 for all Messages in Transmit Direction With function enabled with the parameter advanced parameters | IEC60870-5-101 | time lag | Day of week (DOW) = 0 for all messages with time stamp in transmit direction the weekday (DOW) is always set to 0 by the protocol element. 3.4.2.3. Originator Address = 0 for all Messages in Transmit Direction With function enabled with the parameter advanced parameters | IEC60870-5-101 | originator address in transmit direction = 0 for all messages in transmit direction the originator address is always set to 0 by the protocol element. Note: The originator address (= 2nd byte of the cause of transmission) is only then sent if the number of octets for cause of transmission (COT) is set on the basic system element to 2. Functions Protocol Elements DC0-023-2.01 3-19 Point-to-Point Traffic (BPP) 3.4.2.4. Convert General Interrogation Command in Receive Direction to BROADCAST With function enabled with the parameter advanced parameters | IEC60870-5-101 | GI command "broadcast" all general interrogation commands <TK=100> received from the protocol element are passed on from the transmission line with the "cause of transmission = activation" to the basic system element with the address CASDU = BROADCAST. 3.4.2.5. Emulate ACTCON+ for Clock Synchronization Command The transmission of ACTCON+ by the protocol element for clock synchronization can be set with the parameter advanced parameters | IEC60870-5-101 | ACTCON for clock sychronization command as follows: • • • 3-20 Do not send (=default) Send immediately Send after minute change and internal transfer of the time (DEFAULT) DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) 3.4.2.6. Emulate ACTCON+/- for Commands If ACTCON is not supported by the basic system element or by the peripheral element used, then the emulation of ACTCON can be performed by the protocol element (PRE) as follows: Emulation of Note ACTCON- for <TK=45> single command <TK=46> double command <TK=47> regulating step command <TK=48> setpoint command, normalized value <TK=49> setpoint command, scaled value <TK=50> setpoint command, floating point number ACTCON- send immediately from PRE if * CASDU is not known to the PRE ACTCON+/- from BSE or PE is sent from PRE ACTCON- for <TK=100> (general-) interrogation command ACTCON- send immediately from PRE if * CASDU is not known to the PRE and * CASDU <> FFFF (=BROADCAST) ACTCON+/- from BSE is sent from PRE ACTCON+/- for <TK=101> counter interrogation command ACTCON+ send immediately from PRE if * CASDU is known to the PRE or * CASDU = FFFF (=BROADCAST) ACTCON- send immediately from PRE if * CASDU is not known to the PRE ACTCON+/- for <TK=103> clock synchronization command if ACTCON+ send from PRE if * CASDU = FFFF (=BROADCAST) **) ACTCON- send immediately from PRE if * CASDU <> FFFF (=BROADCAST) Legend: BSE .... Basic system element PRE.... Protocol element PE ...... Protocol element **) The moment for the transmission of ACTCON+ can be parameterized with the parameter advanced parameters | IEC60870-5-101 | ACTCON for clock sychronization command. The emulation of ACTCON by the protocol element (PRE) can be activated with the parameter advanced parameters | IEC60870-5-101 | ACTCON +/- emulation. So that the emulation can be performed by the protocol element, it must be ensured that the INIT-End messages are passed on from the basic system element to the protocol element (required because of the known CASDU addresses). The parameter setting necessary is to be performed on the basic system element (BSE) in the IEC 60870-5-101/104 parameter block. Functions Protocol Elements DC0-023-2.01 3-21 Point-to-Point Traffic (BPP) 3.4.2.7. Emulate ACTCON+ for Commands If ACTCON for commands is not supported by the peripherals element used, then the emulation of ACTCON messages can be performed by the protocol element of the remote terminal unit as follows: Emulation of ACTCON+ Note for <TK=45> single command <TK=46> double command <TK=47> regulating step command ACTCON+ from PRE send immediately (for SELECT and EXECUTE command) ACTCON+/- from BSE is filtered out by PRE and not sent! ACTTERM+/- from BSE is sent from PRE The emulation of ACTCON by the protocol element (PRE) for commands can be activated with the parameter advanced parameters | IEC60870-5-101 | ACTCON emulation. With function activated, ACTCON messages are emulated by the protocol element as shown in the table. All ACTCON+/- messages that are transferred from the basic system element to the protocol element are filtered out by the protocol element and therefore not transmitted. ACTTERM messages that are transferred from the basic system element to the protocol element are transmitted by the protocol element. With function not activated, ACTCON and ACTTERM messages that are transferred from the basic system element to the protocol element are transmitted by the protocol element, no emulation of any kind by the protocol element takes place. Note: This function is not required in ACP 1703 or if the this function is supported by the peripheral elements used! For the emulation of ACTCON- with unknown CASDU, the parameter advanced parameters | IEC60870-5101 | ACTCON +/- emulation is to be enabled. 3-22 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) 3.4.2.8. Emulate ACTCON, ACTTERM for Commands with Control Messages If ACTCON and ACTTERM for commands are not supported by the system, then the emulation of ACTCON and ACTTERM – controlled by control messages – can be emulated by the protocol element (PRE) for a previously received command. This emulation for ACTCON, ACTTERM is often used when a protocol element for the interfacing of external systems or one external system itself does not support this function. The emulation of ACTCON, ACTTERM is activated on the protocol element, if the type identification in the parameter advanced parameters | project specific | ACTCON, ACTTERM for commands controlled by control messages | TI and the monitoring times for ACTCON, ACTTERM "<> 0" are parameterized. The control can be performed by an application program of the open-/closed-loop control function. Due to the control messages the emulation of the messages ACTCON+/- and ACTTERM+/- of a previously received command (TK=45, TK=46, TK=47 - Select or Execute) to the remote station is triggered. A message with optional type identification can be used as control message – the data content of the control messages is not evaluated by the protocol element. The identification of the control message takes place based only on the parameterized address. In addition the protocol element performs a "1 out of n" check for commands. If a further command is received from the remote station, although the previously received command has not yet been terminated, a negative confirmation (ACTCON-) is transmitted immediately by the protocol element to the remote station. The control of the emulation of the messages ACTCON+/-, ACTTERM+/- by the application program of the open/closed-loop control function is monitored by the protocol firmware. If the corresponding control message is not received by the protocol element within the monitoring time, the protocol element itself sends an ACTCON- or ACTTERM- to the remote station. The monitoring time for the reception of the confirmation of activation is to be set on the protocol element with the parameter advanced parameters | project specific | ACTCON, ACTTERM for commands controlled by control messages | monitoring time ACTCON (after ACT). The monitoring time for the reception of the termination of activation is to be set on the protocol element with the parameter advanced parameters | project specific | ACTCON, ACTTERM for commands controlled by control messages | monitoring time ACTTERM (after ACTCON). The IEC 60870-5-101/104 address of the control message (TI, CASDU1, CASDU2, IOA1, IOA2, IOA3) for the emulation of ACTCON+ is to be parameterized with the parameter advanced parameters | project specific | ACTCON, ACTTERM for commands controlled by control messages | TI, CASDU1, CSADU2, IOA1, IOA2, IOA3. The addresses of the other control messages are defined. Address for Control Message *) *) Control Message Parameterized address Control message for emulation ACTCON+ Parameterized address, IOA+1 Control message for emulation ACTCON- Parameterized address, IOA+2 Control message for emulation ACTTERM+ Parameterized address, IOA+3 Control message for emulation ACTTERM- If TK=0 is parameterized, no emulation by the protocol element takes place. ACTCON, ACTTERM messages are transferred from the basic system element to the remote station. Functions Protocol Elements DC0-023-2.01 3-23 Point-to-Point Traffic (BPP) 3.4.2.9. Compatibility TCS100 For the interfacing of SICAM 1703 stations which use the protocol firmware TCS100, corresponding parameters are to be set to ensure the compatibility concerning type of addressing. The type of remote station is set with the parameter advanced parameters | compatibility TCS100 | Remote station TCS100. With the parameter advanced parameters | compatibility TCS100 | Address mappint at TCS100 the type of address parameterized in the TCS100 protocol firmware is to be set. With the parameter advanced parameters | compatibility TCS100 | Attached region number using remote station type TCS100 the region number to be added in receive direction is to be selected. Either the "own region number" or a parameter-settable region number can be added. The parameter-settable region number is to be set with the parameter advanced parameters | compatibility TCS100 | region number of remote station. 3.4.2.10. Settings for Project DBAG / PSI For the implementation of the protocol firmware in DBAG / PSI projects the following special functions can be activated: • • Breaker delay in transmit direction (DBAG-specific special message format <TI=150>) Send originator address with settable value These special functions can be activated with the parameter advanced parameters | project specific | parameter settings for project DBAG/PSI. With function activated, messages in the format <TI=33> "32 Bit bit pattern" in the direction basic system element protocol element are converted by the protocol element to the DBAG-specific message format <TI=150> and transmitted. Messages received in the format <TI=150> are converted by the protocol element to the format <TI=33> "32 Bit bit pattern" and passed on to the basic system element. In transmit direction <TI=33> "32 Bit bit pattern" is converted as follows: Cause of Transmission IEC-Parameter Type Identification for Transmission to the Remote Station spontaneous - <TI=150> DBAG-specific format GI with time (3 octets) <TI=4> GI with time (7 octets) <TI=31> double-point information with time stamp CP56Time2a GI without time <TI=3> double-point information with time stamp double-point information In receive direction <TI=150> is converted as follows: Cause of Transmission spontaneous, GI Note: 3-24 Time Format with time (7 octets) Type Identification for Transmission to Basic System Element <TI=33> Bit pattern of 32 Bit with time stamp CP56Time2a The format <TI=150> is only defined with 7 bytes time, 3 bytes IOA, 2 bytes CASDU and 2 bytes URS! For the format <TI=150> in addition no double transmission is defined as format without time stamp! DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) Breaker delay in transmit direction If the delay of the circuit breaker or the time of the fault current is not available, this time can be added by the protocol element in messages in transmit direction with the parameter advanced parameters | project specific | parameter settings for project DBAG/PSI | switch transfer time in transmit direction. Message structure <TI=150> "Railway-specific Format" (in the private range) 27 26 25 24 23 22 21 20 150 SQ T Type identification Number of information objects P/N variable structure qualifier Cause of transmission Cause of transmission Originator address Station address CASDU1 N CASDU2 Technological Code (TC) IOA1 1 IOA2 0 SK8 Field address SK7 SK6 SK5 SK4 SK3 IOA3 SK2 SK1 Protection criteria (BDK) Protection criteria reserve 0 - 255 Fault code (AK of SLT) 2ms – Code (0-255) IV NT SB BL Breaker delay DPI DIQ of DOM Originator time in format CP56Time2a (corresponds to TL SCHINA, DB_Network) Dual time (7 octets) Send originator address with settable value In DBAG / PSI projects the originator address in transmit direction is always transferred with a fixed parameterized value. The originator address is to be set with the parameter advanced parameters | project specific | parameter settings for project DBAG/PSI | originator address in transmit direction. For this function the setting of the number of octets for cause of transmission to "2 octets" is necessary (see IEC 60870-5-101/104 Parameters on the Basic System Element). Functions Protocol Elements DC0-023-2.01 3-25 Point-to-Point Traffic (BPP) 3.5. Transparent Mode (Tunneling, Container Mode) The Transparent Mode (or Container Mode) is used to pass through external computer messages in IEC 60870-5101 format between a remote station and a third-party control system that is connected to the SICAM 1703 component with IEC 60870-5-104. The container mode thus provides a "tunneling method" within the system SICAM 1703. These external computer messages are transmitted to or received from an external control system in a user data container defined for SICAM 1703 in the private range of the IEC 60870-5-101. The user data container is then not sent to the remote station, rather the IEC 60870-5-101 message contained in the message data of the user data container. As a result either message formats in the public or private range of the IEC 60870-5-101 standard not supported by the System SICAM 1703 can be transmitted from a third-party remote terminal unit to a third-party control system or all messages according to IEC 60870-5-101 which do not need to be routed individually when using the container mode in the System SICAM 1703. In container mode only the user data messages are transmitted transparently through the SICAM 1703 network – messages for protocol control (station initialization, acknowledgement messages,...) are not transmitted and are dealt with directly at the interface to the serial interfaced external system by the protocol element. With special procedures (e.g.: remote parameterization of a third-party system by a third-party control system), before using the container mode it is to be checked whether the changed chronological behavior will be tolerated by the connected third-party system and that no error messages or failures occur as a result. The transmission of the user data container within SICAM 1703 takes place with type identification <TI=142> in the private range of IEC 60870-5-101 or IEC 60870-5-104 respectively. SICAM 1703 internal, several modes are provided for the use of the user data container. The container mode uses the user data container with message type = 128 (=SAT Standard-Format). The container mode can be activated separately for transmit / receive direction with the parameter advanced parameters | project specific | parameter settings for project DBAG/PSI | originator address in transmit direction and the parameter advanced parameters | project specific | parameter settings for project DBAG/PSI | switch transfer time in transmit direction. With container mode activated in receive direction, all valid received messages from the third-party system are entered in a user data container and passed on from the protocol element to the basic system element for further distribution within the system. With container mode activated in transmit direction, data to be sent are transferred from the basic system element to the protocol element in a "user data container <TI=142> and message type = 128“, read out from the user data container and the message data sent to the third-party system. All other data passed on from the basic system element to the protocol element for transmission are sent unchanged to the third-party system. The IEC-address of the user data container is fixed defined and is not to be parameterized. (CASDU = CASDU of the remote terminal unit; IOA1, IOA2 = 255; IOA3 = 191) 3-26 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) Segmentation With user data containers a maximum of 180 bytes of transparent message data can be transmitted. Longer external computer messages (max. 256 bytes) are thus to be transmitted in several part segments and grouped together again before transmission/processing. With missing segments the partially transmitted parameter message is discarded. The transparent mode only utilizes part segments with a max. length of 50 bytes of message data! User data container <TI=142> The user data container is used to pass through external computer messages. 27 26 25 24 23 22 21 20 Type identification = 142 SQ T 1 P/N variable structure qualifier Cause of transmission Cause of transmission Originator address CASDU1 CASDU2 IOA1 IOA2 IOA3 : : : : : : : : : : : : : : : : : : : : : : : : 7 bytes dual time (IEC 60870-5-101) Length of user data in bytes **) 128 Message type = 128 45 UEK = 45 S=1 I=0 Status = 0x02 Number of bytes *) Interface number (process channel) Sum of the segments = 1 Current segment number = 1 Segment information 22 Protocol type = 22 (=IEC 60870-5-101) 0 Reserve Length of the message data in Bits (LSB) Length of the message data in Bits (MSB) 0 0 0 0 : : : : : : : : : : : : Function : : : : : : : : : Message data (0) : : : : : : Message data (n) max. 50 bytes *) Number of bytes of the message data + 6 (max. 56 bytes) **) Length of the user data from the field UEK up to the last byte of the message data (n) Note: Functions Protocol Elements The user data container is described here in the internal format of the protocol element with the essential information fields. DC0-023-2.01 3-27 Point-to-Point Traffic (BPP) Elements of the Message TI .. type identification <TI=142> User data container CASDU, IOA .. Message address O1 .. Octet 1 (CASDU) CASDU = CASDU of the remote station O2 .. Octet 2 (CASDU) CASDU = CASDU of the remote station IOA1 .. = 255 IOA2 .. = 255 IOA3 .. = 191 (subaddress) Cause of transmission 03 .. spontaneous ... in monitoring direction 06 .. activation ... in control direction Time 7 octets dual time Earliest possible acquisition moment of a message in AK 1703, time tag on the basic system element (BSE) Message type = 128 Length of the user data part in octets Length of the user data in octets (exclusive message type) Number of bytes Number of bytes of the message data + 6 Segmentation field Total number of segments Total number of segments (4 Bit) ... Total size = 15 segments each of 50 octets Current segment number Current number of the transmitted segments (4 Bit) ... the 1st segment has segment number 1 Length of the message data in bit in all segments the total length of the message data is always transmitted in bit. Structure of the message data: 27 26 25 24 0 0 0 0 23 22 21 Function 20 Control Byte Message data (0) link address Data (0) : : Data (n) Message data (n) Elements of the Message Control byte "Function" (Bit 0-3) 03 .. User data SEND / CONFIRM 04 .. User data SEND / NO REPLY Link address 3-28 The length of the link address to be sent is determined with a parameter. DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) 3.6. Protocol Element Control and Return Information This function is used for the user-specific influencing of the functions of the protocol elements. This function contains two separate independent parts: • Protocol element control • Protocol element return information The Protocol Element Control enables: • Applicational control of the station interrogation • Setting the control location • Testing the reachability of stations • the suppression of errors with intentionally switched-off stations (Station Service) The Protocol Element Return Information enables: • States of certain state lines to be used as process information • Information about the station status/failure to be obtained Internal distribution for messages with process information Block Diagram Protocol element control Internal function Transmission route Protocol element return information Protocol element Messages with process information Messages with system information Functions Protocol Elements DC0-023-2.01 3-29 Point-to-Point Traffic (BPP) 3.6.1. Protocol Element Control With the help of messages with process information, the protocol element control on the basic system element enables specific functions of the protocol elements to be controlled. The specific functions are determined by the protocol element implemented. The assignment of the messages with process information to the functions is carried out with the help of processtechnical parameters of the ACP 1703 system data protocol element control message. The messages for protocol control are transmitted immediately from the basic system element to the protocol element, regardless of the user data to be sent and the priority control. For messages with process information which are used in ACP 1703 as protocol element control message, an unused CASDU is to be used! All CASDU´s for process information are distributed automatically to the corresponding remote terminal unit. 3-30 DC0-023-2.01 Functions Protocol Elements Point-to-Point Traffic (BPP) Possible functions: Parameter Function SF Station Z-Par Note Send (general) interrogation command 240 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Send (general) interrogation command to GI-group 241 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Set control location 242 Reset command 243 125 65535 Set/delete control location (global) **) SCS=<ON>: Set control location (HKA) (global) SCS=<OFF>: Delete control location (HKA) (global) This function is not presently supported by PRE! Data filter in transmit direction "ON" 0 - - Do not send all messages from BSE Data filter in transmit direction "OFF" 1 - - Send all messages from BSE Data filter in receive direction "ON" 2 - - All received messages not to BSE Data filter in receive direction "OFF" 3 - - All received messages to BSE "Deactivate" interface 4 - - - Reset interface failure - Do not send all messages from BSE - Received messages are discarded "Activate" interface 5 - - Legend: SF..............Control function_(PRE) Station .......Station number (= 125 in point-to-point traffic) Z-Par .........Additional parameter_(PRE) SCS...........Single command state HKA...........Originator address (HKA) = 0 – 255 The setting of the control location can only be performed with a single command <TK=45>! In the PRE-control message to the protocol element the additional parameter is set as follows. SCS = <OFF> ........Additional parameter = HKA+256 SCS = <ON>..........Additional parameter = HKA **) If a PRE-control message is entered in the PST-detailed routing on the BSE, after startup of the PRE the BSE sends a PRE-control message "Set control location" to the PRE. As a result the function for evaluating the control location is activated on the PRE. Functions Protocol Elements DC0-023-2.01 3-31 Point-to-Point Traffic (BPP) 3.6.2. Protocol Element Return Information The protocol element return information on the basic system element generates messages with process information in monitor direction and thereby enables states of the protocol elements to be displayed or processed. There are three different categories of return information: • Status of the status lines • Protocol-specific return information (dependent on the protocol element used) • Status of the stations The assignment of the messages with process information to the return information is carried out on the basic system element with the help of process-technical parameters of the ACP 1703 system data protocol element return information. From which source the parameterized return information are to be generated, is set with the parameters "Supplementary system element" and "Station number". Messages for protocol element return information are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. Possible return information BPP: Parameter Return information function_(PRE) Station Status DTR (1 = state line active) 255 (1) Status DSR (1 = state line active) 255 (1) Station failure 0 Note 1 = Station failed (1) States of the state lines are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. The spontaneous transmission of the current states takes place internally in a 100ms grid. State line changes shorter than 100ms are not guaranteed to be transmitted! 3-32 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4. Multi-Point Traffic (UMP) Multi-point traffic describes a serial communications protocol with which a master station is connected with one or several remote terminal units over a communications link in a linear or star configuration. The data traffic is controlled by the master station. Either data messages or station interrogation messages are transmitted from the master station. Data from the remote terminal unit to the master station can only be transmitted as reply to a station interrogation. Master station TF TF TF TF Remote station-1 Remote station-2 Remote station-n n <= 100 Legende: TF ………..….. Transmission Facility In multi-point traffic an "unbalanced transmission procedure" is used. That means, that as primary station the master station initiates all message transmissions, while the remote terminal units, which are secondary stations, may only transmit when they are called. The multi-point traffic only requires a "half duplex" transmission medium and can be used in a star or linear structure. The master station and the remote terminal units in multi-point traffic function with a communications protocol according to IEC 60870-5-101. The supported functionality (Interoperability) is shown in the document "IEC 608705-101/104 Interoperability ACP" in the chapter "Interoperability for ACP 1703 in Multi-Point Traffic". Functions Protocol Elements DC0-023-2.01 4-1 Multi-Point Traffic (UMP) General Functions Communication between one central station and one or more remote stations (IEC 60870-5-101) • Unbalanced multi-point (multi-point traffic) according to IEC 60870-5-101 UMPMxx is controlling station (primary station), UPMSxx is controlled station (secondary station). ─ Supported functionality according to − ACP 1703 Interoperability IEC 60870-5-101/104 (DC0-013-1) − Ax 1703 Interoperability IEC 60870-5-101/104 (DA0-046-1) ─ ─ ─ ─ Data acquisition by polling (station interrogation) Acquisition of events (transmission of data ready to be sent) General interrogation, outstation interrogation Clock synchronization − Cyclic, can be set in a minute grid; at least 1x per minute. ─ Command transmission − Set control location, control location check ─ Transmission of integrated totals ─ Acquisition of transmission delay (for the correction of time synchronisation) • Standby transmission line over the public telephone network (PSTN) • Data transmission using time slot radio • Co-ordination of several masters • Optimized parameters for selected transmission facilities • Functions for supporting redundant communication routes • Special functions Communication between one central station and one or more remote stations (relay operation) • Unbalanced multi-point in relay operation mode (multi-point traffic with routing) based on IEC 60870-5-101 UMPMxx is controlling station (primary station), UPMSxx is controlled station (secondary station). ─ Supported functionality according to − ACP 1703 Interoperability IEC 60870-5-101/104 (DC0-013-1) − Ax 1703 Interoperability IEC 60870-5-101/104 (DA0-046-1) ─ Data acquisition by polling (station interrogation) ─ Acquisition of events (transmission of data ready to be sent) ─ General interrogation, outstation interrogation ─ Clock synchronization − Cyclic, can be set in a minutes grid ─ Command transmission − Set control location, control location check ─ Transmission of integrated totals ─ Acquisition of transmission delay (for the correction of time synchronisation) 4-2 • Standby transmission line over the public telephone network (PSTN) • Data transmission in relay operation mode (multi-point traffic with routing) • Co-ordination of several masters • Optimized parameters for selected transmission facilities • Functions for supporting redundant communication routes • Special functions DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) The operating mode of the interface is determined by parameters of the protocol element. Standard Operation Mode Unbalanced interchange circuit V.24/V.28 Parameter and Setting Interface Signals on RJ45 Connector Asynchronous / Isochronous Asynchronous RXD, TXD, CTS, RTS, DCD, DTR, DSR/+5V, GND V.28 asynchronous Optional Operation Mode Parameter and Setting Balanced interchange circuit X.24/X.27 Asynchronous / Isochronous V.11 isochronous Interface Signals on RJ45 Connector Isochronous Bit timing internal RXD, TXD, CTS, TXC, DCD, DTR, DSR/+5V, GND Bit timing external RXD, TXD, RTS, RXC, DCD, DTR, DSR/+5V, GND Balanced interface RS-485 Asynchronous / Isochronous V.11 asynchronous Asynchronous RXD, TXD, CTS, RTS, DCD, DTR, DSR/+5V, GND with CM-0829 Optical interface (multimode fibre optic) Asynchronous / Isochronous Asynchronous RXD, TXD, +5V, GND with CM-0827 Functions Protocol Elements DC0-023-2.01 4-3 Multi-Point Traffic (UMP) 4.1. Communication according to IEC 60870-5-101 4.1.1. Data Acquisition by Polling (Station Interrogation) The transmission of the data from the remote terminal units to the master station takes place by means of stationselective station interrogations (interrogation procedure, polling), controlled by the master station; i.e., changed data are stored in the remote terminal unit and transmitted to the master station with the interrogation of this remote terminal unit. The interrogation procedure of the master station ensures, that remote terminal units are interrogated sequentially, whereby remote terminal units with important data can be interrogated more often. Remote terminal units may only transmit when they are called. The interrogation procedure can be influenced with the following parameters: • Continuous cycle • Existing stations • Number of calls until station change • Number of stations to be called until change of priority level • Priority level assignment (each station is assigned one of the 4 priority levels: high priority, medium priority, low priority-A, low priority-B) The interrogation procedure can be performed either continuously (= continuous cycle) or only on request. The continuous interrogation of the remote terminal units by the master station interrogation procedure is to be performed by enabling the parameter advanced parameters | continuous cycle. The station-selective parameters of the master station for the interrogation cycle such as "Stat No", "Link Address", "Station Enabling", "Station failure", "Priority Level" and "Number of calls" are to be set in the parameter Station definition. In every remote terminal unit, the station-selective address must be set with the parameter advanced parameters | Address of the link. This address must be unambiguous for each multi-point traffic line. In the master station and in the remote terminal unit, the number of octets is to be parameterized with which the address field is transmitted on the line with the parameter advanced parameters | IEC60870-5-101 | Address field of the link (number). The prioritization of the station interrogation can be parameterized by means of corresponding parameter setting of the number of stations called until level change with the following parameters: • • • • Station Station Station Station call call call call prioritization prioritization prioritization prioritization | | | | No. No. No. No. of of of of stat. stat. stat. stat. calls calls calls calls in in in in high priority lvl mid. priority lvl low prior. lvl (A) low prior. lvl (B) Through parameterization of the interrogation procedure the following characteristics can be achieved: • • • A remote terminal unit which has a lot of data to send - e.g. continuously changing measured values – does not impair the disposal of the data of the other remote terminal units. Each remote terminal unit is interrogated within a determinable time (deterministic). Remote terminal units with important data or those with a large volume of data to be transmitted can be interrogated more frequently than the others. The interrogation procedure can be performed either continuously (= continuous cycle) or only on request. The control of the interrogation procedure on request can be realized with protocol control messages in the function diagram. 4-4 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) In the running interrogation cycle, data and system messages are transmitted spontaneously from the master station according to the parameter setting as follows: • • One RTU selective (acknowledged) All RTU’s (unacknowledged) If the interrogation cycle has been stopped by protocol control messages or the listening mode is switched on, no station interrogation takes place. With the interrogation cycle stopped, spontaneous data messages continue to be transmitted to the remote terminal units. With listening mode switched on, the messages are normally not transmitted from the master station to the remote terminal units, rather discarded directly on the basic system element (BSE) by the function "User data filter". Example: Prioritization of the station interrogation Below the prioritization of the station interrogation for continuous cycle is shown based on the specified parameters as an example. Parameter for "Station call prioritization" High priority level ...................... Number of stations called until level change = 2 Medium priority level................. Number of stations called until level change = 2 Low priority level (A) ................. Number of stations called until level change = 1 Low priority level (B) ................. Number of stations called until level change = 1 Station U0, U4 .......................... High priority level / Number of calls until station change = 2 Station U1,U2,U3...................... Medium priority level / Number of calls until station change = 2 Station U5,U6,U7, U8 ............... Low priority level (A) / Number of calls until station change = 1 Station U9,U10 ......................... Low priority level (B) / Number of calls until station change = 1 t Z U0 U1 U2 U3 U4 U5 U6 U7 U8 U9 U9 U10 U10 Legend: …..….. Remote station in the „High priority level“ …..….. Remote station in the „Medium priority level“ …..….. Remote station in the „Low priority level (A)“ U10 …..….. Remote station in the „Low priority level (B)“ ,..…...….. Data message, short acknowledgement (remote station master station) ,…..….. Data message (Command), calling message (remote station master station) Z ………….….. Master station U0..U10 ….….. Remote station U0 .. Remote station U10 …………….. Command from master station remote station U0 t ………………. Continous station polling time (request) from remote station U0 (after command from master station remote station U0) Functions Protocol Elements DC0-023-2.01 4-5 Multi-Point Traffic (UMP) For the coupling of different systems with the IEC 60870-5-101 protocol, the setting of the variable elements of the message is required. These parameters are shown in the Interoperability List. The following table provides an overview of which IEC-parameters are to be parameterized on which system elements. IEC 60870-5-101 Parameter Description bytes link address Number of octets for the address field of the link layer PRE Cause of transmission (COT) Number of octets for cause of transmission BSE Common address of ASDU (CASDU) Number of octets for common address of the ASDU BSE Information object address (IOA) Number of octets for the address of the information object BSE Acknowledgement on IEC 60870-5-102 layer Single character or short message (ACK) PRE Maximum message length Time Stamp Legend: 4-6 System Element BSE Number of octets for time stamp SSE = supplementary system element (with serial interfaces this is always configured with a PRE) PRE = Protocol element BSE = Basic system element DC0-023-2.01 Functions Protocol Elements BSE Multi-Point Traffic (UMP) 4.1.1.1. Continuous Interrogation of a Remote Terminal Unit The "continuous interrogation of a remote terminal unit" can be switched on automatically in the master station with the function "Demand" or spontaneously with protocol control messages. With function activated, a station interrogation is always executed by the master station to only one selected station. An automatically started continuous interrogation of one remote terminal following a message transmission is known as a demand. Through a demand, following a message transmission (e.g. command, setpoint value) the master station can quickly fetch changed data from the remote terminal unit (e.g. measured values after command or setpoint value). With demand, the continuous interrogation of a remote terminal unit is terminated after timeout or a message to another remote terminal unit. With control of the interrogation procedure with protocol control messages, the continuous interrogation of a remote terminal unit can be terminated spontaneously through a corresponding protocol control message. With "continuous interrogation of a remote terminal unit" data messages continue to be transmitted to that remote terminal unit to which the function "continuous interrogation of a station" is switched on. 4.1.1.2. Acknowledgement Procedure All data messages transmitted selectively to a remote terminal unit must be acknowledged by this RTU. If, with nonfaulty transmission line, the acknowledgement is missing for longer than the expected acknowledgement time, transmitted messages are repeated up to n-times (n can be parameterized). On expiry of the number of retries, the station is flagged as faulty. The required expected acknowledgement time is determined automatically from the set parameters, but if necessary can be extended accordingly with the parameter advanced parameters | monitoring times | expected_ack_time_corr_factor. This is then the case if additional signal propagation delays, delay times or slow processing times of the connected remote terminal units must be taken into consideration. The number of retries is to be set in the master station for messages for station interrogation and data messages with the parameter Message retries | Retries for data message SEND/CONFIRM (station selective) or for messages for station initialization with the parameter Message retries | Retries for INIT-messages SEND/CONFIRM (station selectiv). The acknowledgement from the remote terminal unit to the master station can be transmitted as single character (E5), if no additional information (such as DCF-Bit or ACD-Bit) is to be transmitted. If additional information is to be transmitted, the acknowledgement is transmitted as message with fixed length (ACK). Instead of the acknowledgement with single character (E5H) the acknowledgement can be transmitted as message with fixed length (ACK). The message type for the acknowledgement can be selected in the remote terminal unit with the parameter advanced parameters | IEC 60870-5-101 | Acknowledgement IEC60870-5-2. Functions Protocol Elements DC0-023-2.01 4-7 Multi-Point Traffic (UMP) 4.1.1.3. Failure Monitoring in the Master Station The monitoring of the interface by the active master station takes place by means of the cyclic running interrogation procedure (station interrogation). A remote terminal unit is reported as failed by the master station after expiry of the number of retries. Retries to a remote terminal unit are thereby always sent in succession immediately after expiry of the expected acknowledgement time i.e. no other remote terminal units are interrogated during a running retry handling. For failed remote terminal units, a communication fault is only then reported if this is parameterized accordingly in the parameter "Station failure" of the station definition. The failure of remote terminal units is thus detected by the master station during the normal interrogation cycle. Failed remote terminal units continue to be interrogated by the master station with the interrogation procedure, however no message retry is performed for such remote terminal units during the station interrogation. The interrogation cycle for failed stations can be set with the parameter advanced parameters | IEC60870-5101 | polling cycle for faulty stations. As a result, failed remote terminal units are removed from the running interrogation procedure for a certain time and from then are only interrogated in the parameterized grid. No data are transmitted from the master station to failed remote terminal units. The data are stored in the data storage of the communication function on the basic system element (BSE) until these are deleted by the dwell time monitoring or are transmitted to the non-failed remote terminal unit. Station failure delay If short-term communication faults lead again and again to station failures, and the number of retries in the master station is not to be increased further, then the transfer of the fault can be delayed. Through the station failure delay, short-term communication faults no longer lead to a station failure. With station failure delay, the failure of a remote terminal unit (after expiry of the number of retries) is not immediately reported as failed, rather only after expiry of a settable delay time. The delay time can be parameterized with the parameter advanced parameters | station failure delay. Station failure (PRE) Station failure delay Station failure delay Station failure (BSE) Legend: …………….. Station failure is forwarded to BSE …………….. Going station failure is forwarded to BSE …………….. Short-term station failure (PRE) not forwarded to BSE due to s tation failure delay The station failure delay is performed by the protocol firmware of the master station station-selective. With station failure delay only the "coming" fault is delayed – a "going" fault is passed on immediately to the basic system element. Note: 4-8 During the station failure delay, no data are transmitted to the affected remote terminal units. → Due to the dwell time monitoring on the BSE, certain data are deleted after expiry of the monitoring time if these could not be transmitted! DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.1.1.4. Failure Monitoring in the Remote Terminal Unit The monitoring of the interface in the remote terminal unit is performed by monitoring for "cyclic message reception with station interrogation or station-selective data messages". The monitoring time is to be set in the remote terminal unit with the parameter advanced parameters | monitoring times | call monitoring time. The monitoring timeout is normally only retriggered in the remote terminal unit with station-selective call messages or station-selective data messages. The parameter advanced parameters | monitoring times | call timeout retrigger also with "request status of link" is only to be used if this function is explicitly required (special functionality or due to downward compatibility). The message "Request Status of Link" is transmitted from the master station during the initialization phase, with the "acquisition time of the transmission time" and with station failure. If during failure of the communication line (e.g. signaling direction only) in the remote terminal unit a failure of the communication link is also to be detected, then the call timeout in the remote terminal unit must not be retriggered with "Request Status of Link"! The monitoring time in the remote terminal unit must be set sufficiently high, so that this does not expire unintentionally during the transmission of larger quantities of data from other remote terminal units (e.g. during general interrogation). With failed interface, data to be transmitted are stored in the data storage on the basic system element (BSE) of the remote terminal unit until these are deleted by the dwell time monitoring or can be transmitted to the master station. 4.1.2. Station Initialization After startup or redundancy switchover, the operation of the interface is begun after successful station initialization. The initialization of the link layer of the remote terminal unit is performed by the master station with: • • "Request for the status of the link layer (REQUEST STATUS OF LINK) Reset of the remote terminal unit link layer (RESET OF REMOTE LINK) Reset Command Function in the Remote Terminal Unit REQUEST STATUS OF LINK - "STATUS OF LINK" is transmitted to the master station RESET of REMOTE LINK - FCB-Bit (Frame Count Bit) is initialized - Acknowledgement for RESET of REMOTE LINK is transmitted to master station Initialization End If "Send Initialization End" is enabled on the basic system element in the IEC 60870-5-101/104 parameter block, after the station initialization is performed, data are only sent from the protocol element if the "INIT-End" has been received from the basic system element for the corresponding ASDU. "<TI=70> Initialization End" is also transmitted to the remote station. The clock synchronization command or general interrogation command may only be transmitted after "INIT-End". Functions Protocol Elements DC0-023-2.01 4-9 Multi-Point Traffic (UMP) 4.1.3. Acquisition of Events (transmission of data ready to be sent) Data of the remote terminal unit ready to be sent are stored on the basic system element (BSE) in the remote terminal unit until transmission. See also chapter "Data Acquisition by Polling (Station Interrogation)". 4.1.3.1. Message from the Remote Terminal Unit to the Master Station Messages from the remote terminal unit to the master station are only transmitted with station interrogation. A quick-check procedure for speeding up the transmission of data is not implemented. 4.1.4. General Interrogation, Outstation Interrogation The general interrogation (outstation interrogation) function is used to update the master station after the internal station initialization or after the master station has detected a loss of information. The function general interrogation of the master station requests the remote terminal unit to transmit the actual values of all its process variables. A general interrogation command "to all" triggered in the system is always transferred by the communications function on the basic system element (BSE) station-selective to the protocol element of the master station and also transmitted station-selective by this to the remote terminal units. Non-Interruptible General Interrogation Spontaneous data are also transmitted from the remote terminal unit during a running general interrogation. With the parameter advanced parameters | IEC 60870-5-101 | Timeout für nicht unterbrechbare GA the spontaneous transmission of data can be disabled in the remote terminal unit during a running general interrogation (monitoring time: "0" = GI uninterruptible; "<> 0" = GI is not uninterruptible). The following parameter settings are necessary on the BSE for the non-interruptible GI: • • "Send Initialization End" (INIT-End) must be enabled General interrogation must take place from the process image (Image-GI) With the INIT-End, the protocol element detects all ASDU's used in transmit direction. This is required with general interrogation to all (BROADCAST) for GI-End detection. With non-interruptible general interrogation, from the moment of "General interrogation command received" all data of the spontaneous priority level from the basic system to the protocol element are inhibited. This block is then terminated by the protocol element, if the general interrogation is complete or the monitoring time "Timeout for noninterruptible GI" has expired. The monitoring time is to be set on the protocol element with the parameter advanced parameters | IEC60870-5-101 | Monitoring time for GI-data and is used in transmit direction for all ASDU's together. The monitoring time is retriggered for messages with the causes of transmission <URS:=2, 7, 20, 21..36>. With general interrogation to a selective ASDU, the monitoring time is stopped if the general interrogation command is received with the cause of transmission <URS:=10> "Termination of Activation", with general interrogation to all ASDU's (BROADCAST), the monitoring time is stopped if for all ASDU's the general interrogation command is received with the cause of transmission "Termination of Activation". 4-10 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.1.5. Clock Synchronization Setting the time The clock synchronization command is sent from the protocol element of the master station to the remote terminal units either station-selective or BROADCAST according to the selected transmission facility. When using the "freely definable transmission facility" the type of transmission of the clock synchronization command can be selected with the parameter Common settings | free defineable transmission facility | Send clock synchronization command to each station selective. With relay operation the clock synchronization command is only transmitted BROADCAST via selected routing paths. Only a few parameterized routing paths are used, with which all stations (remote terminal units and routing stations) can be reached. All stations which receive or forward a clock synchronization command use this for the synchronization of their own clock. Due to this necessary procedure a time setting operation with relay operation can also take several minutes. During the transmission it is ensured, that the time in the clock synchronization command is updated with each new emission. Delay times due to the transmission facility are acquired automatically by the protocol element and taken into consideration during the updating of the time. Messages that are transmitted after a startup, but before the remote terminal unit has the correct time, contain the relative time from startup (reference day: 1.1.2001) with the flagging of the time stamp as invalid. Remote Synchronization The clock synchronization of the remote terminal units can be performed over the serial communication line – controlled by the master station. The remote synchronization is performed cyclic by the master station. The timescale can be set with the parameter advanced parameters | cycle time for sending clock synchronization command. For the remote synchronization a clock synchronization command is sent from the protocol element itself cyclic to the remote terminal units. The typical accuracy that can be achieved through this is ± 20 ms and with relay operation an additional 10 ms per routing station. If the accuracy of the remote synchronization is insufficient, a local time signal receiver must be used in the remote terminal unit. Functions Protocol Elements DC0-023-2.01 4-11 Multi-Point Traffic (UMP) 4.1.6. Command Transmission 4.1.6.1. Message from the Master Station selectively to a Remote Terminal Unit Station-selective data messages in command direction are always inserted into the running interrogation procedure (station interrogation) by the master station with high priority after termination of the data transmission in progress. Data to be sent from the basic system element (=BSE) are always prioritized 1:1 with station interrogations. Demand If the reaction of the remote terminal unit to a transmitted message is to be acquired quickly by the master station, a "Demand" (=parameter-settable station-selective continuous interrogation) can be executed from the master station. This "station-selective demand" is retriggered by further messages to the same station (message parameterized with demand), or aborted by messages to other stations. The selection of the type identification and setting of the continuous interrogation time necessary for the "demand" can be performed in the parameters advanced parameters | call procedure per type identification. The selection of the type identifications is carried out with the parameters advanced parameters | call procedure per type identification | type identification A(TI) ..O(TI) and the setting of the continuous interrogation time assigned to the type identifications is carried out with the parameters advanced parameters | call procedure per type identification | continuous polling time for type identification A..O. Data Flow Control If a remote terminal unit cannot process more data messages (messages), the DFC bit (Data Flow Control) is set in the control field of the message direction remote terminal unit master station. From this moment the protocol firmware of the master station sends no more data messages to the corresponding remote terminal unit, until the remote terminal unit resets the DFC-bit. The protocol firmware also monitors whether the remote terminal unit resets the DFC-bit within a time that can be set with the parameter advanced parameters | IEC 60870-5-101 | DFC-monitoring time. If the DFC-bit is present for longer than the set monitoring time, the warning "DFC-Bit timeout to station No. xx" is output. 4-12 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.1.6.2. Control Location If the function "control location" is activated, commands from the protocol element of the master station are only then transmitted to the addressed remote terminal unit if the command has been sent from an enabled control location (originator address). The setting of the control location itself takes place with a command message in single command format <TI=45> which is converted on the basic system element to a PRE control message (function: set control location) by the protocol control function. A command received with an originator address not enabled as control location is not transmitted from the protocol element of the master station and is discarded. For these commands a negative confirmation of activation (ACTCON-) is sent back immediately by the protocol element to the originator address. 4.1.6.3. Control Location Check The control location check is used to check whether the control location, specified with the originator address in the spontaneous information object "Command", has command authority. The originator address specified in the spontaneous information object "Command" must correspond with one of the control locations previously set. If the originator address in the spontaneous information object "Command" does not match with one of the control locations previously set or if no control location has been preset: • • the command is rejected a negative confirmation of the activation is sent (ACTCON-) The control location check is activated as soon as a PRE control message of the type "Set control location" is entered in the PST detailed routing on the basic system element (BSE) for a protocol element (PRE). After startup of the PRE, the BSE sends a PRE control message "Set control location" to the PRE. As a result the control location check function is activated on the PRE. Functions Protocol Elements DC0-023-2.01 4-13 Multi-Point Traffic (UMP) 4.1.6.4. Set Control Location The control location is set on the PRE with a PRE-control message (Function = Set control location) either globally for all stations or station-selective. The control location can be set or deleted and is applicable for all commands of a protocol element. On the BSE the control location is set by the spontaneous information object "control location" and is valid for all commands of a protocol element. The assignment of this message takes place in the OPM of the Toolbox II with the category ACP 1703 Systemfunktionen / protocol element control message. For the derivation of the control location, the following values in the spontaneous information object "Command" signify the originator address: Note: Originator Address Control Location 0 default 1 ... 127 remote command 128 ... 255 local command The selection of the control location and the generation of the spontaneous information object "Control location" must be programmed in an application program of the open-/closed-loop control function. With the spontaneous information object "Control location" in "single command" format, up to 256 control locations can be set at the same time. The information object "Control location" is converted on the basic system element (BSE) to a PRE-control message and passed on to the protocol element. Due to an information object "Control location" with the single command state "ON", the originator address is added to the list of enabled control locations (="Control location enabled"). Due to an information object "Control location" with the single command state "OFF", the originator address is deleted from the list of enabled control locations (="control location not enabled"). The deleting of the control locations can be carried out either station-selective for each control location individually or globally for all stations and all control locations. No confirmation (ACTCON) and no termination (ACTTERM) of the command initiation is created for the information object "Control location". With each startup of the protocol element, all enabled control locations are reset. The control locations are to be set again after every startup of the protocol element. 4.1.6.5. Message from the Master Station to all Remote Terminal Units (unacknowledged) Messages from the multi-point traffic master station "unacknowledged to all" are inserted at any time into a running interrogation cycle (station interrogation) after termination of the data transmission in progress. The message is thereby transmitted several times by the master station with the parameterized number of message retries according to the parameter Message retries | Retries for data message SEND/NO REPLY (broadcast). Afterwards the interrupted interrogation cycle is resumed. 4-14 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.1.7. Transmission of Integrated Totals A counter interrogation command triggered in the system is transmitted from the protocol element of the master station either station-selective or “to all” (=BROADCAST) according to the parameter advanced parameters | IEC 60870-5-101 | send counter interrogation command as "Broadcast". This parameter is transferred to the basic system element after startup of the protocol element. A counter interrogation command to be sent is then already made available to the protocol element by the basic system element, station-selective or BROADCAST. The functionality implemented in the System SICAM 1703 concerning integrated totals is documented in the document "Common Functions of Peripheral Elements according to IEC 60870-5-101/104". 4.1.8. Acquisition of Transmission Delay The protocol element of the remote terminal unit supports the "Acquisition of transmission delay" and the time correction resulting from this with clock synchronization according to IEC 60870-5. With this procedure the transmission delay is determined with <TI=106> and the corrected time loaded in the remote terminal unit. The correction of the time in the clock synchronization command is carried out in the remote terminal unit. The protocol element of the master station uses a SICAM 1703 specific method for the "acquisition of transmission delay". With this method the transmission delay per remote terminal unit is determined by the protocol firmware of the master station with the sequence "Request Status Of Link" and the reply from the remote terminal unit "Status of Link" and from this an automatically determined correction value is derived. The acquisition of the monitoring time can be carried out cyclic. The cycle time can be set with the parameter advanced parameters | station specific clock sychronization | cycle time for SAT-spec. acquisition of transmission delay. With the parameter advanced parameters | station specific clock sychronization | correction time for clock synchronization command an additional correction value can be parameterized. The clock synchronization command is transmitted station-selective. The time in the clock synchronization command is already corrected by the protocol firmware of the master station with the automatically determined correction value and the parameterized correction value. Functions Protocol Elements DC0-023-2.01 4-15 Multi-Point Traffic (UMP) 4.2. Optimized Parameters for selected Transmission Facilities The protocol element supports selected transmission facilities - for these the parameters are set fixed – the selection of the transmission facility is carried out with the parameter Common settings | interface modem. By selecting the "freely definable transmission facility" certain parameters can be set individually. Most transmission facilities support only certain baud rates or combinations of baud rates in transmit/receive direction – these are to be taken from the descriptions for the transmission facility. The transmission rate (baud rate) is to be set depending on the submodule used for communication, separate for transmit/receive direction with the parameter Common settings | baud rate receiving direction and the parameter Common settings | baud rate transmit direction or for transmit/receive direction together with the parameter Common settings | baud rate. When using the transmission facility "SAT-DLC-Modem (CE0740,-CE0741,-CE0742,-LA0740,-LA0741)" in addition the parameters Common settings | SAT-DLC-Modem | DIP switch S1/1 .. S1/4 and the parameter Common settings | SAT-DLC-Modem | frequency range (=current DIP-switch settings of the DLC-Modem) must be parameterized. These parameters are used for the optimization of the data transmission via SAT-DCLModem and for the automatic setting of the required time settings in the protocol firmware. When using the transmission facility "SATTELLINE 2ASxE Time Slot Radio Modem" in addition the parameter Common settings | Time slot radio modem (SATTELLINE 2ASxE) | failure monitoring, the parameter Common settings | Time slot radio modem (SATTELLINE 2ASxE) | length of time slot and the parameter Common settings | Time slot radio modem (SATTELLINE 2ASxE) | start second of time slot must be parameterized. These parameters are used for the optimization of the data transmission with time slot radio technique. After the transmission of broadcast messages an extra pause can be inserted regardless of the transmission facility used. This pause is required for remote terminal units of third-party manufacturers, if these can only process further messages after a transmission pause following the reception of BROADCAST-messages. The pause after broadcast messages can be set in the master station with the parameter advanced parameters | advanced time settings | pause time after broadcast message (tp_bc) and the parameter advanced parameters | advanced time settings | pause time after broadcast message "time base" (tp_bc). If the pause time is set to "0", a minimum pause of 33 bit is maintained by the protocol element. 4-16 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) Apart from this, a transmission facility, that can be freely defined by the user, can be selected, for which all parameters that are available can be individually set. This is then necessary if transmission facilities are to be used that are not predefined or if modified parameters are to be used for predefined transmission facilities. For the selection of the freely definable transmission facility the parameter Common settings | interface modem is to be set to "freely definable". Only after that are all supported parameters displayed and can be parameterized with the required values (see Table with Default Parameters for Transmission Facilities). For the adaptation to various modems or time requirements of external systems, the following parameters can be set individually: • Common settings | electrical interface [SM2541 only] • Common settings | free defineable transmission facility | asynchron/isochron • Common settings | free defineable transmission facility | source for receive-/transmit clock (only for "Isochronous") • Common settings | free defineable transmission facility | pause time (tp), Common settings | free defineable transmission facility | pause time "time base" (tp) • Common settings | free defineable transmission facility | set up time (tv), Common settings | free defineable transmission facility | set up time "time base" (tv) • Common settings | free defineable transmission facility | run-out time (tn), Common settings | free defineable transmission facility | run-out time "time base" (tn) • advanced parameters | advanced time settings | pause time after broadcast message (tp_bc), advanced parameters | advanced time settings | pause time after broadcast message "time base" (tp_bc), • Common settings | free defineable transmission facility | DCD handling • Common settings | free defineable transmission facility | bounce suppression time (tprell) • Common settings | free defineable transmission facility | disable time (tdis), Common settings | free defineable transmission facility | disable time "time base" (tdis), • Common settings | free defineable transmission facility | stability monitoring time (tstab) • Common settings | free defineable transmission facility | continuous level monitoring time (tcl) • Common settings | free defineable transmission facility | Transmission delay if countinous level (tcldly) • Common settings | free defineable transmission facility | Send clock synchronization command to each station selective • Common settings | free defineable transmission facility | 5V supply (DSR) [only SM0551, SM2551] • Common settings | free defineable transmission facility | Configuration for CM-082x [only SM0551, SM2551] How the individual time settings are effective during the data transmission is shown on the following page in a Timing Diagram. Functions Protocol Elements DC0-023-2.01 4-17 Multi-Point Traffic (UMP) Parameter "5V Supply (DSR)" [only SM0551, SM2551] If necessary the voltage supply of the transmission facility (only 5V) – insofar as this is sufficient – can take place over the state line DSR. The enabling of the voltage supply is performed with the parameter advanced parameters | 5V supply (DSR). The voltage supply is only switched on the DSR state line instead of the DSR signal with corresponding parameter setting. ATTENTION: Required voltage supply and maximum current consumption of the transmission facility must be observed! Parameter "Configuring for CM082x" [only SM0551, SM2551] If an optical transformer of the type CM082x is used as external transmission facility, then the parameter advanced parameters | Konfigurierung für CM082x must be set when using a patch plug of the type CM2860. In addition, for the adaptation of the protocol to the transmission medium used or to the dynamic behavior of the connected remote station, the following parameters are available: • advanced parameters | monitoring times | Character monitoring time, advanced parameters | monitoring times | Character monitoring time "time base" • advanced parameters | monitoring times | idle monitoring time, advanced parameters | monitoring times | idle monitoring time "time base" • advanced parameters | monitoring times | expected_ack_time_corr_factor (see acknowledgement procedure in the master station) The character monitoring time and idle monitoring time is used for message interruption monitoring and message re-synchronization in receive direction. A message interruption is detected if the time between 2 bytes of a message is greater than the set character monitoring time. With message interruption the running reception handling is aborted and the message is discarded. After a detected message interruption a new message is only accepted in receive direction after an idle time on the line (idle time). The protocol element can – insofar as the transmission facility (e.g. VFT-channel) makes this signal available receive-side – evaluate the interface signal DCD and utilize it e.g. for monitoring functions. 4-18 DC0-023-2.01 Functions Protocol Elements Default parameters for transmission facilities with UMPMxx Transmission facility Electrical Multi-Point Traffic (UMP) RTS Interface tp tv tn tp_bc tdis [ms] [ms] [Bit] [ms] [ms] DCD tbs tstab tduration tdelay [ms] [ms] [sec] [ms] A_I T Z 5V CM082x 1) 1) SAT Modem "4-wire transmission line " (SAT-VFM,-WT,-WTK,-WTK-S,-CE0700) RS-232 ON 0 0 3 0 35 YES 5 5 10 200 A I B NO NO SAT Modem "2-wire transmission line " (SAT-VFM,-WT,-WTK,-WTK-S,-CE0700) RS-232 0 30 3 0 35 YES 5 5 10 200 A I B NO NO SAT DMS (ring configuration) RS-232 ON 0 0 5 0 0 NO 0 0 0 0 A I s NO NO SAT-DMS (Ring configuration; AU transmitted with WT) RS-232 0 50 5 0 35 YES 5 5 10 200 A I s NO NO OPTICAL RS-232 0 1 0 0 0 NO 0 0 0 0 A I B YES NO RADIO digital RS-232 30 100 11 0 50 YES 10 5 0 200 A I B NO NO Radio analog RS-232 50 300 50 ms 0 100 YES 10 5 0 200 A I B NO NO Direct connection (RS-485) RS-485 0 1 0 0 0 NO 0 0 0 0 A I B YES NO SAT-DLC-Modem (CE0740,-CE0741,-CE0742,-LA0740,-LA0741) RS-232 0 0 0 0 0 NO 0 0 0 0 A I B NO NO SAT Modem "4-wire transmission line" (SAT-CE0701) RS-232 ON 0 0 3 0 0 YES 5 5 10 200 A I B NO NO SAT Modem "2-wire transmission line" (SAT-CE0701) RS-232 22 30 3 0 0 YES 5 5 10 200 A I B NO NO SAT Modem "2-wire transmission line" (SAT-CE0701 via Modem) RS-232 0 60 5 0 35 YES 5 5 10 200 A I s NO NO SAT Modem "2-wire transmission line" (SAT-CE0701 via Westermo TD-32) RS-232 0 1 0 0 0 NO 0 0 0 0 A I s NO NO SAT Modem "2-wire transmission line" (SAT-CE0701 via Westermo GD-01) RS-232 0 1 0 0 0 NO 0 0 0 0 A I s NO NO Direct connection (RS-232) RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I B NO NO SATTELLINE 2ASxE time slot radio modem RS-232 0 1 0 0 0 NO 0 0 0 0 A I B NO NO Freely definable Legend: electrical interface .......................... Parameter "electrical interface" [only SM2541] RTS................................................... = RTS is switched for the control of the carrier switching of the modem with each message (ON / OFF) tp ...................................................... Parameter "Pause time (tp)", Parameter "Pause time time base (tp)" tv....................................................... Parameter "Set-up time (tv)", Parameter "Set-up time time base (tv)" tn ...................................................... Parameter "overtravel time (tn)", Parameter "overtravel time time base (tn)" tp_bc ................................................ Parameter "Pause time after broadcast message (tp_bc)", Parameter "Pause time after broadcast message_time base (tp_bc)" tdis ................................................... Parameter "Blocking time (tdis)", Parameter "Blocking time time base (tdis)" DCD .................................................. Parameter "DCD-assessment" tbs .................................................... Parameter "Bounce suppression time (tbs)" tstab ................................................. Parameter "Stability monitoring time (tstab)" tduration .......................................... Parameter "Continuous level monitoring time (tduration)" tdelay ............................................... Parameter "transmit delay for level (tdelay)" A_I .................................................... Parameter "Asynchronous_Isochronous" T........................................................ Parameter " Bit timing (only with isochronous)" (I=internal, E=external) Z........................................................ Parameter "send clock synchronization command station-selective" (s=selective, B=BROADCAST) 1) CM082x .............................. ...... Parameter "Configuring for CM082x". Configuring the interface for optical transformer CM-082x with patch plug CM-2860 [only SM0551, SM2551] 1) 5V .............................................. Parameter "5V Supply (DSR)" [only SM0551, SM2551] Functions Protocol Elements DC0-023-2.01 4-19 Default parameters for transmission facilities with UMPSxx Transmission facility Electrical Multi-Point Traffic (UMP) RTS Interface tp tv tn tdis [ms] [ms] [Bit] [ms] DCD tbs tstab tduration tdelay [ms] [ms] [sec] [ms] A_I T 5V CM082x 1) 1) SAT Modem "4-wire transmission line " (SAT-VFM,-WT,-WTK,-WTK-S,-CE0700) RS-232 ON 0 0 3 35 YES 5 5 10 200 A I NO NO SAT Modem "2-wire transmission line " (SAT-VFM,-WT,-WTK,-WTK-S,-CE0700) RS-232 0 30 3 35 YES 5 5 10 200 A I NO NO SAT DMS (ring configuration) RS-232 ON 0 0 5 0 NO 0 0 0 0 A I NO NO SAT-DMS (Ring configuration; AU transmitted with WT) RS-232 0 50 5 35 YES 5 5 10 200 A I NO NO OPTICAL RS-232 0 1 0 0 NO 0 0 0 0 A I YES NO RADIO digital RS-232 30 100 11 50 YES 10 5 0 200 A I NO NO Radio analog RS-232 50 300 50 ms 100 YES 10 5 0 200 A I NO NO Direct connection (RS-485) RS-485 0 1 0 0 NO 0 0 0 0 A I YES NO SAT-DLC-Modem (CE0740,-CE0741,-CE0742,-LA0740,-LA0741) RS-232 0 0 0 0 NO 0 0 0 0 A I NO NO SAT Modem "4-wire transmission line" (SAT-CE0701) RS-232 0 55 3 0 NO 0 0 0 0 A I NO NO SAT Modem "2-wire transmission line" (SAT-CE0701) RS-232 22 30 3 0 YES 5 5 10 200 A I NO NO SAT Modem "2-wire transmission line" (SAT-CE0701 via Modem) RS-232 0 60 5 35 YES 5 5 10 200 A I NO NO Direct connection (RS-232) RS-232 ON 0 0 0 0 NO 0 0 0 0 A I NO NO SATTELLINE 2ASxE time slot radio modem RS-232 0 1 0 0 NO 0 0 0 0 A I NO NO Freely definable Legend: Electrical interface ......................... Parameter "electrical interface" [only SM2541] RTS................................................... = RTS is switched for the control of the carrier switching of the modem with each message (ON / OFF) tp ...................................................... Parameter "Pause time (tp)", Parameter "Pause time time base (tp)" tv....................................................... Parameter "Set-up time (tv)", Parameter "Set-up time time base (tv)" tn ...................................................... Parameter "Overtravel time (tn)", Parameter "Overtravel time time base (tn)" tdis ................................................... Parameter "Blocking time (tdis)", Parameter "Blocking time time base (tdis)" DCD .................................................. Parameter "DCD-assessment" tbs .................................................... Parameter "Bounce suppression time (tbs)" tstab ................................................. Parameter "Stability monitoring time (tstab)" tduration .......................................... Parameter "Continous level monitoring time (tduration)" tdelay ............................................... Parameter "Transmit delay for level (tdelay)" A_I .................................................... Parameter "Asynchronous_Isochronous" T........................................................ Parameter " Bit timing (only with isochronous)" (I=internal, E=external) 1) CM082x .............................. ...... Parameter "Configuring for CM082x". Configuring the interface for optical transformer CM-082x with patch plug CM-2860 [only SM0551, SM2551] 1) 5V .............................................. Parameter "5V Supply (DSR)" [only SM0551, SM2551] 4-20 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) The following picture shows the dynamic behavior (timing) in detail for the data transmission when using transmission facilities with switched carrier. Only for BROADCASTmessages RTS Master station tverz tp tv tn Data transmission tp_bc tsw tp tv TXD tPrell DCD tPrell tverzRTS Data transmission RXD tsignal tsignal tdis t´verzRTS t´verzRTS t´Prell Remote station DCD t´Prell t´signal Data transmission RXD t'dis RTS t'sw tp' t'v Data transmission t'n TXD t'verz tPrell tPrell tstab tstab tdauer Legend: RTS ………….. Request to Send DCD …………. Data Carrier Detect TXD ……...….. Transmit Data RXD ……...….. Receive Data tverzRTS ……….. Processing time of the transmission system Time delay/time difference between activation of transmit part (RTS ) and receiver ready (DCD ) tp ………….….. Break time (delay, before transmit part is activated with RTS) tv ………….….. Setup time (transmission delay, after transmit part was activated with RTS ) tn ………….….. Reset time (delayed switch off of the transmit signal level with RTS after message transmission ) tp_bc ……….….. Break time after BROADCAST-Messages (some systems require a longer break after the transmission of BROADCAST -messages before the next message can be sent ) tsw ….....….….. Internal processing time tsignal ….....….. Signal propagation delays (dependent from the used transmission facility /transmission path) tPrell …...….….. Protective time after positive/negative DCD-edge (debounce of DCD) tstab …...….….. Stability monitoring time – the new DCD-status is only used for message synchronisation after the expiration of the stability monitoring time tdauer …...….….. Continuous level monitoring time tverz …...….….. Transmission delay – in case of a continuous level a further message transmission will be made at the latest after the transmission delay tdis …….….….. Disable time of the receiver after message receiption (to supress faulty signs during level monitoring ) t`x …………….. Corresponding times in the remote stations …………….. DCD valide Functions Protocol Elements DC0-023-2.01 4-21 Multi-Point Traffic (UMP) 4.3. Co-ordination of Several Masters One interface of a SICAM 1703 master station can manage up to 100 remote terminal units. If more than 100 remote terminal units are to be connected on one line to a SICAM 1703 master station (e.g. for radio communication with the same radio frequency), then several interfaces of the SICAM 1703 master station can be connected in parallel (max. 16). These interfaces are then coordinated, so that always only 1 interface is active at one moment and the master function only interrogates those remote terminal units that are assigned to this interface. Coordination connection *) DSR DTR ERR DSR Master station (Interface-1) DTR ERR DSR Master station GND (Interface-2) MASTER-1 DTR ERR Master station GND (Interface-m) MASTER-2 GND MASTER-m m <= 16 TF Remote station-1 T Remote station-1 T Remote station-1 T Remote station-2 T Remote station-2 T Remote station-2 T Remote station-n T Remote station-n T Remote station-n T n <= 100 n <= 100 n <= 100 Legend: T, TF …...…... DSR ……….… DTR …….…… ERR ……….… *) …………….. Transmission facility Data Set Ready (V.24/V.28 Status line) – Coordination signal „OUT“ *) Data Terminal Ready (V.24/V.28 Status line) – Coordination signal „IN“ *) In case of Power OFF or failure of the communication interface the coordination line must be closed „external“ ! The coordination connection requires also a connection of the GND -lines of the V.24/V.28 interfaces of the master stations! The coordination of multiple interfaces is enabled in the protocol element of the master station with the parameter advanced parameters | masterkoordination. The assignment of the remote terminal unit to the associated master (=interface of the master station) is defined in the remote terminal unit with the parameter advanced parameters | radio area identifier/master number. The determination of the master number is carried out in the master station either with the parameter advanced parameters | radio area identifier/master number or with the parameter advanced parameters | coordination several masters | master number for coordination. This assignment must be performed in every remote terminal unit and in every master. The master number is transmitted in the message on the line in the 2nd octet of the link address. The coordination of the interfaces of the master station takes place by means of the interface signals DTR and DSR. Thereby in each case the DTR-line (=output) of an interface is connected with the DSR-line (=input) of the next interface of the master station and in this way a communication link of all interfaces to be coordinated is established. It must be ensured through external circuitry, that with a failure of one interface, the coordination circuit is closed. A coordination of multiple masters is only possible with closed coordination circuit. 4-22 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) For the parallel connection of the interfaces, for each interface of the master station a separate transmission facility must be used or suitable wiring of the interface lines with diodes. Note: Since the interface lines DTR and DSR are used for the coordination, the interface cannot be switched to tristate during inactive coordination! After a restart, the master with the lowest master number first sends an "Initialization Token" on the coordination circuit to the next master after a delay time (t_start_delay). The delay time is calculated automatically by the protocol element according to the set parameters (baud rate, master number,...). All masters which presently do not carry out any station interrogation, relay this "Initialization Token" to the next master. If a master receives the "Initialization Token" it has transmitted itself, it starts with the station interrogation of its remote terminal units. If a master is presently performing the station interrogation of its remote terminal units at this time, this master does not pass on the "Initialization Token" to the next master. When this master has concluded its station interrogations, it steps to the next master with a Stepping Token. The transmit time can be set for every master with the parameter advanced parameters | coordination several masters | max. number of polling messages befor activating next master. On expiry of this time, a "Stepping Token" is transmitted on the coordination circuit and thus stepped to the next master. In addition each master monitors whether it receives a token on the coordination circuit within a time that can be set with the parameter advanced parameters | coordination several masters | monitoring time for cordination of several master. On expiry of this monitoring time, all remote terminal units of a master are flagged as failed. To resume the coordination, the master sends an "Initialization Token" to the next master. On the coordination circuit, "Initialization Token" (100ms pulse) and "Stepping Token" (30ms pulse) are transmitted with different pulse lengths. Master station-n Master station-2 Master station-1 Timing for the coordination of multiple master stations: DTR t_start-delay t_token-tio i w 100ms w w 30ms i` DSR w` w` Data i DTR w i` DSR w w` w` w` Data i DTR i` DSR w w` w w` Data Legend: DTR ……...….. Data Terminal Ready - „Coordination signal (OUT)“ DSR …….……. Data Set Ready - „Coordination signal (IN)“ Data ……...….. Transmission time (Data transmission) of the master station with the own remote stations RXD ……...….. Receive Data i …….…..…….. Initialization Token (OUT) - 100ms i` …...…..…….. Initialization Token (IN) w …...…..…..... Stepping Token (OUT) - 30ms w` …..….…...... Stepping Token (IN) t_token-tio …... Token timeout monitorint time t_start-delay … Delay after RESET – transmission of an initialization token after the end of the delay time …………….. RESET Functions Protocol Elements DC0-023-2.01 4-23 Multi-Point Traffic (UMP) 4.4. Standby Transmission Line over the Public Telephone Network (PSTN) The data transmission between master station and the remote terminal units during fault-free operation takes place over the main transmission line. Failed remote terminal units can be interrogated on the standby transmission line over the public telephone network (PSTN). For this, a connection is established from the interface for standby transmission line over the public telephone network (PSTN), which establishes a transparent communications link to a transmission facility (TF), for multi-point traffic preferably at the other end of the transmission line. The connection setup is thereby initiated with the state line DTR – the telephone number is fixed programmed in the modem. Presently, for the standby transmission line operation over the public telephone network (PSTN) at master station end only the dial-up modem WESTERMO TD32 is supported and at remote terminal units end, the modems WESTERMO TD32 (=analog) or WESTERMO GD01 (=GSM). At the remote terminal unit end, in addition a protocol converter WESTERMO MD54 is required. Schematic configuration for standby transmission line operation over public telephone network (PSTN): Master station Ax-1703 Basic system element (BSE) Function diagram UMPM02 UMPM02 “Main transmission line“ (ZSE = 128 or 130) “Standby transmission line“ (ZSE = 129 or 131) DTR MODEM TF Public telephone network “PSTN“ MODEM Protocol converter TF TF TF TF TF Remote station-1 Remote station-2 Remote station-3 Remote station-n Main transmission line Standby transmission line Legend: TF ………..….. …………….. …………….. …………….. …………….. …………….. Transmission Facility Failed remote stations are signaled to the basic system element as failed . Failed remote stations must be signaled to the standby protocol element with a protocol element control message The standby transmission line via dial-up traffic is established with status line DCD The coordination of main-/standby transmission lines takes place with internal protocol control messages The transmission path for standby must guarantee a transparent connection (no gaps in messages, baud rate and byte frame to TF on standby transmission line must be identical with the baud rate and byte frame used on the main transmission line ) …………….. Example for conductor interruption and hence split in remote stations accessible on main and standby transmission line . The standby transmission line operation over public telephone network (PSTN) is activated on the protocol element of the interface for standby transmission line with the parameter advanced parameters | Master für Ersatzweg (PSTN). 4-24 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) The assignment of the interface for main transmission line and standby transmission line is defined as follows: Main Line Standby Line SSE = 128 SSE = 129 SSE = 130 SSE = 131 Legend: Note The SSEs for main-/standby transmission line must be on the same BSE. SSE = supplementary system element (with serial interfaces this is always configured with a PRE) PRE = Protocol element BSE = Basic system element The remote terminal units are interrogated by the master station predominantly on the main transmission line. If the protocol element of the master station detects a remote terminal unit on the interface of the main transmission line as failed, then this is reported to the basic system element (BSE) as failed. The station failure is to be transferred as protocol control message to the interface for standby transmission line by using the function diagram on the basic system element (BSE). The testing of the standby transmission line is also to be realized with the function diagram. With the parameter advanced parameters | Master for stand-by transmission line via PSTN | delay time for activation of stand-by transmission line the protocol element for standby transmission line performs a station-selective delayed selection of the standby transmission line. If a remote terminal unit reported as failed on the main transmission line is reported as OK again during the delay time, no standby transmission line is established for this remote terminal unit. After expiry of the delay time the standby transmission line is set-up. If the connection setup is not successful, after a pause that can be set with the parameter advanced parameters | Master for stand-by transmission line via PSTN | Pause between not successful dial-up sequence a new connection setup is initiated. If the connection cannot be established over the public telephone network (PSTN) after max. 4 dialing attempts, the corresponding remote terminal units are also reported as failed by the interface for standby transmission line. The established standby transmission line is reported to the protocol element for main transmission line by means of an internal protocol control message. From this moment, the protocol elements of the interfaces for main and standby transmission line coordinate themselves with internal protocol control messages in such a way, that the remote terminal units of the multi-point traffic line are always only interrogated by one interface (main or standby transmission line) at one time. After a concluded message transmission including receipt of the acknowledgement, the control is transferred to the other interface with the internal protocol control message ("send next message"). Station interrogations on the standby transmission line are always first started after a delay time. As a result, messages of a remote terminal unit are received on the main transmission line that are possibly delayed on the standby transmission line. Failed remote terminal units also continue to be interrogated on the main transmission line (but from now on every 10th time). If a failed remote terminal unit can be reached again on the main transmission line, the standby transmission line handling is terminated for this RTU. If all remote terminal units can be reached again on the main transmission line, the connection for standby transmission line is terminated after a delay time of 1 minute. Functions Protocol Elements DC0-023-2.01 4-25 Multi-Point Traffic (UMP) The parameter setting of main-/standby transmission line is carried out in the topology. From this parameter setting the routing of the internal protocol control messages necessary for the coordination is also derived. Functions of the protocol converter for standby transmission line: • Adaptation of the baud rate The baud rate from/to transmission facility (ÜE) on the standby transmission line must be identical with the baud rate from/to transmission facility (ÜE) on the main transmission line. • Adaptation of the byte frame The byte frame from/to transmission facility (ÜE) on the standby transmission line must be identical with the byte frame from/to transmission facility (ÜE) on the main transmission line. • Removal of message gaps Messages to the transmission facility (ÜE) on the standby transmission line must not contain any gaps (pauses). Note: On the protocol element for standby transmission line, in addition a greater time for the message interruption monitoring is to be set with the parameter advanced parameters | monitoring times | Character monitoring time and the parameter advanced parameters | monitoring times | Character monitoring time "time base". 4-26 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.5. Data Transmission using Time Slot Radio With time slot radio the radio transmission may only be utilized during a particular time (typically max. 6 seconds per minute). The remaining time is utilized for the radio transmission of other systems – this transmission method is called "Time Slot Technique". For the utilization of the time slot technique in Germany, for this 5 frequencies are approved nationwide for the exclusive professional data radio transmission using the time slot method. In this method, in each case 10 users can utilize a common frequency for 6 seconds each within 1 minute. The synchronization of the time slot takes place by means of a DCF-77 signal (atomic clock), so that overlaps are excluded. This new method can be used everywhere, where there are no time-critical data or where data are collected over a certain period before the transmission, in order to then send these in a packet. Since no station needs to be mobile, fixed installed local radio data networks can be established. The applications can be seen in the areas of measurement data transmission between fixed stations, power utilities, water, waste water, meteorology, control data to fixed stations, packet-orientated control tasks, alarm transmissions and many more. As a result the user has other benefits: • • • • • • high ranges free point-to-point data transmission free point-to-multipoint data transmission free data transmission in master-slave operation free data transmission for multimaster networks low interferences from neighboring disturbance emitters. Through the use of suitable additional devices (Time Slot Unit) in the master station and the implementation of suitable procedures, it is ensured, that no time slot violation occurs during the data transmission. The SATELLINETSU (Time Slot Unit) is a unit with integrated DCF-77 receiver – this unit switches through the transmission lines between the transmitting station and the connected time slot radio modem for the set time slot. The TSU is normally used in each station that cannot manage the time slot in a highly precise manner. For MASTER / SLAVE configurations the TSU is mostly only used in the MASTER – through suitable measures in the communications protocol implemented, a time slot violation by the SLAVE must be prevented (especially through a message still sent by the SLAVE at the end of the time slot). For this the state line input CTS in the MASTER is wired with the signal CTS of the TSU (Clear to Send). This signal is "ACTIVE" for the respective station during the assigned time slot. The master only sends data during the assigned time slot, but only until the reply from the remote terminal unit is transmitted completely, in all cases within the time slot. The CTS-signal from the TSU is also monitored for plausibility. If the CTS-signal from the TSU switches to inactive during a running message transmission before expiry of the parameterized "Length of the time slot", the interface of the master station is switched immediately to TRISTATE – in addition the CTS-signal of the TSU is monitored for failure. The data transmission using the time slot method is selected by selecting the transmission facility "SATTELLINE 2ASxE time slot radio modem " with the parameter Common settings | interface modem. When using this transmission facility, in addition, in the MASTER the parameter Common settings | Time slot radio modem (SATTELLINE 2ASxE) | failure monitoring and the parameter Common settings | Time slot radio modem (SATTELLINE 2ASxE) | length of time slot und der Parameter Common settings | Time slot radio modem (SATTELLINE 2ASxE) | start second of time slot must be parameterized. These parameters are used for the optimization of the data transmission with time slot radio technique. Functions Protocol Elements DC0-023-2.01 4-27 Multi-Point Traffic (UMP) 4.6. Data Transmission in Relay Operation “Multi-Point Traffic with Routing” In relay operation, messages transmitted from the master station can also reach the remote terminal unit indirectly (and vice versa), namely by way of intermediate stations along the transmission path, that can always communicate directly with their respective adjacent station. Such stations lying along the path between source and destination of a message transmission "only" provide a routing function for the transmission in question (namely reception and forwarding of messages). In this sense, such stations are routing stations. Remote terminal units themselves can also be used as routing stations for other remote terminal units. All stations participating in the multi-point traffic are equipped with protocol elements for relay operation and through this possess the capability of routing – in general besides their process-related tasks and independent from these. The routing paths are defined through parameterization in the master station. The routing for a routing path can take place via up to 7 routing stations. For each station a primary path and a secondary path can be defined. With wired communication, the relay operation can be used for regenerating the signal: if for example a very remote station can only be reached with great difficulty, error-free communication is often only possible with a very high number of retries. By routing the messages over a routing station, the attainability can be improved considerably. With radio communication, it can happen, that due to the geographical location or the limited transmitting power and an insufficient number of transmission frequencies, not all stations can be reached with just one transmitter installed in the master station. With the communication procedure of the relay operation, despite the use of the most simple of radio devices (even with low transmitting power), the required communication tasks are resolved with just one single radio frequency in the entire automation range. The function "Relay Operation" is a SICAM 1703-specific expansion of the IEC 60870-5-101 protocol in multi-point traffic. The function Relay Operation is activated by enabling the parameter advanced parameters | Repeater function (Routing). By enabling this parameter, the parameters required for relay operation such as "Routing method", "Retries until path change" and "Routing paths" are first displayed. 4-28 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) If the relay function is not enabled, the protocol functions according to IEC 60870-5-101. With function enabled, the protocol no longer corresponds with the IEC 60870-5-101 standard, since an extra block is used in the message for the routing information for the relay function. The user data formats themselves continue to be used according to IEC 60870-5-101. LINK Routing-Information IEC 60870-5-1 IEC 60870-5-2 Expansion for relay operation Control field (Length, Index) Routing Station-Nr. „1" Index IEC 60860-5-101 ASDU LINK IEC 60870-5-1 Routing Station-Nr. „n“ Index Parameters for relay operation: • Enabling of the relay function with the parameter advanced parameters | Repeater function (Routing) • Switchover main-/standby transmission line with the parameter advanced parameters | Repeater function (Routing) | retries until switchover to stand-by line • Routing method (optimized/not optimized) with the parameter advanced parameters | Repeater function (Routing) | routing procedure • "Radio circuit identifier/master number" with the parameter advanced parameters | radio area identifier/master number • "Routing paths" (path-type, destination station number, routing station number) with the parameters advanced parameters | Repeater function (Routing) | routing-paths | path type, Destination station number, routing station nr. Functions Protocol Elements DC0-023-2.01 4-29 Multi-Point Traffic (UMP) Multi-point traffic with relay operation over radio In utilities, many small and medium size stations fail to become automated because of communication problems. Where dedicated lines or, because of poor infrastructure, dial-up traffic cannot be used, one often has to fall back on radio communication. Thereby it can happen, that due to the geographical location or the limited transmitting power and an insufficient number of transmission frequencies, not all stations can be reached with just one transmitter installed in the master station. Relay operation solves this problem despite using only the most simple radio communication units (even of low transmitting power) with only one single frequency in the entire automation range. Functioning principle of the radio relay operation In particular in mountainous regions, where even the highest elevation is in most cases insufficient for a radio transmitter, in order to reach every individual valley the radio relay operation provides the solution to the problem. Up to 7 routing stations can be used for the data transfer (with regard to routing and fulfilling process-related tasks e.g. telecontrol functionality - see above). A chronological coordination of all transmitter up-switching operations in the entire network thereby takes place. U1 U3 U2 Z U4 Legend: Z ….…...….….. Master station U1,U2, U3 .….. Remote stations (used as routing stations in this example) U4 ….....….….. Adressed remote station ,,,…..... Messages in direction: master station remote station ,,, …..... Messages in direction: remote station master station …………….. In case of adequate transmission power U3 can also be reached directly from U1 (=shorter path) A message is transported via radio by means of multi-point traffic (half duplex) over a predefined path from the source (master station or RTU depending on the direction) to the destination (RTU or master station depending on the direction). The path leads • either from the source directly to the destination, or – if that is not possible - • Indirectly from the source – via one or more routing stations, which only forward messages – to the destination. From the example in the picture above it can be seen, that individual stations cannot reach others directly via radio because of the mountains situated in between. Stations which are capable of communicating with one another directly via radio communication are located within one "radio region": the example shown includes the following radio regions: (Z, U1), (U1, U2, U3) and (U3, U4). 4-30 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) For the transmission of a message from the master station Z to the remote terminal units U1, U2, U3, and U4, the following routes are possible (reverse direction along the same route): Source Destination Z U1 Z U1 Z U2 Z U1 U2 Z U3 Z U1 U3 shorter route advantageous Z U3 Z U1 U2 U3 longer route disadvantageous Z U4 Z U1 U3 U4 Legend: Z, U U Route Note source, destination routing station In the following picture, radio regions are represented by closed curves. Main transmission line U1 Standby transmission line U3 U2 Z Radio regions U4 Legend: Z ….…...……........ Master station U1,U2, U3, U4 …. Remote stations (U1,U2,U3 serve in this example also as routing stations ) Radio regions …... All stations in the same radio region can communicate with each other (ZU1U3U4, U4U3U1Z) …….... Main transmission line (ZU1U2U3U4, U4U3U2U1Z) ………. Standby transmission line The shortest route along which an outstation can be reached is determined by parameter setting. This route is also contained in the message transmitted. All stations within reach of the respective transmitter will receive the message. However, it will be retransmitted only by the routing station that is next in the routing order and thus be passed on in the relay operation - until it arrives at its destination. The function of the routing stations can be taken over by remote terminal units with process-related tasks. If remote terminal units cannot be reached directly or without gaps over other remote terminal units due to the local circumstances, additional stations must be used for routing (data relay stations). All remote terminal units – even those which only have routing tasks – are interrogated by the master station in a configurable interrogation cycle. Stations with important data can be called several times in one interrogation cycle. The transmission of the data from the remote terminal units to the master station take place by means of a relaywise forwarded, selective station interrogation (Polling). The remote terminal unit stores changed data and transmits these back to the master station in the same manner with a station interrogation of this station. To increase the availability, besides the main transmission line a redundant route (standby transmission line) can be defined. Functions Protocol Elements DC0-023-2.01 4-31 Multi-Point Traffic (UMP) Transmit time limitation of the radio equipment So that remote terminal units or radio equipment that are functionally impaired do not lead to a blocking of the link, it is advisable to equip the radio equipment used with a transmit time limit (e.g. external equipment connected between remote terminal unit and radio equipment, which monitors the RTS signal). This unit should switch the radio equipment off after a settable maximum time. After this protection device has responded in a disturbance event, the interrogation cycle to the remaining stations can continue to be carried out by the master station. Speech The utilization of the radio equipment for telephony cannot be enabled with intermediate routing stations and because of the use of only one radio frequency (speech must be buffered in the routing stations). In this case a separate radio channel is to be used for the transmission of speech (e.g. mobile radio). For remote terminal units that can be reached directly from the master station, the radio equipment of the master station and the remote terminal unit can however be used for speech transmission. So that an interface fault signaling in the master station does not occur with speech transmission (data transmission not possible due to activated speech connection), on switchover of the radio equipment the master station is provided with a binary information, through which the interrogation cycle is stopped. On termination of the speech transmission the interrogation cycle is resumed. Time stamping, clock synchronization The routing often over several routing stations causes longer total transmission times. Here it is particularly advisable to perform the time stamping for process information directly at the point of origin. The management of a real-time clock necessary in each of the remote terminal units for time stamping must often manage without decentral time signal receiver for reasons of cost and poor reception locations in many cases. The clock synchronization of the remote terminal units can also be carried out over the serial communication line. The clock synchronization is typically carried out once per minute by the master station. The typical accuracy that can be achieved through this is ± 20 ms and with relay operation an additional 10 ms per routing station (see also chapter Clock Synchronization). 4-32 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) Radio circuit identifier When using the same radio frequencies in different, local and geographically separated regions, due to over-ranges in the radio communication, a remote terminal unit could receive station interrogations or even commands from a third-party master station. If, for example, several multi-point traffic areas – each with a master station - are formed in one automation network, then a mutual influencing (over-ranges) and an undesirable system behavior caused as a result can be prevented, by • • • assigning a different radio frequency to every multi-point traffic area or/and performing a station number assignment unambiguous over all areas or/and an unambiguous assignment (in the framework of the configuration options) of all stations to their respective own master station with the help of the radio circuit identifier. The radio circuit identifier must be configured in the master station and in every remote terminal unit. The assignment of the remote terminal units to the associated master (=interface of the master station) is defined with the parameter advanced parameters | radio area identifier/master number. The master number is transmitted in the message on the line in the 2nd octet of the link address. All messages from the master station are sent with the configured radio circuit identifier. Messages are only then evaluated by the routing stations, if the radio circuit identifier contained in the message corresponds with that configured. As a result, messages that are received from third-party master stations / remote terminal units (due to over-ranges in the radio communication) are ignored. Functions Protocol Elements DC0-023-2.01 4-33 Multi-Point Traffic (UMP) 4.6.1. Main and Standby Transmission Line For every remote terminal unit that cannot be reached directly, but only via routing stations, the main transmission line must be configured in the master station (Routing Information: series of RTU-addresses, over which a remote terminal unit can be reached from the master station over the shortest route). In addition, for every remote terminal unit a standby transmission line can be configured (Routing Information: series of RTU-addresses, over which a remote terminal unit can also be reached from the master station). The parameters for "Routing" are only displayed by enabling the parameter advanced parameters | Repeater function (Routing). For every routing-path (main or standby transmission line) to a remote terminal unit (destination station number) a new row must be parameterized in the spreadsheet with the parameters for "Destination station No.", "Path type" and "Routing station No.1...7". Every remote terminal unit in multi-point traffic (directly reachable remote terminal unit and routing station) is to be recorded in the parameter "Station definition". Thereby a new row is appended in the spreadsheet for every remote terminal unit and the corresponding stationspecific parameter entered. With fault-free station interrogation, all remote terminal units are interrogated directly, respectively over the configured main transmission line. If remote terminal units cannot be reached from the master station over the main transmission line (failure/fault of transmit/receive systems, of routing stations, the RTU itself, etc.), communication is attempted over the configured standby transmission line. With the parameter advanced parameters | Repeater function (Routing) | retries until switchover to stand-by line the moment for the switchover from main to standby transmission line can be defined. If this attempt to obtain an acknowledgement also fails (expiry of number of retries ) or if no standby transmission line has been configured, the remote terminal unit is flagged as faulty. Configured standby transmission lines are checked in the background at configurable intervals. If stations are only reachable over the standby transmission line, the main transmission line is monitored in the background. With fault-free communication, a standby transmission line configured for a station is checked after every 20 station interrogations (default). With faulty main transmission line, with configured standby transmission line this is checked after every 10 station interrogations. With faulty main or standby transmission line, a warning is generated by the master station in the form of "stationselective binary information". Quality assessment of main and standby transmission line A quality assessment is carried out for the main and standby transmission line. The quality of a route is derived from the message retries required. If the quality of a route is no longer provided, a warning is also derived from the master station. For the quality assessment, the last 16 messages per route are assessed. If from the last 16 messages, more than a configurable number have not been acknowledged, a warning is output. 4-34 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.6.2. Routing Method Received messages are re-transmitted immediately after complete reception by "data relay stations", if these are determined for further transmission based on the "Routing Information" (in the message). Messages received by stations that are not defined as "End station" (= addressed remote terminal unit) or "data relay station" (station is not or not yet provided in the routing information of the message), are not processed further. The received routing information is entered in the reverse order by the addressed "End station" for the reply message to be transmitted. Consequently, the reply message is transmitted through the network over the route specified by the master station. In relay operation, stations can be reached through the "Routing method" implemented over a maximum of 7 "data relay stations" (routing stations). For stations that can be reached directly from the master station, the configuration of routing information is not necessary. The structure of the routing information used in the message is defined with the parameter advanced parameters | Repeater function (Routing) | routing procedure . D7 D6 D5 0 0 Length D4 Index D3 D2 D1 D0 Length Routing station - 1 Index = 0 Routing station - 2 Index = 1 Routing station - 3 Index = 2 Routing station - 4 Index = 3 Routing station - 5 Index = 4 Routing station - 6 Index = 5 Routing station - 7 Index = 6 Legend: Length ...….…..Number of registered routing stations (1..7) - The length of the routing field is dynamically administrated in case of an „optimized routing method“. That means that only those routing stations are registered in the routing fields which are actually required . - „Non-optimized routing methods“ transmit the routing field always in „maximal length“ (8 Bytes) In the routing field „Length“ only the actual number of used fields for routing stations must be entered . Unused routing fields are initialized with „FF“. Index ………… Information about the processed routing fields (0..6). Functions Protocol Elements DC0-023-2.01 4-35 Multi-Point Traffic (UMP) 4.6.2.1. Non-optimized Routing Method With the "non-optimized routing method" the routing information in messages is managed "statically". The routing information is always available with maximum length in messages with fixed/variable block length. I.e., station interrogations / acknowledgements are generally transmitted with the "message format with fixed block length", user data are transmitted with the "message format variable block length". Single characters are not used! Example: Management of the routing information with 3 routing stations for "non-optimized routing method" Z U1 LINK 0 3 Target station-Nr. = U4 0 0 3 U2 LINK Target station-Nr. = U4 0 0 1 3 U3 LINK Target station-Nr. = U4 0 0 2 3 U4 LINK Target station-Nr. = U4 0 0 3 0 U1 0 U1 0 U1 0 U2 1 U2 1 U2 1 U2 1 U3 2 U3 2 U3 2 U3 2 FF 3 FF 3 FF 3 FF 3 FF 4 FF 4 FF 4 FF 4 FF 5 FF 5 FF 5 FF 5 FF 6 FF 6 FF 6 FF 6 Ax-1703 User data Ax-1703 User data Ax-1703 User data Ax-1703 User data LINK LINK LINK LINK LINK Target station-Nr. = U4 3 0 0 3 U1 3 LINK Target station-Nr. = U4 0 0 2 3 LINK Target station-Nr. = U4 0 0 1 3 LINK Target station-Nr. = U4 0 0 0 0 U3 0 U3 0 U3 0 U2 1 U2 1 U2 1 U2 1 U1 2 U1 2 U1 2 U1 2 FF 3 FF 3 FF 3 FF 3 FF 4 FF 4 FF 4 FF 4 FF 5 FF 5 FF 5 FF 5 FF 6 FF 6 FF 6 FF 6 Ax-1703 User data Ax-1703 User data Ax-1703 User data Ax-1703 User data LINK LINK LINK LINK Legende: Z ….…...…... Master station U1,U2, U3 ... Remote stations (serve as routing stations in this example) U4 ….....…... Adressed remote station ,,,….. Message direction: Master station Remote station ,,, ….. Message direction: Remote station Master station 4-36 3 U3 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.6.2.2. Optimized Routing Method With the "optimized routing method for relay operation" the routing information in messages is managed "dynamically". Station interrogations to remote terminal units that can be reached directly from the master station, contain no routing information (= message format with fixed block length). Such remote terminal units, if there are no data to be transmitted, reply with a single character or a short acknowledgement (no routing information in the message). Data are transmitted with the "message format with variable block length" and a "0-Routing Information". Station interrogations to remote terminal units that cannot be reached directly from the master station, contain only the routing information necessary (message format with variable block length). Such remote terminal units, if there are no data to be transmitted, reply with an acknowledgement message and the necessary routing information (message format with variable block length). Data are generally transmitted with the "message format with variable block length" and the necessary routing information. Example: Management of the routing information with 3 routing stations for "optimized routing method" Z U1 LINK 0 0 0 3 Target station Nr. = U4 3 U2 LINK Target station Nr. = U4 0 0 1 3 U3 LINK Target station Nr. = U4 0 0 2 3 U4 LINK Target station Nr. = 0 0 3 U1 0 U1 0 U1 0 U1 0 U2 1 U2 1 U2 1 U2 1 U3 2 U3 2 U3 2 U3 2 Ax-1703 User data Ax-1703 User data Ax-1703 User data Ax-1703 User data LINK LINK LINK LINK LINK Target station Nr. = U4 3 0 0 U4 3 3 LINK Target station Nr. = U4 0 0 2 3 LINK Target station Nr. = U4 0 0 1 3 LINK Target station Nr. = 0 0 0 U4 3 U3 0 U3 0 U3 0 U3 0 U2 1 U2 1 U2 1 U2 1 U1 2 U1 2 U1 2 U1 2 Ax-1703 User data Ax-1703 User data Ax-1703 User data Ax-1703 User data LINK LINK LINK LINK Legend: Z ….…...…... Master station U1,U2, U3 ... Remote stations (serve as routing stations in this example) U4 ….....…... Adressed remote station ,,,….. Message direction: Master station Remote station ,,, ….. Message direction: Remote station Master station Functions Protocol Elements DC0-023-2.01 4-37 Multi-Point Traffic (UMP) 4.7. Function for the Support of Redundant Communication Routes To increase the availability both master stations as well as remote terminal units can be designed redundant. In this chapter, the possible redundancy concepts themselves that can be realized are not described, rather only those functions for the support of redundant communication routes supported by the protocol element. In the master station and the remote terminal unit, with the parameter advanced parameters | project specific | Redundancy control one can select between the following redundancy controls: • • 4.7.1. 1703-Redundancy Norwegian User Conventions (NUC) Redundancy Mode "1703-Redundancy" The switchover of the redundancy state takes place system-internal through redundancy control messages. In the master station, in addition a delay for the switchover of the redundancy state from PASSIVE (=STANDBY) to ACTIVE can be set with the parameter Redundancy | Delay time passive=>active. The operating mode of the interface with redundancy state "PASSIVE" can be set according to the redundancy configuration with the parameter Redundancy | operation if passive as follows: • • • Interface "TRISTATE" – only listening mode Interface "ACTIVE" – only listening mode Interface "ACTIVE" – interrogation mode From the redundant, not active master / remote terminal unit, listened messages are passed on to the basic system element (BSE) and forwarded by this in the system with the identifier "passive" in the state. In redundant master stations that are not active, a failure of the interface is monitored globally and the failure of remote terminal units monitored station-selective. The failure of the interface is detected by the STANDBY master station by monitoring for cyclic message reception. The monitoring time is set with the parameter Redundancy | listening_mode (failure monitoring time). On receive timeout (active master station or transmission facility of the master station has failed) the interface is signaled as failed. The failure of a remote terminal unit is detected by the STANDBY master station through station-selective monitoring for cyclic message reception. On station-selective receive timeout (remote terminal unit or transmission facility of the remote terminal unit has failed) the remote terminal unit is signaled as failed. Station-specific pending faults are reset in a redundant STANDBY master station, if a fault-free message from the respective station is "listened". 4-38 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.7.2. Redundancy Mode "Norwegian User Conventions (NUC)" The redundancy mode "Norwegian User Conventions (NUC)" uses 2 communications lines (main/stand-by transmission line) from the master station (Controlling Station) to the remote terminal unit (Controlled Station). Each of these communications lines is fixed activated to a specific interface in the master station and in the remote terminal unit. The data are only transmitted to the active interface. The passive interface is only monitored by the master. The redundancy mode "Norwegian User Conventions (NUC)" is supported in the master station and in the remote terminal unit and selected with the parameter advanced parameters | project specific | Redundancy control. The operating mode of the interface with redundancy state "PASSIVE" is not to be parameterized for this redundancy mode. The function is defined by the "Norwegian User Conventions (NUC)". Redundancy function according to "Norwegian User Conventions (NUC)" for "unbalanced-Mode": • After startup of the Controlling Station, this starts the communication on both interfaces with the message "Request Status of Link". The Controlling Station decides which of the interfaces is to be switched to "ACTIVE" for the data transmission as main transmission line (Primary-Line). The other interface is used as standby transmission line and remains at "PASSIVE". • After startup of the remote terminal unit (Controlled Station), this waits for the initialization of the interfaces by the master station (Controlling Station) for the redundancy mode. After startup both interfaces are "PASSIVE". The remote terminal unit activates that interface on which the message "Reset of Remote Link" is received from the master station (Controlling Station) as main transmission line (Primary Line). • For monitoring the standby transmission line (Backup Line) the master station sends the message "Request Status of Link" cyclic. • With a communication failure on the main transmission line or with unintentional switchover to the standby transmission line, the Controlling Station sends a message "Reset of Remote Link" on the previous standby transmission line. With that the previous standby transmission line is now used as main transmission line (Primary Line). From now on, the Controlled Station is interrogated by the Controlling Station on the previous main transmission line with "Request Status of Link" and as a result monitored for failure (with "Request Status of Link" switchover to the standby transmission line takes place). • During the switchover from main transmission line-stand-by transmission line, no data loss must occur in the Controlled Station. Transmitted data may only be deleted in the remote terminal unit if these have been explicitly acknowledged by the master station. With switchover, no general interrogation is necessary. The SICAM 1703 master station performs the following functions with redundancy state "PASSIVE": • • • only "Request Status of Link" is sent – with that the failure of the remote terminal units is detected All data in command directions are discarded and not transmitted The interface is always electrically "ACTIVE" (and is not switched to "TRISTATE"). The master station monitors the standby transmission line by means of cyclic "Request Status of Link" messages. If a remote terminal unit no longer replies, on expiry of the number of retries this is reported as failed. As a result, a failure of the interface is monitored globally and the failure of remote terminal units is monitored station-selective. Functions Protocol Elements DC0-023-2.01 4-39 Multi-Point Traffic (UMP) In the SICAM 1703 remote terminal unit, for the redundancy mode "Norwegian User Conventions (NUC)" the LOAD-SHARE-Mode of the communications function must be used on the basic system element. With this mode the basic system element uses 2 fixed assigned interfaces for the transmission of the data from a process image. With the redundancy mode "Norwegian User Conventions (NUC)", data are only interrogated by the master station over the active interface. Through the LOAD-SHARE-Mode a switchover without loss of data is ensured – a doubling of data can occur under certain circumstances. In the remote terminal unit (Ax 1703) the assignment of the interfaces for main transmission line and stand-by transmission line is defined on a basic system element as follows: Note Interface 1 Main/Standby transmission line Interface 2 Main/Standby transmission line SSE = 128 SSE = 129 Redundant interface pair for NUC-Redundancy SSE = 130 SSE = 131 Redundant interface pair for NUC-Redundancy Legend: SSE = Supplementary system element (with serial interfaces, this is always configured with a PRE) The SICAM 1703 remote terminal unit performs the following functions with redundancy state "PASSIVE": • • • No data for emission are requested by the basic system element All data in signaling direction are transmitted over the active interface to the master station The interface is always electrically "ACTIVE" (and is not switched to "TRISTATE") After a restart of the remote terminal unit, for the redundancy mode "Norwegian User Conventions (NUC)" by default both interfaces are switched to "PASSIVE". The master station decides which interface of the remote terminal unit is to be operated as "ACTIVE". The switchover to "ACTIVE" takes place with the message "Reset of Remote Link". The switchover to "PASSIVE " takes place with the message "Request Status of Link". Hints: 4-40 • In the remote terminal unit the parameter advanced parameters | monitoring times | call timeout retrigger also with "request status of link" must be activated! • The message "Request Status of Link" from the master station on the "ACTIVE" interface may only be transmitted to failed remote terminal units. This message is used with NUC-Redundancy for the switchover to "PASSIVE". The message "Request Status of Link" is used with the station-selective clock synchronization of the 1703 master station for the acquisition of the transmission time. With NUC-Redundancy, the clock synchronization command may only be transmitted BROADCAST and not station-selective! DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.8. Message Conversion Data in transmit direction are transferred from the basic system element to the protocol element in the SICAM 1703 internal IEC 60870-5-101/104 format. These are converted by the protocol element to the IEC 60870-5-101 message format on the line and transmitted according to the transmission procedure of the protocol. Data in receive direction are converted by the protocol element from IEC 60870-5-101 format on the transmission line to a SICAM 1703 internal IEC 60870-5-101/104 format and transferred to the basic system element. 4.8.1. Blocking For the optimum utilization of the transmission paths, for the data transmission with IEC 60870-5-101 protocols the "Blocking" according to IEC 60870-5-101 is implemented. This function is performed on the basic system element (BSE) according to the rules applicable for this. Data to be transmitted are thereby already blocked on the basic system element and passed on to the protocol element for transmission. The blocking for data to be transmitted does not support the maximum possible message length according to IEC 60870-5-101! Received data in blocked format according to IEC 60870-5-101 are passed on from the protocol element to the basic system element in blocked format. On the basic system element the blocked data are split up again into individual information objects by the detailed routing function and passed on as such to the further processing. Received messages with maximum length are transmitted SICAM 1703 internal in 2 blocks to the basic system element (BSE) because of the additionally required transport information. The parameters necessary for the blocking are to be set on the basic system element (BSE) in the IEC 60870-5-101/104 parameter block. Functions Protocol Elements DC0-023-2.01 4-41 Multi-Point Traffic (UMP) 4.8.2. Class 1, 2 Data From the remote terminal unit in multi-point traffic, data are normally always transmitted for SICAM 1703 master stations as class 2 data. SICAM 1703 internal mechanisms for the prioritization of the data to be sent provide extensive options in order to be able to transmit important data to the master station. By enabling the parameter advanced parameters | IEC 60870-5-101 | prioritization of data "Class 1 data" and "Class 2 data" according to IEC 60870-5-101 are supported for transmission. On the basic system element the class 1 or class 2 data are to be assigned. The remote terminal unit reports to the master station with the ACD-Bit=1 in the control field of the message, that class 1 data are stored in the remote terminal unit for transmission. For this, on the protocol element a class 1 message is buffered until this is requested by the master station. Send ACTCON, ACTTERM, INIT-End as class 1 data The assignment of the messages ACTCON, ACTTERM and INIT-End to the data class 1 takes place on the protocol element. The enabling of the function is carried out on the protocol element by setting the parameter advanced parameters | IEC 60870-5-101 | prioritization of data to "Class 1,2". The other parameters for the assignment of the messages ACTCON, ACTTERM and INIT-End to the data class 1 are displayed on enabling the function. The assignment of the messages ACTCON, ACTTERM to data class 1 is carried out with the parameter advanced parameters | IEC 60870-5-101 | advanced parameters (prioritization of data) |prioritization of data, ACTCON, ACTTERM (TK 45-51, TK 101-107). The assignment of the message INIT-End to data class 1 is carried out with the parameter advanced parameters | IEC 60870-5-101 | advanced parameters (prioritization of data) | prioritization of data INIT-END (TI 70)"..I Required parameter settings on the basic system element: • 4-42 "Send Initialization End" must be enabled DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.8.3. Special Functions For the coupling to external systems, if necessary the following special functions can be activated for the adaptation of the message conversion: • • • • • • • • • • daylight-saving time bit (SU)=0 for all messages in transmit direction (daylight-saving time bit in the time stamp) Weekday (DOW)=0 for all messages in transmit direction (weekday in the time stamp) Originator address=0 for all messages in transmit direction Send GI-data as class 1 Timeout monitoring for GI-data Convert general interrogation command to BROADCAST in receive direction ACTCON for clock synchronization command Emulate ACTCON+/Emulate ACTCON for commands Message synchronization 4.8.3.1. Daylight-Saving Time Bit = 0 for all Messages in Transmit Direction With function enabled with the parameter advanced parameters | IEC60870-5-101 | time lag | summertime bit(SU) = 0 for all messages with time stamp in transmit direction the daylight-saving time bit (SU) is always set to 0 by the protocol element. 4.8.3.2. Weekday = 0 for all Messages in Transmit Direction With function enabled with the parameter advanced parameters | IEC60870-5-101 | time lag | Day of week (DOW) = 0 for all messages with time stamp in transmit direction the weekday (DOW) is always set to 0 by the protocol element. 4.8.3.3. Originator Address = 0 for all Messages in Transmit Direction With function enabled with the parameter advanced parameters | IEC60870-5-101 | originator address in transmit direction = 0 for all messages in transmit direction the originator address is always set to 0 by the protocol element. Note: The originator address (= 2nd byte of the cause of transmission) is only then sent if the number of octets for cause of transmission (COT) is set on the basic system element to 2. Functions Protocol Elements DC0-023-2.01 4-43 Multi-Point Traffic (UMP) 4.8.3.4. Send GI-Data as Class 1 With the coupling of remote terminal units to third-party systems it can be necessary to transmit all GI-data to the master station as class 1 data. For SICAM 1703 master stations, GI-data are always transmitted as class 2 data. With the parameter advanced parameters | IEC60870-5-101 | prioritization of data (GI-data) the protocol element of the remote terminal unit is instructed to transmit GI-data that are to be transmitted to the master station as reply to a general interrogation command with the set priority (class 1 or class 2), regardless of the SICAM 1703 internal parameter setting. 4.8.3.5. Timeout Monitoring for GI-Data With parameter advanced parameters | IEC60870-5-101 | Monitoring time for GI-data enabled, all data following a general interrogation command are to be transmitted from the protocol element of the remote terminal unit to the master station as class 1 data. A timeout is thereby started with the message "ACTCON for general interrogation command" and retriggered with each message with the cause of transmission "interrogated by station interrogation" or "background scan". As long as the timeout is running, all data are transmitted to the master station as class 1 data regardless of their cause of transmission. This procedure for class 1 data does not conform to IEC 60870-5-101 and is thus only to be implemented when coupling to master stations which specifically require this procedure! 4.8.3.6. Convert General Interrogation Command to BROADCAST in Receive Direction With the parameter advanced parameters | IEC60870-5-101 | GI command "broadcast" enabled, all general interrogation commands <TK=100> received by the protocol element of the remote terminal unit are transferred to the basic system element from the transmission line with the "cause of transmission = activation" with the address CASDU = BROADCAST. 4.8.3.7. Emulate ACTCON+ for Clock Synchronization Command The transmission of ACTCON+ by the remote terminal unit for the clock synchronization can be set with the parameter advanced parameters | IEC60870-5-101 | ACTCON for clock sychronization command as follows: • • • • 4-44 Do not send (=default) Send immediately Send after minute change and internal transfer of the time (DEFAULT) Send immediately and ignore (do not accept clock synchronization command) DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.8.3.8. Emulate ACTCON+/- for Commands If ACTCON is not supported by the basic system element or by the peripheral element used, then the emulation of ACTCON can be performed by the protocol element (PRE) of the remote terminal unit as follows: Emulation of Note ACTCON- for <TK=45> single command <TK=46> double command <TK=47> regulating step command <TK=48> setpoint command, normalized value <TK=49> setpoint command, scaled value <TK=50> setpoint command, floating point number ACTCON- send immediately from PRE if * CASDU is not known to the PRE ACTCON+/- from BSE or PE is sent from PRE ACTCON- for <TK=100> (general-) interrogation command ACTCON- send immediately from PRE if * CASDU is not known to the PRE and * CASDU <> FFFF (=BROADCAST) ACTCON+/- from BSE is sent from PRE ACTCON+/- for <TK=101> counter interrogation command ACTCON+ send immediately from PRE if * CASDU is known to the PRE or * CASDU = FFFF (=BROADCAST) ACTCON- send immediately from PRE if * CASDU is not known to the PRE ACTCON+/- for <TK=103> clock synchronization command if ACTCON+ send from PRE if * CASDU = FFFF (=BROADCAST) **) ACTCON- send immediately from PRE if * CASDU <> FFFF (=BROADCAST) Legend: BSE ....... Basic system element PRE....... Protocol element PE ......... Protocol element **) The moment for the transmission of ACTCON+ in the remote terminal unit can be parameterized with the parameter advanced parameters | IEC60870-5-101 | ACTCON for clock sychronization command. The emulation of ACTCON in the remote terminal unit can be activated on the protocol element with the parameter advanced parameters | IEC60870-5-101 | ACTCON +/- emulation. So that the emulation can be performed by the protocol element, it must be ensured that the INIT-End messages are passed on from the basic system element to the protocol element (required because of the known CASDU addresses). The parameter setting necessary is to be performed on the basic system element (BSE) in the IEC 60870-5-101/104 parameter block. Functions Protocol Elements DC0-023-2.01 4-45 Multi-Point Traffic (UMP) 4.8.3.9. Emulate ACTCON+ for Commands If ACTCON for commands is not supported by the peripherals element used, then the emulation of ACTCON messages can be performed by the protocol element of the remote terminal unit as follows: Emulation of ACTCON+ Note for <TK=45> single command <TK=46> double command <TK=47> regulating step command ACTCON+ from PRE send immediately (for SELECT and EXECUTE command) ACTCON+/- from BSE is filtered out by PRE and not sent! ACTTERM+/- from BSE is sent from PRE The emulation of ACTCON for commands in the remote terminal unit can be activated on the protocol element with the parameter advanced parameters | IEC60870-5-101 | ACTCON emulation. With function activated, ACTCON messages are emulated by the protocol element as shown in the table. All ACTCON+/- messages that are transferred from the basic system element to the protocol element are filtered out by the protocol element and therefore not transmitted. ACTTERM messages that are transferred from the basic system element to the protocol element are transmitted by the protocol element. With function not activated, ACTCON and ACTTERM messages that are transferred from the basic system element to the protocol element are transmitted by the protocol element, no emulation of any kind by the protocol element takes place. Note: This function is not required in ACP 1703 or if the this function is supported by the peripheral elements used! For the emulation of ACTCON- with unknown CASDU, the parameter advanced parameters | IEC60870-5101 | ACTCON +/- emulation is to be enabled. 4.8.3.10. Message Synchronization With the parameter advanced parameters | IEC60870-5-101 | message synchronization one can select between the following methods of synchronization for disturbed reception: Standard (IEC 60870-5-1) Received byte sequences "68,X,Y" (without gaps between the bytes): If X <> Y Message synchronization after a pause (> 33 Bit Idle) 4-46 DC0-023-2.01 Mode-A (68 xx yy) Received byte sequences "68,X,Y" (without gaps between the bytes): If X <> Y The receiver must discard 68 and begin with the IEC message check from X. (without pause > 33 Bit Idle) Functions Protocol Elements Multi-Point Traffic (UMP) 4.9. Transparent Mode (Tunneling) The Transparent Mode (or Container Mode) is used to pass through external computer messages in IEC 60870-5101 format between a remote station and a third-party control system that is connected to the SICAM 1703 component with IEC 60870-5-104. The container mode thus provides a "tunneling method" within the system SICAM 1703. These external computer messages are transmitted to or received from an external control system in a user data container defined for SICAM 1703 in the private range of the IEC 60870-5-101. The user data container is then not sent to the remote terminal unit, rather the IEC 60870-5-101 message contained in the message data of the user data container. As a result either message formats in the public or private range of the IEC 60870-5-101 standard not supported by the System SICAM 1703 can be transmitted from a third-party remote terminal unit to a third-party control system or all messages according to IEC 60870-5-101 which do not need to be routed individually when using the container mode in the System SICAM 1703. In container mode only the user data messages are transmitted transparently through the SICAM 1703 network – messages for protocol control (station initialization, station interrogation, acknowledgement messages,...) are not transmitted and are dealt with directly on the interface to the external remote terminal unit by the protocol element for the master station. With special procedures (e.g.: remote parameterization of a third-party remote terminal unit by a third-party control system), before using the container mode it is to be checked whether the changed chronological behavior will be tolerated by the connected third-party systems and that no error messages or failures occur as a result. The transmission of the user data container within the System SICAM 1703 takes place with type identification <TI=142> in the private range of IEC 60870-5-101 or IEC 60870-5-104 respectively. SICAM 1703 internal, several modes are provided for the use of the user data container. The container mode uses the user data container with message type = 128 (=SAT Standard-Format). The container mode can be activated separately for transmit / receive direction with the parameter advanced parameters | project specific | Container mode in transmit direction and the parameter advanced parameters | project specific | Container mode in receive direction. With container mode activated in receive direction, all valid received messages from the third-party system are entered in a user data container and passed on from the protocol element to the basic system element (BSE) for further distribution within the system. With container mode activated in transmit direction, data to be are transferred from the basic system element (BSE) to the protocol element in a "user data container <TI=142> and message type = 128“, read out from the user data container and the message data sent to the third-party system. All other data passed on from the basic system element (BSE) to the protocol element for transmission are sent unchanged to the third-party system. The IEC-address of the user data container is fixed defined and is not to be parameterized. (CASDU = CASDU of the remote terminal unit; IOA1, IOA2 = 255; IOA3 = 191) Functions Protocol Elements DC0-023-2.01 4-47 Multi-Point Traffic (UMP) Segmentation With user data containers a maximum of 180 bytes of transparent message data can be transmitted. Longer external computer messages (max. 256 bytes) are thus to be transmitted in several part segments and grouped together again before transmission/processing. With missing segments the partially transmitted parameter message is discarded. The transparent mode only utilizes part segments with a max. length of 50 bytes of message data! User data container <TI=142> The user data container is used to pass through external computer messages. 27 26 25 24 23 22 21 20 142 SQ T Type identification 1 P/N variable structure qualifier Cause of transmission Cause of transmission Originator address CASDU1 CASDU2 IOA1 IOA2 IOA3 : : : : : : : : : : : : : : : : : : : : : : : : 7 bytes dual time (IEC 60870-5-101) Length of user data in bytes **) 128 Message type = 128 45 UEK = 45 S=1 I=0 State Number of bytes *) Interface number (process channel) Sum of the segments = 1 Current segment number = 1 Segment information 22 Protocol type = 22 (=IEC 60870-5-101) 0 Reserve Length of the message data in Bits (LSB) Length of the message data in Bits (MSB) 0 0 0 0 : : : : : : : : : : : : Function : : : : : : : : : Message data (0) : : : : : : Message data (n) max. 50 bytes *) Number of bytes of the message data + 6 (max. 56 bytes) **) **) Length of the user data from the field UEK up to the last byte of the message data (n) Note: 4-48 The user data container is described here in the internal format of the protocol element with the essential information fields. DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) Elements of the Message TI .. type identification <TI=142> User data container CASDU, IOA .. Message address O1 .. Octet 1 (CASDU) CASDU = CASDU of the remote terminal unit O2 .. Octet 2 (CASDU) CASDU = CASDU of the remote terminal unit IOA1 .. = 255 IOA2 .. = 255 IOA3 .. = 191 (subaddress) Cause of transmission 03 .. spontaneous ... in monitoring direction 06 .. activation ... in control direction Time 7 octets dual time Earliest possible acquisition moment of a message in AK 1703, time tag on the basic system element (BSE) Message type = 128 Length of the user data part in octets Length of the user data in octets (exclusive message type) Number of bytes Number of bytes of the message data + 6 Segmentation field Total number of segments Total number of segments (4 Bit) ... Total size = 15 segments each of 50 octets Current segment number Current number of the transmitted segments (4 Bit) ... the 1st segment has segment number 1 Length of the message data in bit in all segments the total length of the message data is always transmitted in bit. Structure of the message data: 27 26 25 24 0 0 0 0 23 22 21 Function 20 Control Byte Link address Data (0) : : Data (n) Elements of the Message Control byte "Function" (Bit 0-3) 03 .. User data SEND / CONFIRM 04 .. User data SEND / NO REPLY Link address Functions Protocol Elements The length of the link address to be sent is determined with a parameter. DC0-023-2.01 4-49 Multi-Point Traffic (UMP) 4.10. Protocol Element Control and Return Information This function is used for the user-specific influencing of the functions of the protocol elements. This function contains two separate independent parts: • Protocol element control • Protocol element return information The Protocol Element Control enables: • Applicational control of the station interrogation • Setting control location • Testing the reachability of stations • the suppression of errors with intentionally switched-off stations (Station Service) The Protocol Element Return Information enables: • States of certain state lines to be used as process information • the obtaining of station interrogation information • the obtaining of information about the route state/failure of main/standby transmission line • Information about the station status/failure to be obtained Internal distribution for messages with process information Block Diagram Protocol element control Internal function Transmission route Protocol element return information Protocol element Messages with process information Messages with system information 4-50 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.10.1. Protocol Element Control With the help of messages with process information, the protocol element control on the basic system element enables specific functions of the protocol elements to be controlled. The specific functions are determined by the protocol element implemented. The assignment of the messages with process information to the functions is carried out with the help of processtechnical parameters of the ACP 1703 system data protocol element control message. The messages for protocol control are transmitted immediately from the basic system element to the protocol element, regardless of the user data to be sent and the priority control. For messages with process information which are used in ACP 1703 as protocol element control message, an unused CASDU is to be used! All CASDU´s for process information are distributed automatically to the corresponding remote terminal unit. Possible master station functions: Parameter Function SF Station Z-Par Call cycle START 0 125 - Call cycle STOP (disabling) 1 125 - Call cycle CONTINUE (enabling) 2 125 - Continuous call station x ON 3 0 – 99 065535 Continuous call station x OFF 4 0 – 99 - Main transmission line ACTIVE 5 0 – 99 - Standby transmission line ACTIVE 6 0 – 99 - Add station to station polling 128 0 – 99 - Remove station from station polling 129 0 – 99 0,1 Note Z-Par=continuous call time (n * 100ms) Z-Par=0: Continuous call without time input (stopped by other function) only parameterized RTUs can be added to the station polling. otherwise error "faulty PST-control message" only parameterized RTUs can be removed from the station polling. otherwise error "faulty PST-control message" Z-Par=0: Reset present station fault Z-Par=1: Do not change present station fault Send (general) interrogation command 240 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Send (general) interrogation command to GI-group 241 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Functions Protocol Elements DC0-023-2.01 4-51 Multi-Point Traffic (UMP) Possible master station functions: (continued) Parameter Function **) Set control location Reset command Legend: SF **) Station Z-Par 125 65535 SCS=<ON>: Set control location (HKA) (global) SCS=<OFF>: Delete all control locations (HKA's) (global) 0 – 99 65535 SCS=<ON>: Set control location (HKA) SCS=<OFF>: Reset control location (HKA) 242 Note 243 This function is not presently supported by PRE! SF ............. Control function_(PRE) Station....... Station number 0 - 99 ......Station 0 - 99 of the selected protocol element 125 .........Station 0 - 99 of the selected protocol element (=BROADCAST) Z-Par......... Additional parameter_(PRE) SCS .......... single command state HKA .......... Originator address (HKA) = 0 – 255 The setting of the control location can only be performed with a single command <TK=45>! In the PRE-control message to the protocol element the additional parameter is set as follows. SCS = <OFF>........... Additional parameter = HKA+256 SCS = <ON> ............ Additional parameter = HKA **) If a PRE-control message is entered in the PST-detailed routing on the BSE, after startup of the PRE the BSE sends a PRE-control message "Set control location" to the PRE. As a result the function for evaluating the control location is activated on the PRE. Possible remote terminal unit functions: Parameter Function SF Station Z-Par Note I – Bit handling for time "OFF" 0 - - (1) I – Bit handling for time "ON" 1 - - (1) Send (general) interrogation command 240 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Send (general) interrogation command to GI-group 241 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Reset command 243 This function is not presently supported by PRE! Legend: SF ............. Control function_(PRE) Station....... Station number Z-Par......... Additional parameter_(PRE) (1) The protocol element stores the moment/state for the last received PRE-control message "I – Bit handling for time ON / OFF" (=ti/e/a) from basic system element. For all messages with process information with time stamp in transmit direction, the Invalid-Bit of the time stamp is set by the protocol element, if the time in the message is the same or after the moment ti/e. For all messages with process information with time stamp in transmit direction, the Invalid-Bit of the time stamp is reset by the protocol element, if the time in the message is the same or after the moment ti/a. 4-52 DC0-023-2.01 Functions Protocol Elements Multi-Point Traffic (UMP) 4.10.2. Protocol Element Return Information The protocol element return information on the basic system element generates messages with process information in monitor direction and thereby enables states of the protocol elements to be displayed or processed. There are three different categories of return information: • • • Status of the state lines Status of the stations Protocol-specific return information (dependent on the protocol element used) The assignment of the messages with process information to the return information is carried out on the basic system element with the help of process-technical parameters of the ACP 1703 system data protocol element return information. From which source the parameterized return information are to be generated, is set with the parameters "Supplementary system element" and "Station number". Messages for protocol element return information are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. Possible master station return information: Parameter Return information function_(PRE) Station Note Status DTR (1 = state line active) 255 (1) Status DSR (1 = state line active) 255 (1) Station status 0 – 99 1 = Station enabled for call cycle Station failure 0 – 99 1 = Station failed (1) States of the state lines are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. The spontaneous transmission of the current states takes place internally in a 100ms grid. State line changes shorter than 100ms are not guaranteed to be transmitted! Functions Protocol Elements DC0-023-2.01 4-53 Multi-Point Traffic (UMP) Possible master station return information (continued): Parameter Return information function_(PRE) Station protocol-specific return information 0 0 – 99 Main transmission line parameterized protocol-specific return information 1 0 – 99 Main transmission line OK protocol-specific return information 2 0 – 99 Main transmission line faulty protocol-specific return information 3 0 – 99 Main transmission line NOK protocol-specific return information 8 0 – 99 Standby transmission line parameterized protocol-specific return information 9 0 – 99 Standby transmission line OK protocol-specific return information 10 0 – 99 Standby transmission line faulty protocol-specific return information 11 0 – 99 Standby transmission line NOK protocol-specific return information 0 255 Cycle IDLE - cycle control is stopped. User data messages will be sent furthermore. protocol-specific return information 1 255 Cycle NORMAL MODE - cycle control running in normal mode (cyclic RTU interrogation) protocol-specific return information 2 255 Continuous call - Continuous call of an RTU presently running protocol-specific return information 3 255 Cycle stopped - cycle has been stopped with PST – control message protocol-specific return information 6 255 Sending "Data to all" - User data message "to all" (BROADCAST) is now being transmitted protocol-specific return information 7 255 Sending "data message" - station-selective user data message is now being transmitted Legend: Note Station....... Station number 0 - 99 ......Station 0-99 of the selected protocol element 255 .........Station number not used! Possible remote terminal unit return information: Parameter Return information function_(PRE) Station Status DTR (1 = state line active) 255 (1) Status DSR (1 = state line active) 255 (1) Station failure 0 Note 1 = Station failed (1) States of the state lines are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. The spontaneous transmission of the current states takes place internally in a 100ms grid. State line changes shorter than 100ms are not guaranteed to be transmitted! 4-54 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5. Interfacing of Protective Devices (103) For the interfacing of digital protective devices or protective devices according to IEC 60870-5-103, a serial communications protocol is implemented for multi-point traffic, with which one master station is connected with one or several protective devices (remote terminal units) over a communication link in a linear or star configuration. The data traffic is controlled by the master station. Either data messages or station interrogation messages are transmitted from the master station. Data from the remote terminal unit to the master station can only be transmitted as reply to a station interrogation. Master station TF TF TF TF Remote station-1 Remote station-2 Remote station-n n <= 100 Legende: TF ………..….. Transmission Facility In multi-point traffic an "unbalanced transmission procedure" is used. That means, that as primary station the master station initiates all message transmissions, while the remote terminal units, which are secondary stations, may only transmit when they are called. The multi-point traffic only requires a "half duplex" transmission medium and can be used in a star or linear structure. The master station and the remote terminal units in multi-point traffic function with a communications protocol according to IEC 60870-5-103. The supported functionality (Interoperability) is shown in the document ACP 1703 Interoperability IEC 60870-5-103 (DC0-025-1) or in the document Ax 1703 Interoperability IEC 60870-5-103 (DA0-072-1) respectively. Functions Protocol Elements DC0-023-2.01 5-1 Interfacing of Portective Devices (103) General Functions Communication between one central station and one or more remote protective devices • Unbalanced multi-point (multi-point traffic) according to IEC 60870-5-103 103Mxx is controlling station (primary station), 103Sxx / protective device is controlled station (secondary station). ─ Supported functionality according to − ACP 1703 Interoperability IEC 60870-5-103 (DC0-026-1) − Ax 1703 Interoperability IEC 60870-5-103 (DA0-063-1) ─ ─ ─ ─ Data acquisition by polling (station interrogation) Acquisition of events (transmission of data ready to be sent) General interrogation, outstation interrogation Clock synchronization − Cyclic, can be set in a seconds grid ─ Command transmission − Set control location, control location check ─ File transfer − Disturbance records to SICAM DISTO − Disturbance records to control centre systems according to IEC 60870-5-101/104 ─ Generic functions ─ Acquisition of transmission delay (for the correction of time synchronisation) 5-2 • Resetting the short-circuit location values • Measured value change monitoring • Monitoring intermediate and faulty positions of double-point information • Transmission of parameters and diagnostic information for Reyrolle protection equipment (Embedded REYDISP) • Optimized parameters for selected transmission facilities • Functions for supporting redundant communication routes • Special functions • Message conversion – IEC 60870-5-101 IEC 60870-5-103 – IEC 60870-5-101 – IEC 60870-5-101 IEC 60870-5-103 "Container Mode" DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) The operating mode of the interface is determined by parameters and optional equipment. Standard Operation Mode Unbalanced interchange circuit V.24/V.28 Extras 1) Interface Signals on RJ45 Connector --- RXD, TXD, CTS, RTS, DCD, DTR, DSR/+5V, GND V.28 asynchronous Optional Operation Mode Balanced interface RS-485 Extras 1) Interface Signals on RJ45 Connector CM-0829 RXD, TXD, CTS, RTS, DCD, DTR, DSR/+5V, GND CM-0827 RXD, TXD, +5V, GND V.11 asynchronous with CM-0829 Optical interface (multimode fibre optic) with CM-0827 1) Extras are optional equipment Functions Protocol Elements DC0-023-2.01 5-3 Interfacing of Portective Devices (103) 5.1. Communication according to IEC 60870-5-103 5.1.1. Data Acquisition by Polling (Station Interrogation) The transmission of the data from the remote terminal units to the master station takes place by means of stationselective station interrogations (interrogation procedure, polling), controlled by the master station; i.e., changed data are stored in the remote terminal unit and transmitted to the master station with the interrogation of this remote terminal unit. The interrogation procedure of the master station ensures, that remote terminal units are interrogated sequentially, whereby remote terminal units with important data can be interrogated more often. Remote terminal units may only transmit when they are called. The interrogation procedure can be influenced with the following parameters: • • • • • Continuous cycle Existing stations Number of calls until station change Number of stations to be called until change of priority level Priority level assignment (each station is assigned one of the 4 priority levels: high priority, medium priority, low priority-A, low priority-B) The interrogation procedure can be performed either continuously (= continuous cycle) or only on request. The continuous interrogation of the remote terminal units by the master station interrogation procedure is to be performed by enabling the parameter advanced parameters | continuous cycle. The station-selective parameters of the master station for the interrogation cycle such as "Stat No", "Link Address", "Station Enabling", "Station failure", "Priority Level", "Number of calls", “Block of class 2 data” are to be set in the parameter Station definition. In every remote terminal unit, the station-selective address must be set with the parameter Common settings | Address of the link. This address must be unambiguous for each multi-point traffic line. For IEC 60870-5-103 the number of octets for the "Address field of the link layer" is defined with 1 octet. The prioritization of the station interrogation can be parameterized by means of corresponding parameter setting of the number of stations called until level change with the following parameters: • • • • Station Station Station Station call call call call prioritization prioritization prioritization prioritization | | | | No. No. No. No. of of of of stat. stat. stat. stat. calls calls calls calls in in in in high priority lvl mid. priority lvl low prior. lvl (A) low prior. lvl (B) Through parameterization of the interrogation procedure the following characteristics can be achieved: • • • A remote terminal unit which has a lot of data to send - e.g. continuously changing measured values – does not impair the disposal of the data of the other remote terminal units. Each remote terminal unit is interrogated within a determinable time (deterministic). Remote terminal units with important data or those with a large volume of data to be transmitted can be interrogated more frequently than the others. The interrogation procedure can be performed either continuously (= continuous cycle) or only on request. The control of the interrogation procedure on request can be realized with protocol control messages in the function diagram. 5-4 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) In the running interrogation cycle, data and system messages are transmitted spontaneously from the master station according to the parameter setting as follows: • • One RTU selective (acknowledged) All RTU’s (unacknowledged) If the interrogation cycle has been stopped by protocol control messages or the listening mode is switched on, no station interrogation takes place. With the interrogation cycle stopped, spontaneous data messages continue to be transmitted to the remote terminal units. With listening mode switched on, the messages are normally not transmitted from the master station to the remote terminal units, rather discarded directly on the basic system element (BSE) by the function "User data filter". Example: Prioritization of the station interrogation Below the prioritization of the station interrogation for continuous cycle is shown based on the specified parameters as an example. Parameter for "Station call prioritization" High priority level ...................... Number of stations called until level change = 2 Medium priority level................. Number of stations called until level change = 2 Low priority level (A) ................. Number of stations called until level change = 1 Low priority level (B) ................. Number of stations called until level change = 1 Station U0, U4 .......................... High priority level / Number of calls until station change = 2 Station U1,U2,U3...................... Medium priority level / Number of calls until station change = 2 Station U5,U6,U7, U8 ............... Low priority level (A) / Number of calls until station change = 1 Station U9,U10 ......................... Low priority level (B) / Number of calls until station change = 1 t Z U0 U1 U2 U3 U4 U5 U6 U7 U8 U9 U9 U10 U10 Legend: …..….. Remote station in the „High priority level“ …..….. Remote station in the „Medium priority level“ …..….. Remote station in the „Low priority level (A)“ U10 …..….. Remote station in the „Low priority level (B)“ ,..…...….. Data message, short acknowledgement (remote station master station) ,…..….. Data message (Command), calling message (remote station master station) Z ………….….. Master station U0..U10 ….….. Remote station U0 .. Remote station U10 …………….. Command from master station remote station U0 t ………………. Continous station polling time (request) from remote station U0 (after command from master station remote station U0) Functions Protocol Elements DC0-023-2.01 5-5 Interfacing of Portective Devices (103) For the interfacing of protection equipment with the protocol IEC 60870-5-103, no variable elements of the message are provided. Description IEC 60870-5-103 Number of octets for the address field of the link layer 1 Octet Number of octets for cause of transmission 1 Octet Number of octets for common address of the ASDU 1 Octet ASDU is identical with address of link layer (=station address) Number of octets for the address of the information object 2 Octets IOA1 = Function type IOA2 = Information number Acknowledgement message Single character or short message (ACK) Number of octets for time stamp 5-6 Note 4 Octets DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.1.1.1. Continuous Interrogation of a Remote Terminal Unit The "continuous interrogation of a remote terminal unit" can be switched on automatically in the master station with the function "Demand" or spontaneously with protocol control messages. With function activated, a station interrogation is always executed by the master station to only one selected station. An automatically started continuous interrogation of one remote terminal following a message transmission is known as a demand. Through a demand, following a message transmission (e.g. command, setpoint value) the master station can quickly fetch changed data from the remote terminal unit (e.g. measured values after command or setpoint value). With demand, the continuous interrogation of a remote terminal unit is terminated after timeout or a message to another remote terminal unit. With control of the interrogation procedure with protocol control messages, the continuous interrogation of a remote terminal unit can be terminated spontaneously through a corresponding protocol control message. With "continuous interrogation of a remote terminal unit" data messages continue to be transmitted to that remote terminal unit to which the function "continuous interrogation of a station" is switched on. 5.1.1.2. Acknowledgement Procedure All data messages transmitted selectively to a remote terminal unit must be acknowledged by this RTU. If, with nonfaulty transmission line, the acknowledgement is missing for longer than the expected acknowledgement time, transmitted messages are repeated up to n-times (n can be parameterized). On expiry of the number of retries, the station is flagged as faulty. The required expected acknowledgement time is determined automatically from the set parameters, but if necessary can be extended accordingly with the parameter advanced parameters | monitoring times | expected_ack_time_corr_factor. This is then the case if additional signal propagation delays, delay times or slow processing times of the connected remote terminal units must be taken into consideration. The number of retries is to be set in the master station for messages for station interrogation and data messages with the parameter Message retries | Retries for data message SEND/CONFIRM (station selective) or for messages for station initialization with the parameter Message retries | Retries for INIT-messages SEND/CONFIRM (station selective). The acknowledgement from the remote terminal unit to the master station is transmitted as single character (E5), if no additional information (DCF / ACD-Bit) is to be transmitted. If additional information is to be transmitted, the acknowledgement is transmitted as message with fixed length (ACK). Functions Protocol Elements DC0-023-2.01 5-7 Interfacing of Portective Devices (103) 5.1.1.3. Failure Monitoring in the Master Station The monitoring of the interface by the active master station takes place by means of the cyclic running interrogation procedure (station interrogation). A remote terminal unit is reported as failed by the master station after expiry of the number of retries. Retries to a remote terminal unit are thereby always sent in succession immediately after expiry of the expected acknowledgement time i.e. no other remote terminal units are interrogated during a running retry handling. For failed remote terminal units, a communication fault is only then reported, if this is parameterized accordingly in the parameter Station definition | station failure. The failure of remote terminal units is thus detected by the master station during the normal interrogation cycle. Failed remote terminal units continue to be interrogated by the master station with the interrogation procedure, however no message retry is performed for such remote terminal units during the station interrogation. The interrogation cycle for failed stations can be set with the parameter advanced parameters | IECParameter | polling cycle for faulty stations. As a result, failed remote terminal units are removed from the running interrogation procedure for a certain time and from then are only interrogated in the parameterized grid. No data are transmitted from the master station to failed remote terminal units. The data are stored in the data storage of the communication function on the basic system element (BSE) until these are deleted by the dwell time monitoring or are transmitted to the non-failed remote terminal unit. 5.1.1.4. Failure Monitoring in the Remote Terminal Unit The monitoring of the interface in the remote terminal unit is carried out by monitoring for "cyclic station interrogation". The monitoring time is to be set in the remote terminal unit with the parameter advanced parameters | call monitoring time. The monitoring time in the remote terminal unit must be set sufficiently high, so that this does not expire unintentionally during the transmission of larger quantities of data from other remote terminal units (e.g. during general interrogation). With failed interface, data to be transmitted are stored in the data storage on the basic system element (BSE) of the remote terminal unit until these are deleted by the dwell time monitoring or can be transmitted to the master station. 5-8 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.1.2. Station Initialization The communication with a protective device (remote terminal unit) can only be started after successfully executed station initialization. A distinction is made between a reset of the protection equipment itself and a reset of the communications function of the protective device. The transmission procedure can be set in the remote terminal unit with the parameter Common settings | operating mode of the interface. The corresponding station initialization is selected by means of the selected operating mode. Operating mode of the interface: IEC 60870-5-103, IEC 60870-5-103 (101) A reset of the communications function in the protective device (remote terminal unit) is triggered from the master station by sending a Reset-command. This is generally sent from the master station, if, • • the master station is being initialized (reset or redundancy switchover) the protective device (remote terminal unit) does not reply within a defined time (reset or interface fault) The reset command does not influence the protection function itself, rather only resets the communications part of the protective device. The reset command can be transmitted as, • • Reset of frame count bit (FCB) or Reset of communications unit (KE) After a reset of the master station, the station initialization is always performed with the reset command "Reset of KE". After redundancy switchover or with station failure, remote terminal units are initialized with the reset command "Reset FCB". If the remote terminal unit does not react within a settable time, then the corresponding remote terminal unit is initialized with the reset command "Reset KE". The time for the switchover of the station initialization can be set with the parameter advanced parameters | station initialization timeout. Reset Command Reset KE Reset FCB Functions Protocol Elements Function in the Remote Terminal Unit - FCB-Bit (Frame Count Bit) is initialized - Transmit buffer + process image (SSE+BSE) is deleted - FCB-Bit (Frame Count Bit) is initialized DC0-023-2.01 5-9 Interfacing of Portective Devices (103) Operating mode of the interface: IEC 60870-5-101 If the message conversion mode "IEC 60870-5-101" is parameterized in the SICAM 1703 remote terminal unit, the station initialization takes place according to IEC 60870-5-101. After startup or redundancy switchover, the operation of the interface is begun after successful station initialization. The initialization of the link layer of the remote terminal unit is performed by the master station with: • • "Request for the status of the link layer (REQUEST STATUS OF LINK) Reset of the remote terminal unit link layer (RESET OF REMOTE LINK) Reset Command Function in the Remote Terminal Unit REQUEST STATUS OF LINK - "STATUS OF LINK" is transmitted to the master station RESET of REMOTE LINK - FCB-Bit (Frame Count Bit) is initialized - Acknowledgement for RESET of REMOTE LINK is transmitted to master station Initialization End If "Send Initialization End" is enabled on the basic system element in the IEC 60870-5-101/104 parameter block, after the station initialization is performed, data are only sent from the protocol element if the "INIT-End" has been received from the basic system element for the corresponding ASDU. "<TI=70> Initialization End" is also transmitted to the remote station. The clock synchronization command or general interrogation command may only be transmitted after "INIT-End". 5-10 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.1.3. Acquisition of Events (transmission of data ready to be sent) Data of the remote terminal unit ready to be sent are stored on the basic system element (BSE) in the remote terminal unit until transmission. See also chapter "Data Acquisition by Polling (Station Interrogation)". 5.1.3.1. Message from the Remote Terminal Unit to the Master Station Messages from the remote terminal unit to the master station are only transmitted with station interrogation. A quick-check procedure for speeding up the transmission of data is not implemented. 5.1.3.2. Test Mode In the mode "Test Mode" spontaneous binary information and cyclic measured values are identified in the protective device for the further processing in the control system by means of the cause of transmission "Test Mode". That means, that message that are normally transmitted with cause of transmission "spontaneous" or "cyclic" are transmitted with the cause of transmission "Test Mode". Messages that are transmitted from the remote terminal unit to the master station with cause of transmission "Test Mode" can be discarded by the protocol element of the master function (filtered out) or transferred to the basic system element for further distribution/processing. The handling of the data with cause of transmission "Test Mode" can be set on the protocol element of the master station with the parameter Station definition | test mode. (when using the protocol firmware on SMx551 this parameter is part of the station definition) Functions Protocol Elements DC0-023-2.01 5-11 Interfacing of Portective Devices (103) 5.1.4. General Interrogation, Outstation Interrogation The general interrogation (outstation interrogation) function is used to update the master station after the internal station initialization or after the master station has detected a loss of information. The general interrogation function of the master station requests the remote terminal unit to transmit the actual values of the process variables subject to GI. A general interrogation command "to all" triggered in the system is always transferred from the communications function on the basic system element (BSE) station-selective to the protocol element of the master station and also transmitted station-selective by this to the remote terminal units with "CASDU = BROADCAST". Some protective devices cannot immediately process a general interrogation command in certain situations (e.g. after startup, going interface fault or station initialization). Often, the general interrogation command is then only received by the protection equipment after the transmission of the identification information or after successful clock synchronization. For configurations with such protection equipment, a solution for this problem can be offered with the parameter advanced parameters | send initiation of general interrogation after delay. If generic data are used, this function is to be enabled with the parameter advanced parameters | generic data. With function enabled, a "general interrogation command" triggered in the system is also transmitted as "GIcommand for Generic Data" to the corresponding remote terminal unit. (See also in chapter Message Conversion "Generic Data".) 5-12 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.1.5. Clock Synchronization Setting the time The clock synchronization command is transmitted spontaneously from the protocol element of the master station to the remote terminal units after startup or with a change of the time always BROADCAST (as SEND/NO REPLY service). Messages that are transmitted after a startup, but before the remote terminal unit has the correct time, contain the relative time from startup (reference day: 1.1.2001) with the flagging of the time stamp as invalid. Note: For IEC 60870-5-103 no acquisition of the transmission time is provided! Remote Synchronization The clock synchronization of the remote terminal units can be performed over the serial communication line – controlled by the master station. The clock synchronization is performed cyclic by the master station. The time-scale can be set with the parameter advanced parameters | cycle time for sending clock synchronization command. For the remote synchronization a clock synchronization command is generated by the protocol element itself and sent cyclic to the remote terminal units. The typical accuracy achieved through this is ± 20 ms. If the accuracy of the remote synchronization is insufficient, a local time signal receiver must be used in the remote terminal unit. Functions Protocol Elements DC0-023-2.01 5-13 Interfacing of Portective Devices (103) 5.1.6. Command Transmission 5.1.6.1. Message from the Master Station selectively to a Remote Terminal Unit Station-selective data messages in command direction are always inserted into the running interrogation procedure (station interrogation) by the master station with high priority after termination of the data transmission in progress. Data to be sent from the basic system element (=BSE) are always prioritized 1:1 with station interrogations. Demand If the reaction of the remote terminal unit to a transmitted message is to be acquired quickly by the master station, a "Demand" (=parameter-settable station-selective continuous interrogation) can be executed from the master station. This "station-selective demand" is retriggered by further messages to the same station (message parameterized with demand), or aborted by messages to other stations. The selection of the type identification and setting of the continuous interrogation time necessary for the "demand" can be performed in the parameters advanced parameters | call procedure per type identification. The selection of the type identifications is carried out with the parameters advanced parameters | call procedure per type identification | type identification A(TI) ..O(TI) and the setting of the continuous interrogation time assigned to the type identifications is carried out with the parameters advanced parameters | call procedure per type identification | continuous polling time for type identification A..O. Data Flow Control If a remote terminal unit cannot process more data messages (messages), the DFC bit (Data Flow Control) is set in the control field of the message direction remote terminal unit master station. From this moment the protocol firmware of the master station sends no more data messages to the corresponding remote terminal unit, until the remote terminal unit resets the DFC-bit. The status of the DFC-bit of the corresponding remote terminal units is interrogated cyclic by the master station with "REQUEST STATUS OF LINK". The protocol firmware of the master station also monitors whether the remote terminal unit resets the DFC-bit within a time that can be set with the parameter advanced parameters | IECParameter | DFC-monitoring time. If the DFC-bit is present for longer than the set monitoring time, the station is reported as failed. Remote terminal units with set DFC-Bit can be interrogated with low priority and consequently less often by the master station during the station interrogation. With the parameter advanced parameters | IEC-Parameter | operating mode for "DFC-bit = 1" it can be selected, whether remote terminal units are to continue being interrogated in the interrogation cycle or with low priority in a slower interrogation cycle. The cycle time can be parameterized with the parameter advanced parameters | IEC-Parameter | Polling cycle for stations with "DFC-bit = 1". 5-14 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.1.6.2. Control Location If the function "control location" is activated, commands from the protocol element of the master station are only then transmitted to the addressed remote terminal unit if the command has been sent from an enabled control location (originator address). The setting of the control location itself takes place with a command message in single command format <TI=45> which is converted on the basic system element to a PRE control message (function: set control location) by the protocol control function. A command received with an originator address not enabled as control location is not transmitted from the protocol element of the master station and is discarded. For these commands a negative confirmation of activation (ACTCON-) is sent back immediately by the protocol element to the originator address. 5.1.6.3. Control Location Check The control location check is used to check whether the control location, specified with the originator address in the spontaneous information object "Command", has command authority. The originator address specified in the spontaneous information object "Command" must correspond with one of the control locations previously set. If the originator address in the spontaneous information object "Command" does not match with one of the control locations previously set or if no control location has been preset: • • the command is rejected a negative confirmation of the activation is sent (ACTCON-) The control location check is activated as soon as a PRE control message of the type "Set control location" is entered in the PST detailed routing on the basic system element (BSE) for a protocol element (PRE). After startup of the PRE, the BSE sends a PRE control message "Set control location" to the PRE. As a result the control location check function is activated on the PRE. Functions Protocol Elements DC0-023-2.01 5-15 Interfacing of Portective Devices (103) 5.1.6.4. Set Control Location The control location is set on the PRE with a PRE-control message (Function = Set control location) either globally for all stations or station-selective. The control location can be set or deleted and is applicable for all commands of a protocol element. On the BSE the control location is set by the spontaneous information object "control location" and is valid for all commands of a protocol element. The assignment of this message takes place in the OPM of the Toolbox II with the category ACP 1703 Systemfunktionen / protocol element control message. For the derivation of the control location, the following values in the spontaneous information object "Command" signify the originator address: Note: Originator Address Control Location 0 default 1 ... 127 remote command 128 ... 255 local command The selection of the control location and the generation of the spontaneous information object "Control location" must be programmed in an application program of the open-/closed-loop control function. With the spontaneous information object "Control location" in "single command" format, up to 256 control locations can be set at the same time. The information object "Control location" is converted on the basic system element (BSE) to a PRE-control message and passed on to the protocol element. Due to an information object "Control location" with the single command state "ON", the originator address is added to the list of enabled control locations (="Control location enabled"). Due to an information object "Control location" with the single command state "OFF", the originator address is deleted from the list of enabled control locations (="control location not enabled"). The deleting of the control locations can be carried out either station-selective for each control location individually or globally for all stations and all control locations. No confirmation (ACTCON) and no termination (ACTTERM) of the command initiation is created for the information object "Control location". With each startup of the protocol element, all enabled control locations are reset. The control locations are to be set again after every startup of the protocol element. 5.1.6.5. Message from the Master Station to all Remote Terminal Units (unacknowledged) Messages from the multi-point traffic master station "unacknowledged to all" are inserted at any time into a running interrogation cycle (station interrogation) after termination of the data transmission in progress. The message is thereby transmitted several times by the master station with the parameterized number of message retries according to the parameter Message retries | Retries for data message SEND/NO REPLY (broadcast). Afterwards the interrupted interrogation cycle is resumed. The protocol element for IEC 60870-5-103 master function only sends the clock synchronization command as "Message unacknowledged to all". All other messages are transmitted station-selective. 5-16 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.1.7. Transmission of Integrated Totals A counter interrogation command triggered in the system is transmitted from the protocol element of the master station either station-selective or “to all” (=BROADCAST) according to the parameter advanced parameters | IEC-Parameter | send counter interrogation command as "Broadcast". This parameter is transferred to the basic system element after startup of the protocol element. A counter interrogation command to be sent is then already made available to the protocol element by the basic system element, station-selective or BROADCAST. A station-selective counter interrogation command is however only then sent by the protocol element, if an identification message has been received from the corresponding remote terminal unit during startup with the ASCII text "BC1703ACP". Functions Protocol Elements DC0-023-2.01 5-17 Interfacing of Portective Devices (103) 5.1.8. File Transfer Disturbance records are recorded and stored in protection equipment. These can be read out by the master station with the procedures defined in IEC 60870-5-103 for the transfer of files. The protocol element of the master function supports the following possibilities for reading out and transferring disturbance records: • • Transfer of disturbance records to SICAM DISTO Transfer of disturbance records to IEC 60870-5-101/104 systems The protocol element of the remote terminal unit supports the transfer of disturbance records according to IEC 60870-5-103. The disturbance records are managed either in the System SICAM 1703 on the basic system element (BSE) for protection functions or in another connected protective device. SICAM 1703 internal, the IEC 60870-5-103 messages for the transmission of disturbance records are transmitted in a user data container defined for SICAM 1703 in the private range of the IEC 60870-5-101. IEC 60870-5-101/104 1) IEC 60860-5-103 <TI=142> User data container <TI=23> <TI=26> <TI=27> <TI=28> <TI=29> <TI=30> <TI=31> Disturbance event overview Ready to transmit disturbance data Ready to transmit one channel Ready to transmit marks Transmission of marks Transmission of disturbance values Transmission end <TI=142> User data container <TI=24> <TI=25> Order to transmit disturbance data Acknowledgement for disturbance data transmission 1) all with time stamp CP56Time2a The IEC 60870-5-101/104 address of this user data container (CASDU1, CASDU2, IOA1, IOA2, IOA3) is to be parameterized with the parameter advanced parameters | addr. for user data container in rx (disturbance record) | CASDU1, CSADU2, IOA1, IOA2, IOA3. If the IEC 60870-5-103 protocol element in the remote terminal unit is set to an integrated (local) interface, then the parameter setting of the address of the user data container is not required – the distribution of this user data container takes place automatically in this case. In transmit direction (monitoring direction) a parameter setting of the address of the user data container is not necessary. IEC 60870-5-103 messages in user data containers are always transmitted from the protocol element of the remote terminal unit. 5-18 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.1.8.1. Transfer of Disturbance Records to SICAM DISTO The transfer of disturbance records from protection equipment is controlled by SICAM DISTO (Windows Application). Disturbance records are read out from the protection equipment by SICAM DISTO according to IEC 60870-5-103 and saved to data carrier as file in IEEE Comtrade format. The data transmission between SICAM DISTO and the protocol element to which the protection equipment are connected, is carried out in the System SICAM 1703 with the user data containers provided for this purpose. The protocol element itself performs no special sequences for the transmission of disturbance records. All IEC 60870-5-103 message formats necessary for the transfer of disturbance records from protection equipment are transmitted from the protocol element of the master station between SICAM DISTO and the protocol element of the master function in a user data container defined for SICAM 1703 in the private range of IEC 60870-5-101. Then the user data container is not transmitted to the protection equipment, rather the IEC 60870-5-103 message format contained in the message data of the user data container. The transmission of the user data container within SICAM 1703 takes place with type identification <TI=142> in the private range of IEC 104-5-104. SICAM 1703 internal, several modes are provided for the use of the user data container. For the transfer of disturbance records, the user data container is used with message type = 128 (=SAT Standard-Format). For each interface with protection equipment connected, an unambiguous address must be parameterized for a user data container in transmit and receive direction. The assignment of the message address for the spontaneous information object "User data container" is carried out in the OPM II with the category firmware / Transmit_Container and the category firmware / Receive_Container. The container type is to be set to "Disturbance record container" with the parameter Containter type_Rec and the parameter Containter type_Tra. With the parameterization of the message addresses, the transfer of disturbance records to SICAM DISTO is also activated. In ACP 1703 the addresses of all user data containers for the transfer of disturbance records are to be entered in the data flow filter. In Ax 1703 the addresses of the user data containers are to be entered in the corresponding Ax 1703-PRE detailed routings PDS (QID-ST = 254 ... SSE as source). With the parameter advanced parameters | forward empty list of recorded disturbances (to SAT DISTO) in some protocol firmwares an "Empty disturbance record overview" received from the protection equipment can be blocked for the transmission to SICAM DISTO. This function is no longer required! Note: A disturbance record overview must always be transferred to SICAM DISTO! Functions Protocol Elements DC0-023-2.01 5-19 Interfacing of Portective Devices (103) Segmentation With user data containers a maximum of 180 bytes of transparent message data can be transmitted. Longer parameter messages from REYDISP (max. 256 bytes) are thus to be transmitted in several part segments and grouped together again before transmission/processing. With missing segments the partially transmitted parameter message is discarded. The transparent mode only utilizes part segments with a max. length of 50 bytes of message data! User data container <TI=142> for transmission of disturbance records 27 26 25 24 23 22 21 20 142 Type identification 1 variable structure qualifier Cause of transmission Originator address CASDU1 CASDU2 IOA1 IOA2 IOA3 : : : : : : : : : : : : : : : : : : : : : : : : 7 octets dual time in CP56Time2a format Length of user data in bytes *) 128 Message type = 128 (SAT standard format) 45 UEK = 45 S=1 I=0 1 - 255 R Number of bytes IEC 60870-5-103 message + segment info **) Number of segments Segment number Segment information TI : : : : : : : : : : : : Status = 0x02 Message data (0) IEC 60870-5-103 Format : : : : : : : : : : : : : : : Message data (n) IEC 60870-5-103 Format max. 50 Bytes *) Length of the user data from the field UEK up to the last byte of the message data (n) **) Length of the user data from the field segment information up to the last byte of the message data (n) Note: 5-20 The user data container is described here in the internal format of the protocol element with the essential information fields. DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Elements of the Message TI .. type identification <TI=142> User data container CASDU, IOA .. Message address CASDU1 = LSB of the CASDU CASDU = CASDU of the remote terminal unit CASDU2 = MSB of the CASDU CASDU = CASDU of the remote terminal unit IOA1 IOA2 IOA3 Cause of transmission 03 .. spontaneous ... in monitoring direction 06 .. activation ... in control direction Time 7 octets dual time Earliest possible acquisition moment of a message in AK 1703, time tag on the basic system element (BSE) Message type = 128 Length of the user data part in octets Number of bytes Length of the user data in octets (exclusive message type) Number of bytes for message data incl. segmentation field Segmentation field Number of segments Total number of segments Segment number Current number of the transmitted segment ... the 1st segment has segment number 1 Direction bit (R) 0 = control direction (SAT DISTO PRE) 1 = monitoring direction (PRE SICAM DISTO) Functions Protocol Elements DC0-023-2.01 5-21 Interfacing of Portective Devices (103) 5.1.8.2. Transfer of Disturbance Records to IEC 60870-5-101/104 Systems Disturbance records (fault data) from protection equipment can be transmitted from the protocol element of the master station to a central control system according to IEC 60870-5-101/104 "Transmission of Files in Monitoring Direction (disturbance record transmission of a protective device)". In the control system the disturbance records are displayed for evaluation and saved to data carrier. After the order to transmit the fault data by the higher-level master station has taken place, the selected file is read out from the protective device by the protocol element of the master station according to IEC 60870-5-103 and buffered in the memory of the protocol element. After the transmission of the file from the protective device has concluded, this is transmitted to the higher-level master station according to IEC 60870-5-101/104 "Transfer of Files in Monitoring Direction (disturbance record transmission of a protective device)". The file is only deleted in the protective device after the complete transmission of the file to the higher-level master station. The protocol element only supports the transmission of one file at one time. For the transmission of the file to the higher-level master station, the corresponding IEC 60870-5-101/104 type identifications are processed or generated by the protocol element. SICAM 1703 internal, presently IEC 60870-5-101/104 messages for the transmission of files can only be transported with a maximum length of 200 bytes (a SICAM 1703 internal "Segmentation" of these messages is presently not yet supported). For the transmission to the higher-level control system, if necessary the message length can be parameterized with the parameter advanced parameters | file transfer | Maximum message length for one segment and thus be set "shorter" (concerns "Segment" and "File Directory"). IEC 60870-5-101/104 Messages in Control Direction for the Transmission of Files <TI=122> File directory interrogation, file selection, file interrogation, section interrogation <TI=124> File confirmation, section confirmation IEC 60870-5-101/104 Messages in Monitoring Direction for the Transmission of Files <TI=120> File ready <TI=121> Section ready <TI=123> Last section, last segment <TI=125> Segment <TI=126> File directory The assignment of the message addresses for the spontaneous information objects "sub-directory" is carried out in the OPM II with the category firmware / Filetransfer. For every protective device, the address for the sub-directory and the address for each disturbance record are to be parameterized in the process technique. The protocol element monitors a running transmission of a file both in the direction of the higher-level master station as well as in the direction of the protective device. A failure during a running transmission of a file is detected by the protocol element by means of a monitoring time (Timeout). With the parameter advanced parameters | file transfer | timeout for filetransfer this monitoring time can be parameterized. With a failure of a running transmission, the disturbance file stored in the memory of the protocol element is deleted and the current file directory transmitted to the higher-level master station. Since the disturbance file is only deleted in the protective device after successful transmission to the higher-level master station, in the event of an error this can be transmitted again. The spontaneous transmission of the file directory can be deactivated with the parameter advanced parameters | file transfer | spontaneous transmission of directory list. If the spontaneous transmission is deactivated, the higher-level master station must request the transmission of the file directory. For the transmission of disturbance files to the higher-level master station, the messages of several protective devices can be used with the same CASDU or also per protective device with one unambiguous CASDU. 5-22 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.2. Transfer of Parameters for Reyrolle Protection Equipment If digital protective devices from the firm Reyrolle are used in combination with a control centre system SICAM 230, REYDISP – the Engineering Tool for Reyrolle Protective Devices – can be implemented directly on the control centre system SICAM 230 "Embedded REYDISP". The transfer of parameters from/to Reyrolle protection equipment is controlled by REYDISP. REYDISP is thereby used on the control centre system (SAT 2xx) under Windows. Parameters are transmitted from REYDISP to the protection equipment in the private range of IEC 60870-5-103. The data transmission between REYDISP and the protocol element to which the protection equipment are connected, is carried out in the System SICAM 1703 with the user data containers provided for this purpose. REYDISP does not require its own interface to SICAM 1703 – the communication takes place over the interface of the control centre system (REYDISP is coupled to the software of the control centre system over a software interface). The protocol element itself performs no special sequences for the transmission of parameters. All IEC 60870-5-103 message formats necessary for the transfer of parameters from/to Reyrolle protection equipment are transmitted from the protocol element of the master station between REYDISP and the protocol element of the master function in a user data container defined for SICAM 1703 in the private range of IEC 60870-5-101/104. Then the user data container is not transmitted to the protection equipment, rather the IEC 60870-5-103 message format contained in the message data of the user data container. The transmission of the user data container within SICAM 1703 takes place with type identification <TI=142> in the private range of IEC 104-5-104. SICAM 1703 internal, several modes are provided for the use of the user data container. For the transmission of parameters, the user data container is used with message type = 132 (=REYDISP parameter container). All data sent from REYDISP via user data container are transmitted to the remote terminal units by the protocol firmware on conclusion of the running message transmission sequence. User data containers to non-parameterized remote terminal units are not transmitted by the protocol firmware and are discarded! With station-selective addressing, in addition the reply from the protective device following this is transmitted back to REYDISP via user data container. In addition, all message formats received from the protective devices with unknown type identification are also passed on to REYDISP via user data container. For each interface with protection equipment connected, an unambiguous address must be parameterized for a user data container in transmit and receive direction. The assignment of the message address for the spontaneous information object "User data container" is carried out in the OPM II with the category firmware / Transmit_Container and the category firmware / Receive_Container. The container type is to be set to "Reydisp container" with the parameter Kontaintertyp_Rec and the parameter Kontainertyp_Tra. With the parameterization of the message addresses, the transfer of parameters to REYDISP is also activated. In ACP 1703 the addresses of all user data containers for the transfer of disturbance records are to be entered in the data flow filter. In Ax 1703 the addresses of the user data containers are to be entered in the corresponding Ax 1703-PRE detailed routings PDS (QID-ST = 254 ... SSE as source). Functions Protocol Elements DC0-023-2.01 5-23 Interfacing of Portective Devices (103) Segmentation With user data containers a maximum of 180 bytes of transparent message data can be transmitted. Longer parameter messages from REYDISP (max. 256 bytes) are thus to be transmitted in several part segments and grouped together again before transmission/processing. With missing segments the partially transmitted parameter message is discarded. User data container <TI=142> "REYDISP parameter container" 27 26 25 24 23 22 21 20 142 SQ T Type identification 1 variable structure qualifier P/N 3 Cause of transmission 0 Originator address CASDU1 CASDU2 IOA1 IOA2 IOA3 : : : : : : : : : : : : : : : : : : : : : : : : 7 octets dual time in CP56Time2a format Length of the user data part in bytes **) 132 DIR Message type = 132 ("REYDISP parameter container") Number of segments Segment number Segment information Link Address (station number) Container type Message data (0) : : : : : : : : : : : : : : : : : : : : : : : : : : Message data (n) ... max. 180 Bytes **) Number of bytes from segment information up to and including the last byte of the message data Note: 5-24 The user data container is described here in the internal format of the protocol element with the essential information fields. DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Elements of the Message TI .. type identification <TI=142> User data container CASDU, IOA .. Message address CASDU1 = LSB of the CASDU CASDU = CASDU of the remote terminal unit CASDU2 = MSB of the CASDU CASDU = CASDU of the remote terminal unit IOA1 IOA2 IOA3 Cause of transmission 03 .. spontaneous ... in control direction and monitoring direction Time 7 octets dual time Message type = 132 REYDISP parameter container Length of the user data part in octets Length of the user data in octets (exclusive message type) Segmentation field Number of segments Total number of segments Segment number Current number of the transmitted segment ... the 1st segment has segment number 1 Direction bit (DIR) 0 = control direction (REYDISP PRE) 1 = monitoring direction (PRE REYDISP) Link address Station number of the protection equipment Container type 0 = "IEC 60870-5-103" message 1 = "IEC 60870-5-1/FT1.2" message with fixed block length 2 = "IEC 60870-5-1/FT1.2" single character Functions Protocol Elements DC0-023-2.01 5-25 Interfacing of Portective Devices (103) Container type "1" IEC 60870-5-1/FT1.2 "Message with fixed block length" 27 DIR 26 25 24 23 Number of segments =1 22 21 20 Segment number = 1 Segment information Link Address (station number) 1 Container type 10H Start character 1 FKT-Code = 9 *) Control field Link address (0-254) Station address of the protection equipment Checksum 16H *) Stop character For the transparent transmission of IEC 60870-5-101/FT1.2 message formats, presently only function code < FKT = 9 > "Request Status of Link" is supported! Container type "0" IEC 60870-5-103 message "Message with variable block length" 27 DIR 26 25 24 23 Number of segments 22 21 20 Segment number Segment information Link Address (station number) 0 Container type Type identification (253, 254, 255) IEC 60870-5-103 message format *) SQ T message data (0) variable structure qualifier P/N Cause of transmission CASDU1 Function type Information number : : : : : : : : : Message max. 180 bytes *) The IEC 60870-5-101, IEC 60870-5-102 frame is not transmitted in the REYDISP parameter container. This is regenerated by the protocol element during transmission. Control direction: <TI=254>......REYDISP parameter frames <TI=255>......REYDISP parameter "last frame" Monitoring direction: <TI=253>......REYDISP termination of private data response frame <TI=254>......REYDISP parameter frames <TI=255>......REYDISP parameter "last frame" 5-26 DC0-023-2.01 Functions Protocol Elements data (n) Interfacing of Portective Devices (103) Container type "2" IEC 60870-5-1/FT1.2 "Single character" 27 DIR 26 25 24 23 Number of segments =1 22 21 Segment number = 1 20 Segment information Link Address (station number) *) 2 Container type *) E5H Single character The transparent transmission of IEC 60870-5-101/FT1.2 message formats for single character is only supported in monitoring direction (SICAM 1703 REYDISP)! Functions Protocol Elements DC0-023-2.01 5-27 Interfacing of Portective Devices (103) 5.3. Optimized Parameters for selected Transmission Facilities The protocol element supports selected transmission facilities - for these the parameters are set fixed – the selection of the transmission facility is carried out with the parameter Common settings | interface modem. By selecting the "freely definable transmission facility" certain parameters can be set individually. Most transmission facilities support only certain baud rates or combinations of baud rates in transmit/receive direction – these are to be taken from the descriptions for the transmission facility. The transmission rate (baud rate) is to be set depending on the submodule used for communication, separate for transmit/receive direction with the parameter Common settings | baud rate receiving direction and the parameter Common settings | baud rate transmit direction or for transmit/receive direction together with the parameter Common settings | baud rate. After the transmission of broadcast messages an extra pause can be inserted regardless of the transmission facility used. This pause is required for remote terminal units of third-party manufacturers, if these can only process further messages after a transmission pause following the reception of BROADCAST-messages. The pause after broadcast messages can be set in the master station with the parameter advanced parameters | advanced time settings | pause time after broadcast message (tp_bc) and the parameter advanced parameters | advanced time settings | pause time after broadcast message "time base" (tp_bc). If the pause time is set to "0", a minimum pause of 33 bit is maintained by the protocol element. Apart from this, a transmission facility, that can be freely defined by the user, can be selected, for which all parameters that are available can be individually set. This is then necessary if transmission facilities are to be used that are not predefined or if modified parameters are to be used for predefined transmission facilities. For the selection of the freely definable transmission facility the parameter Common settings | interface modem is to be set to "freely definable". Only after that are all supported parameters displayed and can be parameterized with the required values (see Table with Default Parameters for Transmission Facilities). 5-28 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) For the adaptation to various modems or time requirements of external systems, the following parameters can be set individually: • Common settings | electrical interface [SM2541 only] • Common settings | asynchron/isochron • Common settings | source for receive-/transmit clock (only for "Isochronous") • Common settings | free defineable transmission facility | pause time (tp), Common settings | free defineable transmission facility | pause time "time base" (tp) • Common settings | free defineable transmission facility | set up time (tv), Common settings | free defineable transmission facility | set up time "time base" (tv) • Common settings | free defineable transmission facility | run-out time (tn), Common settings | free defineable transmission facility | run-out time "time base" (tn) • advanced parameters | advanced time settings | pause time after broadcast message (tp_bc), advanced parameters | advanced time settings | pause time after broadcast message "time base" (tp_bc), • Common settings | free defineable transmission facility | DCD handling • Common settings | free defineable transmission facility | bounce suppression time (tprell) • Common settings | free defineable transmission facility | disable time (tdis), Common settings | free defineable transmission facility | disable time "time base" (tdis), • Common settings | free defineable transmission facility | stability monitoring time (tstab) • Common settings | free defineable transmission facility | continuous level monitoring time (tcl) • Common settings | free defineable transmission facility | Transmission delay if countinous level (tcldly) • Common settings | free defineable transmission facility | Send clock synchronization command to each station selective • Common settings | free defineable transmission facility | 5V supply (DSR) [only SM0551, SM2551] • Common settings | free defineable transmission facility | Configuration for CM-082x [only SM0551, SM2551] How the individual time settings are effective during the data transmission is shown on the following page in a Timing Diagram. Parameter "5V Supply (DSR)" [only SM0551, SM2551] If necessary the voltage supply of the transmission facility (only 5V) – insofar as this is sufficient – can take place over the state line DSR. The enabling of the voltage supply is performed with the parameter advanced parameters | 5V supply (DSR). The voltage supply is only switched on the DSR state line instead of the DSR signal with corresponding parameter setting. ATTENTION: Required voltage supply and maximum current consumption of the transmission facility must be observed! Functions Protocol Elements DC0-023-2.01 5-29 Interfacing of Portective Devices (103) Parameter "Configuring for CM082x" [only SM0551, SM2551] If an optical transformer of the type CM082x is used as external transmission facility, then the parameter Common settings | free defineable transmission facility | Configuration for CM-082x must be set when using a patch plug of the type CM2860. In addition, for the adaptation of the protocol to the transmission medium used or to the dynamic behavior of the connected remote station, the following parameters are available: • advanced parameters | monitoring times | Character monitoring time, advanced parameters | monitoring times | Character monitoring time "time base" • advanced parameters | monitoring times | idle monitoring time, advanced parameters | monitoring times | idle monitoring time "time base" • advanced parameters | monitoring times | expected_ack_time_corr_factor (see acknowledgement procedure in the master station) The character monitoring time and idle monitoring time is used for message interruption monitoring and message re-synchronization in receive direction. A message interruption is detected if the time between 2 bytes of a message is greater than the set character monitoring time. With message interruption the running reception handling is aborted and the message is discarded. After a detected message interruption a new message is only accepted in receive direction after an idle time on the line (idle time). The protocol element can – insofar as the transmission facility makes this signal available receive-side – evaluate the interface signal DCD and utilize it e.g. for monitoring functions. When using an optical ring with CM-0821, the status of the optical ring is signaled with the interface signal DCD. A failure of the optical ring is indicated as a warning by the protocol element in the diagnostic. (DCD – active .......... Ring OK; DCD – inactive ........ Warning Ring NOK) 5-30 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Default parameters for transmission facilities with 103M00, 103S00 Transmission facility Electrical RTS Interface tp tv tn tp_bc (2) tdis [ms] [ms] [Bit] [ms] [ms] DCD tbs tstab tduration tdelay [ms] [ms] [sec] [ms] A_I T CM-0821 Ring RS-232 ON 0 1 0 0 0 NO 0 0 0 0 A I CM-0821 Star, CM-0826, CM-0827, CM-0829 RS-232 ON 0 1 0 0 0 NO 0 0 0 0 A I Optical (CM-0827) RS-232 ON 0 1 0 0 0 NO 0 0 0 0 A I Direct connection (RS-485) RS-485 0 1 0 0 0 NO 0 0 0 0 A I DCD A_I T Freely definable 2) only possible for 103M00 (MASTER)! Default parameters for transmission facilities with 103MA0, 103SA0 Transmission facility Electrical RTS Interface tp tv tn tp_bc (2) tdis [ms] [ms] [Bit] [ms] [ms] tbs tstab tduration tdelay [ms] [ms] [sec] [ms] 5V CM082x 1) 1) CM-0821 Ring RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I YES NO CM-0821 Star, CM-0827 RS-232 ON 0 0 0 0 0 NO 0 0 0 0 A I YES NO Direct connection (RS-485 with CM-0829) RS-232 0 1 bit 0 0 0 NO 0 0 0 0 A I YES NO Freely definable 1) on the DSR interface line a 5V voltage is output for the supply of the transmission facility 2) only possible for 103MA0 (MASTER)! Legend: Electrical interface ......................... Parameter "electrical interface" [only SM2541] RTS................................................... = RTS is switched for the control of the carrier switching of the modem with each message (ON / OFF) tp ...................................................... Parameter "Pause time (tp)", Parameter "Pause time time base (tp)" tv....................................................... Parameter "Set-up time (tv)", Parameter "Set-up time time base (tv)" tn ...................................................... Parameter "overtravel time (tn)", Parameter "overtravel time time base (tn)" tp_bc ................................................ Parameter "Pause time after broadcast message (tp_bc)", Parameter "Pause time after broadcast message_time base (tp_bc)" tdis ................................................... Parameter "blocking time (tdis)", Parameter "block time time base (tdis)" DCD .................................................. Parameter "DCD-assessment" tbs .................................................... Parameter "Bounce suppression time (tbs)" tstab ................................................. Parameter "Stability monitoring time (tstab)" tduration .......................................... Parameter "Continuous level monitoring time (tduration)" tdelay ............................................... Parameter "transmit delay for level (tdelay)" A_I .................................................... Parameter "Asynchronous/Isochronous" T........................................................ Parameter "Bit timing (only with isochronous)" (I=internal, E=external) 1) CM082x .............................. ...... Parameter "Configuring for CM082x". Configuring the interface for optical transformer CM-082x with patch plug CM-2860 [only SM0551, SM2551] 1) 5V .............................................. Parameter "5V Supply (DSR)" [only SM0551, SM2551] Functions Protocol Elements DC0-023-2.01 5-31 Interfacing of Portective Devices (103) The following picture shows the dynamic behavior (timing) in detail for the data transmission when using transmission facilities with switched carrier. Only for BROADCASTmessages RTS Master station tverz tp tv tn Data transmission tp_bc tsw tp TXD tPrell DCD tPrell tverzRTS Data transmission RXD tsignal tsignal tdis t´verzRTS t´verzRTS t´Prell Remote station DCD t´Prell t´signal Data transmission RXD t'dis RTS t'sw tp' t'v Data transmission t'n TXD t'verz tPrell tPrell tstab tstab tdauer Legend: RTS ………….. Request to Send DCD …………. Data Carrier Detect TXD ……...….. Transmit Data RXD ……...….. Receive Data tverzRTS ……….. Processing time of the transmission system Time delay/time difference between activation of transmit part (RTS ) and receiver ready (DCD ) tp ………….….. Break time (delay, before transmit part is activated with RTS) tv ………….….. Setup time (transmission delay, after transmit part was activated with RTS) tn ………….….. Reset time (delayed switch off of the transmit signal level with RTS after message transmission ) tp_bc ……….….. Break time after BROADCAST-Messages (some systems require a longer break after the transmission of BROADCAST -messages before the next message can be sent ) tsw ….....….….. Internal processing time tsignal ….....….. Signal propagation delays (dependent from the used transmission facility /transmission path) tPrell …...….….. Protective time after positive/negative DCD-edge (debounce of DCD) tstab …...….….. Stability monitoring time – the new DCD-status is only used for message synchronisation after the expiration of the stability monitoring time tdauer …...….….. Continuous level monitoring time tverz …...….….. Transmission delay – in case of a continuous level a further message transmission will be made at the latest after the transmission delay tdis …….….….. Disable time of the receiver after message receiption (to supress faulty signs during level monitoring ) t`x …………….. Corresponding times in the remote stations …………….. DCD valide 5-32 DC0-023-2.01 Functions Protocol Elements tv Interfacing of Portective Devices (103) 5.4. Function for the Support of Redundant Communication Routes To increase the availability master stations can be designed redundant. In this chapter, the possible redundancy concepts themselves that can be realized are not described, rather only those functions for the support of redundant communication routes supported by the protocol element. 5.4.1. Redundancy Mode "1703-Redundancy" In the master station only the redundancy mode "1703-Redundancy" is supported and does not need to be set with a parameter. In the remote terminal unit, no function for the support of redundant communications routes is supported by the protocol element! The switchover of the redundancy state takes place system-internal through redundancy control messages. In the master station, in addition a delay for the switchover of the redundancy state from PASSIVE (=STANDBY) to ACTIVE can be set with the parameter Redundancy | Delay time passive=>active . The operating mode of the interface with redundancy state "PASSIVE" can be set according to the redundancy configuration with the parameter Redundancy | operation if passive as follows: • • • Interface "TRISTATE" – only listening mode Interface "ACTIVE" – only listening mode Interface "ACTIVE" – interrogation mode From the redundant – non-active master station, listened messages are passed on in the system with the identifier "passive" in the status. In redundant master stations that are not active, a failure of the interface is monitored globally and the failure of remote terminal units monitored station-selective. The failure of the interface is detected by the STANDBY master station by monitoring for cyclic message reception. The monitoring time is set with the parameter Redundancy | listening_mode (failure monitoring time). On receive timeout (active master station or transmission facility of the master station has failed) the interface is signaled as failed. The failure of a remote terminal unit is detected by the STANDBY master station through station-selective monitoring for cyclic message reception. On station-selective receive timeout (remote terminal unit or transmission facility of the remote terminal unit has failed) the remote terminal unit is signaled as failed. Station-specific pending faults are reset in a redundant STANDBY master station, if a fault-free message from the respective station is "listened". Functions Protocol Elements DC0-023-2.01 5-33 Interfacing of Portective Devices (103) 5.4.2. Deactivating the Interface TM 1703 ACP presently does not support any redundancy functions. Simple redundancy solutions can be realized with the possibility of deactivating an interface with protocol control messages. With deactivated interface the transmitter of the interface is switched to "tristate" and the data for emission are fetched from the basic system element and discarded without error message. Received messages are discarded and not passed on to the basic system element. The activation/deactivation of the interface takes place through PRE control messages. With function enabled with the parameter Redundancy | interface deactivation the interface is deactivated after startup of the protocol element. With deactivation of the interface a possibly present failure of the interface is reset if no "listening mode (failure monitoring time)" is parameterized. With activation of the interface, a general interrogation message is transmitted to the remote station by the protocol element. With deactivated interface, no monitoring of the interface takes place! 5-34 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.5. Message Conversion Data in transmit direction are transferred from the basic system element to the protocol element in the SICAM 1703 internal IEC 60870-5-101-/104 format. These are converted by the protocol element to the IEC 60870-5-103 message format on the line and transmitted according to the transmission procedure of the protocol. Data in receive direction are converted by the protocol element from the message format on the transmission line to a SICAM 1703 internal IEC 60870-5-101/104 format and transferred to the basic system element. The protocol element supports the following modes for the message conversion: Message Conversion Mode Communication Protocol to the Protection Equipment Z U IEC 60870-5-101 IEC 60870-5-103 - Transmission procedure: IEC 60870-5-103 - Message formats: IEC 60870-5-103 IEC 60870-5-101 IEC 60870-5-101 - Transmission procedure: IEC 60870-5-101 - Message formats: IEC 60870-5-101 - IEC 60870-5-101 IEC 60870-5-103 (101) "Container Mode" - Data communication control: IEC 60870-5-103 - Message formats: IEC 60870-5-101 (Transparent-Mode) IEC 60870-5-101 messages are transmitted in IEC 60870-5-103 container messages (in the private range) ... with SICAM 1703 configurations with BC 1703 the conversion of IEC 60870-5-101 IEC 60870-5-103 IEC 60870-5-101 can be omitted. Z.......Master station U ......Remote terminal unit (protection equipment) The mode for the message conversion (and also for the transmission procedure) can be set in the remote terminal unit with the parameter Common settings | operating mode of the interface. In the master station no parameter for this is provided, for IEC 60870-5-101 the corresponding protocol firmware for multi-point traffic is to be implemented as master station. The assignment of the message address for the spontaneous information objects with message conversion mode "IEC 60870-5-101 IEC 60870-5-103" is carried out in the OPM II in the category SIP-Telegrammadressumrechnung /... / firmware /. Functions Protocol Elements DC0-023-2.01 5-35 Interfacing of Portective Devices (103) 5.5.1. Message Conversion IEC 60870-5-101 IEC 60870-5-103 Data in control direction are transferred from the basic system element to the protocol element in the SICAM 1703 internal IEC 60870-5-101/104 format. These are converted by the protocol element to the IEC 60870-5-103 message format on the line and transmitted according to the transmission procedure of the protocol. Data in monitoring direction are received by the protocol element depending on the transmission procedure according to IEC 60870-5-103 and converted by the protocol element to the internal IEC 60870-5-101-/104 format and then passed on to the basic system element. The supported functionality (Interoperability) is evident in the document ACP 1703 Interoperability IEC 60870-5103 (DC0-025-1) or in the document Ax 1703 Interoperability IEC 60870-5-103 (DA0-072-1) respectively. Note: Generic data are only limitedly supported! The parameterization of the address conversion from IEC 60870-5-101 IEC 60870-5-103 address and message format takes place with the "SIP-Message Address Conversion". IEC 60870-5-101/104 Station No. SICAM 1703 internal station number (0-99) CASDU1 CASDU2 IOA1 IOA2 IOA3 CASDU TI Type identification diverse Additional info per category IOA 1) IEC 60860-5-103 Link address SICAM 1703 internal station number (0-99) CASDU FUN INF Station address of the protection equipment Function type Information number TI Function type (type identification) 1) 1) See message conversion in transmit/receive direction 5-36 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Message conversion in control direction (public range of IEC 60870-5-103) IEC 60870-5-101/104 IEC 60860-5-103 Z <TI=45> <TI=46> single command double command <TI=20> General command <TI=45> <TI=46> single command double command --- Reset of the fault locations (only acts protocol element internal) <TI=50> Setpoint command, short floating point number <TI=10> --- General interrogation command (SICAM 1703 internal) <TI=142> --<TI=122> <TI=124> U - Generic data (setpoint command) - <TI=7> <TI=21> General interrogation command Generic command (general interrogation command) 2) - User data container "Disturbance record transmission to SICAM DISTO" <TI=24> <TI=25> Order to transmit disturbance data Acknowledgement for disturbance data transmission --- <TI=6> Time synchronization 1) 3) Interrogation of file directory, 4) file selection, file interrogation, section interrogation file confirmation, section confirmation 1) This command is not transmitted (acts only protocol element internal). The fault locations of the parameterized LINK-Address are reset to the corresponding initial value! 2) Only general interrogation command for generic data is supported! 3) Is generated by the protocol element; SICAM 1703 internal, the time management message (function code 156) is used 4) Is generated by the protocol element (only 103MA0); "Transmission of Files in Monitoring Direction (disturbance record transmission of a protective device) according to IEC 60870-5-101/104". Message conversion in control direction (private range of IEC 60870-5-103) IEC 60870-5-101/104 IEC 60860-5-103 Z U <TI=45> <TI=46> single command double command <TI=232> <TI=45,46> <TI=45,46> Command to protective device "ALSTOM" Command with SELECT/EXECUTE "ALSTOM" Command without SELECT/EXECUTE "ALSTOM" - <TI=142> User data container "Parameter messages to Reyrolle protective devices" <TI=254> <TI=255> REYDISP Parameter Frame REYDISP Parameter "Last Frame" - Functions Protocol Elements DC0-023-2.01 5-37 Interfacing of Portective Devices (103) Message conversion in monitoring direction (public range of IEC 60870-5-103) IEC 60870-5-101/104 1) Z U Single-point information with time stamp Double-point information with time stamp Protection event with time stamp Blocked activation of protection with time stamp Blocked tripping of protection with time stamp <TI=1> Binary information with time stamp Single-point information with time stamp Double-point information with time stamp Measured value, short floating point number with time stampProtection event with time stamp Blocked activation of protection with time stamp Blocked tripping of protection with time stamp <TI=2> Binary information with relative time <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp <TI=3> Measured value I <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp <TI=4> Real-time measured values with relative time <TI=30> <TI=31> Single-point information with time stamp Double-point information with time stamp <TI=5> Identification information --- --- <TI=6> Time synchronization, binary information 3) --- --- <TI=8> General interrogation end 3) <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp <TI=9> Measured values II <TI=36> Measured value, short floating point number with time stamp <TI=10> Generic data (measured value) --- <TI=11> Generic identification <TI=23> <TI=26> <TI=27> <TI=28> <TI=29> <TI=30> <TI=31> Disturbance event overview Ready to transmit disturbance data Ready to transmit one channel Ready to transmit marks Transmission of marks Transmission of disturbance values Transmission end <TI=23> <TI=26> <TI=27> <TI=28> <TI=29> <TI=30> <TI=31> Disturbance event overview Ready to transmit disturbance data Ready to transmit one channel Ready to transmit marks Transmission of marks Transmission of disturbance values Transmission end <TI=30> <TI=31> <TI=38> <TI=39> <TI=40> <TI=30> <TI=31> <TI=36> <TI=38> <TI=39> <TI=40> --- 5-38 IEC 60860-5-103 <TI=120> <TI=121> <TI=123> <TI=125> <TI=126> File ready Section ready Last section, last segment Segment File directory <TI=142> User data container "Disturbance record transmission to SICAM DISTO" DC0-023-2.01 4) Functions Protocol Elements 3) 2) Interfacing of Portective Devices (103) 1) all with CP56Time2a time stamp 2) only data in the format GDD [DATATYPE] = 7 (short Real IEEE STD 754) are supported! 3) is generated in the RTU directly by the protocol element! Is generated by the protocol element (only 103MA0); "Transmission of Files in Monitoring Direction (disturbance record transmission of a protective device) according to IEC 60870-5101/104". Functions Protocol Elements DC0-023-2.01 5-39 Interfacing of Portective Devices (103) Message conversion in monitoring direction (private range of IEC 60870-5-103) IEC 60870-5-101/104 1) IEC 60860-5-103 <TI=30> <TI=31> Single-point information with time stamp Double-point information with time stamp <TI=33> Real-time information (SEG protective devices) <TI=30> <TI=30> <TI=31> <TI=31> Single-point information with time stamp Single-point information with time stamp Double-point information with time stamp Double-point information with time stamp <TI=65> <TI=66> <TI=67> <TI=68> Single-point information with time "ALSTOM" Single-point information without time "ALSTOM" Double-point information with time "ALSTOM" Double-point information without time "ALSTOM" <TI=33> Bit pattern 32 Bit with time stamp <TI=71,72 > 32 Bit binary value <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp <TI=140> Measured values SIEMENS <TI=36> Measured value, short floating point number with time stamp <TI=204> Measured value short floating point (Reinhausen TAPCON 240) <TI=36> Measured value, short floating point number with time stamp Integrated totals with time stamp <TI=205> Measured value 28 Bit (SIEMENS Siprotec) User data container "Parameter messages to Reyrolle protective devices" <TI=253> REYDISP termination of Private Data Response Frame REYDISP Parameter Frame REYDISP Parameter "Last Frame" <TI=37> <TI=142> <TI=254> <TI=255> 1) all with CP56Time2a time stamp 5-40 Z DC0-023-2.01 Functions Protocol Elements "ALSTOM" U Interfacing of Portective Devices (103) Causes of transmission in control direction IEC 60870-5-101/103 URS Master Station RTU Cause of transmission 8 Time synchronization, command 9 GI-initiation 19 ALSTOM command <TI:=232> 20 General command 31 Disturbance data transmission 40 Generic write command 42 Generic read command 1) 1) only for ALSTOM protection equipment! Causes of transmission in monitoring direction IEC 60870-5-101/103 URS Z U Cause of transmission 1 spontaneous 2 cyclic 3 Reset information FCB 4 Reset information KE 5 Startup/restart information 6 First start information 7 Test mode 8 Time synchronization, binary information 9 General Interrogation 10 GI-End information 11 Local operation 12 Remote operation 13 Remote operation negative 20 Return information to remote command positive 21 Return information to remote command negative 31 Disturbance data transmission 40 Return information to generic write command positive 41 Return information to generic write command negative 42 Generic reading; data valid 43 Generic reading; data invalid 44 Confirmation of a generic write command 1) 1) only for ALSTOM protection equipment! Functions Protocol Elements DC0-023-2.01 5-41 Interfacing of Portective Devices (103) Type Identification 6: Time Synchronization The assignment of the IEC 60870-5-103 message address for the spontaneous information object "time synchronization" takes place without parameter setting by the protocol element of the master station. The time synchronisation is always transmitted "BROADCAST" (Send/no Reply) from the protocol element of the master station to the protection equipment spontaneously with a change of the time and cyclic in a parameter-settable grid. Elements of the Message (SICAM 1703 internal) BSE PRE Elements of the Message (IEC 60870-5-103) Function code Information code synchronisation Type identification TI 6 .. Time synchronization = 156 = 0 .. Clock Time management (SICAM 1703 internal) not evaluated Message address CASDU = 255.. Station address of the protection equipment (BROADCAST) FUN = 255 .. Global function type INF = 0 .. Information number ZU System function (time synchronization) Cause of transmission (COT) COT = 8 .. Time synchronization Time CP56Time2a ... Dual time with 7 octets 5-42 With this SICAM 1703 internal message, the internal clock of the protocol element is set and a time synchronization of the protection equipment connected in initiated. Time CP56Time2a ... Dual time with 7 octets DC0-023-2.01 In the message the time of the 1st bit is entered on the line Functions Protocol Elements Interfacing of Portective Devices (103) Type Identification 7: General Interrogation Command The assignment of the IEC 60870-5-103 message address for the spontaneous information object "general interrogation command" takes place without parameter setting by the protocol element of the master station. The general interrogation command is transmitted from the protocol element of the master station selectively for every CASDU per Link-Address (station address of the protection equipment). Elements of the Message (SICAM 1703 internal) BSE PRE Elements of the Message (IEC 60870-5-103) Function code Information code Type identification TI 7 .. General interrogation command = 155 = 1 .. Source-GI request General interrogation request (SICAM 1703 internal) not evaluated Message address CASDU .. Station address of the protection equipment Message address CASDU .. Station address of the protection equipment FUN = 255 .. Global function type INF = 0 .. Information number Cause of transmission (COT) <6> .. activation qualifier of interrogation ZU System function Cause of transmission (COT) COT = 9 .. General interrogation initiation not evaluated Cycle number (SCN) SCN = 0-255 .. Cycle number Beginning from 0, the cycle number is increased by 1 with each transmitted general interrogation command (per protective device). All data of a protective device subject to GI that are transmitted following a general interrogation command are transmitted with the cycle number of the general interrogation command. Note: The cycle number is not evaluated in the master station. Note: The IEC 60870-5-103 message in monitoring direction "General interrogation End" is not evaluated by the protocol element of the master station! ACTCON and ACTTERM for general interrogation request are not emulated by the protocol element of the master station! Functions Protocol Elements DC0-023-2.01 5-43 Interfacing of Portective Devices (103) Type identification 20: General Command Type identification 45, 46, 232: General Command (in the private range) The assignment of the message address for the spontaneous information object "general command" is carried out in the OPM II in the master station with the category firmware / transmit_command and in the remote terminal unit with the category firmware / receive_command. Elements of the Message (IEC 60870-5-101/104) BSE PRE Elements of the Message (IEC 60870-5-103) ZU Type identification TI 45 .. single command TI 46 .. double command Type identification 2) TI 20 .. General command TI 232 .. Command to protective device TI 45 .. Command with SELECT / EXECUTE TI 46 .. Command with SELECT / EXECUTE Private range Private range Private range Message address CASDU (CASDU1, CASDU2) IOA (IOA1, IOA2, IOA3) Cause of transmission (COT) <6> .. Activation <7> .. Confirmation of activation <8> .. Abortion of activation <9> .. Confirmation of the abortion of activation <10> .. Termination of activation P/N .. positive/negative confirmation T .. Test Originator address Qualifier of command QU <0> .. no additional definitions QU <1> .. Short command execution time QU <2> .. Long command execution time QU <3> .. persistent command S/E <0> .. execute S/E <1> ..select Single command (SCO) <0> .. OFF <1> .. ON Double command (DCO) <0> .. not allowed <1> .. OFF <2> .. ON <3> .. not allowed Message address CASDU .. Station address of the protection equipment FUN .. Function type INF .. Information number Parameter-settable Parameter-settable PREBSE (after reception of RM or TIO) not supported not supported 1) 1) 1) Parameter-settable Parameter-settable Parameter-settable Return information identification (RII) Parameter-settable Cause of transmission (COT) <20> .. general command <19> .. Only for ALSTOM <TI=232> 1) Only for <TI=45>, <TI=46> 1) PREBSE (after reception of RM or TIO) PREBSE (after reception of RM or TIO) not evaluated see Setting Control Location! Not supported only for IEC 60870-5-103 <TI=45,46> 1) Qualifier of command QU <0> .. no additional definitions QU <1> .. Short command execution time QU <2> .. Long command execution time QU <3> .. persistent command S/E <0> .. execute S/E <1> .. select Double command (DCO) <0> .. Not allowed <1> .. OFF <2> .. ON <3> .. not permitted 1) Command message in the private range of IEC 60870-5-103 to "ALSTOM" protection equipment (qualifier of command as for IEC 60870-5-101) only supported by master station! 2) TI is defined with the additional info in the OPM (see Special Functions). 5-44 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Special functions (SIP-message address conversion of the master station): • <0> = <1> = <2> = <3> = Additional info General command <TI=20> General command <TI=232> General command <TI=45,46> General command <TI=45,46> according to IEC 60870-5-103 to ALSTOM protective device in the "Private range" to ALSTOM protective device in the "Private range" with SELECT / EXECUTE to ALSTOM protective device in the "Private range" without SELECT / EXECUTE • Cross-over (exchange) of the double command states ON OFF during the message conversion IEC 60870-5-101 IEC 60870-5-103 • Return information monitoring time The master station monitors whether the return information for a command is received within a settable time from the remote terminal unit. With IEC 60870-5-103, the return information for the command is always transmitted with the address of the command. Emulation of Condition ACTCON+ - Return information is received from the protection equipment with COT=<20> or return information monitoring time = "0" ACTCON+ emulate from PRE to BSE ACTCON- - No return information received (return information monitoring time expired) - Return information is received from the protection equipment with COT=<21> ACTCON- emulate from PRE to BSE ACTTERM+ - Return information is received from the protection equipment with COT=<20> or return information monitoring time = "0" ACTTERM+ emulate from PRE to BSE ACTTERM- - No return information received (return information monitoring timeout) but ACTCON+ already transferred - Return information is received from the protection equipment with COT=<13> ACTTERM- emulate from PRE to BSE Legend: BSE ........Basic system element PRE........Protocol element Functions Protocol Elements DC0-023-2.01 5-45 Interfacing of Portective Devices (103) Type Identification 10: Generic Data (Setpoint Command) The assignment of the message address for the spontaneous information object "Generic Data (Setpoint Command)" is carried out in the OPM II with the category firmware / Send_generic_setpoint value (GDD=7). Elements of the Message (IEC 60870-5-101/104) BSE PRE Elements of the Message (IEC 60870-5-103) ZU Type identification TI 50 .. Setpoint command, short floating point number Type identification TI 10 .. Generic data Setpoint Command Message address CASDU (CASDU1, CASDU2) IOA (IOA1, IOA2, IOA3) Cause of transmission (COT) <6> .. Activation <7> .. Confirmation of activation <8> .. Abortion of activation <9> .. Confirmation of the abortion of activation <10> .. Termination of activation P/N .. positive/negative confirmation T .. Test Originator address Parameter-settable Parameter-settable Message address CASDU .. Station address of the protection equipment FUN = 254 .. Generic function type INF = 250 .. Information number Generic function Cause of transmission (COT) <40> .. generic write command PREBSE (immediately by PRE) not supported not supported not supported positive not evaluated not evaluated Generic data description (data record) RII = 0 .. Return information identification NGD = 1 .. Number of generic data records GIN .. Generic identification number KOD = 1 .. Actual Value GDD [DATATYPE] = 7 .. IEEE STD 754 GDD [DATASIZE] = 4 .. 4 octets GDD [NUMBER] = 1 GDD [CONT] =0 Data short floating point number IEEE STD 754 32 Bit floating point value Identifier for setpoint command (QOS) QL <0> .. not defined QL <1..127> S/E <0> .. execute S/E <1> ..select Not supported Not supported Not supported Not supported 5-46 Parameter-settable Generic data GID = short floating point number (IEEE STD 754) DC0-023-2.01 Not supported parameter-settable GIN [ group, entry ] short Real IEEE STD 754 Number of data elements No following data elements 32 Bit floating point value Functions Protocol Elements Interfacing of Portective Devices (103) Type Identification 21: Generic Command (general interrogation command for generic data) The assignment of the message address for the spontaneous information object "Generic command (general interrogation command for generic data)" is carried out without parameter setting by the protocol element of the master station. The general interrogation command is transmitted selectively for every CASDU per Link-Address (station address of the protection equipment). Elements of the Message (SICAM 1703 internal) BSE PRE Elements of the Message (IEC 60870-5-103) Function code Information code Type identification TI 21 .. Generic command = 155 = 1 .. Source-GI request General interrogation request (SICAM 1703 internal) not evaluated Message address CASDU .. Station address of the protection equipment Message address CASDU .. Station address of the protection equipment FUN = 254 .. Generic function type INF = 245 .. Information number Cause of transmission (COT) <6> .. Activation T .. Test P/N .. positive/negative confirmation Originator address Not evaluated Not evaluated Not evaluated qualifier of interrogation not evaluated ZU General interrogation command for generic data Generic function Cause of transmission (COT) COT = 9 .. General interrogation initiation Generic data description (data record) RII = 0 .. Return information identification (=cycle number) Beginning from 0, the cycle number is increased by 1 with each transmitted general interrogation command (per protective device). All data of a protective device subject to GI that are transmitted following a general interrogation command are transmitted with the cycle number of the general interrogation command. Note: The cycle number is not evaluated in the master station. NOG = 0 .. Number of generic identifications Note: ACTCON and ACTTERM for general interrogation request are not emulated by the protocol element of the master station! Functions Protocol Elements DC0-023-2.01 5-47 Interfacing of Portective Devices (103) Type Identification 253: REYDISP termination of Private Data Response Frame Type Identification 254: REYDISP Parameter Frame Type Identification 255: REYDISP Parameter "Last Frame" The assignment of the message address for the spontaneous information object "user data container" is carried out in the OPM II with the category firmware / Sende_Container und der Kategorie firmware / Empf_Container. The parameter "Containter-type_Rec" and the parameter "Container-type_Tra" are to be set to "Reydisp container". (See also chapter "Transmission of Parameters for Reyrolle Protection Equipment") Elements of the Message (IEC 60870-5-101/104) BSE PRE Elements of the Message (IEC 60870-5-103) Type identification TI 142.. User data container Type identification TI 253 .. REYDISP termination of Private Data Response Frame TI 254 .. REYDISP Parameter Frame TI 255 .. REYDISP Parameter "Last Frame" Message address CASDU (CASDU1, CASDU2) IOA (IOA1, IOA2, IOA3) Cause of transmission (COT) <3> .. spontaneous T .. Test P/N .. positive/negative confirmation Originator address User data part User data container for REYDISP parameter data Parameter-settable Parameter-settable Message address CASDU .. Station address of the protection equipment FUN = xx .. is not evaluated! INF = xx .. is not evaluated! 1) 1) Cause of transmission (COT) COT = xx .. is not evaluated! 1) ZU Monitoring direction control/monitoring direction control/monitoring direction Parameter-settable Not evaluated Not evaluated Not evaluated IEC 60870-5-103 message formats for the transmission of REYDISP parameter data are transmitted in the user data part of the user data container. 1) These items of information are copied 1:1 from the user data container into IEC 60870-5-103 without assessment. 5-48 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Type Identification 23: Disturbance Event Overview Type Identification 24: Order to Transmit Disturbance Data Type Identification 25: Acknowledgement for Disturbance Data Transmission Type Identification 26: Ready to Transmit Disturbance Data Type Identification 27: Ready to Transmit One Channel Type Identification 28: Ready to Transmit Marks Type Identification 29: Transmission of Marks Type Identification 30: Transmission of Disturbance Values Type Identification 31: Transmission End The assignment of the message address for the spontaneous information object "user data container" is carried out in the OPM II with the category firmware / Trans_Container and the category firmware / Rec_Container. The parameter "Containter-type_Rec" and the parameter "Container-type_Tra" are to be set to "Disturbance record container". (See also in chapter "File Transfer") BSE PRE Elements of the Message (IEC 60870-5-101/104) Type identification TI 142 .. User data container User data container for disturbance record transmission Message address CASDU (CASDU1, CASDU2) IOA (IOA1, IOA2, IOA3) Parameter-settable Parameter-settable Cause of transmission (COT) <3> .. spontaneous <6> .. Activation T .. Test P/N .. positive/negative confirmation Originator address in monitoring direction in control direction not evaluated not evaluated not evaluated User data part 1) ZU Elements of the Message (IEC 60870-5-103) Type identification TI 23 .. Disturbance event overview TI 24 .. Order to Transmit Disturbance Data TI 25 .. Acknowledgement for Disturbance Data Transmission TI 26 .. Ready to Transmit Disturbance Data TI 27 .. Ready to Transmit One Channel TI 28 .. Ready to Transmit Marks TI 29 .. Transmission of Marks TI 30 .. Transmission of Disturbance Values TI 31 .. Transmission End Monitoring direction Control direction Control direction Monitoring direction Monitoring direction Monitoring direction Monitoring direction Monitoring direction Monitoring direction Message address CASDU .. Station address of the protection equipment FUN = 255 .. Only for TI 24 2) INF = 0 … only for TI 24 2) Cause of transmission (COT) <31> .. only with TI 24 Parameter-settable 2) 1) IEC 60870-5-103 message formats for the transmission of files are transmitted in the user data part of the user data container. 2) These items of information only have the specified values with TI 24 – with all other TI's these items of information are copied 1:1 from the user data container into IEC 60870-5-103 without assessment. Functions Protocol Elements DC0-023-2.01 5-49 Interfacing of Portective Devices (103) Type Identification 1: Binary Information with Time Stamp Type Identification 2: Binary Information with Relative Time The assignment of the message address for the spontaneous information object "binary information" is carried out in the OPM II in the master station with the category firmware / Rec_binary information and in the remote terminal unit with the category firmware / Trans_binary_information. Elements of the Message (IEC 60870-5-101/104) Type identification (with time stamp CP56Time2a) TI 30 .. Single-point information TI 31 .. Double-point information TI 32 .. Measured value, short floating point number TI 38 .. Protection event TI 39 .. Blocked activation of protection TI 40 .. Blocked triggering of the protection Message address CASDU (CASDU1, CASDU2) IOA (IOA1, IOA2, IOA3) Cause of transmission (COT) <3> .. spontaneous <20> .. Interrogated by station interrogation <12> .. Return information, caused by a local command <11> .. Return information, cause by a remote command T .. Test P/N .. positive/negative confirmation Originator address Quality descriptor BL = 0 .. blocked SB = 0 .. substituted NT .. not topical IV EI 5-50 = x .. invalid = 0 .. Elapsed time (0/1 = valid/invalid) BSE PRE Only for relative time as measured value Parameter-settable Parameter-settable Elements of the Message (IEC 60870-5-103) ZU Type identification TI 1 .. Binary information with time stamp TI 2 .. Binary information with relative time 1) Message address CASDU .. Common address of ASDU FUN .. Function type INF .. Information number Cause of transmission (COT) <1> .. spontaneous <9> .. General interrogation <11> .. Local operation <12> Parameter-settable Parameter-settable Parameter-settable 2) .. Remote operation Not defined Not used Not used Emulated by the basic system element on failure of the protocol element or the remote terminal unit only TI 39,40 Not used DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Elements of the Message (IEC 60870-5-101/104) - Double-point information state (DPI) - Binary information state (ES) <0> .. undetermined state <1> .. OFF <2> .. ON <3> .. undetermined state BSE PRE only TI 31 only TI 38 intermediate position faulty position Time CP56Time2a ... Dual time with 7 octets Elements of the Message (IEC 60870-5-103) ZU Double-point information (DPI) <0> .. not used <1> .. OFF <2> .. ON <3> .. not used Time CP32Time2a ... Dual time with 4 octets start events of protection equipment SRD .. start of operation in reverse direction SIE .. start of operation IE (earth current) SL3 .. start of operation phase L3 SL2 .. start of operation phase L2 SL1 .. start of operation phase L1 GS .. General start of operation only TI 39 The IEC 60870-5-103 binary information state can be assigned one of these binary informations Binary information to the output current of the protection equipment CL3 .. command to output circuit phase L3 CL2 .. command to output circuit phase L2 CL1 .. command to output circuit phase L1 GC .. General command to output circuit only TI 40 The IEC 60870-5-103 binary information state can be assigned one of these binary informations - Measured value, short floating point number - Elapsed time (CP16Time2a) - relay duration time (CP16Time2a) - relay operation time (CP16Time2a) only TI 36 (relative time as measured value) only TI 38 only TI 39 only TI 40 Relative time (CP16Time2a) - Measured value, short floating point number only TI 36 Fault number Additional information (SIN) 3) 1) Binary information with relative time is not supported by SICAM 1703 remote terminal unit! 2) Binary information with other causes of transmission are discarded! 3) Controlling station: not evaluated! Controlled station: In monitoring direction the additional information (SIN) is used as follows: Cause of transmission = general interrogation SIN = cycle number of the GI-command Cause of transmission = command acknowledgement SIN = return information identification of the command Cause of transmission = other SIN = not used! Functions Protocol Elements DC0-023-2.01 5-51 Interfacing of Portective Devices (103) Suggestions for the SIP message address conversion of the master station: 5-52 • Type information (selection of the data to be converted from the IEC 60870-5-103 message) From IEC 60870-5-103 messages in the format "Binary information with time stamp", the state of the double-point information can be converted to a IEC 60870-5-101/104 message format. The correct type identification (TI) is to be parameterized for the selected data. From IEC 60870-5-103 messages in the format "Binary information with relative time", the state of the double-point information or the relative time or the fault number can be converted to IEC 60870-5-101/104 message format. The correct type identification (TI) is to be parameterized for the selected data. For every data type selected, a routing record must be entered in the SIP message address conversion. • Additional info ... binary information type With additional info "only coming binary information", after the transfer of the received binary information "coming", the binary information "going" is emulated by the protocol element with the "received time + 10 ms". • GI-initiation ... Initiation of a general interrogation command on reception of this binary information • Double-point information assignment With this function, 2 received single-point informations can be converted to one double-point information. Note: For both single-point informations, the same SICAM 1703 address of the double-point information must be parameterized! • Intermediate/faulty position suppression_t: (intermediate/faulty position suppression time) If no intermediate/faulty position suppression time is parameterized, then a received double-point information is transferred immediately to the basic system element. With intermediate/faulty position suppression time parameterized, a received double-point information with intermediate or faulty position is not transferred to the basic system element. The double-point information is buffered on the protocol element and an intermediate or faulty position suppression is performed. If a valid switching state (ON or OFF) is received during the suppression time, then this double-point information state is transferred immediately to the basic system element and the intermediate/faulty position suppression handling is terminated. After expiry of the suppression time, the intermediate/faulty position of the double-point information is transmitted to the basic system element. DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Type Identification 33: Binary Information with Time Stamp Type Identification 65: Single-Point Information Type Identification 66: Single-Point Information with Time Stamp Type Identification 67: Double-Point Information Type Identification 68: Double-Point Information with Time Stamp The assignment of the message address for the spontaneous information object "binary information" is carried out in the OPM II in the master station with the category firmware / Empf_Meldung. Elements of the Message (IEC 60870-5-101/104) BSE PRE Type identification (with time stamp CP56Time2a) TI 30 .. Single-point information TI 31 .. Double-point information Message address CASDU (CASDU1, CASDU2) IOA (IOA1, IOA2, IOA3) 1a) 1b) Elements of the Message (IEC 60870-5-103) ZU Type identification TI 33 .. Binary information with time stamp 1a) TI 65 .. Binary information without time stamp 1b) TI 66 .. Binary information with time stamp 1b) TI 67 .. Binary information without time stamp 1b) TI 68 .. Binary information with time stamp 1b) Parameter-settable Parameter-settable Message address CASDU .. Common address of ASDU FUN .. Function type INF .. Information number Parameter-settable Parameter-settable Parameter-settable Binary information with time stamp SEG-protective device – private range! Binary information with time stamp ALSTOM-protective device – private range! Functions Protocol Elements DC0-023-2.01 5-53 Interfacing of Portective Devices (103) Type Identification 4: Real-Time Measured Values with Relative Time The assignment of the message address for the spontaneous information object "measured value" is carried out in the OPM II in the master station with the category firmware / Empf_Messwert. Elements of the Message (IEC 60870-5-101/104) BSE PRE Type identification (with time stamp CP56Time2a) TI 34 .. Measured value, normalized value TI 35 .. Measured value, scaled value 1) TI 36 .. Measured value, short floating point number Message address CASDU (CASDU1, CASDU2) IOA (IOA1, IOA2, IOA3) Parameter-settable Parameter-settable Elements of the Message (IEC 60870-5-103) ZU Type identification TI 4 .. Real-time measured values with relative time Fault location values Message address CASDU .. Common address of ASDU FUN .. Function type INF .. Information number Parameter-settable Parameter-settable Parameter-settable 1) ... Short-circuit location values that are converted to the IEC 60870-5-101/104 message format "<TI35> measured value, scaled value with time stamp", can, if necessary, be multiplied by a parameter-settable factor before the conversion. As a result, the places after the decimal point that are otherwise truncated can be shown in the new format. The factor can be set with the parameter advanced parameters | multiplication factor for fault location value (fract.digit). 5-54 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.5.2. Message Conversion IEC 60870-5-101 IEC 60870-5-101 If the IEC 60870-5-103 protocol element in the remote terminal unit is used on an integrated (local) interface, the if necessary the transmission protocol can be switched over from IEC 60870-5-103 to IEC 60870-5-101. As a result, no additional configuration of a protocol element is necessary. This is only meaningful, if a SICAM 1703 master station is used and all remote terminal units are also connected with IEC 60870-5-101. In this case, the otherwise necessary message conversion from IEC 60870-5-103 IEC 60870-5-101 can be omitted and the messages are transferred 1:1 in transmit/receive direction. The remote terminal unit then behaves like a IEC 60870-5-101 remote terminal unit in multi-point traffic. Data in transmit direction are transferred from the basic system element to the protocol element in the SICAM 1703 internal IEC 60870-5-101/104 format. These are converted by the protocol element to the IEC 60870-5-101 message format on the line and transmitted according to the transmission procedure of the protocol. Data in receive direction are converted by the protocol element from IEC 60870-5-101 format on the transmission line to a SICAM 1703 internal IEC 60870-5-101/104 format and transferred to the basic system element. Functions Protocol Elements DC0-023-2.01 5-55 Interfacing of Portective Devices (103) 5.5.3. Message Conversion IEC 60870-5-101 IEC 60870-5-103 (101) The transmission protocol IEC 60870-5-103 is implemented on the line. With this operation mode, all data in IEC 60870-5-101 format between SICAM 1703 master/remote terminal units are transmitted with a user data container in the private range of IEC 60870-5-103. As a result, between SICAM 1703 systems, no parameterization of the address conversion IEC 60870-5-101 IEC 60870-5-103 is required. The data transmission to protection equipment (remote terminal units) of other manufacturers is carried out according to IEC 60870-5-103. Data messages are transmitted from the basic system element in SICAM 1703 internal IEC 60870-5-101/104 message format to the protocol element and transmitted from this 1:1 in a IEC 60870-5-103 user data container message (in the private range) defined for SICAM 1703. In receive direction, the IEC 60870-5-101 message format is read out from the user data container and transferred to the basic system element in the SICAM 1703 internal IEC 60870-5-101/104 message format. The operating mode for the message conversion (101-Mode) is signaled to the master station from the 1703 Bay-Controller with the startup signal. Hints: - In the master station and in the remote terminal unit, the IEC-parameters (number of bytes for COT, CASDU, IOA) must be set identical. - In the master station (ACP 1703), in the receive detailed routing the message conversion for a binary information (IEC 60870-5-103 IEC 60870-5-101) must be entered, even if this is not received due to the parameterized address conversion IEC 60870-5-101 IEC 60870-5-103(101). This "Dummy parameter setting" is presently required due to the "self-teaching data flow" in ACP. IEC 60870-5-103 User Data Container <TI=200> 27 26 25 24 23 22 21 20 Type identification SQ T 1 P/N 1 = spontaneous variable structure qualifier : Cause of transmission : Z U: = 255 Z U: = device address CASDU (common address of ASDU) : Z U: = 178 Z U: = 178 FUN (function type) : Z U: = 0 Z U: = 0 INF (information address) Type identification SQ T IEC 60870-5-103 variable structure qualifier P/N IEC 60870-5-103 IEC 60870-5-101 : Cause of transmission Originator address CASDU1 CASDU2 IOA1 IOA2 IOA3 : : : : : : : : : : : : : : : : : : : : : : : : IEC 60870-5-101 5-56 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.5.4. Blocking The data transmission according to IEC 60870-5-103 defines no blocking! The protocol element of the remote terminal unit thus also does not support any blocking in the "IEC 60870-5-103" operating mode of the interface. The protocol element of the remote terminal unit supports other operating modes for the operation with a SICAM 1703 master station, with which the transmission of IEC 60870-5-101 message formats can be performed without conversion to IEC 60870-5-103. With the "IEC 60870-5-101" operating mode of the interface, the transmission procedure according to IEC 60870-5101 is implemented with IEC 60870-5-101 message formats. With the "IEC 60870-5-103(101)" operating mode of the interface, the transmission procedure according to IEC 60870-5-103 is implemented with IEC 60870-5-101 message formats. For the optimum utilization of the transmission paths, with the data transmission with IEC 60870-5-101 message formats, the "Blocking" according to IEC 60870-5-101 is implemented. This function is performed on the basic system element (BSE) according to the rules applicable for this. Data to be transmitted are thereby already blocked on the basic system element and passed on to the protocol element for transmission. Received data in blocked format according to IEC 60870-5-101 are passed on from the protocol element to the basic system element in blocked format. On the basic system element the blocked data are split up again into individual information objects by the detailed routing function and passed on as such to the further processing. The parameters necessary for the blocking are to be set on the basic system element (BSE) in the IEC 60870-5-101/104 parameter block. 5.5.5. Class 1, 2 Data Measured values are normally transmitted from the protection equipment (remote terminal units) as "Class 2 data" and all other information as "Class 1 data". If protection equipment only supply "Class 1 data", then the master station can omit an interrogation for "Class 2 data" for these stations. For this the type of data interrogation can be determined selectively for every remote terminal unit in the master station in the parameters for the station definition with the parameter Stationsdefinition | Datenpriorisierung. In the "IEC 60870-5-103" operating mode of the interface, the protocol element of the remote terminal unit supports class 1 data and class 2 data according to IEC 60870-5-103. The assignment of the data to class 1 data or class 2 data is performed by the protocol element of the remote terminal unit without necessary parameterization. If binary information are to be transmitted from the remote terminal unit, these are buffered on the protocol element until these class 1 data are interrogated by the master station. Class 1 data stored for transmission are indicated to the master station with ACD-Bit=1 in the control field of every message. In the "IEC 60870-5-101" and "IEC 60870-5-103(101)" operating mode of the interface, only class 2 data are supported! SICAM 1703 internal mechanisms for the prioritization of the data to be sent provide extensive options in order to be able to transmit important data to the master station. Functions Protocol Elements DC0-023-2.01 5-57 Interfacing of Portective Devices (103) 5.5.6. Special Functions For the coupling of protection equipment, if necessary the following special functions can be activated for the adaptation of the message conversion: • • • • • • • • Send short-circuit location values with GI Resetting the short-circuit location values Signaling / measured value disabling Technological adaptation for measured values Measured value change monitoring Monitoring intermediate and faulty positions of double-point information Transfer of the information "blocked activation/tripping of the protection" Transmit non-updated process images 5.5.6.1. Send Short-Circuit Location Values with GI With general interrogation, short-circuit location values are not transmitted from the protection equipment. If the short-circuit location values are also expected with general interrogation in higher-level control centre systems, then with a general interrogation these can be emulated by the protocol element from the internal process image. This function is set with the parameter advanced parameters | send fault location values within GI. 5.5.6.2. Resetting the Short-Circuit Location Values Short-circuit location values are transmitted from the protection equipment in monitoring direction with the type identification "<TI=4> real-time measured values with relative time". Short-circuit location values are not reset by the protection equipment! For the processing of the short-circuit location values in the control centre system, the protocol element provides the following special functions: • • Reset short-circuit location values with command Reset short-circuit location values automatically The short-circuit location values are reset in the internal process image of the protocol element and from this emulated spontaneously to the BSE with the parameterized initial values. A large number of short-circuit location values to be emulated with initial value, can soon lead to a high data load in the system, through which problems can occur with the further distribution in the system. The resetting of the short-circuit location values can be slowed with the parameter advanced parameters | send initial values with delay. Thereby, a parameterized pause is always maintained after 5 short-circuit location values emulated with initial value (=measured value messages). The pause is also parameterized with the parameter advanced parameters | send initial values with delay. 5-58 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.5.6.2.1. Reset the Short-Circuit Location Values with Command After the spontaneous transmission of the short-circuit location values from the protective devices, these can be reset on the protocol element with a special command message. The reset short-circuit location values are transmitted spontaneously from the protocol element with the parameterized initial value. The assignment of the message address for the spontaneous information object "Command to reset the shortcircuit location values" is carried out in the OPM II with the category firmware / Transmit_Command_Reset_shortcircuit location. With an IEC 60870-5-101/104 command message, all short-circuit location values received from one protection device (<TI=4> real-time measured values with relative time), can be reset in the process image of the protocol element of the master station. A specific command message must be used for each protective device (i.e. per LINK-address). This command is not transmitted, rather only processed "protocol element internal". The short-circuit location values are reset to the parameter-settable "Initial value". The initial values for the short-circuit location values can be parameterized for the various IEC 60870-5-101/104 measured value formats with the parameter advanced parameters | initialization value 16 bit normalized (TI 34), the parameter advanced parameters | initialization value 16 bit scaled (TI 35) and the parameter advanced parameters | initialization value Floating Point (TI 36). 5.5.6.2.2. Reset Short-Circuit Location Values automatically After the spontaneous transmission of the short-circuit location values from the protective devices, these can be reset by the protocol element after a parameter-settable time. The reset short-circuit location values are transmitted spontaneously from the protocol element with the parameterized initial value. This function is activated with the parameter advanced parameters | Fehlerortwerte rücksetzen and the parameter advanced parameters | imitate initialization values. In addition, with the parameter advanced parameters | Fehlerortwerte rücksetzen the delay time is also set. The initial values for the short-circuit location values can be parameterized for the various IEC 60870-5-101/104 measured value formats with the parameter advanced parameters | initialization value 16 bit normalized (TI 34), the parameter advanced parameters | initialization value 16 bit scaled (TI 35) and the parameter advanced parameters | initialization value Floating Point (TI 36). The IEC 60870-5-101/104 format for every short-circuit location value is parameterized in the SIP message address conversion. Functions Protocol Elements DC0-023-2.01 5-59 Interfacing of Portective Devices (103) 5.5.6.3. Signaling / Measured Value Disabling The signaling / measured value disabling is a function of the protection equipment and can be activated globally (for binary information and measured values together) for example by means of a keylock switch or by means of a control input in the protection equipment. Through the signaling / measured value disabling function, the spontaneous transmission of the data from the protection equipment to the master station is deactivated. With activation/deactivation of the signaling / measured value disabling in the protection equipment, the signal "signaling / measured value disabling" is transmitted spontaneously to the master station. The signaling / measured value disabling is transmitted as last signal with activation and as first signal with deactivation. With activation of the signaling / measured value disabling, the data concerned are not emulated to the basic system element by the protocol element of the master station with the status "Blocked" in the IEC 60870-5-101/104 format. With deactivation of the signaling / measured value disabling, to update the data a general interrogation can be triggered to the protection equipment by the protocol element of the master function. So that the general interrogation can be triggered with deactivation of the signaling / measured value disabling, the information "signaling / measured value disabling" of the protection equipment must be entered in the SIP message address conversion in receive direction with the category firmware / Rec_binary_information. In addition, in the category the setting "initiate GI with going edge" must be selected in the field GI-initiation. 5.5.6.4. Technological Adaptation for Measured Values The technological adaptation enables the measured value supplied by the protection equipment to be transformed into a technological or normalized value. Into which value conversion can take place, is dependent on the format of the spontaneous information object "Measured value" to be transferred. Spontaneous Information Object Measured value, normalized value Value Range -15 - 1 ... + 1-2 Measured value, scaled value - 32768 ... + 32767 Measured value, short floating point - 8,43 * 10-37 ... + 3,37 * 1038 Meaning normalized, percental representation technological, integer technological, floating point Depending on the protocol element, the parameters for the technological adaptation are parameterized per measured value as • • adaptation line with 2 interpolation points (X_0%, X_100%, Y_0%, Y_100%) or adaptation line with "kx+d" . The received measured value is adapted linear according to the parameter setting by the protocol element before transfer to the basic system element. The adaptation line with 2 interpolation points is to be parameterized for each measured value with the parameters "X_0%", "X_100%", "Y_0%" and "Y_100%". For this, the technological value Y0 is parameterized for the lower limit of the measuring range X0 and the technological value Y100 for the upper limit of the measuring range X100. The adaptation line with "kx+d" is to be parameterized for each measured value with the parameters "Faktor_k" and "Offset_d". 5-60 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Bipolar measured values without zero-range suppression and plausibility check Example: Value Meaning Parameter X0 -2000 lower boundary of the measuring range (set by parameter) X_0% X100 +2000 upper boundary of the measuring range (set by parameter) X_100% Y0 -1 technological value at X0 Y100 +1 technological value at X100 Y100 Y_0% Y_100% Normalized value X0 X100 Y0 Data point quality descriptor IV OV 0 Functions Protocol Elements DC0-023-2.01 5-61 Interfacing of Portective Devices (103) 5.5.6.5. Measured Value Change Monitoring Measured values are transmitted from some protection equipment with the smallest changes in measured value or even cyclic. So as not to load the following transmission facilities unnecessarily, the measured value is monitored for change in accordance with the following rules: • The first value received after startup is transmitted immediately • Every change of the quality descriptors blocked, invalid or overflow triggers an immediate transmission • Change monitoring in accordance with the method of the additive threshold value procedure Additive threshold value procedure In the parameterized processing grid the measured value is monitored for change. If the deviation from the last spontaneously transmitted measured value is greater than the parameterized "Threshold_absolute", the new measured value is transmitted immediately. Otherwise, in the parameterized processing grid the deviations from the last spontaneously transmitted measured value are totalled according to the polarity sign. Only when the amount of this total exceeds the parameterized Thresh_additive is the current measured value spontaneously transmitted. A transmission of the measured value due to a general interrogation does not influence the threshold value procedure. By means of parameterization it is established: ─ ─ ─ ─ Processing grid Threshold_Unit (optional) Thresh_uncond Thresh_additive 1s % 0.00% 0.0% - 25.5s 103.00% 1000.0% or or or Absolute 0.0 - 999.9 0.0 - 999.9 The percentages given refer to the parameterized value for Y100 – Yat X=0. The processing grid is to be parameterized for all measured values with the parameter advanced parameters | Measured value thresholds | cycle time for measured change monitoring. The thresholds are to be parameterized depending on the protocol element either for every measured value with the parameter thresh_additive and the parameter thresh_uncond or one can be selected from max. 16 parameter-settable measured value thresholds for each measured value with the parameter Measured value threshold. The measured value thresholds are to be parameterized with the parameters advanced parameters | Measured value thresholds | "thresh_additive 0, 1, 2 .. 15 and the parameter advanced parameters | Measured value thresholds | "thresh_uncond 0, 1, 2 .. 15. 5-62 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) The following example describes a standard case, in which the adaptation line goes through the zero point (origin) (Yat X=0 = 0). Examples Technological value Y100 Processing grid Thresh_uncond Thresh_additive Example 1: 4000 0.1s 2.00% 150.0% represents a change of 80 represents an additive total of 6000 After transmission due to the exceeding of the large threshold, the value has changed once by 79 (< the large threshold) and subsequently remains constant. The measured value is transmitted after 7.5 seconds. 0.0s 0.1s 0.2s 0.3s 0.4s 0.5s 0.6s 0.7s 0.8s ... 7.4s 7.5s Measured value 300 379 379 379 379 379 379 379 379 ... 379 379 Difference >80 79 79 79 79 79 79 79 79 ... 79 79 Additive total 0 79 158 237 316 395 474 553 632 ... 5925 6004 Transmission x Example 2: x After transmission due to the exceeding of the large threshold, the value has changed once by 1 (< the large threshold) and subsequently remains constant. The measured value is transmitted after 10 minutes. 0.0s 0.1s 0.2s 0.3s 0.4s 0.5s 0.6s 0.7s 0.8s ... 599.9 600s Measured value 300 301 301 301 301 301 301 301 301 ... 301 301 Difference >80 1 1 1 1 1 1 1 1 ... 1 1 Additive total 0 1 2 3 4 5 6 7 8 ... 5999 6000 Transmission x Example 3: x After transmission due to the exceeding of the large threshold, the value continually changes by ±1. The measured value is not transmitted. 0.0s 0.1s 0.2s 0.3s 0.4s 0.5s 0.6s 0.7s 0.8s ... 7.4s 7.5s Measured value 300 301 300 299 300 301 300 301 299 ... 300 301 Difference >80 1 0 -1 0 1 0 1 -1 ... 0 1 Additive total 0 1 0 1 0 1 0 1 1 ... 0 1 Transmission x Functions Protocol Elements DC0-023-2.01 5-63 Interfacing of Portective Devices (103) 5.5.6.6. Monitoring Intermediate and Faulty Positions of Double-Point Information Double-point information that are transmitted from the protection equipment, or single-point information that are transmitted from protection equipment and converted to double-point information on the protocol element, can be monitored by the protocol element for intermediate and faulty position. (in most cases protection equipment do not have any monitoring for intermediate and faulty position implemented) Thereby, the transfer of an intermediate position (neither ON- nor OFF binary information exists) or a faulty position (both ON- as well as OFF binary information exists) is suppressed by the protocol element for a parameter-settable time. On reception of a double-point information with intermediate or faulty position, a monitoring time is started and the double-point information is not transferred. If the double-point information is received during the monitoring time with valid binary information state (ON or OFF), the monitoring time is stopped and the double-point information with the valid binary information state is transferred. On expiry of the monitoring time, the double-point information with the state "intermediate or faulty position" is transferred with the received time. The assignment of the message address for the spontaneous information object "Double-point information" is carried out in the OPM II with the category SIP-Telegrammadressumrechnung /... / firmware / Receive_information. A suppression time can be parameterized for the suppression of intermediate and faulty position for each doublepoint information (parameter Diff-/Störunterdrückungs_t). 5-64 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.5.6.7. Transfer of the Information "Blocked Activation/Tripping of the Protection" Disturbance information from protection equipment can be transferred in the direction IEC 60870-5-101/104 with the message formats provided especially for this "blocked activation of protection" and "blocked triggering of protection". With the message "blocked activation of protection" several protection activation signals and the relay duration time are transmitted. With the message "blocked triggering of protection" several binary informations are transmitted to the output current circuit of the protective device and the relay operation time. IEC 60870-5-101/104 IEC 60860-5-103 <TI=39> Blocked activation of protection with time stamp <TI=2> Binary information with relative time <TI=40> Blocked triggering of protection with time stamp <TI=2> Binary information with relative time <TI=39> Blocked Activation of Protection with Time Stamp Start events of Protection Equipment (SPE) GS SL1 SL2 SL3 SIE SRD general start of operation start of operation phase L1 start of operation phase L2 start of operation phase L3 start of operation IE (earth current) start of operation in reverse direction <TI=40> Blocked Triggering of Protection with Time Stamp Binary information to the output current circuit of the protection equipment (OCI) GC CL1 CL2 CL3 general command to output circuit command to output circuit phase L1 command to output circuit phase L2 command to output circuit phase L3 IEC 60860-5-103 Disturbance Information 1) <INF=84> <INF=64> <INF=65> <INF=66> <INF= > <INF= > general start of operation activation L1 activation L2 activation L3 IEC 60860-5-103 Disturbance Information 1) <INF=68> <INF=69> <INF=70> <INF=71> General triggering triggering L1 triggering L2 triggering L3 1) INF ... the specified information number represents the default values according to IEC 60870-5-103 (protection equipment can also transmit these disturbance binary informations with different address) The assignment of the message address for the spontaneous information object "blocked activation/triggering of protection" is carried out in the OPM II with the category SIP-message address conversion /... / firmware / Rec_packed_start_event_output_circuit. The disturbance binary information are always transmitted from the protection equipment as single binary information messages. For the transfer with the IEC 60870-5-101/104 message format, the binary information state of several start events of protection equipment and a relay duration time/relay operation time (relative time) are transmitted in one message. The moment of transfer of the IEC 60870-5-101/104 message can be determined with the parameter advanced parameters | packed start events/output circuit of protection equipment. • • • Transfer with change of a binary information state Transfer only with going general start of operation or trip information The message is time stamped again by the protocol element with the transfer. Transfer only with going general start of operation or trip information. With the transfer, the message is time stamped by the protocol element with the time of the coming general start of operation or trip information. Functions Protocol Elements DC0-023-2.01 5-65 Interfacing of Portective Devices (103) Transfer with change of a binary information state The message "blocked activation of protection" or "blocked triggering of protection" is transferred with each binary information change in the message. As relay duration time/relay operation time the relative time of the changed disturbance information is entered. Transfer only with going general start of operation or trip information (time from PRE) IEC 60870-5-103 disturbance information are only received by the protocol element after coming disturbance information for general activation /-tripping and buffered until transfer of the IEC 60870-5-101/104 message "blocked activation/triggering of protection“. The message "blocked activation of protection" or "blocked triggering of protection" is only transferred after reception of the going disturbance information for general activation/-triggering. As relay duration time/relay operation time the relative time of the going disturbance information is entered. If no going disturbance information arrives within 60 seconds after a coming disturbance information for general activation/-triggering, then the message "blocked activation of protection" or "blocked triggering of protection" is transferred by the protocol element. As relay duration time/relay operation time the relative time of the last changed disturbance information is entered. Transfer only with going general start of operation or trip information (time from protection) The function is identical as for "Transfer only with going general start of operation or trip information (time from PRE)", but with the transfer the message is time stamped by the protocol element with the time of the coming general activation or trip information (time from the protection equipment). 5-66 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.5.6.8. Transmit Non-Updated Process Images After a general interrogation, the protocol firmware of the master station sends all non-received but parameterized data points for binary information with status "interrogated by station interrogation". The quality descriptor of the data points of failed remote terminal units is transmitted with "not topical". The emulation of these data points takes place after a fixed set time (number of stations * 5 seconds) – from transmission of the general interrogation command. The emulation of these data points can be deactivated with the parameter advanced parameters | not updated process data base. The emulation of the data not received for GI must then be deactivated, if in combination with the automatic data flow routing in ACP 1703 a general parameter setting (surplus) for the data of protection equipment is used. The reason is, that the protection equipment are not always configured the same, i.e. they do not always supply the same volume of data. In this case, data have been emulated by the protocol element following a general interrogation, which are possibly not transferred at all by the protection equipment. If in the master station a surplus quantity of the data model is parameterized, emulated but not received data points would always be signaled as "faulty". Functions Protocol Elements DC0-023-2.01 5-67 Interfacing of Portective Devices (103) 5.6. Protocol Element Control and Return Information This function is used for the user-specific influencing of the functions of the protocol elements. This function contains two separate independent parts: • Protocol element control • Protocol element return information The Protocol Element Control enables: • Applicational control of the station interrogation • Setting control location • Testing the reachability of stations • the suppression of errors with intentionally switched-off stations (Station Service) The Protocol Element Return Information enables: • States of certain state lines to be used as process information • the obtaining of station interrogation information • Information about the station status/failure to be obtained Internal distribution for messages with process information Block Diagram Protocol element control Internal function Transmission route Protocol element return information Protocol element Messages with process information Messages with system information 5-68 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) 5.6.1. Protocol Element Control With the help of messages with process information, the protocol element control on the basic system element enables specific functions of the protocol elements to be controlled. The specific functions are determined by the protocol element implemented. The assignment of the messages with process information to the functions is carried out with the help of processtechnical parameters of the ACP 1703 system data protocol element control message. The messages for protocol control are transmitted immediately from the basic system element to the protocol element, regardless of the user data to be sent and the priority control. For messages with process information which are used in ACP 1703 as protocol element control message, an unused CASDU is to be used! All CASDU´s for process information are distributed automatically to the corresponding remote terminal unit. Functions Protocol Elements DC0-023-2.01 5-69 Interfacing of Portective Devices (103) Possible master station functions: Parameter Function SF Station Z-Par Call cycle START 0 125 - Call cycle STOP (disabling) 1 125 - Call cycle CONTINUE (enabling) 2 125 - Continuous call station x ON 3 0 – 99 065535 Continuous call station x OFF 4 0 – 99 - "Deactivate" interface 5 - - "Activate" interface 6 - - Note Z-Par=continuous call time (n * 100ms) Z-Par=0: Continuous call without time input (stopped by other function) - Reset interface failure - Do not send all messages from BSE - Received messages are discarded Send (general) interrogation command 240 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Send (general) interrogation command to GI-group 241 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Set control location Reset command Legend: **) 125 65535 SCS=<ON>: Set control location (HKA) (global) SCS=<OFF>: Delete all control locations (HKA's) (global) 0 – 99 65535 SCS=<ON>: Set control location (HKA) SCS=<OFF>: Reset control location (HKA) 242 243 This function is not presently supported by PRE! SF ............. Control function_(PRE) Station....... Station number 0 - 99 ......Station 0 - 99 of the selected protocol element 125 .........Station 0 - 99 of the selected protocol element (=BROADCAST) Z-Par......... Additional parameter_(PRE) SCS .......... single command state HKA .......... Originator address (HKA) = 0 – 255 The setting of the control location can only be performed with a single command <TK=45>! In the PRE-control message to the protocol element the additional parameter is set as follows. SCS = <OFF>........... Additional parameter = HKA+256 SCS = <ON> ............ Additional parameter = HKA **) If a PRE-control message is entered in the PST-detailed routing on the BSE, after startup of the PRE the BSE sends a PRE-control message "Set control location" to the PRE. As a result the function for evaluating the control location is activated on the PRE. 5-70 DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Possible remote terminal unit functions: Parameter Function SF Station Z-Par Note Send (general) interrogation command 240 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Send (general) interrogation command to GI-group 241 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Reset command 243 This function is not presently supported by PRE! Legend: SF..............Control function_(PRE) Station .......Station number Z-Par .........Additional parameter_(PRE) Functions Protocol Elements DC0-023-2.01 5-71 Interfacing of Portective Devices (103) 5.6.2. Protocol Element Return Information The protocol element return information on the basic system element generates messages with process information in monitor direction and thereby enables states of the protocol elements to be displayed or processed. There are three different categories of return information: • • • Status of the state lines Status of the stations Protocol-specific return information (dependent on the protocol element used) The assignment of the messages with process information to the return information is carried out on the basic system element with the help of process-technical parameters of the ACP 1703 system data protocol element return information. From which source the parameterized return information are to be generated, is set with the parameters "Supplementary system element" and "Station number". Messages for protocol element return information are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. Possible master station return information: Parameter Return information function_(PRE) Station Note Status DTR (1 = state line active) 255 (1) Status DSR (1 = state line active) 255 (1) Station status 0 – 99 1 = Station enabled for call cycle Station failure 0 – 99 1 = Station failed protocol-specific return information 0 255 Cycle IDLE - cycle control is stopped. User data messages will be sent furthermore. protocol-specific return information 1 255 Cycle NORMAL MODE - cycle control running in normal mode (cyclic RTU interrogation) protocol-specific return information 2 255 Continuous call - Continuous call of an RTU presently running protocol-specific return information 3 255 Cycle stopped - cycle has been stopped with PST – control message protocol-specific return information 6 255 Sending "Data to all" - User data message "to all" (BROADCAST) is now being transmitted protocol-specific return information 7 255 Sending "data message" - station-selective user data message is now being transmitted (1) States of the state lines are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. The spontaneous transmission of the current states takes place internally in a 100ms grid. State line changes shorter than 100ms are not guaranteed to be transmitted! Legend: 5-72 Station....... Station number 0 - 99 ......Station 0-99 of the selected protocol element 255 .........Station number not used! DC0-023-2.01 Functions Protocol Elements Interfacing of Portective Devices (103) Possible remote terminal unit return information: Parameter Return information function_(PRE) Station Status DTR (1 = state line active) 255 (1) Status DSR (1 = state line active) 255 (1) Station failure 0 Note 1 = Station failed (1) States of the state lines are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. The spontaneous transmission of the current states takes place internally in a 100ms grid. State line changes shorter than 100ms are not guaranteed to be transmitted! Functions Protocol Elements DC0-023-2.01 5-73 Interfacing of Portective Devices (103) 5-74 DC0-023-2.01 Functions Protocol Elements SICAM 1703 Field Bus (SFB) 6. SICAM 1703 Field Bus (SFB) The SICAM 1703 Field Bus describes a serial communications protocol with which a SICAM 1703 master station in multi-point traffic is connected with one or several SICAM 1703 remote terminal units over a communications link in a linear or star configuration. The data traffic is controlled by the master station and is optimized for the application as field bus. Either data messages or station interrogation messages are transmitted from the master station. Data from the remote terminal unit to the master station can only be transmitted as reply to a station interrogation. Master station TF TF TF TF Remote station-1 Remote station-2 Remote station-n n <= 100 Legende: TF ………..….. Transmission Facility In multi-point traffic an "unbalanced transmission procedure" is used. That means, that as primary station the master station initiates all message transmissions, while the remote terminal units, which are secondary stations, may only transmit when they are called. The multi-point traffic only requires a "half duplex" transmission medium and can be used in a star or linear structure. The master station and the remote terminal units in multi-point traffic operate with a communications protocol according to IEC 60870-5-101. Functions Protocol Elements DC0-023-2.01 6-1 SICAM 1703 Field Bus (SFB) General Functions The SICAM 1703 field bus is based on IEC 60870-5-101 and supports the following functions: Communication between one central station and up to 100 remote stations • Unbalanced multi-point (multi-point traffic) SFBMxx is controlling station (primary station), SFBSxx is controlled station (secondary station). ─ ─ ─ ─ Data acquisition by polling (station interrogation) Acquisition of events (transmission of data ready to be sent) General interrogation, outstation interrogation Clock synchronization − Cyclic, every 5 seconds ─ Command transmission ─ Transmission of integrated totals • Optimized parameters for selected transmission facilities • Functions for supporting redundant communication routes The operating mode of the interface is determined by parameters of the protocol element and optional equipment. Operating mode Unbalanced interchange circuit V.24/V.28 Parameter and Setting Asynchronous / Isochronous Interface Signals on RJ45 Connector TXD, RXD, GND, RTS, DTR, DSR/+5V, DCD, CTS Asynchronous V.28 asynchronous Optical interface (multimode fibre optic) Asynchronous / Isochronous RXD, TXD, CTS, DCD, DTR, DSR/+5V, GND Asynchronous with CM-0827 Balanced interface RS-485 RXD, TXD, CTS, RTS, DCD, DTR, DSR/+5V, GND V.11 asynchronous 6-2 DC0-023-2.01 Functions Protocol Elements SICAM 1703 Field Bus (SFB) 6.1. Communication 6.1.1. Data Acquisition by Polling (Station Interrogation) The transmission of the data from the remote terminal units to the master station takes place by means of stationselective station interrogations (interrogation procedure, polling), controlled by the master station; i.e., changed data are stored in the remote terminal unit and transmitted to the master station with the interrogation of this remote terminal unit. The interrogation procedure of the master station ensures, that remote terminal units are interrogated sequentially, whereby remote terminal units with important data are interrogated more often. Remote terminal units may only transmit when they are called. The interrogation procedure is performed continuously (= continuous cycle). The station-selective parameters of the master station for the interrogation cycle such as "Stat No", "Station Enabling", "Station failure", are to be set in the parameters in the Station definition. In every remote terminal unit, the station-selective address must be set with the parameter Common settings | Address of the link (=own station number). This address must be unambiguous for each field bus line. The prioritization of the station interrogation cannot be influenced through parameterization. The interrogation procedure executes a station change after every station interrogation. The interrogation procedure can be performed either continuously (= continuous cycle) or only on request. The control of the interrogation procedure on request can be realized with protocol control messages in the function diagram. In the running interrogation cycle, data and system messages are transmitted spontaneously from the master station according to the parameter setting as follows: • • One RTU selective (acknowledged) All RTU’s (unacknowledged) If the interrogation cycle has been stopped by protocol control messages or the listening mode is switched on, no station interrogation takes place. With the interrogation cycle stopped, spontaneous data messages continue to be transmitted to the remote terminal units. With listening mode switched on, the messages are normally not transmitted from the master station to the remote terminal units, rather discarded directly on the basic system element (BSE) by the function "User data filter". Functions Protocol Elements DC0-023-2.01 6-3 SICAM 1703 Field Bus (SFB) Example: Prioritization of the station interrogation Number of calls until station change = 1 (for all stations) Station change: Below, as an example, the prioritization of the station interrogation is shown for continuous cycle. t Z U0 U1 U2 U3 U4 U5 U6 U7 U8 U9 U10 Legend: …..….. Remote stations ,..…...….. Data message, short acknowledgement (remote station master station) ,…..….. Data message (Command), calling message (remote station master station) Z ………….….. Master station U0..U10 ….….. Remote station U0 .. Remote station U10 …………….. Command from master station remote station U0 t ………………. Continous station polling time (request) from remote station U0 (after command from master station remote station U0) For the interfacing of the SICAM 1703 remote terminal units with the field bus protocol according to IEC 60870-5101, the setting of the variable elements of the message is to be set as required. The following table provides an overview of which IEC-parameters are to be parameterized on which system elements. IEC 60870-5-101 Parameter Description bytes link address Number of octets for the address field of the link layer PRE Cause of transmission (COT) Number of octets for cause of transmission BSE Common address of ASDU (CASDU) Number of octets for common address of the ASDU BSE Information object address (IOA) Number of octets for the address of the information object BSE Acknowledgement on IEC 60870-5-102 layer Single character 1) PRE Maximum message length Time Stamp BSE Number of octets for time stamp 1) fixed by the protocol element! Legend: 6-4 System Element SSE = supplementary system element (with serial interfaces this is always configured with a PRE) PRE = Protocol element BSE = Basic system element DC0-023-2.01 Functions Protocol Elements BSE SICAM 1703 Field Bus (SFB) 6.1.1.1. Continuous Interrogation of a Remote Terminal Unit The "continuous interrogation of a remote terminal unit" can be switched on automatically in the master station with the function "Demand" or spontaneously with protocol control messages. With function activated, a station interrogation is always executed by the master station to only one selected station. An automatically started continuous interrogation of one remote terminal following a message transmission is known as a demand. The selection of the type identification and setting of the continuous interrogation time necessary for the "demand" can be performed in the parameters advanced parameters | call procedure per type identification. The selection of the type identifications is carried out with the parameters advanced parameters | call procedure per type identification | type identification A(TI) ..O(TI) and the setting of the continuous interrogation time assigned to the type identifications is carried out with the parameters advanced parameters | call procedure per type identification | continuous polling time for type identification A..O. Through a demand, following a message transmission (e.g. command, setpoint value) the master station can quickly fetch changed data from the remote terminal unit (e.g. measured values after command or setpoint value). With demand, the continuous interrogation of a remote terminal unit is terminated after timeout or a message to another remote terminal unit. With "continuous interrogation of a remote terminal unit" data messages continue to be transmitted to that remote terminal unit to which the function "continuous interrogation of a station" is switched on. 6.1.1.2. Acknowledgement Procedure All data messages transmitted selectively to a remote terminal unit must be acknowledged by this RTU. If, with nonfaulty transmission line, the acknowledgement is missing for longer than the expected acknowledgement time, transmitted messages are repeated up to n-times (n can be parameterized). On expiry of the number of retries, the station is flagged as faulty. The required expected acknowledgement time is determined automatically from the set parameters, but if necessary can be extended accordingly with the parameter advanced parameters | monitoring times | expected_ack_time_corr_factor. This is then the case if additional signal propagation delays, delay times or slow processing times of the connected remote terminal units must be taken into consideration. The number of retries is to be set in the master station for messages for station interrogation and data messages with the parameter Message retries | Retries for data message SEND/CONFIRM (station selective) or for messages for station initialization with the parameter Message retries | Retries for INIT-messages SEND/CONFIRM (station selective). The acknowledgement from the remote terminal unit to the master station is always transmitted with the single character (E5H). Functions Protocol Elements DC0-023-2.01 6-5 SICAM 1703 Field Bus (SFB) 6.1.1.3. Failure Monitoring in the Master Station The monitoring of the interface by the active master station takes place by means of the cyclic running interrogation procedure (station interrogation). A remote terminal unit is reported as failed by the master station after expiry of the number of retries. Retries to a remote terminal unit are thereby always sent in succession immediately after expiry of the expected acknowledgement time i.e. no other remote terminal units are interrogated during a running retry handling. For failed stations, a communication fault is only then reported if this is parameterized accordingly in the parameter "Station failure" of the Station definition. The failure of remote terminal units is thus detected by the master station during the normal interrogation cycle. Failed remote terminal units continue to be interrogated by the master station with the interrogation procedure, however no message retry is performed for such remote terminal units during the station interrogation. No data are transmitted from the master station to failed remote terminal units. The data are stored in the data storage of the communication function on the basic system element (BSE) until these are deleted by the dwell time monitoring or are transmitted to the non-failed remote terminal unit. 6.1.1.4. Failure Monitoring in the Remote Terminal Unit The monitoring of the interface in the remote terminal unit is carried out by monitoring for "cyclic station interrogation". The monitoring time is to be set in the remote terminal unit with the parameter advanced parameters | call monitoring time. In addition, with the parameter advanced parameters | call timeout retrigger also with "request status of link" it can also be set whether the monitoring time is to be retriggered not only by station-selective call or data messages, but also with station-selective messages for station initialization – these are only transmitted during the initialization phase. The monitoring time in the remote terminal unit must be set sufficiently high, so that this does not expire unintentionally during the transmission of larger quantities of data from other remote terminal units (e.g. during general interrogation). With failed interface, data to be transmitted are fetched by the protocol firmware and negatively acknowledged internally to the basic system element. As a result, the data are stored in the data storage on the basic system element (BSE) of the remote terminal unit until these are deleted by the dwell time monitoring or can be transmitted to the master station. 6-6 DC0-023-2.01 Functions Protocol Elements SICAM 1703 Field Bus (SFB) 6.1.2. Station Initialization After startup or redundancy switchover, the operation of the interface is begun after successful station initialization. The initialization of the link layer of the remote terminal unit is performed by the master station with: • • "Request for the status of the link layer (REQUEST STATUS OF LINK) Reset of the remote terminal unit link layer (RESET OF REMOTE LINK) Reset Command Function in the Remote Terminal Unit REQUEST STATUS OF LINK - "STATUS OF LINK" is transmitted to the master station RESET of REMOTE LINK - FCB-Bit (Frame Count Bit) is initialized - Acknowledgement for RESET of REMOTE LINK is transmitted to master station Initialization End The initialization end according to IEC 60870-5-101 is not supported by this protocol element! 6.1.3. Acquisition of Events (transmission of data ready to be sent) Data of the remote terminal unit ready to be sent are stored on the basic system element (BSE) in the remote terminal unit until transmission. For the optimization of the reaction time, up to 10 messages are already fetched by the protocol element in the remote terminal unit from the basic system element before a station interrogation and stored in the internal memory of the protocol element. With a station interrogation, a message is transmitted to the master station from the internal memory. If the internal memory on the protocol element is empty, the protocol element of the remote terminal unit function replies with a short acknowledgement ("have no more data"). 6.1.3.1. Message from the Remote Terminal Unit to the Master Station Messages from the remote terminal unit to the master station are only transmitted with station interrogation. A quick-check procedure for speeding up the transmission of data is not implemented. Functions Protocol Elements DC0-023-2.01 6-7 SICAM 1703 Field Bus (SFB) 6.1.4. General Interrogation, Outstation Interrogation The general interrogation (outstation interrogation) function is used to update the master station after the internal station initialization or after the master station has detected a loss of information. The function general interrogation of the master station requests the remote terminal unit to transmit the actual values of all its process variables. A general interrogation command "to all" triggered in the system is always transferred by the communications function on the basic system element (BSE) station-selective to the protocol element of the master station and also transmitted station-selective by this to the remote terminal units. 6.1.5. Clock Synchronization Setting the time The clock synchronization command is transmitted cyclic by the protocol element of the master station every 5 seconds to all remote terminal units with a BROADCAST message. Messages that are transmitted after a startup, but before the remote terminal unit has the correct time, contain the relative time from startup (reference day: 1.1.2001) with the flagging of the time stamp as invalid. Remote Synchronization The clock synchronization of the remote terminal units is performed over the serial communication line – controlled by the master station. To achieve a time accuracy of 1 ms in the remote terminal units over the field bus, the clock synchronization command is transmitted cyclic by the master station every 5 seconds. The time-scale for the transmission of the clock synchronization command <TI=103> is fixed beginning from the 3rd second in the 5 second grid (i.e. at every 3,8,13,18,23,28,33,38,43,48,53,58-th second a clock synchronization command is transmitted). The protocol element in the remote terminal unit corrects the time contained in the message with the message delay and adds the exact reception moment in units of 1ms. For this purpose, the firmware splits up the 10ms ticker provided by the system into a 1ms clock pulse. In addition, the clock synchronization message (FC = 156) is specially identified for the time server in the system (Bit# 5 of the migration status). Based on this identifier the time server performs a synchronization of the system time every 10th second. Attention: The 1ms accuracy is presently only provided in the System AM 1703, since only the time server in AM 1703 supports this functionality! 6-8 DC0-023-2.01 Functions Protocol Elements SICAM 1703 Field Bus (SFB) 6.1.6. Command Transmission 6.1.6.1. Message from the Master Station selectively to a Remote Terminal Unit Station-selective data messages in command direction are always inserted into the running interrogation procedure (station interrogation) by the master station with high priority after termination of the data transmission in progress. Data to be sent from the basic system element (=BSE) are always prioritized 1:1 with station interrogations. If the reaction of the remote terminal unit to a transmitted message is to be acquired quickly by the master station, a "Demand" (=parameter-settable station-selective continuous interrogation) can be executed from the master station. This "station-selective demand" is retriggered by further messages to the same station (message parameterized with demand), or aborted by messages to other stations. The selection of the type identification and setting of the continuous interrogation time necessary for the "demand" can be performed in the parameters advanced parameters | call procedure per type identification. The selection of the type identifications is carried out with the parameters advanced parameters | call procedure per type identification | type identification A(TI) ..O(TI) and the setting of the continuous interrogation time assigned to the type identifications is carried out with the parameters advanced parameters | call procedure per type identification | continuous polling time for type identification A..O. 6.1.6.2. Message from the Master Station to all Remote Terminal Units (unacknowledged) Messages from the multi-point traffic master station "unacknowledged to all" are inserted at any time into a running interrogation cycle (station interrogation) after termination of the data transmission in progress. The message is thereby transmitted several times by the master station with the parameterized number of message retries according to the parameter Message retries | Retries for data message SEND/NO REPLY (broadcast). Afterwards the interrupted interrogation cycle is resumed. 6.1.7. Transmission of Integrated Totals A counter interrogation triggered in the system is always transmitted station-selective by the protocol element of the master station to the remote terminal units. A counter interrogation command to be sent is then already made available station-selective to the protocol element by the basic system element. Functions Protocol Elements DC0-023-2.01 6-9 SICAM 1703 Field Bus (SFB) 6.2. Optimized Parameters for selected Transmission Facilities The protocol element supports selected transmission facilities - for these the parameters are set fixed – the selection of the transmission facility is carried out with the parameter Common settings | interface modem. By selecting the "freely definable transmission facility" certain parameters can be set individually. Most transmission facilities support only certain baud rates or combinations of baud rates in transmit/receive direction – these are to be taken from the descriptions for the transmission facility. The transmission rate (baud rate) is to be set depending on the submodule used for communication, separate for transmit/receive direction with the parameter Common settings | baud rate receiving direction and the parameter Common settings | baud rate transmit direction or for transmit/receive direction together with the parameter Common settings | baud rate. Apart from this, a transmission facility, that can be freely defined by the user, can be selected, for which all parameters that are available can be individually set. This is then necessary if transmission facilities are to be used that are not predefined or if modified parameters are to be used for predefined transmission facilities. For the selection of the freely definable transmission facility the parameter Common settings | interface modem is to be set to "freely definable". Only after that are all supported parameters displayed and can be parameterized with the required values (see Table with Default Parameters for Transmission Facilities). For the adaptation to various modems or time requirements of external systems, the following parameters can be set individually: • Common settings | free defineable transmission facility | 5V supply (DSR) [only SM0551, SM2551] • Common settings | free defineable transmission facility | Configuration for CM-082x [only SM0551, SM2551] How the individual time settings are effective during the data transmission is shown on the following page in a Timing Diagram. 6-10 DC0-023-2.01 Functions Protocol Elements SICAM 1703 Field Bus (SFB) Parameter "5V Supply (DSR)" [only SM0551, SM2551] If necessary the voltage supply of the transmission facility (only 5V) – insofar as this is sufficient – can take place over the state line DSR. The enabling of the voltage supply is performed with the parameter advanced parameters | 5V supply (DSR). The voltage supply is only switched on the DSR state line instead of the DSR signal with corresponding parameter setting. ATTENTION: Required voltage supply and maximum current consumption of the transmission facility must be observed! Parameter "Configuring for CM082x" [only SM0551, SM2551] If an optical transformer of the type CM082x is used as external transmission facility, then the parameter common settings | free defineable transmission facility | Configuration for CM082x must be set when using a patch plug of the type CM2860. In addition, for the adaptation of the protocol to the transmission medium used or to the dynamic behavior of the connected remote station, the following parameters are available: • advanced parameters | monitoring times | expected_ack_time_corr_factor (see acknowledgement procedure in the master station) Functions Protocol Elements DC0-023-2.01 6-11 SICAM 1703 Field Bus (SFB) Default parameters for transmission facilities with UMPM01, UMPS01 Transmission facility Electrical Interface RTS tp [ms] tv [ms] tn [Bit] tdis [ms] DCD tbs [ms] tstab [ms] tdurati on [sec] tdelay [ms] CM-0821 Ring RS-232 0 1 0 0 NO 0 0 0 0 CM-0821 Star, CM-0826, CM-0827, CM-0829 RS-232 0 1 0 0 NO 0 0 0 0 Electrical Interface RTS tp [ms] tv [ms] tn [Bit] tdis [ms] DCD tbs [ms] tstab [ms] tdurati on [sec] tdelay [ms] 5V CM082x 1) 1) CM-0821 Ring RS-232 0 0 0 0 NO 0 0 0 0 YE S NO CM-0821 Star, CM-0826, CM-0827, CM-0829 RS-232 0 0 0 0 NO 0 0 0 0 YE S NO Freely definable Default parameters for transmission facilities with SFBMA1, SFBSA1 Transmission facility Freely definable Legend: Electrical interface ................. Parameter "electrical interface" [only SM2541] RTS.......................................... = RTS is switched for the control of the carrier switching of the modem with each message (ON / OFF) tp ............................................. "Pause time (tp)", "Pause time time base (tp)" tv ............................................. "Set-up time (tv)", "Set-up time time base (tv)" tn ............................................. "overtravel time (tn)", "overtravel time time base (tn)" tdis .......................................... "disable time (tdis)", "disable time time base (tdis)" DCD ......................................... "DCD-assessment" tbs ........................................... "Bounce suppression time (tbs)" tstab ........................................ "Stability monitoring time (tstab)" tduration ................................. "Continuous level monitoring time (tduration)" tdelay ...................................... "transmit delay with level (tdelay)" 1) CM082x ............................... Parameter "Configuring for CM082x". Configuring the interface for optical transformer CM-082x with patch plug CM-2860 [only SM0551, SM2551] 1) 5V ....................................... Parameter "5V Supply (DSR)" [only SM0551, SM2551] 6-12 DC0-023-2.01 Functions Protocol Elements SICAM 1703 Field Bus (SFB) The following picture shows the dynamic behavior (timing) in detail for the data transmission when using transmission facilities with switched carrier. RTS Master station tverz tp tv tn Data transmission tsw TXD tPrell DCD tPrell tverzRTS Data transmission RXD tsignal tsignal tdis t´verzRTS t´verzRTS t´Prell Remote station DCD t´Prell t´signal Data transmission RXD t'dis RTS t'sw tp' t'v Data transmission t'n TXD t'verz tPrell tPrell tstab tstab tdauer Legend: RTS ………….. Request to Send DCD …………. Data Carrier Detect TXD ……...….. Transmit Data RXD ……...….. Receive Data tverzRTS ……….. Processing time of the transmission system Time delay/time difference between activation of transmit part (RTS ) and receiver ready (DCD ) tp ………….….. tv ………….….. tn ………….….. tsw ….....….….. tsignal ….....….. Break time (delay, before transmit part is activated with RTS) Setup time (transmission delay, after transmit part was activated with RTS) Reset time (delayed switch off of the transmit signal level with RTS after message transmission ) Internal processing time Signal propagation delays (dependent from the used transmission facility /transmission path) tPrell …...….….. Protective time after positive/negative DCD-edge (debounce of DCD) tstab …...….….. Stability monitoring time – the new DCD-status is only used for message synchronisation after the expiration of the stability monitoring time tdauer …...….….. Continuous level monitoring time tverz …...….….. Transmission delay – in case of a continuous level a further message transmission will be made at the latest after the transmission delay tdis …….….….. Disable time of the receiver after message receiption (to supress faulty signs during level monitoring) t`x …………….. Corresponding times in the remote stations …………….. DCD valide Functions Protocol Elements DC0-023-2.01 6-13 tp tv SICAM 1703 Field Bus (SFB) 6.3. Function for the Support of Redundant Communication Routes To increase the availability master stations can be designed redundant. In this chapter, the possible redundancy concepts themselves that can be realized are not described, rather only those functions for the support of redundant communication routes supported by the protocol element. In the master station the following operating modes are supported for redundancy: • 6.3.1. 1703-Redundancy (Standard) Redundancy Mode "1703-Redundancy" The switchover of the redundancy state takes place system-internal through redundancy control messages. In the master station, in addition a delay for the switchover of the redundancy state from PASSIVE (=STANDBY) to ACTIVE can be set with the parameter Redundancy | Delay time passive=>active . In the master station only the redundancy mode "1703-Redundancy" is supported and does not need to be set with a parameter. In the remote terminal unit, no function for the support of redundant communications routes is supported by the protocol element! From the redundant – non-active master station, listened messages are passed on in the system with the identifier "passive" in the status. The operating mode of the interface with redundancy state "PASSIVE" can be set according to the redundancy configuration with the parameter Redundancy | operation if passive as follows: • • • Interface "TRISTATE" – only listening mode Interface "ACTIVE" – only listening mode Interface "ACTIVE" – interrogation mode In redundant master stations that are not active, a failure of the interface is monitored globally and the failure of remote terminal units monitored station-selective. The failure of the interface is detected by the STANDBY master station by monitoring for cyclic message reception. The monitoring time is set with the parameter Redundancy | listening_mode (failure monitoring time). On receive timeout (active master station or transmission facility of the master station has failed) the interface is signaled as failed. The failure of a remote terminal unit is detected by the STANDBY master station through station-selective monitoring for cyclic message reception. On station-selective receive timeout (remote terminal unit or transmission facility of the remote terminal unit has failed) the remote terminal unit is signaled as failed. Station-specific pending faults are reset in a redundant STANDBY master station, if a fault-free message from the respective station is "listened". 6-14 DC0-023-2.01 Functions Protocol Elements SICAM 1703 Field Bus (SFB) 6.4. Message Conversion Data in transmit direction are transferred from the basic system element to the protocol element in the SICAM 1703 internal IEC 60870-5-101-/104 format. These are converted by the protocol element to the IEC 60870-5-101 message format on the line and transmitted according to the transmission procedure of the protocol. Data in receive direction are converted by the protocol element from IEC 60870-5-101 format on the transmission line to a SICAM 1703 internal IEC 60870-5-101/104 format and transferred to the basic system element. 6.4.1. Blocking For the optimum utilization of the transmission paths, for the data transmission with IEC 60870-5-101 protocols the "Blocking" according to IEC 60870-5-101 is implemented. This function is performed on the basic system element (BSE) according to the rules applicable for this. Data to be transmitted are thereby already blocked on the basic system element and passed on to the protocol element for transmission. The blocking for data to be transmitted does not support the maximum possible message length according to IEC 60870-5-101! Received data in blocked format according to IEC 60870-5-101 are passed on from the protocol element to the basic system element in blocked format. On the basic system element the blocked data are split up again into individual information objects by the detailed routing function and passed on as such to the further processing. Received messages with maximum length are transmitted SICAM 1703 internal in 2 blocks to the basic system element (BSE) because of the additionally required transport information. The parameters necessary for the blocking are to be set on the basic system element (BSE) in the IEC 60870-5-101/104 parameter block. 6.4.2. Class 1, 2 Data From the remote terminal units in multi-point traffic, data are always transmitted to the master station as class 2 data. SICAM 1703 internal mechanisms for the prioritization of the data to be sent provide extensive options in order to be able to transmit important data to the master station. Functions Protocol Elements DC0-023-2.01 6-15 SICAM 1703 Field Bus (SFB) 6.5. Protocol Element Control and Return Information This function is used for the user-specific influencing of the functions of the protocol elements. This function contains two separate independent parts: • Protocol element control • Protocol element return information The Protocol Element Control enables: • Applicational control of the station interrogation • Setting control location • Testing the reachability of stations • the suppression of errors with intentionally switched-off stations (Station Service) The Protocol Element Return Information enables: • States of certain state lines to be used as process information • the obtaining of station interrogation information • Information about the station status/failure to be obtained Internal distribution for messages with process information Block Diagram Protocol element control Internal function Transmission route Protocol element return information Protocol element Messages with process information Messages with system information 6-16 DC0-023-2.01 Functions Protocol Elements SICAM 1703 Field Bus (SFB) 6.5.1. Protocol Element Control With the help of messages with process information, the protocol element control on the basic system element enables specific functions of the protocol elements to be controlled. The specific functions are determined by the protocol element implemented. The assignment of the messages with process information to the functions is carried out with the help of processtechnical parameters of the ACP 1703 system data protocol element control message. The messages for protocol control are transmitted immediately from the basic system element to the protocol element, regardless of the user data to be sent and the priority control. For messages with process information which are used in ACP 1703 as protocol element control message, an unused CASDU is to be used! All CASDU´s for process information are distributed automatically to the corresponding remote terminal unit. Possible master station functions: Parameter Function SF Station Z-Par Call cycle START 0 125 - Call cycle STOP (disabling) 1 125 - Call cycle CONTINUE (enabling) 2 125 - Continuous call station x ON 3 0 – 99 065535 4 0 – 99 - Continuous call station x OFF Note Z-Par=continuous call time (n * 100ms) Z-Par=0: Continuous call without time input (stopped by other function) Send (general) interrogation command 240 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Send (general) interrogation command to GI-group 241 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Set control location Reset command Legend: **) 125 65535 SCS=<ON>: Set control location (HKA) (global) SCS=<OFF>: Delete control location (HKA) (global) 0 – 99 65535 SCS=<ON>: Set control location (HKA) SCS=<OFF>: Reset control location (HKA) 242 243 This function is not presently supported by PRE! SF..............Control function_(PRE) Station .......Station number 0 - 99...... Station 0 - 99 of the selected protocol element 125......... Station 0 - 99 of the selected protocol element (=BROADCAST) Z-Par .........Additional parameter_(PRE) SCS...........single command state HKA...........Originator address (HKA) = 0 – 255 The setting of the control location can only be performed with a single command <TK=45>! In the PRE-control message to the protocol element the additional parameter is set as follows. SCS = <OFF> ...........Additional parameter = HKA+256 SCS = <ON>.............Additional parameter = HKA **) If a PRE-control message is entered in the PST-detailed routing on the BSE, after startup of the PRE the BSE sends a PRE-control message "Set control location" to the PRE. As a result the function for evaluating the control location is activated on the PRE. Functions Protocol Elements DC0-023-2.01 6-17 SICAM 1703 Field Bus (SFB) Possible remote terminal unit functions: Parameter Function Station Z-Par Note Send (general) interrogation command 240 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Send (general) interrogation command to GI-group 241 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Reset command 243 This function is not presently supported by PRE! Legend: 6-18 SF SF ............. Control function_(PRE) Station....... Station number Z-Par......... Additional parameter_(PRE) DC0-023-2.01 Functions Protocol Elements SICAM 1703 Field Bus (SFB) 6.5.2. Protocol Element Return Information The protocol element return information on the basic system element generates messages with process information in monitor direction and thereby enables states of the protocol elements to be displayed or processed. There are three different categories of return information: • • • Status of the state lines Status of the stations Protocol-specific return information (dependent on the protocol element used) The assignment of the messages with process information to the return information is carried out on the basic system element with the help of process-technical parameters of the ACP 1703 system data protocol element return information. From which source the parameterized return information are to be generated, is set with the parameters "Supplementary system element" and "Station number". Messages for protocol element return information are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. Possible master station return information: Parameter Return information function_(PRE) Station Note Status DTR (1 = state line active) 255 (1) Status DSR (1 = state line active) 255 (1) Station status 0 – 99 1 = Station enabled for call cycle Station failure 0 – 99 1 = Station failed protocol-specific return information 0 255 Cycle IDLE - cycle control is stopped. User data messages will be sent furthermore. protocol-specific return information 1 255 Cycle NORMAL MODE - cycle control running in normal mode (cyclic RTU interrogation) protocol-specific return information 2 255 Continuous call - Continuous call of an RTU presently running protocol-specific return information 3 255 Cycle stopped - cycle has been stopped with PST – control message protocol-specific return information 6 255 Sending "Data to all" - User data message "to all" (BROADCAST) is now being transmitted protocol-specific return information 7 255 Sending "data message" - station-selective user data message is now being transmitted (1) States of the state lines are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. The spontaneous transmission of the current states takes place internally in a 100ms grid. State line changes shorter than 100ms are not guaranteed to be transmitted! Legend: Station .......Station number 0 - 99...... Station 0-99 of the selected protocol element 255......... Station number not used! Functions Protocol Elements DC0-023-2.01 6-19 SICAM 1703 Field Bus (SFB) Possible remote terminal unit return information: Parameter Return information function_(PRE) Station Status DTR (1 = state line active) 255 (1) Status DSR (1 = state line active) 255 (1) Station failure 0 Note 1 = Station failed (1) States of the state lines are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. The spontaneous transmission of the current states takes place internally in a 100ms grid. State line changes shorter than 100ms are not guaranteed to be transmitted! 6-20 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7. Dial-Up Traffic (DIA) Dial-up traffic describes a serial communications protocol with which a master station is connected with one or more remote terminal units over the public telephone network "PSTN" (ISDN, GSM, analog/digital). A connection setup for the transmission of data over the telephone network can be performed spontaneously by the master station as well as by the remote terminal unit. With connection established, the data traffic is controlled by the master station. Either data messages or station interrogation messages are transmitted from the master station. Data from the remote terminal unit to the master station can only be transmitted as reply to a station interrogation. Master station TF TF Telephone network “PSTN“ (ISDN, GSM, analog/digital ) TF TF TF Remote station-1 Remote station-2 Remote station-n n <= 100 Legend: TF ………..….. Transmission facility (Modem) In dial-up traffic, with connection established an "unbalanced transmission procedure" is used. That means, that with connection established, as primary station the master station initiates all message transmissions, while the remote terminal units, which are secondary stations, may only transmit when they are called. The dial-up traffic only requires a "half duplex" transmission medium. The master station and the remote terminal units in multi-point traffic operate with a communications protocol based on IEC 60870-5-101. Principle of the dial-up traffic protocol: • • • • Connection setup control via modem commands with AT-Hayes, V.25bis, X.20, X.28 Access control (LOGIN with password) in the private range of IEC 60870-5-101 Data transmission with established connection (after LOGIN) according to IEC 60870-5-101 Disconnection control in the private range of IEC 60870-5-101 Functions Protocol Elements DC0-023-2.01 7-1 Dial-Up Traffic (DIA) General Functions Communication between one central station and up to 100 remote stations • Unbalanced multi-point (dial-up traffic) based on IEC 60870-5-101 DIAMxx is controlling station (primary station), DIASxx is controlled station (secondary station). • Controlling connection establishment and disconnection ─ Connection establishment spontaneously and cyclically, controlling station controlled station − Establishing a connection cyclically at a settable interval (monitoring cycle) ∗ for transmission of low-priority data ∗ for monitoring the station availability ∗ for clock synchronization ─ Controlling connection establishment by means of modem commands − AT Hayes, V.25bis, X.20, X.28 − Arbitrary main telephone number of a telephone network (PSTN) ─ Access control (LOGIN with password) in the private range of IEC 60870-5-101 ─ Disconnection control in the private range of IEC 60870-5-101 • Communication when a connection is established according to unbalanced multi-point (dial-up traffic) based on IEC 60870-5-101 ─ ─ ─ ─ Data acquisition by polling (station interrogation) Acquisition of events (transmission of data ready to be sent) General interrogation, outstation interrogation Clock synchronization − Each time a connection has been established − When a connection is established, one time per minute ─ Command transmission ─ Transmission of integrated totals • Co-ordination of several masters in "multi-master operation" (availability and data throughput) ─ The controlling station can simultaneously establish connections to different controlled stations • Standby transmission line(s) by means of standby telephone numbers of the same or another (PSTN) telephone network • Multi-hierarchical configurations • Optimized parameters for selected transmission facilities • Toll-Saving Transmission Strategies • Having a telephone set connected in parallel • Functions for supporting redundant communication routes The operating mode of the interface is determined by the protocol element. Operating mode Unbalanced interchange circuit V.24/V.28 Parameter and Setting Asynchronous / Isochronous Interface Signals on RJ45 Connector TXD, RXD, GND, RTS, DTR, DSR/+5V, DCD, CTS Asynchronous V.28 asynchronous 7-2 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.1. Control of Connection Setup and Disconnection A connection setup for the transmission of data over the telephone network can be performed spontaneously or cyclic by the master station as well as by the remote terminal unit. A spontaneous connection setup always takes place when important spontaneous data are to be transmitted, a general interrogation or even a monitoring cycle is to be performed. A cyclic connection setup can be performed by the master station as well as by the remote terminal unit at a settable interval (monitoring cycle) and is used in particular for: • • • Monitoring the station availability Transmission of low priority data Clock synchronization The connection setup and disconnection via the data transmission facilities is controlled with AT-Hayes, CCITT V.25bis, X.20 or X.28 commands (modem control). With connection established, a communication protocol based on IEC 60870-5-101 "Unbalanced Multi-Point (multi-point traffic)" is used. The protocol element uses special administration messages in the private range of IEC 60870-5-101 to control the connection setup and disconnection, the use of a standby transmission line, and access (password protection). Co-ordination of several masters in "multi-master mode" In the so-called multi-master mode, provided there are several dial-up modems available in the master station and just as many SM-25xx/DIAMxx protocol elements, more than one connection can be established simultaneously with different remote stations, whereby no fixed assignment of the remote terminal units to one specific master is required. By means of that higher availability and higher data throughput is achieved. Red Telephone In the master station one interface can be established for dial-up traffic with a separate dial-up modem as "Red Telephone". This interface is used by the master station only for incoming calls. With that, at least one line is kept free for incoming calls in the central station for important data from the remote terminal units. In the remote terminal unit, commonly only one telephone number (main telephone number) of the master station is parameterized. The stepping to the individual modems in the master station is normally carried out by the function "Private branch series or telephone number stepping" of the telephone system or by a corresponding service of the telephone network operator. An active connection setup is not carried out by the master station over this interface. The function "Red Telephone" is only implemented in combination with the function "Multimaster in dial-up traffic" and is enabled in the expanded parameters with the parameter advanced parameters | red telephone. The failure management of the remote terminal units is carried out over the other interfaces in multimaster dial-up traffic. The modem can only be monitored by a monitoring cycle controlled by the protocol element. Functions Protocol Elements DC0-023-2.01 7-3 Dial-Up Traffic (DIA) Common utilization of one modem by different interfaces An "active interface" established by the redundancy state in dial-up traffic always requires one specific transmission facility. A coordinated utilization of a transmission facility by several different interfaces is not supported! If interfaces are designed redundant, only one transmission facility is necessary. The active interface carries out the control of the modem and the transmission of data – the passive interface switches all interface lines to "tristate" and can perform a listening function of the transmitted data in receive direction. 7.1.1. Connection Establishment spontaneously and cyclically, Controlling Station Controlled Station With an error-free state, a connection setup by the master or remote terminal unit is always initiated to the telephone number (first telephone number) of the remote station, which is set according to the parameter Connection setup | Stand-by transm. line switchover mode. After a successful connection establishment, the following functions are performed: • • • • Access control (LOGIN with password) Clock synchronization of the remote terminal unit by the master station Transmission of the user data between master station and remote terminal unit GI-request of the master station to the remote terminal unit (optional) The general interrogation function after every active connection establishment can be activated in the master station with the parameter Connection setup | Send online GI with active connection setup. The general interrogation command is thereby generated by the protocol element of the master station itself and transmitted to the remote terminal unit. 7-4 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Redials If with an active connection setup attempt no connection can be established, the connection setup attempt is repeated after a settable delay (Pause-1). After a settable number of dialing attempts, if necessary switching to a differently parameterized delay (Pause-2) can be performed. If standby telephone numbers are also available for the connection setup to the remote station, these can be used for redials. The use of main/standby telephone numbers is established by the mode for connection setup – this is set with the parameter Connection setup | Stand-by transm. line switchover mode. If no standby telephone number is parameterized, all connection setup attempts are performed only to the parameterized main telephone number. Redials are thereby always performed directly one after the other on expiry of the parameterized timeouts and delays. Redials from the master station to a remote terminal unit are not interrupted by data to another remote terminal unit. In the master station, if another remote terminal unit calls during a dialing pause for redials, the handling for redials in progress is interrupted and the incoming call is accepted. After termination of this connection, a new connection setup is performed to that remote terminal unit whose redials were previously interrupted. For this remote terminal unit, the redials are not resumed, rather started again. If a connection still cannot be established after expiry of the parameterized maximum number of dialing attempts, the remote station is reported as failed. In the master station, the message not transmitted is discarded after expiry of the dialing attempts. In the remote terminal unit, the message is negatively acknowledged to the basic system element and as a result offered for transmission again until the dwell time for this message has expired. If no dwell time is parameterized, this message is offered for transmission again and again. If there is a message to be sent to a failed remote terminal unit or master station, with the parameter Connection setup | 1st dialling attempt with faulty station it can be defined whether redials are to be performed or not. After a successful connection establishment and communication with a previously failed or unreachable remote station, the failure is reset and redials performed again from the next connection setup. If an existing connection is interrupted during a running station interrogation and there are no more data or acknowledgements to be transmitted, a fault or warning is notified but the connection is not re-established immediately. If there are still data to be transmitted, afterwards a connection setup is performed again immediately. The maximum number of dialing attempts is set with the parameter Connection setup | Number of dialling attempts. The delay (pause) between the dialing attempts is set with the parameter Connection setup | Pause -1 between dialling retries and the parameter Connection setup | Pause -2 between dialling retries. The switchover of the delay can be parameterized with the parameter Connection setup | Pause switchover at "n" dialling retries. If a passive connection triggering occurs during the transmission of data, then the message sent but not yet acknowledged by the remote station is negatively acknowledged to the basic system element (BSE) and transmitted again after the next connection establishment. A fault is however only then set, if this faulty behavior occurs several times in succession. The limit is set with the parameter Connection setup | Failure number of attempts. Functions Protocol Elements DC0-023-2.01 7-5 Dial-Up Traffic (DIA) Call acceptance (passive connection setup) An incoming call is accepted either immediately or after a call acceptance delay. The delay time can be set with the parameter Connection setup | Call acception delay. Connection setup modes of the master station If a second telephone number (standby telephone number) is parameterized for the remote terminal unit in the master station in addition to the main telephone number, the connection setup to the remote terminal unit is performed to that telephone number that is determined with the selected "Mode for connection setup". Depending on the "Mode for connection setup" for the selection of the telephone number the criteria "Number of redials already performed", "PRE-control message (selection of the telephone number)" or the moment in time are evaluated. Use of telephone numbers during connection setup Telephone numbers (per remote terminal unit) Main telephone number Standby telephone number (optional) Mode-0 Mode-1 Mode-2 Mode-3 Mode-4 The main telephone number of every remote terminal unit is to be set in the master station with the parameters Station definition | Main Tel No. The standby telephone number of every remote terminal unit is to be set in the master station with the parameters Station definition | Secondary phone number. 7-6 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Mode for Connection Setup Note Mode-0 Main number A connection setup to the remote terminal unit is only performed to the main telephone number. Mode-1 Main number + standby number A connection setup to the remote terminal unit is always performed to the main telephone number first. If the connection to the main telephone number cannot be established, after a number of redials that can be set with the parameter Connection setup | Mode 1 switchover after "m" dialling retrys | Number of redials until changover ("m"), further dialing attempts are performed to the standby telephone number. The main telephone number is to be set with the parameter Connection setup | Telephon number mode 1 | Main phone number. The standby telephone number is to be set with the parameter Connection setup | Telephon number mode 1 | substitute telephone number 1. Mode-2 Main number + standby number (alternating telephone numbers) A connection setup to the remote terminal unit is always performed to the main telephone number first. If the connection to the main telephone number cannot be established, further dialing attempts are made alternating to the standby telephone number and then to the main telephone number again. Mode-3 Main number + standby number (day/night operation) A connection to the remote terminal unit is established either to the main telephone number or to the standby telephone number depending on the time of day. The time range in which the main telephone number is used is to be parameterized with the parameter Connection setup | Mode 3 day_night | day number – hour and with the parameter Connection setup | Mode 3 day_night | day number – minute. The time range in which the standby telephone number is used is to be parameterized with the parameter Connection setup | Mode 3 day_night | night number – hour and with the parameter Connection setup | Mode 3 day_night | night number – minute. Example: from 08:00 - 20:00 … connection to the remote terminal unit only via the main telephone number from 20:00 - 08:00 … connection to the remote terminal unit only via the standby telephone number Mode-4 Main number + standby number (selection with PRE control message) A connection to the remote terminal unit is established to that telephone number (main or standby telephone number) selected via PRE control message. If the connection to this telephone number cannot be established, redials are only performed to the selected telephone number. Functions Protocol Elements DC0-023-2.01 7-7 Dial-Up Traffic (DIA) Connection setup modes of the remote terminal unit If other telephone numbers (standby telephone numbers) are parameterized for the master station in the remote terminal unit in addition to the main telephone number, the connection setup to the master station is performed to that telephone number that is determined with the selected "Mode for connection setup". Depending on the "Mode for connection setup" for the selection of the telephone number the criteria "Number of redials already performed", "PRE-control message (selection of the telephone number)" or the moment in time are evaluated. Use of telephone numbers during connection setup Master Station Telephone Number(s) Mode-0 Mode-1 Mode-2 Mode-3 Mode-4 Mode-5 Main telephone number (MASTER 1) Standby telephone number 1 (MASTER 1) Standby telephone number 2 (MASTER 1) Standby telephone number 3 (MASTER 1) Main telephone number (MASTER 2) Standby telephone number 1 (MASTER 2) Standby telephone number 2 (MASTER 2) Standby telephone number 3 (MASTER 2) Connection Setup Mode Mode-0 Note Main number A connection setup to the master station is only performed to the main telephone number. The main telephone number is to be set with the parameter Connection setup | Telephon number mode 0 | Main phone number . Mode-1 Main number + standby number A connection setup to the master station is always performed to the main telephone number first. If the connection to the main telephone number cannot be established, after a number of redials that can be set with the parameter Connection setup | Mode 1 switchover after "m" dialling retrys | Number of redials until changover ("m"), further dialing attempts are performed to the standby telephone number. The main telephone number is to be set with the parameter Connection setup | Telephon number mode 1 | Main phone number. The standby telephone number is to be set with the parameter Connection setup | Telephon number mode 1 | Substitute telephone number 1. 7-8 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Mode-2 Main number + 3 standby numbers (alternating telephone numbers) A connection setup to the master station is always performed to the main telephone number first. If the connection to the main telephone number cannot be established, every other dialing attempt is performed to the next parameterized standby telephone number. If all parameterized standby telephone numbers have been used for a connection setup, this is continued again with the main telephone number. The main telephone number is to be set with the parameter Connection setup | Telephon number mode 2 | Main phone number. The standby telephone numbers are to be set with the parameter Connection setup | Telephon number mode 2 | Substitute telephone number 1, 2, 3. Functions Protocol Elements DC0-023-2.01 7-9 Dial-Up Traffic (DIA) Connection Setup Mode Mode-3 Note Main number + standby number (day/night operation) A connection to the master station is established either to the main telephone number or to the standby telephone number depending on the time of day. The time range in which the main telephone number is used is to be parameterized with the parameter Connection setup | Mode 3 day_night | day number – hour and with the parameter Connection setup | Mode 3 day_night | day number – minute. The time range in which the standby telephone number is used is to be parameterized with the parameter Connection setup | Mode 3 day_night | night number – hour and with the parameter Connection setup | Mode 3 day_night | night number – minute. Example: from 08:00 - 20:00 … connection to the master station only via the main telephone number from 20:00 - 08:00 … connection to the master station only via the standby telephone number The main telephone number is to be set with the parameter Connection setup | Telephon number mode 3 | Main phone number. The standby telephone number is to be set with the parameter Connection setup | Telephon number mode 3 | Substitute telephone number 1. Mode-4 Main number + standby number (selection with PRE control message) A connection to the master station is established to that telephone number (main or standby telephone number) selected via PRE control message. If the connection to this telephone number cannot be established, redials are only performed to the selected telephone number. The main telephone number is to be set with the parameter Connection setup | Telephon number mode 4 | Main phone number. The standby telephone number is to be set with the parameter Connection setup | Telephon number mode 4 | Substitute telephone number 1. 7-10 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Connection Setup Mode Mode-5 Note Standby transmission line via dialup traffic Remote terminal units are connected to the master station over the main transmission line (SICAM 1703 multi-point traffic or point-to-point protocol). Every remote terminal unit is also equipped with a dial-up modem. If the remote terminal unit is no longer reachable on the main transmission line, a connection over the telephone network (dial-up traffic) is established automatically. The standby transmission line over dial-up traffic is only activated after that time that can be set with the parameter "Delay time for selection of the standby transmission line". If the remote terminal unit can be reached again on the main transmission line during this delay time, the standby transmission line is not activated. An activated standby transmission line over dial-up traffic is only terminated after expiry of that time that can be set with the parameter "Delay time after termination of the standby transmission line". The main telephone number for Master 1 is to be set with the parameter Connection setup | Telephon number mode 5 | Master 1 main phone number. The main telephone number for Master 2 is to be set with the parameter Connection setup | Telephon number mode 5 | Master 2 main phone number. The standby telephone numbers for the Master 1 are to be set with the parameters Connection setup | Telephon number mode 5 | Master 1 Substitute telephone number 1, 2, 3. The standby telephone numbers for the Master 2 are to be set with the parameters Connection setup | Telephon number mode 5 | Master 2 Substitute telephone number 1, 2, 3. Functions Protocol Elements DC0-023-2.01 7-11 Dial-Up Traffic (DIA) 7.1.1.1. Cyclic Connection Setup at a settable Interval (monitoring cycle) A cyclic connection setup can be performed by the master station as well as by the remote terminal unit at a settable interval (monitoring cycle) and is used in particular for: • • • Monitoring the station availability, monitoring the remote station Transmission of low priority data from the remote terminal unit to the master station Clock synchronization of the remote terminal unit by the master station In the monitoring cycle of the master station, a connection setup is performed 1 x to every parameterized remote terminal unit. Through the monitoring cycle, failed remote terminal units are detected by the master station and signaled as failed. In the monitoring cycle – triggered by the remote terminal unit, a connection setup is performed 1x to the master station. Through this monitoring cycle, if necessary a failure of the master stations can be detected by the remote terminal unit. For failed remote terminal units, a cyclic monitoring can be performed - in a shorter time-scale as required. After a connection establishment during the monitoring cycle, the following functions are always performed: • • • Monitoring message (REQUEST STATUS OF LINK) is transmitted from the master station to the remote terminal unit Clock synchronization of the remote terminal unit by the master station Transmission of low priority data from the remote terminal unit to the master station (these data are stored in the remote terminal unit and first transmitted with the next connection setup) Spontaneous data from the master station to another remote terminal unit during a running monitoring cycle are transmitted after the disconnection of an existing connection. The monitoring cycle is thereby interrupted by spontaneous data and then resumed – these remote terminal units are then no longer handled in the monitoring cycle. Spontaneous data from the master station to that remote terminal to which a connection has just been established through the monitoring cycle are transmitted immediately. The monitoring cycle is enabled with the parameter advanced parameters | monitoring times | carry out monitoring. The monitoring can thereby be performed cyclic, time-controlled or time-controlled by the multimaster function on the basic system element. 7-12 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Cyclic monitoring The cyclic monitoring starts after startup of the master or remote terminal unit after the very first expiry of the parameterized monitoring time and is therefore not performed immediately after startup and also not at defined absolute moments. In the remote terminal unit, the period for cyclic monitoring is retriggered with every connection setup. The cycle time for the cyclic monitoring can be set with the parameter advanced parameters | monitoring times | cyclic monitoring | multiplicator and the parameter advanced parameters | monitoring times | cyclic monitoring | time base. The cyclic monitoring can be performed in the time range of 1x / minute to max. 1x / 42 days. The cycle time for the cyclic monitoring of failed remote terminal units by the master station can be set with the parameter Connection setup | monitoring cycle for failed stations. The cyclic monitoring of failed remote terminal units can be performed in the time range of 1x / minute to max. 1x / 4 hours. In the "Multimaster" operating mode, cyclic monitoring is not supported. ( Parameter error if cyclic monitoring is parameterized) Time-controlled monitoring With time-controlled monitoring, the monitoring cycle is started at defined absolute moments. The moments are to be set with the following parameters: • Moment 1: advanced parameters | monitoring times | time controlled monitoring | time 1 hour, advanced parameters | monitoring times | time controlled monitoring | time 1 minute • Moment 2: advanced parameters | monitoring times | time controlled monitoring | time 2 hour, advanced parameters | monitoring times | time controlled monitoring | time 2 minute • Moment 3: advanced parameters | monitoring times | time controlled monitoring | time 3 hour, advanced parameters | monitoring times | time controlled monitoring | time 3 minute • Moment 4: advanced parameters | monitoring times | time controlled monitoring | time 4 hour, advanced parameters | monitoring times | time controlled monitoring | time 4 minute Functions Protocol Elements DC0-023-2.01 7-13 Dial-Up Traffic (DIA) Time-controlled monitoring by basic system element (multimaster) For the multimaster operating mode in the master station, a time-controlled monitoring can be implemented, controlled by the multimaster function of the basic system element. When the moment for a monitoring cycle is reached on the basic system element, beginning from the next minute a monitoring cycle over all assigned multimaster interfaces (except the interface for "Red telephone") to the first remote terminal units is started. In a minute grid, a monitoring cycle to the next remote terminal units is then initiated, until all remote terminal units have been handled by this. If the number of connected remote terminal units is greater than the number of multimaster interfaces of a basic system element in the master station, then it is ensured, that every modem also uses a multimaster interface and has thus been tested. 7.1.2. Connection Setup Control via Modem Commands The connection setup is controlled, depending on the parameterized procedure, either with a state line (telephone number of the remote station is stored in the modem) or with messages for the control of the modem (telephone number is contained in the message). Supported connection setup procedures: • • • • • • AT-Hayes AT-Hayes (ETSI) V.25bis (108.1) V.25bis (108.2) X.20 X.28 In most cases the required procedure for the connection setup control is determined by the transmission facility used (modem). With the selection of a predefined transmission facility, the connection setup procedure is determined automatically – with the selection of the "freely definable transmission facility" the procedure can be set with the parameter Common settings | Modem free definable | Connection setup (procedure). 7.1.2.1. AT-Hayes The Hayes command set (also AT command set) is a command set for the control of modems. It was developed by the company Hayes, still applicable today as recognized industry standard. With the AT-Hayes commands, the modem is parameterized, the modem status interrogated, the connection setup initiated and modem binary information transmitted. The control of modems with AT-Hayes commands takes place only in Command Mode. With established connection, the data are transmitted transparently with corresponding parameter setting of the modems. 7-14 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.1.2.2. AT-Hayes (ETSI) The Hayes command set (also AT command set) is a command set for the control of modems and has been expanded by ETSI (European Telecommunications Standard Institute) especially for TETRA modems. The essential difference is in the different format for the return information from the modem. (see also AT-Hayes) 7.1.2.3. V.25bis According to the interface procedure for the V.25bis connection setup control, the following methods of operation are provided: • Method 108.1 The connection setup to the remote station in dial-up traffic is controlled with a state line. The telephone number of the remote station is stored in the modem. This method can be implemented in remote terminal units in dial-up traffic. • Method 108.2 The connection setup to the remote station in dial-up traffic is controlled with a message in Command Mode. The telephone number of the remote station is stored in the terminal and is transmitted to the modem with every connection setup. This method can be implemented in master stations and remote terminal units in dial-up traffic. 7.1.2.4. X.20 X.20 is an ITU-T (CCITT) recommendation for interfaces between data terminal equipment (DTE) and data transmission equipment (DÜE) for Asynchronous-Duplex-Transmission in public telephone networks. X.20 defines a transmission procedure for the connection setup between one data terminal equipment (DTE) and one transmission equipment (DCE) in Start-Stop mode. The X.20 interface is applicable for the Start-Stop mode, which is intended for transmission rates between 50 Bit/s and 300 Bit/s according to X.1. The DÜE is used here purely as converter circuit between the interface lines and the transmission line. The interface according to X.20 manages with one line each for the transmit and receive data, in addition there is a return line (operating earth). 7.1.2.5. X.28 The X-recommendations of the ITU (CCITT) refer to the data transmission in public data networks (PDN). With the help of the X.28-interface data terminal equipment operating asynchronously can access the data transmission service transferred by data packet. For the X.28-interface there are three user classes provided, which differ in the transmission rate. The classes lie between 50 Bit/s and 1200 Bit/s. Network operators can however offer higher transmission rates. The data terminal equipment (SICAM 1703) is thereby coupled to a data transmission equipment "PAD" (= Packed Assembler Disassembler). Functions Protocol Elements DC0-023-2.01 7-15 Dial-Up Traffic (DIA) 7.1.2.6. Arbitrary Main Telephone Number in a Telephone Network (PSTN) For the establishment of a connection in dial-up traffic the telephone number of the remote station is required. To increase the availability in dial-up traffic, depending on operating mode there are one or several standby telephone numbers available. If a remote station cannot be reached via its main telephone number, it can be called over a standby telephone number – if such a one is available. The own telephone number must always be parameterized. This is transmitted to some modems and can be used by the network operator for error detection. e.g.: if an incorrect telephone number is parameterized in the master or remote terminal unit and as a result a subscriber is called again and again by one modem. Telephone numbers in the master station In the master station the own telephone number and a main and standby telephone number for each remote terminal unit can be parameterized. The telephone numbers of the remote terminal units are entered for each RTU in the parameters of the Station definition. For the parameterization of the telephone numbers, the following parameters are available: 7-16 • Own telephone number: with the parameter Common settings | own phone number • Main telephone number: per RTU with the parameter Station definition | Main tel no • Standby telephone number: per RTU with the parameter Station definition | Secondary phone number DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Telephone numbers in the remote terminal unit In the remote terminal unit the own telephone number and up to 8 different telephone numbers can be parameterized. With a connection setup, based on the parameter Connection setup | Stand-by transm. line switchover mode, the parameter Connection setup | Pause switchover at "n" dialling retries, the error states and the moment, it is decided, which telephone number is used. For the transmission of SMS information, in addition an own telephone number to be parameterized is used. For the parameterization of the telephone numbers, the following parameters are available: • Own telephone number: Common settings | own phone number • Main telephone number of the master: (based on the mode used for connection setup) Connection setup | Telephon number mode 0 | Main phone number Connection setup | Telephon number mode 1 | Main phone number Connection setup | Telephon number mode 2 | Main phone number Connection setup | Telephon number mode 3 | Main phone number Connection setup | Telephon number mode 4 | Main phone number Connection setup | Telephon number mode 5 | Master 1 main phone number Connection setup | Telephon number mode 5 | Master 2 main phone number • Standby telephone numbers of the master: (based on the mode used for connection setup) Connection setup | Telephon number mode 1 | Substitute telephone number 1 Connection setup | Telephon number mode 2 | Substitute telephone number 1 Connection setup | Telephon number mode 2 | Substitute telephone number 2 Connection setup | Telephon number mode 2 | substitute telephone number 3 Connection setup | Telephon number mode 3 | substitute telephone number 1 Connection setup | Telephon number mode 4 | substitute telephone number 1 Connection setup | Telephon number mode 5 | Master 1 substitute telephone Connection setup | Telephon number mode 5 | Master 1 substitute telephone Connection setup | Telephon number mode 5 | Master 1 substitute telephone Connection setup | Telephon number mode 5 | Master 2 substitute telephone Connection setup | Telephon number mode 5 | Master 2 substitute telephone Connection setup | Telephon number mode 5 | Master 2 substitute telephone • Mobile telephone number (SMS recipient) : Common settings | Modem GSM-TC35 Datenbox | mobile phone number Functions Protocol Elements DC0-023-2.01 number number number number number number (SMS-receiver) 7-17 1 2 3 1 2 3 Dial-Up Traffic (DIA) Parameterization of the telephone numbers The telephone number consists of max. 32 ASCII characters, whereby special characters – depending on the selected connection setup procedure – can be inserted for special functions. The own telephone number must always be parameterized. This is transmitted to certain modems and used for diagnostic purposes. Permissible Characters in the parameterized Telephone Number AT-Hayes V.25bis (108.2) X.20 X.28 0…9 0…9 0…9 0…9 Wait until dialing tone detected (continuous tone) : : Dialing pause 1 second < < Dialing pause 3 seconds = = Dialing pause for AT-Hayes modems , Press earthing key > > Flash key & & Pulse dial P P Tone dial T T <BLANK> <BLANK> Telephone number End of the telephone number (1) <BLANK> V.25bis (108.1) <BLANK> <BLANK> (1) … the end of the telephone number is defined with <BLANK> (=space). Note: With the parameterization of the telephone number, the non-used characters at the end of the telephone number are filled automatically by the OPM with <BLANK's>. if the telephone number is now to be changed and additional characters are required for this, then the <BLANK's> at the end of the telephone number must be deleted before entering the new characters. Example: 0,01291290 … getting a trunk line with the numeral <0>, dialing pause with the character <,> 7-18 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.1.3. Access Control (LOGIN with Password) in the Private Range of IEC 60870-5-101 To increase the security against unauthorized access, after a successful connection establishment (regardless whether the connection setup has been initiated by the master station or remote terminal unit) a Login procedure is performed with password verification. After the connection establishment, an identification of the remote terminal unit is performed by the master station with a "Quick-Check procedure". For this, the master station sends a general request to the remote terminal unit for access request ("Request Status of Link" as broadcast message). This message is replied to by the remote terminal unit with a "Status of Link" (with the link address of the remote terminal unit). After the connection establishment and the procedure for station identification, the LOGIN procedure is initiated by the master station. The master station sends a LOGIN-message to the remote terminal unit with the password parameterized in the master station. If the identified remote terminal unit is not parameterized in the master station or is dynamically deactivated, the LOGIN-message is sent with the password "BLOCK". The LOGIN-message is acknowledged by the remote terminal unit. • Positive confirmation If in the remote terminal unit, the password received matches the password parameterized in the remote terminal unit, the transmission of user data to the master station is enabled and the LOGIN-message sent with positive confirmation during the following station interrogation. The data transmission from the remote terminal unit to the master station is activated and a possibly present fault "Modem blockade" is reset. • Negative confirmation If the password does not match or the password "Block" has been received, the remote terminal units sends the LOGIN-message with negative conformation and the data transmission from the remote terminal unit to the master station remains blocked. - With negative confirmation, the master station nevertheless sends user data to the remote terminal unit – these are discarded in the remote terminal unit. - The connection remains established at most until the maximum connection time – the connection time is however not retriggered. - the remote terminal unit sends no data to the master station. - in the master station, the warning "Modem blockade of Station-x" is signaled. - in the remote terminal unit, the warning "Dialing blockade due to false password" is signaled. The password is parameterized in the master station and in the remote terminal unit for each protocol element for dial-up traffic with the parameter Common settings | Login-Passwort. Note: With the parameterization of the password, the non-used characters at the end of the password are filled automatically by the OPM with <BLANK's>. If the password is now to be changed and additional characters are necessary for this, then the <BLANK's> at the end of the password must be deleted before entering the new characters. The access control (LOGIN with password) takes place with a message in the private range of the IEC 60870-5-101 with type identification <TI:=146>. The LOGIN procedure can not be deactivated with a parameter setting! Functions Protocol Elements DC0-023-2.01 7-19 Dial-Up Traffic (DIA) 7.1.4. Disconnection Control in the Private Range of IEC 60870-5-101 For the cost-optimized transmission of data in dial-up traffic, the connection should only then be established when it is really required and a connection should thereby only be established as long as absolutely necessary. An existing connection in dial-up traffic is normally only disconnected by the master station at the earliest after the "minimum connection time" in the following cases: • • • The maximum connection time is reached The connection time per type identification has elapsed and the remote terminal unit has no more data to transmit The remote terminal unit has no more data to transmit An existing connection in dial-up traffic is disconnected by the remote terminal unit in the following cases: • • • The remote terminal unit does not dial the master station due to an incorrectly parameterized telephone number. The disconnection has been performed by the master station, but the modem in the remote terminal unit does 1) not detect the connection as terminated. With connection established, the remote terminal unit is no longer called by the master station within a time that 1) can be set with the parameter advanced parameters | monitoring times | timeout station call. 1) the cause for these problems is in most cases a faulty or incorrectly switched DCD state line The disconnection control is initiated by the master station with the message "HANG UP DIALED LINE" (in the private range of IEC 60870-5-101) to the remote terminal unit with the cause of transmission "ACTIVATION". As soon as the remote terminal unit has received this message, no more data for transmission are received from the basic system element. Afterwards the master station sends one more interrogation message for class 2 data in order to still fetch data that are already prepared for transmission in the remote terminal unit. After that the connection is disconnected by the master station. If the "Multi-Master" function is used in the master station, the master station always terminates the connection to a station, so that the next connection setup to this station is always performed with FCB-Bit=1 (Frame Count Bit). Through this it is ensured, that with a connection setup over another multimaster interface, the FCB-Bit has the correct status. The connection time can be transmitted to the basic system element from the protocol element as protocol element return information. On the basic system element, if necessary this can be distributed for further processing in the system. In the master station the connection time is managed for each remote terminal unit. The connection time can be generated as absolute value or as relative value. The connection time as absolute value is the sum of the connection times to one remote terminal since reset or since the last reset of the connection time counter with PRE control message. The connection time as relative value is the connection duration of the last connection. Whether the connection time counter is to be managed as absolute value or relative value can be set with the parameter advanced parameters | connection time counter. 7-20 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Maximum connection time With connection established, the connection is terminated by the master station on expiry of the maximum connection time at the latest (regardless of "connection time per message type" or if the remote terminal unit still has more data to transmit). The maximum connection time is to be set in the master station with the parameter advanced parameters | monitoring times | connection time maximum. Minimum connection time An established connection is terminated at the earliest after expiry of the minimum connection time if the remote terminal unit has no more data to transmit. The minimum connection time is to be set in the master station with the parameter advanced parameters | monitoring times | connection time minimum. Remote terminal unit has no more data to transmit An established connection is terminated prematurely by the master station if no message-type specific connection time is active and the remote terminal unit has no more data to transmit. If the remote terminal unit has no more data to transmit, station interrogations of the master station are replied to by the remote terminal unit with short acknowledgements (=single character "E5H"). The connection is disconnected by the master station after a parameter-settable number of short acknowledgements in succession. The number of short acknowledgements for the premature connection release is to be set in the master station with the parameter advanced parameters | monitoring times | connection initiation no data. Functions Protocol Elements DC0-023-2.01 7-21 Dial-Up Traffic (DIA) Connection time per message type After the transmission of certain messages in transmit or receive direction, the connection can remain established for a settable time, controlled by the master station, even if the remote terminal unit has no data to transmit during this time. This function enables the master station to transmit a command or setpoint value to the remote terminal unit in the same connection establishment and to acquire a binary information or measured value change (caused by the command or setpoint value). With remote parameterization, remote diagnostic and firmware loading of the remote terminal unit, the connection must also be established for longer and consequently the "maximum connection time" set accordingly. The "connection time per message type" is retriggered with each message of the selected type identifications. An established connection is terminated prematurely by the master station after expiry of the "connection time per type identification", if the remote terminal unit has no more data to transmit. A connection is terminated by the master station at the latest after expiry of the maximum connection time. For the transmission of the following messages, the connection must not be terminated prematurely: • • • • System messages for loading the firmware System messages for remote parameterization System messages for remote diagnostic Command or setpoint value with continuous call of a remote terminal unit (demand) The selection of the type identification and setting of the connection time can be carried out in the advanced parameters advanced parameters | connection time for each type identification. The selection of the type identifications is carried out with the parameters advanced parameters | connection time for each type identification | type identification A(TI) .. O(TI) and the setting of the connection time assigned to the type identifications is carried out with the parameters advanced parameters | connection time for each type identification | connection time for type identification A..O. For system messages (system data container with type identification TI=135), in addition the connection times can be parameterized for 10 freely selectable function codes. The selection of the function codes and setting of the connection time can be carried out in the parameters advanced parameters | connection time for TK135. The selection of the function codes is carried out with the parameters advanced parameters | connection time for TK135 | Funktionscode A, B ..O and the setting of the connection times assigned to the function codes is carried out with the parameters advanced parameters | connection time for TK135 | connection time for Funktionscode A, B ..O . Function Code (Index) Function Code Connection Time (default) Designation Function code A 128 20 sec Service command with confirmation Function code B 129 20 sec Service reply Function code C 130 20 sec Service message SK-format --- 131 --- Service command without confirmation In the system message container, all system messages are transmitted that are not covered by the public range (remote parameterization, firmware loading,…). 7-22 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.2. Communication with existing Connection according to IEC 60870-5-101 With connection established, the data traffic is controlled by the master station. If the connection setup has been carried out by the remote terminal unit, the master station still requires the station address for the cyclic station interrogation with connection established. The link address of the remote terminal unit (=station address) is determined by the master station with a "Quick-Check Procedure". For this, the master station sends a general request to the remote terminal unit for access request ("Request Status of Link" as broadcast message). This message is replied to by the remote terminal unit with a "Status of Link" (with the link address of the remote terminal unit). Either data messages or station interrogation messages are transmitted from the master station. Data from the remote terminal unit to the master station can only be transmitted as reply to a station interrogation. 7.2.1. Data Acquisition by Polling (Station Interrogation) The transmission of the data from the remote terminal unit to the master station with established connection takes place by means of station-selective station interrogations (interrogation procedure, polling), controlled by the master station; i.e., changed data are stored in the remote terminal unit and transmitted to the master station with the interrogation of this remote terminal unit. The interrogation procedure of the master station ensures, that the remote terminal unit to which the connection has been established is interrogated permanently as long as the connection exists. The remote terminal unit may only then transmit data when it is called. The interrogation procedure in dial-up traffic cannot be influenced with parameters! The station-selective parameters of the master station for dial-up traffic, such as "Stat No", "Station enable", "Station failure", "Main telephone number", "Standby telephone number", "BD Main number", "BD Standby number" and "RTU modem” are to be set in the parameters Stationsdefinition. In every remote terminal unit, the station-selective address (= station address) must be set with the parameter Common settings | Address field of the link. This address must be unambiguous for each dial-up traffic line. The length of the "Address field of the link layer (number of octets)" is fixed for dial-up traffic at 1 octet in the master station and in the remote terminal unit. In dial-up traffic with connection established, data and system messages are always transmitted selectively and acknowledged from the master station to the remote terminal unit during the running interrogation cycle. Data to all remote terminal units are either already handled by the basic system element itself or station-selective by the protocol element. With the redundancy state "Passive", no connection setup is carried out by the master station and no station interrogation takes place. In addition, messages to be sent are not transmitted from the master station to the remote terminal units, rather discarded directly on the basic system element (BSE) by the function "User data filter". For the coupling of different systems with the IEC 60870-5-101 protocol in dial-up traffic, the setting of the variable elements of the message is required. These parameters are shown in the Interoperability List or the corresponding description. Functions Protocol Elements DC0-023-2.01 7-23 Dial-Up Traffic (DIA) The following table provides an overview of which IEC-parameters are to be parameterized on which system elements. IEC 60870-5-101 Parameter Description bytes link address Number of octets for the address field of the link layer Cause of transmission (COT) Number of octets for cause of transmission BSE Common address of ASDU (CASDU) Number of octets for common address of the ASDU BSE Information object address (IOA) Number of octets for the address of the information object BSE Acknowledgement on IEC 60870-5-102 layer Single character or short message (ACK) Maximum message length Time Stamp Legend: --- --BSE Number of octets for time stamp (1) The "number of bytes link address" is fixed defined for dial-up traffic with 1 byte (octet) (2) As "acknowlegedement to IEC 60870-5-102 layer" only the single character is used for dial-up traffic. 7-24 System Element SSE = supplementary system element (with serial interfaces this is always configured with a PRE) PRE = Protocol element BSE = Basic system element DC0-023-2.01 Functions Protocol Elements BSE (1) (2) Dial-Up Traffic (DIA) 7.2.1.1. Continuous Interrogation of a Remote Terminal Unit The "Continuous interrogation of a remote terminal unit in dial-up traffic" is always performed with connection established. The master station thereby carries out a permanent station interrogation for the duration of the connection only to that remote terminal unit to which a connection is established. The duration of the connection can be controlled dynamically within the maximum connection time through the parameterization of the connection time per message type. The connection time per message type is retriggered with the parameterized time with each message. Through the continuous interrogation, following a message transmission (e.g. command, setpoint value) the master station can quickly fetch changed data from the remote terminal unit (e.g. measured values after command or setpoint value). The continuous interrogation is terminated after expiry of the connection time. During "continuous interrogation of one remote terminal unit" no data ate transmitted to other remote terminal units. These remain stored on the basic system element and are transmitted after disconnection of the connection. The connection setup can also be carried out with protocol control messages. Thereby, the connection time and thus the continuous interrogation of a remote terminal unit can be determined independent of the parameter setting. For spontaneous messages to the remote terminal unit, the connection time is determined by the connection time per message type. The maximum connection time is however always limited by the parameter setting. 7.2.1.2. Acknowledgement Procedure With connection established, all data messages transmitted to a remote terminal unit must be acknowledged by this RTU. If, with non-faulty transmission line, the acknowledgement is missing for longer than the expected acknowledgement time, transmitted messages are repeated up to n-times (n can be parameterized). On expiry of the number of retries, the remote terminal unit is flagged as faulty. The connection remains established – further messages are transmitted without retries. The connection is terminated by the master station at the latest after expiry of the maximum connection time. The required expected acknowledgement time is determined automatically from the set parameters, but if necessary can be extended accordingly with the parameter advanced parameters | monitoring times | expected_ack_time_corr_factor. This is then the case if additional signal propagation delays, delay times or slow processing times of the connected remote terminal units must be taken into consideration. For the automatic determination of the expected acknowledgement time, the times of the selected transmission facility in the remote terminal unit are also taken into consideration by the DIAMA0 protocol firmware. The number of retries is to be set in the master station for messages for station interrogation and data messages with the parameter Message retries | Retries for data message SEND/CONFIRM (station selective) or for messages for station initialization with the parameter Message retries | Retries for INIT-messages SEND/CONFIRM (station selective). In the master station, in addition the number of retries for the "Quick-Check-Procedure" for interrogation for access request can be set with the parameter Message retries | Retries für Request nach Zugriffsanforderung. The acknowledgement from the remote terminal unit to the master station is transmitted as single character (E5). Functions Protocol Elements DC0-023-2.01 7-25 Dial-Up Traffic (DIA) 7.2.1.3. Failure Monitoring in the Master Station The monitoring of the remote terminal unit by the active master station with connection established takes place by means of the cyclic running interrogation procedure (station interrogation). If there are no user data to be transmitted, the remote terminal units are monitored by the cyclic or time-controlled monitoring cycle. In the monitoring cycle of the master station, a connection setup is performed 1 x to every parameterized remote terminal unit. Through the monitoring cycle, failed remote terminal units are detected by the master station and signaled as failed. With connection established, a remote terminal unit is reported as failed by the master station after expiry of the number of retries. Retries to a remote terminal unit are thereby always sent in succession immediately after expiry of the expected acknowledgement time i.e. the connection is not disconnected and no other remote terminal units are interrogated during a running retry handling. For failed remote terminal units, a communication fault is only then reported, if this is parameterized accordingly in the parameter Stationsdefinition | Stationsausfall. With connection established, the failure of remote terminal units is thus detected by the master station during the normal interrogation cycle or the monitoring cycle. Failed remote terminal units continue to be interrogated by the master station in the monitoring cycle. Redials to failed remote terminal units can be deactivated with the parameter Connection setup | 1. Wahlversuch bei gestörten Stationen. For failed remote terminal units, a cyclic monitoring can be performed - in a shorter time-scale as required. The time-scale can be set with the parameter Connection setup | monitoring cycle for failed stations. Data from the master station to the remote terminal unit which could not be transmitted during the redials are discarded. 7.2.1.4. Failure Monitoring in the Remote Terminal Unit In the remote terminal unit, with connection established, the monitoring of the master station is carried out by the function "Monitoring for cyclic message reception“. If there are no user data to be transmitted, if necessary the remote terminal unit can monitor the master station with the cyclic or time-controlled monitoring cycle. In the monitoring cycle of the remote terminal unit, a connection setup is performed 1 x to the master station. Through the monitoring cycle, a failed master station is detected by the remote terminal unit and signaled as failed. The monitoring time for cyclic message reception is to be set in the remote terminal unit with the parameter advanced parameters | monitoring times | timeout station call. This monitoring time is retriggered in the remote terminal unit by station-selective call messages or station-selective data messages. If the monitoring time elapses, the connection is terminated by the remote terminal unit. With failed interface, data to be transmitted are stored in the data storage on the basic system element (BSE) of the remote terminal unit until these are deleted by the dwell time monitoring or can be transmitted to the master station. 7-26 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.2.2. Station Initialization After a connection setup, the station initialization is performed by the master station in the following cases: • • • After restart of the master station or remote terminal unit After redundancy switchover of the master station After going interface failure of a remote terminal unit After successful station initialization, with a connection setup no further station initialization is performed. The initialization of the link layer of the remote terminal unit is performed by the master station with: • • "Request for the status of the link layer (REQUEST STATUS OF LINK) Reset of the remote terminal unit link layer (RESET OF REMOTE LINK) Reset Command Function in the Remote Terminal Unit REQUEST STATUS OF LINK - "STATUS OF LINK" is transmitted to the master station RESET of REMOTE LINK - FCB-Bit (Frame Count Bit) is initialized - Acknowledgement for RESET of REMOTE LINK is transmitted to master station Initialization End The initialization end according to IEC 60870-5-101 is not supported by this protocol element! Functions Protocol Elements DC0-023-2.01 7-27 Dial-Up Traffic (DIA) 7.2.3. Acquisition of Events (transmission of data ready to be sent) Data that are to be transmitted from the remote terminal unit to the master station are stored on the basic system element (BSE) in the remote terminal unit until transmission. See also chapter "Data Acquisition by Polling (Station Interrogation)". In dial-up traffic, the remote terminal unit itself can establish a connection to the master station and in this way ensure a fast transmission of the data. Data that are not to be transmitted immediately, are stored in the remote terminal unit and transmitted during the next connection setup. For special applications (redundancy configurations or standby transmission line operation via dial-up traffic) all data to be transmitted can be deleted in the remote terminal unit as long as no connection is established. This function can be set in the remote terminal unit with the parameter advanced parameters | Verhalten bei nicht aufgebauter Verbindung. 7.2.3.1. Message from the Remote Terminal Unit to the Master Station With connection established, messages from the remote terminal unit to the master station are only transmitted with station interrogation. A quick-check procedure for speeding up the transmission of data is not implemented. 7.2.4. General Interrogation, Outstation Interrogation The general interrogation (outstation interrogation) function is used to update the master station after the internal station initialization or after the master station has detected a loss of information. The function general interrogation of the master station requests the remote terminal unit to transmit the actual values of all its process variables. In dial-up traffic, the general interrogation of remote terminal units must be carried out station-selective by the master station and due to the connection setup required to every selective remote terminal unit according to the transmission facility used / number of remote terminal units and the parameters set for connection time, takes accordingly long (up to 1 hour and even more). A general interrogation command "to all" triggered in the system is always transferred by the communications function on the basic system element (BSE) station-selective to the protocol element of the master station and also transmitted station-selective by this to the remote terminal units. For communication in dial-up traffic, the general interrogation function can be triggered after every active connection setup by the master station. This function can be activated in the master station with the parameter Connection setup | Send online GI with active connection setup. The general interrogation command is thereby generated by the protocol element of the master station itself and transmitted to the remote terminal unit. 7-28 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.2.5. Clock Synchronization Setting the time In dial-up traffic, the clock of remote terminal units can be set and synchronized by the master station over the communications link. In dial-up traffic, the setting of the clock of remote terminal units must be carried out station-selective by the master station and due to the connection setup required to every selective remote terminal unit according to the transmission facility used / number of remote terminal units and the parameters set for connection time, takes accordingly long (up to 1 hour and even more). A clock synchronization is performed by the master station immediately after every connection setup (regardless whether spontaneous or cyclic, initiated by the master or remote terminal unit) – with connection established cyclic every minute, as long as the connection exists. The clock synchronization command is not transmitted spontaneously by the protocol element of the master station with a change of the time. For switchover from/to daylight-saving time, so that this can be performed punctually in remote terminal units, this is emulated by the protocol firmware in the remote terminal unit. The moments for the switchover from/to daylightsaving time are parameterized in the remote terminal unit on the basic system element in the parameters for time management. Messages that are transmitted from the remote terminal unit after a startup, but before the remote terminal unit has the correct time, contain the relative time from startup (reference day: 1.1.2001) with the flagging of the time stamp as invalid. Remote Synchronization In dial-up traffic, the clock synchronization of the remote terminal units can be performed cyclic over the serial communications link – controlled by the master station. The remote synchronization is performed in the monitoring cycle. Due to the cost-optimized transmission in dial-up traffic (typical remote synchronization 1x / day) and the delayed transmission of data in the telephone network (especially with GSM), the accuracy that can be achieved is rather modest. The achievable accuracy is also dependent on the quartz used in the electronics of the remote terminal unit. Remote Synchronization 1x / Day Quartz Accuracy 10-5 10 -4 Max. Inaccuracy [per hour] (1) Example Max. Inaccuracy [per day] (1) 360 ms 8.6 sec AK 1703 3.6 sec 86.4 sec TM 1703 mic (1) … Inaccuracy due to the delay of the data transmission in the telephone network is NOT taken into consideration here. i.e. depending on the transmission facility used, additional delays are also possible here. If the accuracy of the remote synchronization is insufficient, a local time signal receiver must be used in the remote terminal unit. Functions Protocol Elements DC0-023-2.01 7-29 Dial-Up Traffic (DIA) 7.2.6. Command Transmission 7.2.6.1. Message from the Master Station selectively to a Remote Terminal Unit Station-selective data messages in command direction are always inserted into the running interrogation procedure (station interrogation) by the master station with high priority after termination of the data transmission in progress. Data to be sent from the basic system element (=BSE) are always prioritized 1:1 with station interrogations. Demand If the reaction from the remote terminal unit to a transmitted message is to be acquired quickly by the master station, the connection – controlled by the master station – can remain established for a settable time, even if the remote terminal unit has no data to transmit during this time. This function enables the master station to transmit a command or setpoint value to the remote terminal unit in the same connection establishment and to acquire a binary information or measured value change (caused by the command or setpoint value). The "connection time per message type" is retriggered with each message of the selected type identifications. An established connection is terminated prematurely by the master station after expiry of the "connection time per type identification", if the remote terminal unit has no more data to transmit. A connection is terminated by the master station at the latest after expiry of the maximum connection time. The selection of the type identification and setting of the connection time can be carried out in the advanced parameters advanced parameters | connection time for type identification. The selection of the type identifications is carried out with the parameters advanced parameters | connection time for type identification | type identification A(TI) .. O(TI) and the setting of the connection time assigned to the type identifications is carried out with the parameters advanced parameters | connection time for type identification | connection time for type identification A..O. For system messages (system data container with type identification TI=135), in addition the connection times can be parameterized for 10 freely selectable function codes. The selection of the function codes and setting of the connection time can be carried out in the parameters advanced parameters | connection time for TK135. The selection of the function codes is carried out with the parameters advanced parameters | connection time for TK135 | Funktionscode A, B ..O and the setting of the connection times assigned to the function codes is carried out with the parameters advanced parameters | connection time for TI135 | connection time for type identification A, B ..O . 7-30 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.2.6.2. Control Location If the function "control location" is activated, commands from the protocol element of the master station are only then transmitted to the addressed remote terminal unit if the command has been sent from an enabled control location (originator address). The setting of the control location itself takes place with a command message in single command format <TI=45> which is converted on the basic system element to a PRE control message (function: set control location) by the protocol control function. A command received with an originator address not enabled as control location is not transmitted from the protocol element of the master station and is discarded. For these commands a negative confirmation of activation (ACTCON-) is sent back immediately by the protocol element to the originator address. 7.2.6.3. Control Location Check The control location check is used to check whether the control location, specified with the originator address in the spontaneous information object "Command", has command authority. The originator address specified in the spontaneous information object "Command" must correspond with the control location previously set. If the originator address in the spontaneous information object "Command" does not match the control locations previously set or if no control location has been preset: • • the command is rejected a negative confirmation of the activation is sent (ACTCON-) The control location check is activated as soon as a PRE control message of the type "Set control location" is entered in the PST detailed routing on the basic system element (BSE) for a protocol element (PRE). After startup of the PRE, the BSE sends a PRE control message "Set control location" to the PRE. As a result the control location check function is activated on the PRE. Functions Protocol Elements DC0-023-2.01 7-31 Dial-Up Traffic (DIA) 7.2.6.4. Set Control Location The control location is set on the PRE with a PRE-control message (Function = Set control location) either globally for all stations or station-selective. The control location can be set or deleted and is applicable for all commands of a protocol element. On the BSE the control location is set by the spontaneous information object "control location" and is valid for all commands of a protocol element. The assignment of this message takes place in the OPM of the Toolbox II with the category ACP 1703 Systemfunktionen / protocol element control message. For the derivation of the control location, the following values in the spontaneous information object "Command" signify the originator address: Note: Originator Address Control Location 0 Not defined 1 ... 127 remote command 128 ... 255 local command The selection of the control location and the generation of the spontaneous information object "Control location" must be programmed in an application program of the open-/closed-loop control function. With the spontaneous information object "Control location" in "single command" format, up to 256 control locations can be set at the same time. The information object "Control location" is converted on the basic system element (BSE) to a PRE-control message and passed on to the protocol element. Due to an information object "Control location" with the single command state "ON", the originator address is added to the list of enabled control locations (="Control location enabled"). Due to an information object "Control location" with the single command state "OFF", the originator address is deleted from the list of enabled control locations (="control location not enabled"). The deleting of the control locations can be carried out either station-selective for each control location individually or globally for all stations and all control locations. No confirmation (ACTCON) and no termination (ACTTERM) of the command initiation is created for the information object "Control location". With each startup of the protocol element, all enabled control locations are reset. The control locations are to be set again after every startup of the protocol element. 7.2.6.5. Message from the Master Station to all Remote Terminal Units (unacknowledged) In dial-up traffic, unacknowledged messages from the master station to all remote terminal units are not supported! Since a BROADCAST-transmission is not possible in dial-up traffic, messages to all must always be transmitted selectively to all remote terminal units. 7-32 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.2.7. Transmission of Integrated Totals In dial-up traffic, the counter interrogation command to remote terminal units must be transmitted station-selective by the master station and due to the connection setup required to every selective remote terminal unit according to the transmission facility used / number of remote terminal units and the parameters set for connection time, takes accordingly long (up to 1 hour and even more). A counter interrogation command "to all" triggered in the system is always transferred by the communications function on the basic system element (BSE) station-selective to the protocol element of the master station and also transmitted station-selective by this to the remote terminal units. 7.2.8. Acquisition of Transmission Delay In dial-up traffic, the protocol element of the remote terminal unit does not support "Acquisition of the transmission delay" and the correction of the time resulting from this for clock synchronization according to IEC 60870-5. The protocol element of the master station uses a SICAM 1703 specific method for the "acquisition of transmission delay". With this method, the transmission delay is always determined after connection setup by the master station with the procedural sequences "Request Status Of Link" and the reply from the remote terminal unit "Status of Link" and a correction value derived automatically from this. With connection established, the clock synchronization command is transmitted from the master station selectively to the connected remote terminal unit. The time in the clock synchronization command is already corrected by the protocol firmware of the master station with the automatically determined correction value. Functions Protocol Elements DC0-023-2.01 7-33 Dial-Up Traffic (DIA) 7.3. SMS Messages The remote terminal unit in dial-up traffic can also transmit SMS messages (Short Message Service) to a parameterized telephone number (mobile telephone) with the GSM-Modem "Siemens TC35". For the transmission of SMS messages, no connection is established to the master station for the transmission of data. The transmission of an SMS message (ASCII text) to the GSM-modem is carried out with the AT-Hayes commands implemented in the GSM-Modem for the transmission of SMS messages. SMS messages are transmitted to the telephone number (mobile phone) parameterized with the parameter Common settings | Modem GSM-TC35 data box | mobile phone number (SMS-receiver). The transmission of the SMS messages takes place unacknowledged. SMS messages are triggered with messages for protocol element control. Format of the SMS message: [designation of the remote terminal unit]:[ASCII text of the SMS message] Example: Transformer station Siemensstraße: Transformer voltage Phase 3 failed Date + Time for the SMS messages is presently not transmitted by the remote terminal unit. In the remote terminal unit, freely parameter-settable ASCII texts for max. 10 different SMS messages can be parameterized with the parameters Common settings | Modem GSM-TC35 data box | 1. SMS information, … 10. SMS information. In addition, with the parameter Common settings | Modem GSMTC35 data box | Name of the RTU for SMS an unambiguous designation of the remote terminal unit can be parameterized. This is always sent together with the transmission of an SMS message. 7-34 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.4. Co-ordination of several Masters in "Multi-Master Mode" In the so-called multi-master mode, provided there are several dial-up modems available in the master station and just as many SM-25xx/DIAMxx protocol elements, more than one connection can be established simultaneously with different remote stations, whereby no fixed assignment of the remote terminal units to one specific master is required. By means of that higher availability and higher data throughput is achieved. For the data transmission to a remote terminal unit, the multi-master function on the basic system element decides over which assigned protocol element the data are sent. If a message cannot be transmitted over one multimaster interface, this is transmitted from the basic system element over one of the remaining multimaster interfaces. The data transmission is ended when the data have been deleted on the basic system element by the dwell time monitoring or the data could not be successfully transmitted over any of the interfaces. Through protocol element control messages, a connection setup/disconnection to the remote terminal unit can be performed over a specific selected protocol element or by a protocol element selected by the multimaster function on the basic system element. In multimaster mode, a remote terminal unit is only then signaled as failed by the basic system, if this cannot be reached over any of the assigned protocol elements. The multimaster mode can only be used with the protocol elements of the assigned basic system element. An independent multimaster function can be implemented on any basic system element. A multimaster mode is not possible with protocol elements of another basic system element! For the multimaster mode, all assigned interfaces with master function (MASTER) must be parameterized identically! In multimaster mode, the connection time counters in the protocol element return information are only transferred from the protocol element of the master station as relative values (=connection time of the last connection). In multimaster mode, no standby number is supported for the connected remote terminal units! Functions Protocol Elements DC0-023-2.01 7-35 Dial-Up Traffic (DIA) 7.5. Standby Transmission Line(s) over Standby Telephone Number(s) In dial-up traffic – provided there are several modem connections in the master station or remote terminal unit – standby transmission lines can be realized over standby telephone numbers in the same or another telephone network (PSTN). This way, a remote terminal unit can call the master station over a standby telephone number, if the master station cannot be reached with the main telephone number. 7.6. Multi-Hierarchical Configurations In dial-up traffic, multi-hierarchical configurations can also be realized. This means that additional stations can be connected to a dial-up remote station, also using different communication protocols. 7-36 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.7. Standby Transmission Line via Dial-up Traffic The data transmission between master station and the remote terminal units during fault-free operation is carried out over the main transmission line in point-to-point or multi-point traffic - for ACP 1703 also over LAN. Every remote terminal unit is also equipped with a dial-up modem. If the remote terminal unit is no longer reachable on the main transmission line, a connection over the standby transmission line (telephone network) is established automatically. For remote terminal units in multi-point traffic, a station-selective switchover to the standby transmission line takes place. Schematic configuration for standby transmission line operation over public telephone network (PSTN): Master station Ax/ACP-1703 Basic system element (BSE) UMPMxx DIAMxx DIAMxx DIAMxx DIAMxx “Main transmission line“ “Standby transmission line“ (ZSE = 128) “Standby transmission line“ (ZSE = 129) “Standby transmission line“ (ZSE = 130) “Standby transmission line“ (ZSE = 131) Main transmission line BPPxx “Main transmission line“ TF TF MODEM Main transmission line ET02 “Main transmission line“ (only ACP 1703) MODEM MODEM MODEM Telephone network “PSTN“ Main transmission line Standby transmission line ET02 MODEM TF MODEM TF MODEM TF MODEM DIASxx UMPSxx DIASxx UMPSxx DIASxx UMPSxx DIASxx Remote station-1 (only ACP 1703) Remote station-2 Remote station-3 Remote station-n Legend: TF ………..….. Transmission facility …………….. Failed remote stations are signaled to the b asic system element (BSE) or will be detected from the BSE. …………….. If required, a connection to a failed remote station can be established from the BSE via the standby transmission line . In the remote terminal unit (Ax 1703) the assignment of the interface for main transmission line and stand-by transmission line is defined on a basic system element as follows: Main Line Standby Line SSE = 128 SSE = 129 SSE = 130 SSE = 131 Legend: Note The SSEs for main/standby transmission line must be on the same BSE. SSE = supplementary system element (with serial interfaces this is always configured with a PRE) PRE = Protocol element BSE = Basic system element Functions Protocol Elements DC0-023-2.01 7-37 Dial-Up Traffic (DIA) In the Ax 1703 remote terminal unit, for the interfaces (main transmission line + standby transmission line) the "Data Split Mode" must be used for the communication to redundant remote stations. In the remote terminal unit, the data are only to be routed for the main transmission line. The activated standby transmission line is reported by the protocol element for dial-up traffic in the remote terminal unit to the assigned protocol element for main transmission line. As a result a failure of the main transmission line is detected early in the remote terminal unit and the measures required for activating the standby transmission line are implemented. In ACP 1703 the assignment of the interface for main and standby transmission line is not defined. The parameter setting of main-/standby transmission line is carried out in the topology. From this parameter setting the routing of the internal protocol control messages necessary for the coordination is also derived. The remote terminal units are interrogated by the master station predominantly on the main transmission line. If the protocol element of the master station detects a remote terminal unit on the interface of the main transmission line as failed, then this is reported to the basic system element (BSE) as failed. The failure of the remote terminal unit is detected on the basic system element either by means of the station failure information (Ax 1703) or by means of special "Keep Alive" messages (ACP 1703) transmitted cyclic by the remote terminal unit. The standby transmission line operation over dial-up traffic is only activated to a remote terminal unit no longer reachable on the main transmission line after a time that can be set with the parameter Redundancy | delay time for activation of stand-by transmission line. The standby transmission line establishes a connection to the remote terminal unit over the public telephone network (PSTN). If the remote terminal unit can be reached again on the main transmission line during this delay time, the standby transmission line operation is not activated. The connection to the remote terminal unit over the standby transmission line is only established if there are data to be transmitted. The connection time is limited by the parameter for the limitation of the connection time. When the remote terminal unit can be reached again on the main transmission line, the standby transmission line operation over dial-up traffic to this remote terminal unit is terminated again after a time that can be set with the parameter Redundancy | delay time after finalizing of the stand-by trans. line. Failed remote terminal units continue to be also interrogated on the main transmission line. If a failed remote terminal unit can be reached again on the main transmission line, the standby transmission line handling is terminated for this after a delay time. The standby transmission line is tested by the cyclic monitoring function of the master station. 7-38 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.8. Optimized Parameters for selected Transmission Facilities The protocol element supports selected transmission facilities - for these the essential parameters are set fixed – the selection of the transmission facility is carried out with the parameter Common settings | interface modem. Some transmission facilities require additional parameters – these are then to be set according to application. By selecting the "freely definable transmission facility" certain parameters can be set individually. Note: After modem exchange (or for some modems also after switching on the supply voltage again) it is advisable to perform a reset of the master or remote terminal unit! With that it is ensured that the modems are loaded with the default settings. Settings for all supported modems • Transmission rate Transmission facilities mostly support only certain baud rates – these are shown in the descriptions for the transmission equipment. The transmission rate (baud rate) for the transmission of data is to be set according to the transmission facility used, for transmit/receive direction together with the parameter Daten Mode baud rate in the "General Settings" of the selected transmission facility. e.g.: Common settings | Modem GSM-TC35 data box | Daten Mode baud rate The transmission rate (baud rate) for the transmission of commands to the modem is set fixed according to the transmission facility used and can not be changed. • AT-Hayes Commands For modems that are controlled with AT-Hayes commands, additional AT-Hayes commands can be parameterized, that are transmitted to the modem either during the initialization of the modem after startup of the station or before every connection setup. With these AT-Hayes commands, either additional parameters can be set in the selected modem or all necessary parameters in the modem can be set with the selection of the "freely definable transmission facility". AT-Hayes commands that are to be transmitted to the modem during the initialization, are to be parameterized with the parameters advanced parameters | AT-Kommandos | modem-initialisation 00, … modeminitialisation 09. AT-Hayes commands that are transmitted to the modem before every connection setup are to be parameterized with the parameters advanced parameters | AT-Kommandos | before connection setup 00, … before connection setup 09. Functions Protocol Elements DC0-023-2.01 7-39 Dial-Up Traffic (DIA) • Idle monitoring time, character monitoring time The idle monitoring time and character monitoring time are used to adapt the protocol to the transmission medium used or to the dynamic behavior of the connected remote station respectively. The character monitoring time and idle monitoring time is used for message interruption monitoring and message re-synchronization in receive direction. A message interruption is detected if the time between 2 bytes of a message is greater than the set character monitoring time. With message interruption the running reception handling is aborted and the message is discarded. After a detected message interruption a new message is only accepted in receive direction after an idle time on the line (idle time). These monitoring times are to be set with the parameters advanced parameters | monitoring times | Character monitoring time, advanced parameters | monitoring times | Character monitoring time "time base", and advanced parameters | monitoring times | idle monitoring time, advanced parameters | monitoring times | idle monitoring time "time base". The DIAMA0 protocol firmware automatically sets the required character monitoring time for the selected transmission facility of the remote terminal unit. Specific settings for modem: "GSM-TC35 Datenbox" • Pin Code When using the transmission facility "GSM-TC35 Datenbox", the parameter Common settings | Modem GSM-TC35 data box | GSM M20 Box - pincode must be set if the input of the PIN-Code in the SIM-card of the GSM network provider is activated. Note: If the PIN-Code request is not required, then for this the SIM-card must be inserted into a mobile telephone and the PIN-Code request deactivated. This setting is stored on the SIM-card. In the protocol element, the PIN-Code request is deactivated by setting the parameter Common settings | Modem GSM-TC35 data box | GSM M20 Box – pincode to the value "10000". 7-40 • SMS messages When using the transmission facility in the remote terminal unit, by using the function "SMS Messages", freely definable ASCII texts for max. 10 different SMS messages can be parameterized with the parameters Common settings | Modem GSM-TC35 data box | 1. SMS Meldung, … 10. SMS Meldung. In addition, with the parameter Common settings | Modem GSM-TC35 data box | Name of the RTU for SMS an unambiguous designation of the remote terminal unit can be parameterized. This is always sent together with the transmission of an SMS message. • Telephone number SMS recipient When using the transmission facility in the remote terminal unit, SMS messages are transmitted to the mobile telephone number set with the parameter Common settings | Modem GSM-TC35 data box | mobile phone number (SMS-receiver). • Line modulation (V.32, V.110) When using the transmission facility TC35 in the remote terminal unit and the transmission facility WESTERMO ID90 V.90 (ISDN) in the master station, in the remote terminal unit the parameter Common settings | Modem GSM-TC35 data box | line modulation is to be set to V.110. DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Specific settings for modem: "Westermo ID90 (ISDN)" • B-channel protocol (X.75, V.110) With ISDN, information for the connection setup, information about service detection etc. are transmitted on the D-channel. On the B-channel, the conversation, fax or data are transmitted. When using the modem "WESTERMO ID90/V90" in the master station, in the remote terminal units either ISDN/analog/ or GSM modems can be used. Depending on the modem used in the remote terminal units, a corresponding B-channel protocol setting is required for all ISDN modems. X.75 (CCITT-Standard) Protocol for 64 KBit/s transmissions in the ISDN B-channel, mostly with 2 KByte packet length, optionally with V.42bis data compression. Must be used as B-channel protocol, if a station in dial-up traffic uses the KABELMETALL LGM 64K. V.110 Designation for a standard for the transmission of data between an analog connection and an ISDN connection (data rate 1,200 to 19,200 Bit/s, asynchronous) or between two ISDN connections (data rate 56 or 64 kBit/s) on the B-channel. Must be used as B-channel protocol, if a station in dial-up traffic uses a GSM or an analog modem. When using the transmission facility "Westermo ID90 (ISDN)", the transmission protocol to be used can be set with the parameter Common settings | Modem Westermo ID90 V.90 | B-Channel protocol. Functions Protocol Elements DC0-023-2.01 7-41 Dial-Up Traffic (DIA) Specific settings for modem: "freely definable" Apart from this, a transmission facility, that can be freely defined by the user, can be selected, for which all parameters that are available can be individually set. This is then necessary if transmission facilities are to be used that are not predefined or if modified parameters are to be used for predefined transmission facilities. For the selection of the freely definable transmission facility the parameter Common settings | interface modem is to be set to "freely definable". Only after that are all supported parameters displayed and can be parameterized with the required values (see Table with Default Parameters for Transmission Facilities). When using the transmission facility "freely definable", the following parameters can be set: • 5V Supply (DSR) If necessary the voltage supply of the transmission facility (only 5V) – insofar as this is sufficient – can take place over the state line DSR. The enabling of the voltage supply is performed with the parameter Common settings | Modem free definable | 5V supply (DSR). The voltage supply is only switched on the DSR state line instead of the DSR signal with corresponding parameter setting. ATTENTION: Required voltage supply and maximum current consumption of the transmission facility must be observed! 7-42 • Automatic call acceptance by the modem An incoming call can be accepted immediately by the modem through corresponding setting of the parameter Common settings | Modem free definable | automatic call acception by modem. If an incoming call is not to be accepted by the modem, then the call acceptance is controlled by the protocol element. The call acceptance takes place after the call acceptance delay time by means of a corrsponding control message to the modem in command mode. • Command mode baud rate The transmission rate (baud rate) for the transmission of messages in command mode to/from the modem, is either "defined", "freely parameter-settable in specific ranges" or "identical to the transmission rate in data transmission mode", depending on the transmission facility used. Some modems require a particular baud rate for the data transmission in command mode, which can then also be different from the baud rate used in data mode. The transmission rate (baud rate) for the transmission of data in command mode is to be set for transmit/receive direction together with the parameter Common settings | Modem free definable | Command Mode baud rate. • Data mode baud rate The transmission rate (baud rate) for the transmission of data messages to/from the modem can be parameterized in specific ranges depending on the transmission facility used. The transmission rate (baud rate) for the transmission of data messages in data mode is to be set for transmit/receive direction together with the parameter Common settings | Modem free definable |Daten Mode baud rate. DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) • Command mode data bits, parity, stop bits, end character, message end For the data transmission of messages from/to the modem in command mode, the byte frame can be set with the parameter Common settings | Modem free definable | command mode data bits, the parameter Common settings | Modem free definable | command mode parity and the parameter Common settings | Modem free definable | command mode stop bits. The data transmission in command mode always takes place in ASCII mode. The character at the end of the message (<CR>, <LF>,…) can be set with the parameter Common settings | Modem free definable | command mode message end character. If no end character is parameterized, a message received by the modem is processed after a settable time from the last received character. This time can be set with the parameter Common settings | Modem free definable | command mode message end. • Data mode data bits, parity, stop bits For the transmission of messages from/to the modem in data mode, the byte frame can be set with the parameter Common settings | Modem free definable | data mode data bits, the parameter Common settings | Modem free definable | data mode parity and the parameter Common settings | Modem free definable | data mode stop bits. • Data mode "ASCII transmission" Some transmission facilities do not support the transmission of data with "8 data bits". With these transmission facilities, the data transmission must be carried out in ASCII mode. The data transmission in ASCII mode and the corresponding byte frame must be set identical in the master station and in all connected remote terminal units. The data transmission in ASCII mode is to be set with the parameter Common settings | Modem free definable | data mode ASCII-transmission. The character at the end of the message (<CR>, <LF>,…) can be set with the parameter Common settings | Modem free definable | data mode end character if ASCII. Note: With the data transmission in ASCII mode the message length is doubled! • CRC generator polynomial The transmission of data messages (in data mode) can also be secured by means of a CRC generator polynomial. This additional security can be activated with the parameter Common settings | Modem free definable | data mode CRC-generatorpolynom. The additional message security with CRC generator polynomial should always be used if modems do not support the transmission of the parity bit. • Connection setup procedure The connection setup/disconnection is to be controlled with a procedure supported by the modem depending on the connected modem. The selected procedure is to be set with the parameter Common settings | Modem free definable | connection setup (procedure). • Connection setup V25.bis command With the parameter Common settings | Modem free definable | connection setup V25.bis_commands it is determined whether the connection setup with V.25bis (108.2) is to be performed with the command CRI or CRN. • Call acceptance with call acceptance delay With the parameter Common settings | Modem free definable | Call acception while call accept. delay it is parameterized with which command the call acceptance is performed with call acceptance delay. For AT-Hayes the call acceptance takes place with the command "ATA", for V.25bis the control of the call acceptance is carried out with the commands "DIC" (Disconnect Incoming Call) and "CIC (Connect Incoming Call). • Evaluate modem messages in data mode If the data transmission is carried out in ASCII mode, then the function for the detection of the modem commands must be parameterized with the parameter Common settings | Modem free definable | Assessment of modem inform. (data mode). Only through this function is an unambiguous detection of command mode and data transmission mode possible. Functions Protocol Elements DC0-023-2.01 7-43 Dial-Up Traffic (DIA) 7-44 • Use DCD state line for the connection setup/disconnection control with AT-Hayes For the connection setup (procedure) with AT-Hayes, (if the ASCII transmission data mode is not used) the DCD state line must be used for the connection setup/disconnection control. The status of the DCD state line is used especially for the detection whether the connection is established or has been terminated again and thus for the detection of command mode and data transmission mode. The assessment of the state line is to be set with the parameter Common settings | Modem free definable | DCD is used if AT-Hayes. • Disconnection using escape sequence (AT-Hayes) If the data transmission is carried out in ASCII mode, then the disconnection of the connection can be performed with the so-called "escape sequence". For the connection setup (procedure) with AT-Hayes, as escape sequence the character string "+++" is transmitted to the modem and with connection setup (procedure) with X.28, the character string "0x10". Through this "escape sequence" the connection is disconnected and the modem switches over from data transmission mode to command mode. The disconnection of the connection using “escape sequence" is enabled with the parameter Common settings | Modem free definable | Conn. release via escape seq. (AT-Hayes). • Disconnection via command With the connection setup (procedure) with AT-Hayes, the disconnection of the connection can be carried out with the command "ATH0". For the connection setup (procedure) with X.28, the disconnection of the connection can be carried out with the command "CLR". If the function "Disconnect the connection with command" is not enabled with the parameter Common settings | Modem free definable |connection release v command, the disconnection of the connection is controlled over state lines. DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Parameters for transmission facilities Transmission Facility Westermo TD32 Westermo TD35 Coherent Eurocom-24 Siemens M20-Box Siemens TC35 Westermo ID90 Westermo ID90 V.90 Kabelmetall LGM/H 64K "Direct Mode" Kabelmetall LGM/H 64K "Normal Mode" Freely definable Parameter "5V Supply (DSR)" NO NO YES NO NO NO NO NO NO NO Parameter "Automatic call acceptance by modem" NO NO NO NO NO NO NO NO NO NO Parameter "Command mode baud rate" 9600 9600 1200 9600 9600 9600 9600 19200 19200 Parameter "Command mode data bits" 8 8 8 8 8 8 8 8 8 8 <CR> <LF> <CR> <LF> <CR> <LF> <CR> <LF> <CR> <LF> <CR> <CR> <CR> <LF> <CR> <LF> <CR> <LF> No No No No No No No No No No 1 1 1 1 1 1 1 1 1 1 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit 100 Bit Parameter "Use DCD with AT-Hayes" YES YES YES YES YES YES YES YES YES YES Parameter "Data mode ASCII transmission" NO NO NO NO NO NO NO NO NO NO Parameter "Data mode baud rate" 9600 9600 1200 9600 9600 9600 9600 19200 19200 Parameter "Data mode CRC generator polynomial" YES YES YES YES YES YES YES YES YES Parameter "Command mode end character" Parameter "Command Mode Parity" Parameter "Command mode stop bits" Parameter "Command mode message end" Parameter "Data mode data bits" Parameter "Data mode end character if ASCII" Parameter "Daten Mode Parity" Parameter "Data mode stop bits" NO 8 8 8 8 8 8 8 8 8 8 <CR> <LF> <CR> <LF> <CR> <LF> <CR> <LF> <CR> <LF> <CR> <LF> <CR> <LF> <CR> <LF> <CR> <LF> <CR> <LF> No No No No No No No Even Even No 1 1 1 1 1 1 1 1 1 1 Parameter "Evaluate modem messages (data mode)" NO NO NO NO NO NO NO NO NO NO Parameter "Call acceptance with call acceptance delay" YES YES YES YES YES YES YES YES YES YES Do not send Do not send Do not send Do not send Do not send Do not send Do not send Do not send Do not send Do not send NO NO NO NO NO NO NO NO NO NO Parameter "Connection setup (procedure)" AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes AT-Hayes Parameter "Connection setup V25.bis_command" CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> CRI,<C> Parameter "Disconnection via escape sequence (ATHayes)" Parameter "Disconnection via command" Functions Protocol Elements DC0-023-2.01 7-45 Dial-Up Traffic (DIA) Transmission Facility SIMOCO SRM1000 SEPURA Parameter "5V Supply (DSR)" NO NO Parameter "Automatic call acceptance by modem" NO NO 38400 38400 Parameter "Command mode baud rate" Parameter "Command mode data bits" Parameter "Command mode end character" Parameter "Command Mode Parity" Parameter "Command mode stop bits" Parameter "Command mode message end" 8 8 <CR> <CR> <LF> No No 1 1 100 Bit 100 Bit Parameter "Use DCD with AT-Hayes" NO YES Parameter "Data mode ASCII transmission" YES NO 38400 38400 YES NO 8 8 <CR> <LF> <CR> <LF> No No 1 1 Parameter "Evaluate modem messages (data mode)" YES NO Parameter "Call acceptance with call acceptance delay" YES YES Parameter "Disconnection via escape sequence (ATHayes)" send send Parameter "Disconnection via command" YES YES Parameter "Connection setup (procedure)" AT-Hayes AT-Hayes "ETSI" Parameter "Connection setup V25.bis_command" CRI,<C> CRI,<C> Parameter "Data mode baud rate" Parameter "Data mode CRC generator polynomial" Parameter "Data mode data bits" Parameter "Data mode end character if ASCII" Parameter "Daten Mode Parity" Parameter "Data mode stop bits" 7-46 INSYS GSM INSYS PSTN 56K DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Time settings for "freely definable transmission facility" Note: For a freely definable transmission facility, if necessary time seetings are also to be set with the parameters advanced parameters | Software test points | timeout for user modems. The time settings are stored permanently in the protocol firmware for the predefined transmission equipment. Default Setting Parameter "Timeout 2" 100 Parameter "Timeout 3" 5 Parameter "Timeout 4" 600 Parameter "Timeout 5" 300 Parameter "Timeout 6" 50 Parameter "Timeout 7 Active" 10 Parameter "Timeout 7 Passive" 10 Parameter "Timeout 9" 5 Parameter "Timeout A" 300 Parameter "Timeout B" 300 Parameter "Timeout D" 5 Parameter "Timeout E" 50 Parameter "Timeout F" 2 Parameter "Timeout 10" 2 Parameter "Timeout 12" 30 Parameter "Timeout 13" 100 Parameter "Timeout 17" 30 Parameter "Timeout 18" 0 Parameter "Timeout 19" 30 Parameter "Timeout 1C" 200 Parameter "Timeout 1D" 10 Parameter "Timeout 1E" 10 Parameter "Timeout 1F" 10 Parameter "Timeout 22" 0 Parameter "Timeout 24" 50 Parameter "Timeout 26" 200 Parameter "Timeout 27" 200 Parameter "Timeout 28" 2 Parameter "Timeout 2B" 20 Parameter "Timeout 2C" 30 Functions Protocol Elements DC0-023-2.01 Note 7-47 Dial-Up Traffic (DIA) 7.8.1. Permissible combinations for transmission facilities Remote terminal unit ( SLAVE) (*) Master Station (MASTER) - Siemens TC35 - Wavecom WMO2 (5) - FALCOM A2 (5) (*) Westermo - TD32 - TD36 Westermo - TD35 - TD36 Coherent Eurocom-24 Siemens M20-Box analog analog analog GSM X X X X X X GSM Westermo - ID90 V.90 - IDW90 (3) Kabelmetall LGM/H 64K "Direct Mode" (1) Kabelmetall LGM/H 64K "Normal Mode" (2) ISDN,analog,GSM ISDN ISDN Westermo - TD-32 - TD36 analog Westermo - TD-35 - TD36 analog Coherent Eurocom24 analog X X Siemens M20-Box GSM X X X X X X X X X X GSM - Siemens TC35 - Wavecom WMO2 - FALCOM A2 Westermo - ID90 - IDW90 ISDN Kabelmetall LGM/H 64K "Direct Mode" ISDN Kabelmetall LGM/H 64K "Normal Mode" ISDN X Freely definable X X X (4) X X X Freely definable (*) the designated modem type must be selected as transmission facility in the protocol firmware.! 7-48 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Remote terminal unit ( SLAVE) (*) Master Station (MASTER) SIMOCO SRM1000 TETRA SEPURA TETRA INSYS GSM 4.1 GSM SIMOCO SRM1000 SEPURA INSYS 56K PSTN (6) INSYS GSM 4.1 (5) TETRA TETRA analog GSM X X (*) X X (*) the designated modem type must be selected as transmission facility in the protocol firmware.! (1) ISDN transmission in "Direct-Mode" (=fast); The transmission rate for the data mode must be set the same in all stations! LGM 64K (ISDN modem as single-Euroformat module), LGH 64K (ISDN modem as DIN rail module) Note: The direct mode can only be used with the same modem type in the master station and remote terminal unit. A subsequent expansion with ISDN modems of other manufacturers is not possible without changing parameters! (2) ISDN transmission in "Normal Mode" (=slow); The transmission rate for the data mode can be set differently in stations! Note: ISDN transmission in "Normal Mode" should be used where possible subsequent expansion with different systems more easily possible (possibly dissimilar baud rate)! The jumpers on the LGM/H 64K modem must be set to "Auto bauds"! LGM 64K (ISDN modem as single-Euroformat module), LGH 64K (ISDN modem as Din rail module) (3) only SMx551/DIAMA0 (4) As B-channel protocol, either X.75 (=X.75 transparent with LGM/H64K) or V.110 (=Normal Mode with LGM/H64K) must be set! (5) Internally these modems use the SIEMENS TC-35 GSM Engine and are thus compatible with the Siemens TC35 GSM Modem! (6) This modem can presently not be selected, but has been tested with internal tests with the settings "freely definable" as modem for the master station. Functions Protocol Elements DC0-023-2.01 7-49 Dial-Up Traffic (DIA) 7.8.2. ASCII Mode With connection established, the data transmission is preferably carried out in the format 8E1 defined according to IEC 60870-5-101 (1 Start Bit, 8 Data Bits, 1 Parity Bit "Even", 1 Stop Bit). Transmission facilities do not always support the transparent transmission in the 8 Bit format for data. When using such transmission equipment, the ASCII mode must be used. In ASCII mode, the transmission is carried out in the 7 Bit format for data. The byte frame for the ASCII mode can be set with the parameter Common settings | Modem free definable | data mode data bits, the parameter Common settings | Modem free definable | data mode parity and the parameter Common settings | Modem free definable | data mode stop bits. The protocol element thereby converts every HEX-character to be transmitted to 2 ASCII-characters. e.g.: 68H … is transmitted as <68> (= 36H, 38H). Due to the ASCII mode the message length doubles, but the data bytes are transmitted with shorter byte frames. In addition, in ASCII mode an extra message header is inserted at the beginning of the message ":" and optionally at the end of the message. The extra message header at the end of the message can be parameterized with the parameter Common settings | Modem free definable | data mode end character if ASCII. The ASCII mode is activated automatically for transmission equipment which do not support any 8 Bit mode for data. With selected transmission facility (ÜE) "USER defined Modem" the ASCII mode can be activated with the parameter "Data Mode ASCII transmission". Note: With ASCII mode activated, due to the required message frame, even with connection established the data transmission no longer corresponds with the IEC 60870-5-101! The user data themselves are transmitted with message formats according to IEC 60870-5-101 – in ASCII-Mode. : LINK *) IEC 60860-5-101 ASDU *) IEC 60870-5-1 IEC 60870-5-2 CRC-CCITT *) optional LINK *) <CR> <LF> IEC 60870-5-1 *) all printable ASCII-signs in range 0..9, A..F (30H .. 39H, 41H-46H) Optionally, in ASCII mode an additional message protection (CRC-CCITT) can be inserted, since especially with formats "without Parity Bit" the transmission protection d=4 is not longer provided. Note: CRC-CCITT consists of 4 characters in ASCII-Mode. 7-50 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.8.3. CRC Generator Polynomial With connection established, the SICAM 1703 dial-up traffic uses a transmission procedure according to IEC 60870-5-101 "unbalanced". To increase the transmission protection an extra block is inserted for message protection (CRC-CCITT), which is not provided according to IEC 60870-5-101. If with connection established the transmission procedure definitely according to IE C60870-5-101 must be used, then this extra block for the message protection (with selected transmission facility (ÜE) "USER defined Modem" can be deactivated with the parameter "Data Mode CRC generator polynomial". In ASCII mode, this extra block for message protection is definitely required especially for formats "without Parity Bit", since otherwise considerable deterioration of the transmission protection could occur. : LINK IEC60870-5-1 IEC60870-5-2 CRC-CCITT IEC 60860-5-101 ASDU LINK IEC60870-5-1 CS 16 <CR> <LF> The calculation of the extra block for message protection takes place beginning with the control field (IEC 60870-52) including all IEC 60870-5-101 data bytes (the checksum field is no longer included). The extra block for message protection is inserted in the message before the checksum field (CS). Generator polynomial for CRC-CCITT (CRC16): g(x) = x 16 + x12 + x5 + 1 Note: The calculation of the checksum (CS) takes place according to IEC 60870-5-1 beginning with the control field (IEC 60870-5-2) including all IEC 60870-5-101 data bytes and including the optionally inserted CRCCCITT block. Functions Protocol Elements DC0-023-2.01 7-51 Dial-Up Traffic (DIA) 7.9. Toll-Saving Transmission Strategies By means of corresponding parameterization (maximum connection time, prioritization, selection of process data for spontaneous transmission when data have changed, etc.) the transmission of data can be reduced to a minimum necessary for the process management. Whenever a station (central station, remote station) has data ready for spontaneous transmission, it makes a connection to the partner station. Apart from the spontaneous transmission, there is the so-called "monitoring cycle": DIAMxx and DIASxx can also establish a cyclic connection to the remote stations and thus verify their availability. It is common to parameterize the master in such a way, that it monitors its remote terminal units cyclic. If necessary, every remote terminal unit can also be parameterized, so that it monitors its master. When a connection is established – be it spontaneous or cyclic – all data ready to be transmitted are in all cases transmitted – regardless whether they are selected for spontaneous transmission or not. 7.10. Having a Telephone Set connected in Parallel One can also make a normal telephone call over a telephone connection which is used with a modem for the transmission of data, as long as the operation of a parallel telephone set is supported by the modem. If there is no data connection, phone calls can be made at any time. If a data connection is established it cannot be influenced by the telephone set. If a call comes in the modem takes the call either immediately or after a settable delay. Before the modem accepts a call, the call can also be accepted by hand over the telephone. 7-52 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.11. Functions for supporting Redundant Communication Routes To increase the availability master stations can be designed redundant. The switchover of the redundancy state takes place system-internal through redundancy control messages. In the master station the information "Ring" (it rings) can be used as protocol return information for the control of the redundancy state. 7.11.1. Redundancy Mode "1703-Redundancy" In the master station only the redundancy mode "1703-Redundancy" is supported and does not need to be set with a parameter. In the remote terminal unit, no functions for the support of redundant communications routes are supported by the protocol element! From the redundant, non-active master station, listened messages are passed on to the basic system element (BSE) and forwarded by this in the system with the identifier "passive" in the state. The operating mode of the interface with redundancy state "PASSIVE" can be set according to the redundancy configuration with the parameter Redundancy | operation if passive as follows: • • Interface "TRISTATE" – only listening mode Interface "ACTIVE" – only listening mode With redundancy state "PASSIVE" all transmit-side interface signals are switched to "TRISTATE". With redundancy state "PASSIVE" the interface may only be switched to "ACTIVE" if no common modem is used (e.g.: with locally separated redundant masters). In redundant master stations that are not active (=PASSIVE master station), no failure of the interface is monitored and also no station-selective failure of remote terminal units. Station-specific pending faults are reset in a redundant STANDBY master station, if a fault-free message from the respective station is "listened". For configurations with locally separated redundant master stations and the use of the function "Telephone number stepping", the protocol element return information "It’s ringing (RING)" can be utilized for the control of the redundancy switchover. The telephone number stepping is offered as a service by the operator of the telephone network. In the remote terminal unit, commonly only one telephone number of the master station is stored. If the master station on the main connection does not accept the call within a defined time, the call of the remote terminal unit is transferred to another connection (to the STANDBY master) by the telephone number stepping. Functions Protocol Elements DC0-023-2.01 7-53 Dial-Up Traffic (DIA) 7.12. Message Conversion Data in transmit direction are transferred from the basic system element to the protocol element in the SICAM 1703 internal IEC 60870-5-101-/104 format. These are converted by the protocol element to the IEC 60870-5-101 message format on the line and transmitted according to the transmission procedure of the protocol. Data in receive direction are converted by the protocol element from IEC 60870-5-101 format on the transmission line to a SICAM 1703 internal IEC 60870-5-101/104 format and transferred to the basic system element. 7.12.1. Blocking For the optimum utilization of the transmission paths, for the data transmission with IEC 60870-5-101 protocols the "Blocking" according to IEC 60870-5-101 is implemented. This function is performed on the basic system element (BSE) according to the rules applicable for this. Data to be transmitted are thereby already blocked on the basic system element and passed on to the protocol element for transmission. The blocking for data to be transmitted does not support the maximum possible message length according to IEC 60870-5-101! Received data in blocked format according to IEC 60870-5-101 are passed on from the protocol element to the basic system element in blocked format. On the basic system element the blocked data are split up again into individual information objects by the detailed routing function and passed on as such to the further processing. Received messages with maximum length are transmitted SICAM 1703 internal in 2 blocks to the basic system element (BSE) because of the additionally required transport information. The parameters necessary for the blocking are to be set on the basic system element (BSE) in the IEC 60870-5-101/104 parameter block. 7.12.2. Class 1, 2 Data In dial-up traffic, data from the remote terminal unit are always transmitted to the master station as class 2 data (except TM 1703 mic as remote terminal unit in dial-up traffic). SICAM 1703 internal mechanisms for the prioritization of the data to be sent provide extensive options in order to be able to transmit important data to the master station. In dial-up traffic, with the assignment of the data to be sent, it is defined through the priority whether a connection setup is to be performed immediately when these data change or whether these data are only to be transmitted during the next connection setup. 7-54 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) 7.13. Protocol Element Control and Return Information This function is used for the user-specific influencing of the functions of the protocol elements. This function contains two separate independent parts: • Protocol element control • Protocol element return information The Protocol Element Control enables: • Applicational control of the station interrogation • Setting control location • Testing the reachability of stations • the suppression of errors with intentionally switched-off stations (Station Service) The Protocol Element Return Information enables: • States of certain state lines to be used as process information • the obtaining of station interrogation information • the obtaining of information about the route state/failure of main/standby transmission line • Information about the station status/failure to be obtained Internal distribution for messages with process information Block Diagram Protocol element control Internal function Transmission route Protocol element return information Protocol element Messages with process information Messages with system information Functions Protocol Elements DC0-023-2.01 7-55 Dial-Up Traffic (DIA) 7.13.1. Protocol Element Control With the help of messages with process information, the protocol element control on the basic system element enables specific functions of the protocol elements to be controlled. The specific functions are determined by the protocol element implemented. The assignment of the messages with process information to the functions is carried out with the help of processtechnical parameters of the ACP 1703 system data protocol element control message. The messages for protocol control are transmitted immediately from the basic system element to the protocol element, regardless of the user data to be sent and the priority control. For messages with process information which are used in ACP 1703 as protocol element control message, an unused CASDU is to be used! All CASDU´s for process information are distributed automatically to the corresponding remote terminal unit. Multi-Master or Single-Master In the master station, protocol element control messages can be distributed to a protocol element directly with "PRE_(PST) = 128 – 131" or with "PRE_(PST) = 254" to the multimaster function on the basic system element (BSE). The multimaster function on the BSE then decides to which assigned protocol element the protocol element control message is sent. 7-56 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Possible master station functions "Single-Master" (or PST direct to PRE): Protocol element control messages with "PRE_(PST) = 128-131" are distributed further by the basic system element directly to the respective selective protocol element. Parameter Function SF Station Start monitoring cycle (initiate) 0 125 065535 Z-Par=0.65535: no minimum connection time Z-Par=1-65534: minimum connection time (n * 100ms) Connection setup to remote terminal unit 1 0 – 99 065535 Z-Par=0.65535: no minimum connection time Z-Par=1-65534: minimum connection time (n * 100ms) Connection release 2 0 – 99, 125 - Reset connection time counter (or connection setup counter) 3 0 – 99, 125 - The function of the counter is defined with a parameter. Use main telephone number first 4 0 – 99, 125 - A connection setup to the remote terminal unit is carried out to the main telephone number first. (see Mode-4, connection setup procedure) Use standby telephone number first 5 0 – 99, 125 - A connection setup to the remote terminal unit is carried out to the standby telephone number first. (see Mode-4, connection setup procedure) Terminate call attempts (abort) 6 0 – 99, 125 - Via dial-up traffic switch standby transmission line operation ON for remote terminal unit 7 0 – 99 - Via dial-up traffic switch standby transmission line operation OFF for remote terminal unit 8 0 – 99 - 10 Activate standby transmission line and connection setup to remote terminal unit over activated standby transmission line 0 – 99 065535 Connection release to remote terminal unit and deactivate standby transmission line 11 0 – 99 - Add station to station polling 128 0 – 99 - only parameterized RTUs can be added to the station polling. otherwise error "faulty PST-control message" Remove station from station polling 129 0 – 99 0,1 only parameterized RTUs can be removed from the station polling. otherwise error "faulty PST-control message" Z-Par=0: Reset present station fault Z-Par=1: Do not change present station fault Send (general) interrogation command 240 This function is processed on the BSE and not transferred to the protocol element as PRE-control message! Send (general) interrogation command to GI-group 241 This function is processed on the BSE and not transferred to the protocol element as PRE-control message! Set control location Functions Protocol Elements **) Z-Par Note Z-Par=0.65535: no minimum connection time Z-Par=1-65534: minimum connection time (n * 100ms) 125 65535 SCS=<ON>: Set control location (HKA) (global) SCS=<OFF>: Delete all control locations (HKA's) (global) 0 – 99 65535 SCS=<ON>: Set control location (HKA) SCS=<OFF>: Reset control location (HKA) 242 DC0-023-2.01 7-57 Dial-Up Traffic (DIA) Possible master station functions "Multimaster" (PST to Multimaster function on BSE): Protocol element control messages with "PRE_(PST) = 254" are distributed further by the multimaster function on the basic system element (BSE) to a freely assigned multimaster interface (protocol element). Parameter Function SF Station Connection setup to remote terminal unit 1 0 – 99 065535 Connection release 2 0 – 99 - Terminate call attempts (abort) 6 0 – 99 - 10 Activate standby transmission line and connection setup to remote terminal unit over activated standby transmission line 0 – 99 065535 Connection release to remote terminal unit and deactivate standby transmission line 11 0 – 99 - Send (general) interrogation command 240 Legend: Z-Par Note Z-Par=0.65535: no minimum connection time Z-Par=1-65534: minimum connection time (n * 100ms) … is only transferred by the multimaster function if a connection is established to this station. Z-Par=0.65535: no minimum connection time Z-Par=1-65534: minimum connection time (n * 100ms) … is only transferred by the multimaster function if a connection is established to this station. This function is processed on the BSE and not transferred to the protocol element as PRE-control message! SF …….… Control function_(PRE) Station …. Station number 0 – 99 … selective station 0 – 99 of the selected protocol element 125 …… all parameterized stations of the selected protocol element Z-Par......... Additional parameter_(PRE) SCS .......... single command state HKA .......... Originator address (HKA) = 0 – 255 The setting of the control location can only be performed with a single command <TK=45>! In the PRE-control message to the protocol element the additional parameter is set as follows. SCS = <OFF>........... Additional parameter = HKA+256 SCS = <ON> ............ Additional parameter = HKA **) If a PRE-control message is entered in the PST-detailed routing on the BSE, after startup of the PRE the BSE sends a PRE-control message "Set control location" to the PRE. As a result the function for evaluating the control location is activated on the PRE. 7-58 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Possible remote terminal unit functions: Parameter Function SF Station Z-Par Start monitoring cycle (initiate) 0 - - Reset connection time counter (or connection setup counter) 3 - - Use main telephone number first 4 - - A connection setup to the master station is carried out to the main telephone number first. (see Mode-4, connection setup procedure) Use standby telephone number first 5 - - A connection setup to the master station is carried out to the standby telephone number first. (see Mode-4, connection setup procedure) Terminate call attempts (abort) 6 - - Send SMS message 1 7 - - Send SMS message 2 8 - - Send SMS message 3 9 - - Send SMS message 4 10 - - Send SMS message 5 11 - - Send SMS message 6 12 - - Send SMS message 7 13 - - Send SMS message 8 14 - - Send SMS message 9 15 - - Send SMS message 10 16 - - Send (general) interrogation command 240 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Send (general) interrogation command to GI-group 241 This function is processed on the BSE and not transferred to the protocol element as PREcontrol message! Legend: Note SF..............Control function_(PRE) Station .......Station number (not used = 255) Z-Par .........Additional parameter_(PRE) Functions Protocol Elements DC0-023-2.01 7-59 Dial-Up Traffic (DIA) 7.13.2. Protocol Element Return Information The protocol element return information on the basic system element generates messages with process information in monitor direction and thereby enables states of the protocol elements to be displayed or processed. There are three different categories of return information: • • • Status of the state lines Status of the stations Protocol-specific return information (dependent on the protocol element used) The assignment of the messages with process information to the return information is carried out on the basic system element with the help of process-technical parameters of the ACP 1703 system data protocol element return information. From which source the parameterized return information are to be generated, is set with the parameters "Supplementary system element" and "Station number". Messages for protocol element return information are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. 7-60 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Possible master station return information "Single-Master": Parameter Return information function_(PRE) Station Note Status RTS (1= state line active) 255 1) Status CTS (1 = state line active) 255 1) Status DCD (1 = state line active) 255 1) Status DTR (1 = state line active) 255 1) Status DSR (1 = state line active) 255 1) Station status 0 – 99 1 = Station enabled for call cycle Station failure 0 – 99 1 = Station failed protocol-specific return information 0 0 – 99 Connection setup "stored (flagged in advance)" protocol-specific return information 1 0 – 99 Connection setup "in progress" protocol-specific return information 2 0 – 99 Connection "established" protocol-specific return information 3 0 – 99 Connection setup "not possible" (number of redials elapsed without success) 2) protocol-specific return information 4 0 – 99 Connection setup executed successfully 2) protocol-specific return information 5 0 – 99 protocol-specific return information 6 0 – 99 Connection "terminated" protocol-specific return information 7 0 – 99 Connection setup not possible (Station not enabled on protocol element) Dialing pause (after an unsuccessful connection setup attempt, a dialing pause is performed. Afterwards a new connection setup is initiated) 2) 2) protocol-specific return information 9 0 – 99 "The telephone line has been unplugged" Status of Layer 1 interrogation. (only applicable for Kabelmetall ISDN terminal adapter) protocol-specific return information 14 255 "It’s ringing" (RING) With redundant configurations this information can be used for redundancy switchover. Functions Protocol Elements DC0-023-2.01 7-61 Dial-Up Traffic (DIA) Possible master station return information "Multi-Master": Parameter Return information function_(PRE) Station Note Status RTS (1= state line active) 255 1) Status CTS (1 = state line active) 255 1) Status DCD (1 = state line active) 255 1) Status DTR (1 = state line active) 255 1) Status DSR (1 = state line active) 255 1) Station status 0 – 99 1 = Station enabled for call cycle Station failure 0 – 99 1 = Station failed protocol-specific return information 1 0 – 99 Connection setup "in progress" protocol-specific return information 2 0 – 99 Connection "established" protocol-specific return information 3 0 – 99 Connection setup "not possible" (number of redials elapsed without success) protocol-specific return information 6 0 – 99 Connection "terminated" protocol-specific return information 14 255 "It’s ringing" (RING) With redundant configurations this information can be used for redundancy switchover. protocol-specific return information 0 255 PRE0 assigned (Multimaster function cannot perform any connection setup over this PRE) protocol-specific return information 1 255 PRE1 assigned (Multimaster function cannot perform any connection setup over this PRE) protocol-specific return information 2 255 PRE2 assigned (Multimaster function cannot perform any connection setup over this PRE) protocol-specific return information 3 255 PRE3 assigned (Multimaster function cannot perform any connection setup over this PRE) protocol-specific return information 15 255 All PRE's assigned (Multimaster function cannot perform any connection setup over these PRE's) Legend: 2) 2) Station....... Station number 0 - 99 ......Station 0-99 of the selected protocol element 255 .........Station number not used! PRE ......... Protocol element (1) States of the state lines are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. The spontaneous transmission of the current states takes place internally in a 100ms grid. State line changes shorter than 100ms are not guaranteed to be transmitted! (2) These informations are transmitted as "transient information". Transmit general interrogation command to basic system element. (ON/OFF-status of the information is transmitted immediately in succession) 7-62 DC0-023-2.01 Functions Protocol Elements Dial-Up Traffic (DIA) Possible remote terminal unit return information: Parameter Return information function_(PRE) Station Note Status RTS (1= state line active) 255 (1) Status CTS (1 = state line active) 255 (1) Status DCD (1 = state line active) 255 (1) Status DTR (1 = state line active) 255 (1) Status DSR (1 = state line active) 255 (1) Station status 255 1 = Station enabled for call cycle Station failure 255 1 = master station failed protocol-specific return information 0 255 Connection setup "stored (flagged in advance)" protocol-specific return information 1 255 Connection setup "in progress" protocol-specific return information 2 255 Connection "established" protocol-specific return information 3 255 Connection setup "not possible" (number of redials elapsed without success) 2) protocol-specific return information 4 255 Connection setup executed successfully 2) protocol-specific return information 5 255 protocol-specific return information 6 255 Connection "terminated" protocol-specific return information 7 255 Connection setup not possible (Station not enabled on protocol element) protocol-specific return information 9 Legend: 255 Dialing pause (after an unsuccessful connection setup attempt, a dialing pause is performed. Afterwards a new connection setup is initiated) 2) 2) "The telephone line has been unplugged" Status of Layer 1 interrogation. (only applicable for Kabelmetall ISDN terminal adapter) Station .......Station number 255......... Station number not used! (1) States of the state lines are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. The spontaneous transmission of the current states takes place internally in a 100ms grid. State line changes shorter than 100ms are not guaranteed to be transmitted! (2) These informations are transmitted as "transient information". Transmit general interrogation command to basic system element. (ON/OFF-status of the information is transmitted immediately in succession) Functions Protocol Elements DC0-023-2.01 7-63 Dial-Up Traffic (DIA) 7-64 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8. LAN Communication (104) The IEC 60870-5-104 protocol is a transmission protocol on OSI-layer 5-7 for the communication between control systems or between master stations and remote terminal units. For OSI-layer 3+4 the TCP/IP protocol is implemented. The protocol is especially suitable for SCADA applications. In contrast to the IEC 60870-5-101 protocol, which establishes connections over serial interfaces, the IEC 60870-5104 interface enables the communication over networks (Local Area Network "LAN" and Wide Area Network "WAN"). Thereby common network components such as switches and routers can be used. The IEC 60870-5-104 protocol uses a signal-orientated data model. Every message represents one data point, such as e.g. one measured value, setpoint value, command or alarm. This message is thereby defined by an address and a data type. The address then determines which signal is concerned, i.e. transmitter and receiver must know the meaning of the address. For the transmission of data, a "TCP-Connection" is established between 2 participating stations. One station can establish an independent connection to several different stations. Each station has equal access and can spontaneously perform a data transmission. Master station-1 Master station-2 Switch Switch Router Router Master station-n LAN/WAN-Network Router Router Router Switch Switch Switch LAN-Interface LAN-Interface Remote station-1 LAN-Interface Remote station-2 LAN-Interface Remote station-n max. 100 connections per LAN-Interface Functions Protocol Elements DC0-023-2.01 8-1 LAN-Communikation (104) General Functions Communication between one station and one or more remote stations (IEC 60870-5-104) • LAN/WAN Communication over Ethernet TCP/IP according to IEC 60870-5-104 ─ Supported functionality according to − ACP 1703 Interoperability IEC 60870-5-101/104 (DC0-013-1) − Ax 1703 Interoperability IEC 60870-5-101/104 (DA0-046-1) ─ Acquisition of events (transmission of data ready to be sent) ─ General interrogation, outstation interrogation ─ Clock synchronization − Clock synchronization with one or more NTP servers ∗ Server synchronized via GPS (DCF77 on inquiry) ∗ One NTP server can serve several automation units − − − NTP (network time protocol) according to RFC 1305 Up to 4 different NTP servers can be interrogated (redundancy) Cyclic, can be set in a seconds grid; self-adapting ─ Command transmission − Supervision of maximum transport delay in control direction (command received too late) ─ Transmission of integrated totals • SICAM TOOLBOX II connection over LAN/WAN ("remote connection") ─ Connection is made via TELNET (Port 2001) according to RFC 854 ─ At one time, exactly one SICAM TOOLBOX II can be served • Functions for supporting redundant communication routes ─ Redundant connections managed by the basic system element and/or protocol element (according to IEC 60870-5-104 Edition 2.0) − controlling station − controlled station ─ Synchronous redundant connections 8-2 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.1. LAN/WAN Communication over Ethernet TCP/IP according to IEC 60870-5-104 8.1.1. Layer Model – General Information about the Protocols used Protocols according to the IEC 60870-5-104 standard are based on the OSI layer model. IEC 60870-5-5 Application Procedures 7 6 5 IEC 60870-5-104 APCI TELNET TCP 4 3 2 HTTP APDU NTP UDP IP ICMP IP Encapsulation ARP Legende: APDU ……….. Application Protocol Data Unit (IEC 60870-5-104) APCI ……...…. Application Protocol Control Information (IEC 60870-5-104) ARP ……...….. Address Resolution Protocol HTTP ….....….. Hyper Text Transfer Protocol ICMP …..…….. Internet Control Message Protocol IP …………….. Internet Protocol NTP ………….. Network Time Protocol TCP …….……. Transmission Control Protocol UDP ……….…. User Datagram Protocol IP Encapsulation RFC 894 1 Ethernet Layer …. IEC 60870-5-104 Task Functions, Characteristics, Comments 7 - Application Application • Transmit handling • Receive handling • Management of multiple connections 6 - Presentation Data format • IEC 60870-5-104 APDU's to Ax 1703 / ACP 1703 and compatible systems In the "private range" according to IEC 60870-5-104, Ax 1703 / ACP 1703-specific system messages and some user data are implemented 5 - Session Interface between data format and communication protocol • IEC 60870-5-104 APCI • NTP according to RFC 1305 • TELNET according to RFC 854 4 - Transport 3 - Network Communication protocol • TCP/IP according to RFC 791 and RFC 793 • ICMP according to RFC 792 2 - Data Link 1 - Physical LAN interface • Ethernet 10/100 Mbps according to IEEE 802.3 • Medium and transmission rate can be selected with SICAM TOOLBOX II • Connection technique (on the master control or communication element) RJ45 for copper and MT-RJ connector for FO • ARP according to RFC 826 • IP Encapsulation according to RFC 894 Note: In the supplement there is a short description of the protocols (layer 1-5). Functions Protocol Elements DC0-023-2.01 8-3 LAN-Communikation (104) 8.1.2. Definition of the Connections IP Addresses Every device which is connected to a TCP/IP network has an unambiguous IP address. 32 The protocol firmware supports only IP addresses in the format IPv4 (=32 Bit). With that, 2 , in other words 4,294,967,296 addresses can be represented. The IP address is mostly represented in the dotted decimal notation. Example: 130. 94.122.195 The IP address of the own station is to be parameterized in the system-technical parameters with the parameter IP-address | own IP-address. The IP address of the remote station is to be parameterized for each connection in the system-technical parameters of the Connection definitionen. Port number Every IP connection is defined by the IP address of the own station and the remote station and the port number. The port numbers are defined by the IANA (Internet Assigned Numbers Authority). Port numbers used in the LAN/WAN protocol firmware: Port Number Protocol 2004 Standard IEC 60870-5-104 IEC 60870-5-104 Edition 2.0 80 HTTP (Hypertext Transfer Protocol) RFC 2616 (HTTP/1.1) 123 NTP V3 (Network Time Protocol) RFC 1305 Telnet RFC 854 2001 1) Legend: RFC .. Request for Comments 1) this port number is not registered with IANA! Default Router (Default Gateway) If the own network is connected by means of a router, then the IP address of the default router is to be set in the system-technical parameters of the protocol firmware with the parameter IP-address | Default-Router (Default-Gateway). 8-4 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) Subnet Mask The subnet mask is a bit mask, which splits up an IP address into a network part and a device part (host part). It is used in IP networks to make routing decisions. The subnet mask is to be set in the system-technical parameters of the protocol firmware with the parameter IPaddress | Subnet mask. The subnet mask is exactly as long as the IP address on which it is applied (therefore 32 Bit for IPv4). All bits of the network part are set to "1" and all bits of the device part to "0". Predominantly, the notation of a network mask is not performed binary, rather (as for IP addresses too) frequently in decimal notation (dotted decimal notation). Consequently, the IPv4 network mask for a 27 bit network part reads 255.255.255.224. The usable address space of a network is defined by the subnet mask. For a 27 bit network part, the first 27 places of the IP address of the network part are identical and for all hosts of the network. The network part is continuous in all practical cases of application (without zeros in between). Example: Calculation of network and host section IPv4 address = 130.94.122.195 Network part = 27 Bit Subnet mask = 255 . 255 . 255 . 224 11111111 11111111 11111111 11100000 IP Address Network mask Network part Decimal 130.094.122.195 255.255.255.224 130.094.122.192 Binary 10000010 01011110 01111010 11000011 11111111 11111111 11111111 11100000 10000010 01011110 01111010 11000000 Calculation IP address AND Subnet mask = Network part IP Address Network mask Device part 130.094.122.195 255.255.255.224 3 10000010 01011110 01111010 11000011 11111111 11111111 11111111 11100000 00000000 00000000 00000000 00000011 IP address AND (NOT subnet mask) = Device part A network mask with 27 bits set produces a network part of 130.94.122.192. 5 bits, and therefore 32 addresses, remain for the device part. In the example above, the smallest host address ends with 11000000 (decimal: 192), the largest possible host address with the octet 11011111 (decimal: 223). The address range for the subnet in the example is therefore 130.094.122.192 to 130.094.122.223. The largest address is by definition reserved for the IP broadcast and the smallest address describes the network itself. They are therefore not included among the freely usable addresses. In practice, the default gateway is often assigned to the smallest (in the example, binary: 11000001, decimal: 193) or the largest (in the example, binary: 11011110, decimal: 222) usable IP address in the network. Functions Protocol Elements DC0-023-2.01 8-5 LAN-Communikation (104) Connection-specific parameters In the master station and in the remote terminal unit(s), the required settings are to be carried out in the parameters of the Connection definition for every connection. The following parameters can be set per connection: • Parameter "Stat. No" The station number is used SICAM 1703 internal for the routing of the data, diagnostic treatment and failure management. The station number is the SICAM 1703 internal reference for that connection to which an IP address is assigned. During the data transmission, only the IP address assigned to the station number is transmitted, the station number is not transmitted. For the data flow routing, the data to be transmitted are routed to a "station number" (connection number = destination station number). The station number (Stat. No.) is to be entered in the parameter Connection definition | Stat. no. for each connection. • Parameter "Connection" A parameterized connection can be activated/deactivated with the parameter Connection definition | Connection. e.g. this way connections can be prepared, that are first activated at a later time by means of parameterization. • Parameter "Connection setup" For every TCP/IP connection, one party is either "Listener (Server)" or "Connector (Client)". The TCP/IP connection is always only established by the "Connector (Client)". With the parameter Connection definition | connection setup the role of the own station is to be parameterized for every connection. • Parameter "Data flow control" Through the plant configuration, it is determined for every connection whether a station according to IEC 608705-104 is a "Controlling Station" or a "Controlled Station". Therefore for every connection one party is to be parameterized either as "Controlling Station" or as "Controlled Station". The IEC 60870-5-104 data flow is started/stopped by the "Controlling Station". With the parameter Connection definition | data flow control the role of the own station is to be parameterized for every connection. • Parameter "IP address A", "IP address B", "IP address C", "IP address D" For every connection the IP address of the remote station is to be parameterized. The IP address (Internet-Protocol) is a number, which permits the addressing of parties in LAN/WAN IP networks. This address must always be unambiguous in one network. The IP address is to be parameterized as follows: Example: 130. 94.122.195 A B C D … IP address The IP address of the remote station is to be parameterized for every connection with the parameters Connection definition | IP-addr A, IP-addr B, IP-addr C, IP-addr D. • Parameter "IP-addr" [only ETA2] For every connection the IP address of the remote station is to be parameterized. The IP address (Internet-Protocol) is a number, which permits the addressing of parties in LAN/WAN IP networks. This address must always be unambiguous in one network. The IP address is to be parameterized as follows: Example: 130. 94.122.195 The IP address of the remote station is to be parameterized for every connection with the parameters Connection definition | IP-addr. 8-6 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) • Parameter "Redundancy" For every connection, its redundancy function is to be determined for the selected redundancy control. Possible redundancy functions: - No redundancy [Default] - Real connection - Virtual connection - Connection has IEC 60870-5-104 Controlling functionality - i.e. no redundancy For further details about this, refer to chapter "Functions for the support of redundant communication routes". With the parameter Connection definition | Redundancy the function of the own station is to be parameterized for every connection. • Parameter "RedGroup" When using the redundancy according to IEC 60870-5-104, every connection can be assigned to one of several redundancy groups. For further details about this, refer to chapter "Functions for the support of redundant communication routes". With the parameter Connection definition | RedGroup the redundancy group number is parameterized for the connection. • Parameter "Stop behavior" If the own station is parameterized as "Controlled Station" and the IEC 60870-5-104 data flow has been stopped by the "Controlling Station" with "STOP DataTransfer activation)", with the parameter Connection definition | stop behaviour it can be selected whether the data to be sent are saved or discarded. • Parameter "104-Parameter" and "104-Par. expanded" [ET02] For every connection, with the parameters Connection definition | 104-parameter and Connection definition | 104-par. extended one from max. 4 possible 104-Parameter parameter-groups can be selected. In these parameter groups, IEC 60870-5-104 specific parameters are to be set. 104-Parameter Groups: - Standard, Group 0 - Standard, Group 1 - Expanded, Group 0 - Expanded, Group 1 • Parameter "104-Parameter" [ETA2] For every connection, with the parameter Connection definition | 104-parameter one from max. 4 possible 104-Parameter parameter-groups can be selected. In these parameter groups, IEC 60870-5-104 specific parameters are to be set. 104-Parameter Groups: - Group 0 - 3 • Parameter "Failure" For certain redundancy configurations or operating modes, for the SICAM 1703 internal diagnostics, the failure of a connection can be suppressed with the parameter Connection definition | Failure. If the failure is suppressed, the connection is never signaled in the diagnostic as failed and all messages in transmit direction (also INIT-End) are discarded until the connection is established! Note: As a result a ring overflow is avoided with non-connected remote stations. • Parameter "Weekday" With function enabled with the parameter Connection definition | day of week the weekday (DOW field of the time stamp) is always set to “0” by the LAN/WAN protocol element for all messages in transmit direction. • Parameter "Daylight-saving time" With function enabled with the parameter Connection definition | summertime the summer time bit (SU bit of the time stamp) is always set to “0” by the LAN/WAN protocol element for all messages in transmit direction. • Parameter "Originator address" With function enabled with the parameter Connection definition | originator address the originator address is always set to “0” by the LAN/WAN protocol element for all messages in transmit direction. For the coupling of different systems with the IEC 60870-5-104 protocol, the setting of the variable elements of the message according to IEC 60870-5-104 to the following defined values is required: Functions Protocol Elements DC0-023-2.01 8-7 LAN-Communikation (104) IEC 60870-5-101 Parameter Description Cause of transmission (COT) Number of octets for cause of transmission = 2 BSE Common address of ASDU (CASDU) Number of octets for common address of the ASDU = 2 BSE Information object address (IOA) Number of octets for address of the information object = 3 BSE Maximum message length max. 253 BSE Time Stamp Number of octets for time stamp = 7 BSE Legend: BSE = Basic system element Note: If one parameter does not correspond to the required setting, a parameter error is reported! 8-8 System Element DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) IEC 60870-5-104 Parameters The IEC 60870-5-104 specific parameters for "Definition of monitoring times" and "Maximum number of unacknowledged I-format frames k and acknowledgement w" are grouped into parameter groups. The protocol firmware supports 4 parameter groups. One of these parameter groups can be selected for every connection. ATTENTION: The modifying of the 104 specific parameters requires detailed knowledge of the IEC 60870-5104 protocol and should therefore only be performed by communications experts or after consultation! The following IEC 60870-5-104 parameters can be set per parameter group: • Timeout Connection Setup t0 Timeout for connection setup (Default=30sec) Note: The parameters 104-parameter | standard group x | timeout connection setup and 104parameter | extended group x | timeout connection setup are not evaluated by the protocol! • Timeout Transmit t1 Timeout for transmit or test frames (Default=15sec). Transmitted data (Information/Transmit-/Test frames) must be acknowledged by the remote station at the latest before expiry of the Timeout t1 with a transmit or test frame. On timeout the connection is terminated and then re-established. The Timeout t1 is to be parameterized with the parameter 104-parameter | standard group x | timeout transmit t1 or with the parameter 104-parameter | extended group x | timeout transmit t1. • Timeout Transmission Acknowledgement t2 Timeout for acknowledgement, if no data are transmitted t2<t1 (Default=10sec). With the simultaneous transmission of user data (I-Frames) in both directions, acknowledgements are sent together in the user data messages. For the data transmission of user data in only one direction, an acknowledgement (S-frame) is sent after Timeout t2 at the latest. The Timeout t2 is to be parameterized with the parameter 104-parameter | standard group x | timeout transmit acknowledge t2 or with the parameter 104-parameter | extended group x | timeout transmit acknowledge t2. • Timeout Connection Test t3 Timeout for the transmission of Test-Frames, if no data traffic t3>t1 (Default=10sec). If no data are transmitted with connection established, then a test frame (TESTFRact) is sent after t3 at the latest. This must be replied to by the remote station, also with a Test-Frame (TESTFRcon). This test procedure can be performed independently by both sides of a connection. The Timeout t2 is retriggered by the reception of Information/Transmit/Test frames. The Timeout t3 is to be parameterized with the parameter 104-parameter | standard group x | timeout transmit t1 or with the parameter 104-parameter | extended group x | timeout transmit t1. Functions Protocol Elements DC0-023-2.01 8-9 LAN-Communikation (104) The following parameters can be set for each parameter group for "Maximum number of unacknowledged I-format frames k and acknowledgement w": 8-10 • Maximum number of unacknowledged APDUs (k) Greatest difference between receive sequence number and transmit status variable (Default = 12 APDU's). User data are transmitted from one station to the remote station without needing to receive an immediate acknowledgement for the transmitted user data. However, if after a max. number (k) of transmitted but not yet acknowledged ASDUs no acknowledgement has been received, no further data are sent until the reception of the acknowledgement. An acknowledgement must now be sent by the remote station before expiry of t1. For IEC 60870-5-104 a sum acknowledgement is used i.e. all consecutively numbered messages received without error up to a moment in time are acknowledged with an acknowledgement message. The maximum number of unacknowledged APDUs (k) is to be parameterized with the parameter 104parameter | standard group x | Max. no. of APDUs until acknowledgement (k) or with the parameter 104-parameter | extended group x | Max. no. of APDUs until acknowledgement. • Number of APDUs until acknowledgement (w) Acknowledgement at the latest after reception of "w" I-format APDUs (Default = 8 APDU's). User data are transmitted from one station to the remote station without needing to receive an immediate acknowledgement for the transmitted user data. An acknowledgement is sent after the reception of a max. number (w) of user data messages (APDUs). Recommendation: "w" should not exceed 2/3 of the "k"-value. The number of APDUs until acknowledgement (w) is to be parameterized with the parameter 104-parameter | standard group x | number of APDUs until acknowledgement (w) or with the parameter 104parameter | extended group x | number of APDUs until acknowledgement (w). DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) TCP/IP Parameters (Settings) The following TCP/IP parameters are supported by the protocol firmware: • MSS (Maximum Segment Size) transmit direction One TCP packet typically has a maximum size of 1500 Bytes. It may only be so large, that it fits in the transmission layer situated below, the Internet protocol IP. TCP and IP protocols each define a header of 20 Bytes size. Therefore 1460 bytes are left over for the user data in a TCP/IP packet. With the parameter advanced parameters | TCP/IP optimization | MSS (maximum segment size) transmit direction the maximum user data length is determined in the TCP/IP packet (max. 1460 Bytes). The modification of the parameter "MSS (Maximum Segment Size) transmit direction" is then definitely required, if TCP/IP is implemented in combination with transmission systems which cannot transmit the TCP packets with the max. defined size (e.g. GPRS supports max. 500 Bytes). • Transmission optimization The data transmission over TCP/IP can be optimized with the parameter advanced parameters | TCP/IP optimization | transmission optimization for the following requirements: - Default (ACK-Delay, no Nagle) - Bandwidth (ACK-Delay, Nagle) - Throughput (no ACK-Delay, Nagle) - Reaction time (no ACK-Delay, no Nagle) (for details about this, refer to chapter "Data Transmission Procedure") • Initial value TCP expected acknowledgement time The data transmission at TCP-level starts with the set initial value for the expected acknowledgement time. The initial value is to be set with the parameter advanced parameters | TCP/IP optimization | TCP retransmission timeout | initial TCP retransmission timeout. Depending on the quality of the connection, the expected acknowledgement time is adapted dynamically between the parameterized minimum and maximum TCP expected acknowledgement time. • Maximum TCP expected acknowledgement time The maximum TCP expected acknowledgement time can be modified with the parameter advanced parameters | TCP/IP optimization | TCP retransmission timeout | Maximum TCP retransmission timeout. • Minimum TCP expected acknowledgement time The minimum TCP expected acknowledgement time can be modified with the parameter advanced parameters | TCP/IP optimization | TCP retransmission timeout | Minimum TCP retransmission timeout. By default, the parameters are set so that no modification is necessary. ATTENTION: The modifying of the TCP/IP specific parameters requires detailed knowledge of the TCP/IP and IEC 60870-5-104 protocol and should therefore only be performed by communications experts or after consultation! Functions Protocol Elements DC0-023-2.01 8-11 LAN-Communikation (104) 8.1.2.1. Data Transmission Procedure The transmission of the data from the remote terminal unit to the master station as well as from the master station to the remote terminal unit takes place spontaneously for each LAN connection. For each LAN connection, the data transmission is comparable with that between 2 stations over a virtual point-to-point connection. The transmission rate (10/100 Mbit/s) and the method of transmission (full duplex/half duplex) on the ethernet is determined with the parameter advanced parameters | Ethernet-speed and -duplex. In the default setting this parameter is set to "autosense" (=automatic detection) and only needs to be specifically adjusted in exceptional cases. Note: If problems occur with the default setting when coupling other systems directly with cross-over cables or when using HUB's or other network components, here "half duplex" is to be used. The prioritization and 104-blocking of the data to be sent takes place on the basic system element (BSE). The data transmission is started after a startup or with redundancy switchover after establishment of the TCP/IP connection and after "STARTDTact". The data storage on the basic system element is managed individually for each LAN connection (excluded from this are special redundancy modes such as e.g. "synchronous connections"). Data messages "to all" are already split up selectively for every LAN connection by the communications function on the basic system element (BSE). The data processing of the TCP packets can be influenced by the parameter advanced parameters | transmission optimization – the moment for the transmission of a TCP packet is controlled by the Nagle algorithm. The Nagle algorithm is applied with the TCP protocol and should prevent too small packets, for which the additional overhead due to header etc. is considerably larger than the actual user data. Nagle algorithm for the transmission of TCP packets: • • If a TCP packet is full, then send immediately If a TCP packet is not full, then this is first sent when a TCP acknowledgement is received. The data pick-up from the basic system element is performed in such a way, that on the one hand the blocking per connection is optimally utilized, and on the other, one connection with a lot of data does not block others unnecessarily long. With the data pick-up for transmission, the connections are processed in ascending order. The communications function on the basic system element performs the prioritization of the data per connection. During the data pick-up, the highest priority data object is always offered for transmission. Note: - For the optimum prioritization and blocking of the data with LAN/WAN communication, only 1 priority level is to be used. As a result a more favorable prioritization for LAN is achieved, since the data for transmission for each connection (=destination station) are requested in groups (=blocked) by the LAN/WAN protocol element. In addition, through the blocking at TCP/IP level, several messages for this connection are transmitted. Due to this the processing of the connections according to the Round-Robin principle is ensured. (Connections are processed in ascending order) System data are processed with high priority by the communications function on the basic system element and transferred to the LAN/WAN protocol element for transmission as fast as possible. 8-12 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) Data transmission control with Start/Stop (data flow block) For every TCP connection, one station is either "Listener (Server)" or "Connector (Client)". After startup, redundancy switchover or after a failure of the connection, every connection on TCP level is established by that station defined as "Connector (Client)". For IEC 60870-5-104 the data transfer is controlled by the Controlling-Station with the messages Start/Stop data transfer. After establishment of a connection at TCP/IP level, the transmission of the data according to IEC 608705-104 is stopped. The data transfer according to IEC 60870-5-104 is started by that station defined as "Controlling Station" with STARTDTact (Start Data Transfer Activation). After reception of the confirmation from the remote station (STARTDTcon = Start Data Transfer Confirmation) the connection is ready for the transmission of the data. According to IEC 60870-5-104 the data transmission must be started by the Controlling Station with STARTDTact (Start Data Transfer ACTIVATION). The start must be confirmed by the remote station (Controlled Station) with STARTDTcon (Start Data Transfer CONFIRMATION). If no STARTDTcon has been received within t1 after sending STARTDTact, the connection is terminated again. User data may only be transmitted after successful connection establishment. The data transmission is stopped by the Controlling Station with STOPDTact (Stop Data Transfer ACTIVATION). STOPDTact is confirmed by the remote station (Controlled Station) with STOPDTcon (Stop Data Transfer CONFIRMATION). Start-/Stop data transfer messages are transmitted with U-Frames "Unnumbered Control Functions" and are used by the Controlling Station in order to control the data transfer from a Controlled Station. Stop Data Transfer is used especially when several connections are established to one station but one connection (e.g. due to redundancy) is not used. Start/Stop Data Transfer is intended to prevent a possible loss of data during the switchover to another connection. The duration of the stopped data transfer is not monitored! If, as Controlling Station, one remote station blocks the data transfer for a longer period, an overflow of the data storage (rings) on the basic system element (BSE) can occur and through this a fault in the system is signaled. The handling of the user data with stopped "Data Transfer" can be parameterized for each connection with the parameter Connection definition | stop behaviour. Handling of the user data if the data transmission is stopped with STOPDTact: • "Save" [Default] The data are stored in the data storage of the communications function on the basic system element (BSE) until these are deleted by the dwell time monitoring or can be transmitted to the remote station. Advantage: Storage of the data with stopped data transfer Disadvantage: Ring overflow possible • "Discard" All data in transmit direction are read out immediately from the basic system element (BSE) by the protocol firmware, not transmitted and discarded without error message. As a result an overflow of the data storage (rings) is prevented. Advantage: Ring overflow is prevented Disadvantage: Data loss Functions Protocol Elements DC0-023-2.01 8-13 LAN-Communikation (104) 8.1.2.2. Acknowledgement Procedure For each connection, all data messages transmitted must be acknowledged by the remote station. Thereby, not every individual IEC 60870-5-104 packet that can contain several IEC 60870-5-104 message objects must be acknowledged, rather several consecutively numbered messages received without error up to a moment in time can also be acknowledged in one operation with one acknowledgement message (sum acknowledgement procedure). With this sum acknowledgement procedure, user data are transmitted from a station to the remote station without an acknowledgement needing to be received immediately for the transmitted user data. If no acknowledgement has been received after a maximum number (k) of transmitted but not yet acknowledged IEC 60870-5-104 packets (ASDU's), no further data are sent until reception of the acknowledgement. The max. number (k) of messages is to be set with the parameter 104-parameter | standard group x | Max. no. of APDUs until acknowledgement (k) (k) or the parameter 104-parameter | extended group x | Max. no. of APDUs until acknowledgement (k) (k). An acknowledgement must now be sent by the remote station before expiry of t1. With the simultaneous transmission of user data (I-Frames) in both directions, acknowledgements are sent together in the user data messages. For the data transmission of user data in only one direction, an acknowledgement (Sframe) is sent after Timeout t2 at the latest. On reception of IEC 60870-5-104 packets (APDUs) with user data, an acknowledgement must be sent at the latest after reception of a settable maximum number of messages. The max. number (w) of messages is to be set with the parameter 104-parameter | standard group x | number of APDUs until acknowledgement (w) or with the parameter 104-parameter | extended group x | number of APDUs until acknowledgement (w). The retries are (insofar as necessary) performed automatically by the TCP/IP layer of the protocol until the termination of the connection and can only be influenced indirectly with the parameter advanced parameters | TCP/IP optimization | TCP retransmission timeout | initial TCP retransmission timeout, advanced parameters | TCP/IP optimization | TCP retransmission timeout | Maximum TCP retransmission timeout, and the parameter advanced parameters | TCP/IP optimization | TCP retransmission timeout | Minimum TCP retransmission timeout. The data transmission at TCP level starts the data transmission with the settable initial value for the expected acknowledgement time. Depending on the quality of the connection, the expected acknowledgement time is adapted dynamically between the parameterized minimum and maximum TCP expected acknowledgement time. If, with connection established, the IEC 60870-5-104 acknowledgement for transmitted data (information/transmit/test frames) is missing for longer than the set 104 expected acknowledgement time (timeout t1), all IEC 60870-5-104 messages already sent but not yet acknowledged are negatively acknowledged to the basic system element (BSE), the TCP connection is terminated with RST and the remote station flagged as failed. The connection is setup again after a fixed implemented delay time of 2 seconds. Note: The parameter 104-parameter | standard group x | timeout connection setup t0 and the parameter 104-parameter | extended group x | timeout connection setup t0 are not evaluated by the LAN/WAN protocol element! The error message for the failed connection is reset after successfully established connection at TCP level. 8-14 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.1.2.3. Failure Monitoring The monitoring of every established connection is carried out by the active master / remote terminal unit either by means of (subject to acknowledgement) spontaneously transmitted user data messages or by means of cyclic transmitted messages (Test-Frames). The failure monitoring can be carried out independently by both participating stations of a connection. The Test-Frames are generated by the protocol firmware itself and are not transferred to the basic system element. If no user data are transmitted with a connection established and activated data transfer, a Test-Frame (TESTFRact) is sent at the latest after expiry of the time t3 (Timeout Connection Test). This Test-Frame must be replied to (acknowledged) by the remote station with a Test-Frame (TESTFRcon) at the latest before expiry of the timeout t1. The "Test function of the link layer" also enables a cyclic message transmission and monitoring controlled by the basic system element. This test function can be parameterized on the basic system element (BSE) in the IEC870-5-101/104 parameter block. The timeout t3 is retriggered with the transmission of user data messages or test frames. After a message transmission, the remote station is signaled as failed after expiry of the monitoring time t1 (Timeout) and the TCP connection is terminated with RST. For details see also chapter Acknowledgement Procedure! No further data are sent to failed remote stations until successful establishment of the connection. The data are stored in the data storage of the communication function on the basic system element (BSE) until these are deleted by the dwell time monitoring or can be transmitted to the re-reachable remote station. Functions Protocol Elements DC0-023-2.01 8-15 LAN-Communikation (104) 8.1.3. Station Initialization After startup, the connection for every connection is established to TCP/IP level and then to 104-level by the Controlling Station by means of STARTDTact (Start Data Transfer Activation). Afterwards the transmission of user data and other system messages to the remote station is started either immediately or only after the transmission of the INIT-End message. Initialization End The INIT-End message "<TI=70> Initialization End" is only transmitted to the remote station for each ASDU after startup of the component or the basic system element, if the following preconditions are fulfilled: • • • • 8.1.4. Connection is established at TCP/IP level Connection is established at IEC 60870-5-104 level with STARTDTact „Send Initialization End“ must be enabled on the basic system element in the IEC 60870-5-101/104 parameter block "INIT-End" has been received by the basic system Acquisition of Events (transmission of data ready to be sent) The transmission of the data from the remote terminal unit to the master station as well as from the master station to the remote terminal unit takes place spontaneously with connection established and for each connection. The prioritization and 104-blocking of the data ready to be sent takes place on the basic system element (BSE). The data transmission is started after a startup or, with redundancy switchover, after successful establishment of the connection. For further details, refer to chapter "Data Transmission Procedure"! 8.1.5. General Interrogation, Outstation Interrogation The general interrogation (outstation interrogation) function is used to update the master station after the internal connection initialization or after the master station has detected a loss of information. The general interrogation function of the master station requests the remote terminal unit connected over one connection to transmit the current values of all its process variables. A general interrogation command "to all" triggered in the system is always transferred by the communications function on the basic system element (BSE) station-selective (per connection) to the protocol element of the master station and transmitted by this to the remote terminal units. 8-16 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.1.6. Clock Synchronization In networks and in systems with time-critical tasks, a precise time is essential. The clock synchronization for IEC 60870-5-104 can be performed in the following ways: • • Clock synchronization command <TI:=103> Network Time Protocol (NTP) according to RFC 1305 Messages that are transmitted after a startup, but before the station has the correct time, contain the relative time from startup (reference day: 1.1.2001) with the flagging of the time stamp as invalid. 8.1.6.1. Clock Synchronization Command The procedure defined in IEC 60870-5-5 for the clock synchronization is not recommended for LAN communication, since with LAN communication the exact moment of the transmission cannot be determined. However, the clock synchronization with the clock synchronization command <TI:=103> can be implemented in configurations with networks if the "maximum network delay" is less than the accuracy required for time synchronization. Example: If the network provider guarantees, that the maximum delay for the transmission in the network is never greater than 400 milliseconds and the accuracy required for the time synchronization is only 1 second, then this procedure can be used for clock synchronization. Functions Protocol Elements DC0-023-2.01 8-17 LAN-Communikation (104) 8.1.6.2. Clock Synchronization with Network Time Protocol (NTP) The Network Time Protocol (NTP) is a standard for the synchronization of clocks in systems over IP communication networks. NTP is a hierarchical protocol over which time servers can determine a common time amongst each other. The NTP protocol determines the delay of packets in the network and compensates these for the clock synchronization. The NTP protocol uses port number 123. The NTP protocol is a Client/Server protocol. NTP clients can request the time from NTP servers. The Network Time Protocol (NTP) uses the connectionless network protocol UDP. The NTP protocol has been developed especially to enable a reliable time tagging over networks with variable packet delay. The NTP protocol is defined in the standard "RFC 1305: NTP V3". The time stamps in NTP are 64 bits long. 32 bits encode the seconds since the 1st January 1900 00:00:00 hours, 32 the other 32 bits the seconds fraction. In this way, a time period of 2 seconds (about 136 years) can be −32 represented with a resolution of 2 seconds (about 0.25 nanoseconds). NTP uses a UTC time scale and supports switching seconds, but not daylight-saving time and winter time. NTP uses a hierarchical system of different levels. The level specifies how far the NTP server is from an external time source. As time source an atomic clock, a DCF77 receiver or a GPS receiver can be used. A Layer-1 server is connected directly with a time source and uses this as reference for its time. A Layer-2 server uses a Layer-1 server as reference and synchronizes itself with other servers on its level if the connection to the higher level fails. The highest level is 16 and signifies, that this NTP server has not yet calibrated itself with other servers. As a rule no more than 4 levels exist, since otherwise the time would deviate too much. 8-18 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.1.6.2.1. Clock Synchronization with one or several NTP Servers For the clock synchronization of a component, the time information can be requested from one or several NTP servers in the network. The NTP servers themselves are synchronized either directly with DCF77 or GPS receiver, or by interrogating the time information from other NTP servers. Clock synchronization over LAN: • • • • • Clock synchronization with one or several NTP servers - Server synchronized over GPS (DCF77 on request) - One server can service several automation units Protocol: NTP V3 (Network Time Protocol) according to RFC 1305 Up to 4 different NTP servers can be interrogated (redundancy) Cyclic time interrogation of the NTP servers, settable in seconds grid, self-adapting Achievable accuracy: approx. 3ms (dependent on the quality of the IP network) If the clock synchronization with NTP is activated on a LAN/WAN protocol element, the transfer of a received clock synchronization command with <TI:=105> to the basic system element is disabled. Functions Protocol Elements DC0-023-2.01 8-19 LAN-Communikation (104) Parameters for NTP time synchronization (NTP Client): • NTP Time Synchronization The time synchronization by means of NTP is enabled with the parameter NTP-time synchronisation client | NTP-time synchronisation. The other parameters for NTP time synchronization are only displayed after the function has been enabled. • NTP Maximum Time Deviation If the deviation of the time between the own component and the NTP server is greater than the parameterized value, an error is signaled. The maximum time deviation is to be parameterized with the parameter NTP-time synchronisation client | NTP optimization | NTP maximum time deviation. • NTP Minimum Cycle Time The interrogation of the time from the NTP server (NTP Request) is performed cyclic by the protocol element in time scale between NTP maximum cycle time and NTP minimum cycle time. Note: With the communication over GPRS the cycle time must not be set too short, since due to the cyclic time request, corresponding transmission charges accumulate. • NTP Maximum Cycle Time See NTP Minimum Cycle Time. • NTP Cycle Time until synchronized Until the 1st synchronization, the interrogation of the time from the NTP servers (NTP-Requests) can be carried out in a shorter time scale. The time scale is parameterized with the parameter NTP-time synchronisation client | NTP optimization | NTP cycle time until synchronized. After successful synchronization, the interrogation of the time is carried out cyclic in a time scale between "NTP Minimal Cycle Time" and "NTP Maximum Cycle Time". The cycle times are to be parameterized with the parameters NTPtime synchronisation client | NTP optimization | NTP minimal cycle time, and NTP-time synchronisation client | NTP optimization | NTP maximal cycle time. • NTP Server 1 IP address NTP Server 2 IP address NTP Server 3 IP address NTP Server 4 IP address The protocol firmware supports max. 4 different redundant NTP servers. The time is always requested from all parameterized NTP servers. The time for the synchronization is determined by means of a defined algorithm from the times received from the NTP servers. For every NTP server the unambiguous IP address of the NTP server is to be parameterized in the format IPv4 (32 Bit) in dotted decimal notation. Example: 130. 94.122.200 The IP addresses of the NTP servers are to be parameterized with the parameters NTP-time synchronisation client | NTP-Server 1 IP-address, … NTP-Server 4 IP-address. • 8-20 Error Signalization Delay For problems during the interrogation of the time from NTP servers, the signalization of the error "No valid time from NTP server" can be delayed with the parameter NTP-time synchronisation client | NTP optimization | Delay error signalization. Through this, short-term faults or load problems in the network do not lead to any error. DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.1.6.2.2. Clock Synchronization for one or several NTP Clients In configurations with less demand on the accuracy for time synchronization, the LAN/WAN protocol firmware in the SICAM 1703 component provides an integrated NTP server for other systems. This function is then helpful if the clock synchronization of the remote terminal unit is carried out by means of DCF77 receiver or over a serial interface, and in this remote terminal unit other devices are connected over LAN/WAN, which require a time synchronization with NTP. Through this the additional procurement of an NTP server for the subnet in the remote terminal unit is not necessary! The time of the integrated NTP server is controlled by the local time of the component. The accuracy is therefore dependent on the accuracy of the clock synchronization of the component itself. Clock synchronization over LAN: (NTP Server) • • • • • • Protocol: NTP V4 (for NTP V4 there is presently no public specification) Level 14 (… based on the achievable accuracy with remote synchronization over serial communication line) The achievable accuracy is dependent on the accuracy of the clock synchronization of the component The NTP server supports only the request of the time (BROADCAST transmission of the time is not supported by the integrated NTP server) max. 100 clients with a time request 1x per minute Comment: This limit is an experimental value (the limit results from the system load utilization) Reaction time (transmission of the requested time by the protocol firmware): Typically 300-900us Parameters for NTP time synchronization (Client): • NTP Server The integrated NTP server function of the LAN/WAN communications firmware is enabled with the parameter NTP-time synchronisation server | NTP-Server. • Synchronization with invalid time With function enabled with the parameter NTP-time synchronisation server | synchronisation with invalid time NTP reply messages are also sent when the time of the SICAM 1703 component is not yet set. Functions Protocol Elements DC0-023-2.01 8-21 LAN-Communikation (104) 8.1.7. Command Transmission With connection established (Data Transfer must be started and the number of unacknowledged APDUs must not be reached) data messages in command direction are always transmitted spontaneously from the master station to the remote station. The prioritization and 104-blocking of the data to be sent already takes place on the basic system element (BSE). Commands and other messages defined according to IEC 60870-5-104 are always transmitted without 104-blocking. For further details, refer to chapter "Data Transmission Procedure" and “Message Conversion”! 8.1.7.1. Command Transfer Monitoring (dwell time monitoring for data in the network) During the transmission of data in networks, unwanted delays can occur. So that no unwanted process behavior is triggered due to a delayed output of commands, the LAN/WAN protocol element can monitor the transmission time (dwell time) of the data in the network for selected process information in control direction. Through this monitoring the output of "old commands" is prevented. If the monitoring is activated, on reception of a command message over the LAN interface, the time stamp in the message is compared with the current time of the component. If the determined command delay time (transmission time of the data in the network) is greater than the parameterized command delay monitoring or the time of the component is not yet set, the command message is discarded without error message. The commanding station detects the failed command output through the missing of the confirmation of activation (ACTCON). The time for the command delay monitoring is to be parameterized on the basic system element (BSE) in the IEC 870-5-101/104 parameters per protocol element. The command delay monitoring can also be deactivated (command delay monitoring = 0). To localize the error, the number of commands discarded by the command delay monitoring since RESET is summed for each connection and the last discarded command messages are also saved in a diagnostic ring. The counters and the diagnostic ring can be read out with the Toolbox (ST-Emulation). Monitoring the command delay for the following message types (TI's): • • • • • • • • <TI:=58> Single command with time stamp CP56Time2a <TI:=59> Double command with time stamp CP56Time2a <TI:=60> Regulating step command with time stamp CP56Time2a <TI:=61> Setpoint command, normalized value with time stamp CP56Time2a <TI:=62> Setpoint command, scaled value with time stamp CP56Time2a <TI:=63> Setpoint command, short floating point number value with time stamp CP56Time2a <TI:=64> Bit pattern of 32 bit with time stamp CP56Time2a <TI:=107> Check command with time stamp CP56Time2a Hints: - The message conversion in receive direction can also generate the assigned message types without time stamp. As a result, indirectly the internal type identifications <TI=45, 46, 47, 48, 59, 50, 51 and 104> are also affected. - The command delay monitoring is only carried out for command messages with the cause of transmission ACT (Activation)! 8-22 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.1.7.2. Transmission of Integrated Totals A counter interrogation command "to all" triggered in the system is always transferred by the communications function on the basic system element (BSE) station-selective (per connection) to the protocol element of the master station and transmitted by this to the remote terminal units. The functionality implemented in the System SICAM 1703 concerning integrated totals is documented in the document "Common Functions of Peripheral Elements according to IEC 60870-5-101/104". Functions Protocol Elements DC0-023-2.01 8-23 LAN-Communikation (104) 8.2. Function for the Support of Redundant Communication Routes To increase the availability both master stations as well as remote terminal units can be designed redundant. The following redundancy modes are supported: • • • 8.2.1. PSI-Redundancy (Synchronous Connections) 104-Redundancy - Norwegian User Conventions (NUC) 1703-Redundancy PSI-Redundancy (Synchronous Connections) The redundancy mode "PSI-Redundancy (synchronous connections)" is a proprietary function and is only implemented in plants with a control system (Controlling Station) from the manufacturer "PSI". This redundancy function is not defined in the IEC 60870-5-104 standard! This redundancy mode is selected by setting the parameter Redundancy | Redundancy mode to PSIRedundancy and with that is continuously activated. A switchover/control of the redundancy through system-internal redundancy control messages as well as the redundancy functions of the Controlling Station are not supported for this redundancy mode! Functioning method of synchronous connections: 8-24 • The data are sent over the synchronous connections with the same data content • The data are sent over the synchronous connections in the same order • The data are sent over the synchronous connections with the same IEC 60870-5-104 sequence number The data to the first synchronous connection established are transmitted beginning with the sequence number "0". The data to other synchronous connections established later are transmitted with the current consecutive sequence number. (the sequence number for received data is individual for each synchronous connection) • The data are transmitted over the synchronous connections with as little chronological offset as possible • In receive direction, there is no specific function for synchronous connections – received data are transferred to the basic system element for each synchronous connection DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) Controlling Station 1 Controlling Station 2 Controlling Station(s) Network (optional) [PRE] Controlled Station [PRE] Legend: VC ….. Data in transmission direction are stored in one central process image for the virtual connection (=for all synchronous connections together ) . ….. The data of the (1703-internal) virtual connection are transmitted with - equal data content - equal sequence numbers - preferably small temporal offset on the synchronous connections to the connected remote stations . (Control of the data transmission with STARTDTact may not be used with synchronous connections) Process image ….. The data transmission between BSE and PRE takes place via a „virtual connection“ [BSE] ….. Data in receive direction are passed from each of the synchronous connections to the basic system element (BSE) either with the „virtual connection“ or with the „real connection“ (settable). Logical connection On the LAN/WAN protocol element, synchronous connections for PSI redundancy and normal connections (without redundancy) can be used mixed. For synchronous connections, system internal only 1 virtual connection may be parameterized and at least 2 or more real connections. The synchronous connections form a group – these are handled as one connection in transmit direction from the perspective of the communications function on the basic system element. The synchronism of the connections is controlled directly by the LAN/WAN protocol element. The data transferred from the basic system element for transmission to the synchronous connections are duplicated by the LAN/WAN protocol element to the assigned connections. Due to the synchronism of the connections during transmission, the data throughput is defined by the slowest remote station. With acknowledgement required, a further transmission can only then take place when all remote stations have acknowledged. In transmit direction, on the basic system element the data are only routed to the "virtual connection“ and passed on immediately to the remote station by the LAN/WAN protocol element without TCP/IP blocking. If the control of the data transmission is stopped for one connection, the data for this connection are discarded. In receive direction, the data are passed on to the basic system element either with the station number of the virtual connection or with the station number of the real connection. The selection of the station number is performed with the parameter Redundancy | station number for received telegrams. On failure of one real connection, this is signaled as failed. On failure of all real connections, in addition the virtual connection is signaled as failed. Functions Protocol Elements DC0-023-2.01 8-25 LAN-Communikation (104) Necessary parameter settings for synchronous connection on the LAN/WAN protocol element: • Virtual Connection A selected connection is to be defined as virtual connection in the parameters Connection definition | Redundancy. The virtual connection is only used for the internal communication with the basic system element. This connection does not exist on the LAN (the IP address of the virtual connection is of no significance and is not used). • Synchronous Connections (real connections) All connections to the connected remote stations that are to be handled as synchronous connections are to be defined as real connections in the parameters Connection definition | Redundancy. For the real connections, in addition all necessary parameters of the Connection definition (such as IP address of the remote station,…) must be parameterized. • IEC 60870-5-104 Data Flow Control of the own station (Controlling/Controlled) The data flow control is defined for all synchronous connections together with the parameter Connection definition | data flow control for the virtual connection! Note: For connections that are operated without redundancy, the parameter Connection definition | Redundancy is to be set to "none". Necessary parameter settings of the communications function/topology on the basic system element for synchronous connections in transmit direction: • • • • • • • Deactivation of the state compression All user data must be assigned to one priority level For the failure management, the real connections must be entered in the topology For the real connections the disabling of system data must be activated in the topology For the failure management of the data in receive direction, the parameter setting of the topology and the source ID is required. The virtual connection and all real connections must be parameterized as "Controlled". No data may be routed to a real connection. Limitations: • • • • • 8-26 A special handling for synchronous connections is only implemented in transmit direction! Synchronous connections to one SICAM 1703 component must not be used! With synchronous connections the remote station may not use Start/Stop for the control of the data transmission! The formation of redundancy groups for synchronous connections is not supported! Data in transmit directions may not be routed "to all"! DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.2.2. 104-Redundancy - Norwegian User Conventions (NUC) With 104-redundancy, one remote terminal unit (Controlled Station) is connected with one or several redundant master stations (Controlling Stations) over several logical connections. The data transmission always takes place only over 1 started connection per redundancy group. The 104-redundancy is based on 2 or more connections that are jointly managed in one redundancy group. The redundancy mode "104-Redundancy" is defined in the IEC 60870-5-104 standard and in the country-specific standard Norwegian User Conventions (NUC). This redundancy mode is selected by setting the parameter Redundancy | Redundancy mode to 104Redundancy and through the connection-specific settings. A switchover/control of the redundancy through system-internal redundancy control messages as well as the redundancy functions of the Controlling Station are not supported for this redundancy mode! Redundancy function according to IEC 60870-5-104 and Norwegian User Conventions (NUC): • The master station (Controlling Station) and the remote terminal unit (Controlled Station) support multiple "logical connections" • Multiple logical connections are grouped to form one redundancy group • Within a redundancy group only 1 logical connection may be started • Only the master station (Controlling Station) decides which logical connection within a redundancy group is started • All logical connections of a redundancy group are monitored by means of test frames • One redundancy group is only supplied by one process image Functions Protocol Elements DC0-023-2.01 8-27 LAN-Communikation (104) 8.2.2.1. 104-Redundancy with 1 Ethernet Interface The 104-redundancy with 1 ethernet interface enables the interfacing of one component to remote stations with redundant ethernet interfaces over 1 ethernet network. Example for a remote station with redundant interfaces is e.g. one system with two ethernet interfaces or two systems that are operated redundantly or a combination of both. A TCP connection exists for every redundant ethernet interface of the remote station and these redundant connections are grouped to form a redundancy group. Only one of these redundant connections may be started by the Controlling Station and data transmitted. Simplified, on the NIP the 104-redundancy group can be seen as a switch that selects to which connection the data to be sent are transferred. For details about Start/Stop refer to chapter "Control of the Data Transmission with Start/Stop". The Controlling Station switches between the redundant connections. There are two types of redundancy switchover, the "soft switchover" and the "hard switchover". The soft switchover takes place applicational, e.g. during tests or if a part of the controlling station is to be taken out of operation. First the previously started connection is stopped with a STOPDTact. Only when STOPDTcon has been received by the controlling station is a STARTDTact sent to another connection. This then becomes the new started connection. The hard switchover occurs when the controlling station detects a connection failure (e.g. through a 104-Timeout). A STARTDTact is then sent immediately over another connection. This then becomes the new started connection. If at this moment in the controlled station the previously started connection is still established (because the controlled station has not detected any connection failure), it is closed immediately. Several redundancy groups independent of each other are possible. Precisely one redundancy group can be assigned to each connection. The SICAM 1703 internal redundancy control messages are not used in the controlled station. In the SICAM 1703 controlling station the entire LAN/WAN protocol element is switched to "ACTIVE/PASSIVE" by the SICAM 1703 internal redundancy control messages. 8-28 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) Redundancy group 1 Redundancy group 2 Controlling Station Controlling Station Interface 1 Interface 2 Interface 1 Interface 2 Network VC [PRE] VC (optional) [PRE] Controlled Station Legend: ….. Data in transmit direction are stored in a central process image for each redundancy group for the virtual connections . (RG1 = Redundancy group 1, RG2 = Redundancy group 2) ….. The data transmission takes only place via the connection on which the IEC60870-5-104 data transfer was startet with STARTDTact. ( Data transmission may only be activated on 1 connection ) Process image Process image RG1 RG2 ….. The data transmission between BSE and PRE takes place via a „virtual connection“ per redundancy group ….. Data in receive direction are transmitted with the „virtual connection“ [BSE] „logical connections“ towards the remote station (s) started „logical connections“ towards the remote station (s) stopped Functioning method of the 104-Redundancy in the Controlled Station: • Several redundancy groups can be defined for each LAN/WAN protocol element • Every redundancy group consists of one or more "real" connections and only 1 "virtual connection" for the communication to the basic system element. The connections of a redundancy group in transmit direction are handled as one connection (=virtual connection) from the perspective of the communications function on the basic system element. • The data are transmitted from the basic system element to the LAN/WAN protocol element over the "virtual connection" assigned to the redundancy group. As a result, the connections of a 104-redundancy group are supplied from only one process image. • The data are only transmitted to the remote station over the started "real connection" of the 104-redundancy group. The data transmission is controlled by the controlling station with START/STOP Data Transfer. • Every connection (and therefore the 104-sequence numbers also) is managed independently • In receive direction, the data of a 104-redundancy group are transmitted to the basic system element with the station number assigned to the "virtual connection" On the LAN/WAN protocol element, connections for 104-redundancy and normal connections (without redundancy) can be used mixed. Special parameter settings for 104-Redundancy in the "Controlling Station" on the LAN/WAN protocol element: Functions Protocol Elements DC0-023-2.01 8-29 LAN-Communikation (104) • Redundancy Mode The parameter Redundancy | Redundancy mode must be set to "104-Redundancy". • Redundancy For all connections with controlling functionality according to 104-redundancy, the parameter Connection definition | Redundancy is to be set to "104-Contr-Red". For the connections, in addition all necessary parameters of the Connection definition (such as IP address of the remote station,…) must be parameterized. • IEC 60870-5-104 data flow control of the own station (Controlling/Controlled) For all connections with controlling functionality according to 104-redundancy, the parameter Connection definition | data flow control is to be set to "controlling". • Stop Behavior For all connections with controlling functionality according to 104-redundancy, the parameter Connection definition | stop behaviour is to be set to "save". Parameter settings for 104-Redundancy in the "Controlled Station" on the LAN/WAN protocol element: 8-30 • Redundancy Mode The parameter Redundancy | Redundancy mode must be set to "104-Redundancy". • Virtual Connection For each 104-redundancy group, one connection is to be defined as "virtual connection" in the parameters Connection definition | Redundancy. The virtual connection is only used for the internal communication with the basic system element. This connection does not exist on the LAN (the IP address of the virtual connection is of no significance and is not used). Note: Virtual connections may not be parameterized in the connection definitions as "deactivated" or "without error signalization"! • Real Connections All connections of the 104-redundancy groups to the remote stations are to be defined in the parameters Connection definition | Redundancy as "real connections". For the real connections, in addition all necessary parameters of the Connection definition (such as IP address of the remote station,…) must be parameterized. Note: Real connections may not be parameterized in the parameters Connection definition | Connection as "deactivated"! • Redundancy Group With 104-redundancy a connection can be assigned to one of several redundancy groups. Each redundancy group can be controlled independently of the other 104-redundancy groups. For each 104-redundancy group, the data transmission can be activated over 1 of the assigned connections. The redundancy group is defined with the parameter Connection definition | RedGroup. • IEC 60870-5-104 data flow control of the own station (Controlling/Controlled) The data flow control is to be set to "controlled" for all connections of the IEC 60870-5-104 redundancy group with the parameter Connection definition | data flow control. DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.2.2.2. 104-Redundancy with 2 Ethernet Interfaces [only ACP 1703] The 104-redundancy with 2 ethernet interface enables the redundant interfacing of one component to remote stations with redundant ethernet interfaces over 2 ethernet networks. Example for a remote station with redundant interfaces is e.g. one system with two ethernet interfaces or two systems that are operated redundantly or a combination of both. A TCP connection exists for every redundant ethernet interface of the remote station and these redundant connections are grouped to form a redundancy group. Only one of these redundant connections may be started by the Controlling Station and data transmitted. Simplified, on the NIP the 104-redundancy group can be seen as a switch that selects to which connection the data to be sent are transferred. With 104-redundancy with two ethernet interfaces, on the BSE there is also a switch that selects to which NIP the data to be sent are transferred and consequently the redundancy group extends over both NIPs and the BSE. For details about Start/Stop refer to chapter "Control of the Data Transmission with Start/Stop". The controlling station switches between the redundant connections. There are two types of redundancy switchover, the "soft switchover" and the "hard switchover". The soft switchover takes place applicational, e.g. during tests or if a part of the controlling station is to be taken out of operation. First the previously started connection is stopped with a STOPDTact. Only when STOPDTcon has been received by the controlling station is a STARTDTact sent to another connection. This then becomes the new started connection. The hard switchover occurs when the controlling station detects a connection failure (e.g. through a 104-Timeout). A STARTDTact is then sent immediately over another connection. This then becomes the new started connection. If at this moment in the controlled station the previously started connection is still established (because the controlled station has not detected any connection failure), it is closed immediately. Functions Protocol Elements DC0-023-2.01 8-31 LAN-Communikation (104) Several redundancy groups independent of each other are possible. Precisely one redundancy group can be assigned to each connection. The SICAM 1703 internal redundancy control messages are not used in the controlled station. In the SICAM 1703 controlling station the entire LAN/WAN protocol element is switched to "ACTIVE/PASSIVE" by the SICAM 1703 internal redundancy control messages. Controlling Station (Redundant) Controlling Station Interface 2 Interface 1 Interface 3 Network Interface 4 Network Controlled Station [PRE] VC VC [PRE] Legend: ….. Data in transmit direction are stored in a central process image for each redundancy group for the virtual connections . ….. The data transmission takes only place to those LAN /WAN-PRE on which the IEC60870-5-104 data transfer was started with STARTDTact. ( Data transmission may only be activated on 1 connection ) Process image ….. The data transmission between BSE and PRE takes place via a „virtual connection“ ( the virtual connection numbers must be set equal on both PRE’s ). ….. Data in receive direction are transmitted with the „virtual connection“ „logical connections“ towards the remote station (s) started [BSE] „logical connections“ towards the remote station (s) stopped 8-32 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) Functioning method of the 104-Redundancy in the Controlled Station: • Several redundancy groups can be defined for each LAN/WAN protocol element • Every redundancy group consists of one or more "real" connections and only 1 "virtual connection" for the system-internal communication. The connections of a redundancy group in transmit direction are handled as one connection (=virtual connection) from the perspective of the communications function on the basic system element. • The data transmission is started by the controlling station with the messages STARTDTact and only 1 connection may be activated per redundancy group. i.e. for each redundancy group a connection is activated either on interface 1 or on interface 2. The data transmission from the basic system element to the LAN/WAN protocol element is also only activated for the "virtual connection" of the corresponding interface assigned to the redundancy group. • The data are transmitted from the basic system element to the LAN/WAN protocol element over the "virtual connection" assigned to the redundancy group. As a result, the connections of a redundancy group for 2 ethernet interfaces are supplied from only one process image. • The data are only transmitted to the remote station over the activated "real connection" of the redundancy group on one ethernet interface. • For all non-activated connections the connection is established at TCP level – every connection is monitored with test frames • Every connection (and therefore the sequence numbers also) is managed independently • In receive direction, the data of a 104-redundancy group are transmitted to the basic system element with the assigned "virtual connection" On the LAN/WAN protocol element, connections for 104-redundancy and normal connections (without redundancy) can only be used mixed on the less significant protocol element (SSE = 128 or 129). Parameter settings for 104-Redundancy in the "Controlled Station" on the LAN/WAN-PRE: • For 104-redundancy with 2 ethernet interfaces, the same rules are applicable for parameter settings as for 104redundancy with 1 ethernet interface • In addition, the virtual connections must be parameterized the same on both LAN/WAN-PRE's (same number of virtual connections, same assignment to station numbers, same redundancy groups) Functions Protocol Elements DC0-023-2.01 8-33 LAN-Communikation (104) 8.2.3. Redundancy Mode "1703-Redundancy" With the redundancy mode “1703-redundancy”, one remote terminal unit (Controlled Station) is connected with one or several master stations (Controlling Stations) over several logical connections. The data transmission takes place over all connections. The redundancy mode "1703-Redundancy" is selected by setting the parameter Connection definition | Redundancy to "none". The switchover of the redundancy state ("ACTIVE" "PASSIVE") takes place system-internal through redundancy control messages. Redundancy function of the standard redundancy mode: • The data transmission is started by the controlling station for every connection with STARTDTact but not stopped with redundancy state "PASSIVE". • The data transmission is carried out on all connections independent of the other connections • All data transferred from the basic system element to the LAN/WAN protocol element for transmission are transmitted to the remote station even with the redundancy state "PASSIVE". • The data transmission is controlled from one specific process image for each connection • The switchover to "PASSIVE" takes place globally per LAN/WAN protocol element and not selectively per connection In the redundancy state "PASSIVE", the message <TI:=107> check command with time stamp CP56Time2a can be disabled for transmission by the LAN/WAN protocol element with the parameter Redundancy | send test command (TI107) if passive and the message <TI:=103> clock synchronization command with the parameter Redundancy | send time setting (TI103) if passive. 8-34 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.3. Message Conversion Data in transmit direction are transferred from the basic system element to the protocol element in the SICAM 1703 internal format. These are converted by the protocol element to the IEC 60870-5-104 message format on the line and transmitted according to the transmission procedure of the IEC 60870-5-104 protocol. Data in receive direction are converted on the transmission line by the protocol element from IEC 60870-5-104 format to a SICAM 1703 internal format and transferred to the basic system element. Object Numbering All IEC 60870-5-104 message objects are transmitted with an unambiguous IEC 60870-5-104 sequence number. In one TCP-packet several IEC 60870-5-104 message objects can be transmitted. A blocked IEC 60870-5-104 message (with several individual messages) is handled as one message object. The sequence number is managed for each connection and is an ascending number in the range 0-32767 (modulus 32768). The sequence number is used for the acknowledgement procedure defined for IEC 60870-5-104. 8.3.1. Blocking For the optimum utilization of the transmission paths, for the data transmission with IEC 60870-5-104 protocols the "Blocking" according to IEC 60870-5-101/104 is implemented. This function is performed on the basic system element (BSE) according to the rules applicable for this. Data to be transmitted are thereby already blocked on the basic system element and passed on to the protocol element for transmission. With LAN-communication, several messages blocked according to IEC 60870-5-104 can be entered in one TCPpacket before this is transmitted. Received data in blocked format according to IEC 60870-5-104 are passed on from the protocol element to the basic system element in blocked format. On the basic system element the blocked data are split up again into individual information objects by the detailed routing function and passed on as such to the further processing. Received messages with maximum length are transmitted SICAM 1703 internal in several blocks to the basic system element (BSE) because of the additionally required transport information. The parameters necessary for the blocking are to be set on the basic system element (BSE) in the IEC 60870-5-101/104 parameter block. Functions Protocol Elements DC0-023-2.01 8-35 LAN-Communikation (104) 8.3.2. Special Functions For the coupling to external systems, if necessary the following special functions can be activated for the adaptation of the message conversion: • • • • daylight-saving time bit (SU)=0 for all messages in transmit direction (daylight-saving time bit in the time stamp) Weekday (DOW)=0 for all messages in transmit direction (weekday in the time stamp) Originator address=0 for all messages in transmit direction Settings for Project DBAG / PSI 8.3.2.1. Daylight-Saving Time Bit = 0 for all Messages in Transmit Direction With the setting of the parameter Connection definition | summertime to “suppress”, for all messages with time stamp in transmit direction the daylight-saving time bit (SU) is always set to “0” by the protocol element. 8.3.2.2. Weekday = 0 for all Messages in Transmit Direction With the setting of the parameter Connection definition | day of week to “suppress”, for all messages with time stamp in transmit direction the weekday (DOW) is always set to “0” by the protocol element. 8.3.2.3. Originator Address = 0 for all Messages in Transmit Direction With the setting of the parameter Connection definition | originator address to “suppress”, for all messages in transmit direction the originator address is always set to “0” by the protocol element. 8-36 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.3.2.4. Settings for Project DBAG / PSI For the implementation of the protocol firmware in DBAG / PSI projects the following special functions can be activated: • • Breaker delay in transmit direction (DBAG-specific special message format <TI=150>) Send originator address with settable value These special functions can be activated with the parameter advanced parameters | application settings | parameter settings for project DBAG/PSI. With function activated, messages in the format <TI=33> "32 Bit bit pattern" in the direction basic system element protocol element are converted by the protocol element to the DBAG-specific message format <TI=150> and transmitted. Messages received in the format <TI=150> are converted by the protocol element to the format <TI=33> "32 Bit bit pattern" and passed on to the basic system element. In transmit direction <TI=33> "32 Bit bit pattern" is converted as follows: Cause of Transmission IEC-Parameter Type Identification for Transmission to the Remote Station spontaneous - <TI=150> DBAG-specific format GI with time (3 octets) <TI=4> GI with time (7 octets) <TI=31> double-point information with time stamp CP56Time2a GI without time <TI=3> double-point information with time stamp double-point information In receive direction <TI=150> is converted as follows: Cause of Transmission spontaneous, GI Note: Functions Protocol Elements Time Format with time (7 octets) Type Identification for Transmission to Basic System Element <TI=33> Bit pattern of 32 Bit with time stamp CP56Time2a The format <TI=150> is only defined with 7 bytes time, 3 bytes IOA, 2 bytes CASDU and 2 bytes URS! For the format <TI=150> in addition no double transmission is defined as format without time stamp! DC0-023-2.01 8-37 LAN-Communikation (104) Breaker delay in transmit direction If the delay of the circuit breaker or the time of the fault current is not available, this time can be added by the protocol element in messages in transmit direction with the parameter advanced parameters | application settings | train-specific parameter settings | switch transfer time in transmit direction. Message structure <TI=150> "Railway-specific Format" (in the private range) 27 26 25 24 23 22 21 20 150 SQ T Type identification Number of information objects P/N variable structure qualifier cause of transmission Cause of transmission Originator address Station address CASDU1 N CASDU2 Technological Code (TC) IOA1 1 IOA2 0 SK8 Field address SK7 SK6 SK5 SK4 SK3 IOA3 SK2 SK1 Protection criteria (BDK) Protection criteria reserve 0 - 255 Fault code (AK of SLT) 2ms – Code (0-255) IV NT SB BL Breaker delay DPI DIQ of DOM Originator time in format CP56Time2a (corresponds to TL SCHINA, DB_Network) Dual time (7 octets) Send originator address with settable value In DBAG / PSI projects the originator address in transmit direction is always transferred with a fixed parameterized value. The originator address is to be set with the parameter advanced parameters | application settings | train-specific parameter settings | originator address in transmit direction. For this function the setting of the number of octets for cause of transmission to "2 octets" is necessary (see IEC 60870-5-101/104 Parameters on the Basic System Element). 8-38 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.3.2.5. Settings for Project RWE For the implementation of the protocol firmware in RWE projects the following special functions can be activated: • • • • Bit by bit marking of the field Cyclic measured values Address of the return information for selection command 2 NT-Bit, IV-Bit according to RWE requirements These special functions can be activated with the parameter advanced parameters | application settings | RWE-functions and are effective for all connections of the LAN/WAN protocol element. Functions Protocol Elements DC0-023-2.01 8-39 LAN-Communikation (104) 8.3.2.5.1. Bit by Bit Marking of the Field For RWE switchgear projects, the configuration of the plants is divided into "voltage level", "station number" and "field". This structuring is represented on the 5-stage IEC 60870-5-101/104 address of the data. The definition of which part of the address (CASDU, IOA) the field addresses is carried out in the parameters advanced parameters | application settings | RWE-functions | bit-level flag of bay for CASDU1, CASDU2, IOA1, IOA2, and IOA3. All set bits in the "Bit by bit marking of the field" define the range of the address of the field. All reset bits in the mask define the range of the addresses for data points within the fields. The assignment of the measured values to the fields is determined by the structuring of the address. For cyclic group 0 measured values, no field-specific functions are implemented on the LAN/WAN protocol element. The transmission of cyclic group 2 measured values is activated by field-specific selection commands. On the LAN/WAN protocol element the cyclic measured values are not activated/deactivated by the selection command itself, rather indirectly by the return information for the selection command. With the return information for selection command 2, those cyclic group 2 measured values whose address for the field after masking matches the mask for "Bit by bit marking of the field“ are activated/deactivated for transmission. Bit by Bit marking of the Field "Mask" Address Range for Fields [HEX] BIN Dec, [HEX] CASDU1 FF 11111111 0-255 [00-FF] CASDU2 FF 11111111 0-255 [00-FF] IOA1 00 00000000 -- IOA2 00 00000000 -- IOA3 FC 11111100 252-255 [FC-FF] Hints: - all bits with "1" in the mask declare the address range of the field - all bits with "0" in the mask declare the address range of the data points within the field - The bit by bit marking of the field is always the same for RWE projects! Example: Parameterized Return Information Address 8-40 Bit by Bit marking of the Field "Mask" Addresses of the Return Information determined by this [HEX] [BIN] [HEX] BIN Dec, [HEX] CASDU1 00 00000000 FF 11111111 0-255 [00-FF] CASDU2 00 00000000 FF 11111111 0-255 [00-FF] IOA1 21 00100001 00 00000000 21 IOA2 56 01010110 00 00000000 56 IOA3 03 00000011 FC 11111100 3,7,11,15,19,…,255 [03,07,0F,13,…,FF] DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.3.2.5.2. Cyclic Measured Values Measured values can be transmitted cyclic to the remote station from the internal process image by the protocol element itself. For this special function, the activation of the "RWE-specific functions" and the use of the selective data flow in ACP-1703 is required. For cyclic measured values the following groups are supported: • • Group 0: cyclic measured values with a parameter-settable cycle time (default cycle time) Group 2: cyclic measured values – are only transmitted for selection 2 (high priority cycle time) Group 2 measured values (PSG measured values) are first transmitted cyclic after activation with the selection command 2. The selection of the measured values for the cyclic transmission and the assignment of the measured values to the group is carried out in the process-technical parameter setting for the selective data flow in ACP 1703 in the field "Function group". Function Group Group Note 0-249 --- No cyclic measured value! (measured value is transmitted spontaneous) 250 0 Cyclic measured value with a parameter-settable cycle time (default cycle time; typically 3 sec) 251 1 Cyclic measured value – is only transmitted for activation with selection command 1; not used with LAN/WAN protocol element! 252 2 Cyclic measured value – is only transmitted for activation with selection command 2 (high priority cycle time; typically 0.5 sec) Note: The functional groups required for cyclic measured values must not be used for other functions! The updating of the process image for cyclic measured values takes place during the transmission of spontaneous measured values or during general interrogation to the LAN/WAN protocol element – from now on these measured values are transmitted cyclic (not spontaneous and not with GI) to the remote station. For the transmission of the cyclic measured values, SICAM 1703 internal (between basic system element and LAN/WAN protocol element) the message format "<TI:=35> measured value, scaled value with time stamp CP56Time2a" is used. Cyclic measured values are always transmitted from the LAN/WAN protocol element to the remote station without time stamp with the message format "<TI:=11> measured value, scaled value" and with the cause of transmission "cyclic". The cycle time for the transmission of cyclic measured values can be set with the parameter advanced parameters | application settings | RWE-functions | cyclic measured value | base cycle time and the parameter advanced parameters | application settings | RWE-functions | cyclic measured value | high priority cycle time. The transmission of the cyclic measured values to the remote station takes place with maximum possible blocking according to IEC 60870-5-104. The blocking for cyclic measured values is performed by the LAN/WAN communications element itself. The parameters provided for the blocking on the basic system element (BSE) in the IEC 60870-5-101/104 parameter block are not evaluated. Functions Protocol Elements DC0-023-2.01 8-41 LAN-Communikation (104) During the transmission of the cyclic measured values, the transmission of spontaneous data is disabled. All cyclic measured values are prepared for transmission in one operation at the respective cycle moment. Limitations: • • • • • max. 2000 cyclic measured values Cyclic measured values are only supported in ACP 1703 with selective data flow An address conversion for cyclic measured values is not supported Cyclic measured values are only supported for 1 connection (only to the 1st connection in the detailed routing) Cyclic measured values must not be routed to a redundant connection Note: So that the process data are transmitted with the latest values as fast as possible after a going interface fault, the function "delete ring with communication failure" is to be deactivated in the communications function on the basic system element. This setting is therefore necessary, because the general interrogation in the system is only triggered later and consequently, until the updating of the cyclic measured values, due to the general interrogation, old values are transmitted to the remote station. Group 0 measured values With function enabled, group 0 measured values are always transmitted cyclic. The cycle time can be set with the parameter advanced parameters | application settings | RWEfunctions | cyclic measured value | base cycle time. Group 1 measured values (selection command 1) Group 1 measured values are not supported! Group 2 measured values (selection command 2) Group 2 measured values (PSG measured values) are first transmitted cyclic after activation with the selection command 2. If the transmission of the measured values is not activated with the selection command 2, these measured values are not transmitted. After startup, by default these measured values are not transmitted. The activation of the group 2 measured values takes place on the LAN/WAN protocol element not directly with the selection command 2, rather with the return information for the selection command 2. The cycle time can be set with the parameter advanced parameters | application settings | RWEfunctions | cyclic measured value | high priority cycle time. 8-42 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.3.2.5.3. Address of the Return Information for Selection Command The activation of the group 2 measured values does not take place on the LAN/WAN protocol element with the selection command 2 itself, rather with the return information for the selection command 2. The selection command is processed in the function diagram of the component according to the RWE requirements and with successful selection the return information is generated for the selection command 2. The selection of the group 2 measured values is supported for all fields, whose address range has been determined by the "Bit by bit marking of the field". The address of the return information for the selection command 2 is to be parameterized with the parameters advanced parameters | application settings | RWE-functions | Cyclic measured value | address of the return information of select command 2 | CASDU1, CASDU2, IOA1, IOA2 and IOA3. As return information address, only those sections of the address are to be parameterized that are not part of the address range for the field. Consequently, as return information address only the field-internal address is to be parameterized. The bits of the address which identify the field in the return information address for selection command 2 are not evaluated by the LAN/WAN protocol element. For the return information of the selection command 2, SICAM 1703 internal only the message format "<TI:=30> single-point information with time stamp CP56Time2a" is used. The cyclic transmission of the group 2 measured values is activated with the single-point information state "ON" and deactivated with the state "OFF". The selection of the group 2 measured values can be carried out either "Locally" or "Remotely". The return information for the selection command 2 is only transmitted spontaneously to the remote station with the cause of transmission "Return information, caused by a remote command" or "Return information, caused by a local command". With general interrogation, the return information for the selection command is not transmitted to the remote station! The assignment of the measured values to the fields is determined by the structuring of the address for RWE. With the return information for selection command 2, those cyclic group 2 measured values whose address for the field after masking matches the mask for "Bit by bit marking of the field“ are activated/deactivated for transmission. Functions Protocol Elements DC0-023-2.01 8-43 LAN-Communikation (104) 8.3.2.5.4. NT-Bit, IV-Bit according to RWE Requirements For projects for the customer RWE, a special handling can be activated for the NT-bit and the IV-bit of the quality descriptor of the messages in transmit direction. If the RWE-specific functions are not activated, the NT-bit and the IV-bit in the messages are transferred to the remote station unchanged. If the RWE-specific functions are activated, the special handling for the NT-bit and the IV-bit can be selected with the parameter advanced parameters | application settings | RWE-functions | convert of the NT bits to the IV bit in transmit direction from the following options: • • Variant a: NT-bit is set to "0", IV-bit is not changed Variant b: NT-bit is set to "0", IV-bit is set if NT-bit (internal) or IV-bit (internal) is set. SICAM 1703 internal NT-Bit IV-Bit To Remote Station (Variant a) NT-Bit IV-Bit To Remote Station (Variant b) NT-Bit 0 x 0 x 0 x 1 x 0 x 0 1 0 0 0 0 0 0 0 1 0 1 0 1 1 0 0 0 0 1 1 1 0 1 0 1 Legend: x = optional state, or state is not changed! 8-44 IV-Bit DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.4. Protocol Element Control and Return Information This function is used for the user-specific influencing of the functions of the protocol elements. This function contains two separate independent parts: • Protocol element control • Protocol element return information The Protocol Element Control enables: • Applicational control of the station interrogation • Setting control location • Testing the reachability of stations • the suppression of errors with intentionally switched-off stations (Station Service) The Protocol Element Return Information enables: • States of certain state lines to be used as process information • the obtaining of station interrogation information • the obtaining of information about the route state/failure of main/standby transmission line • Information about the station status/failure to be obtained Internal distribution for messages with process information Block Diagram Protocol element control Internal function Transmission route Protocol element return information Protocol element Messages with process information Messages with system information Functions Protocol Elements DC0-023-2.01 8-45 LAN-Communikation (104) 8.4.1. Protocol Element Control Presently no messages for protocol element control are supported by the LAN/WAN protocol element! 8.4.2. Protocol Element Return Information The protocol element return information on the basic system element generates messages with process information in monitor direction and thereby enables states of the protocol elements to be displayed or processed. There are three different categories of return information: • • • Status of the state lines Status of the stations Protocol-specific return information (dependent on the protocol element used) The assignment of the messages with process information to the return information is carried out on the basic system element with the help of process-technical parameters of the ACP 1703 system data protocol element return information. From which source the parameterized return information are to be generated, is set with the parameters "Supplementary system element" and "Station number". Messages for protocol element return information are transmitted spontaneously from the protocol element to the basic system element with change or as reply to a general interrogation command. Possible LAN return information: Parameter Return information function_(PRE) 8-46 Station Note Station failure 0 – 99 1 = Station failed Status DATA TRANSFER 0 – 99 0 = IEC 60870-5-104 Data Transfer is stopped (STOPDTact) 1 = IEC 60870-5-104 Data Transfer is started (STARTDTact) DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.5. WEB Server A WEB server is integrated into the protocol firmware for internal diagnostic information. This information can be read out comfortably with a common WEB Browser (e.g. Microsoft Internet Explorer). For the access to the WEB server the communications protocol "HTTP (Hyper Text Transfer Protocol)" is used with the port number 80. The integrated WEB server is addressed by means of direct specification of the IP address of the ethernet interface of the automation unit. By default the WEB server is deactivated for security reasons. Also for security reasons, an authentication can be configured for the access to the WEB server (specification of a password). Via the integrated WEB server the following information can be read out: • • • • • Display of the network information (IP address, default gateway, subnet mask) Read memory (e.g.: RAM, Task-Stack, EEPROM) Statistical information (Ethernet) Display of the software revisions (operating system, TCP/IP-Stack,…) Triggering of a ping command Parameters for the WEB server: • HTTP-Webserver The integrated WEB server can if necessary be enabled for access by the user with the parameter HTTPWebserver | HTTP-Webserver. • Authentication For security reasons, for the access to the integrated WEB server a compulsory authentication can be requested. The authentication is activated with the parameter HTTP-Webserver | autentification. With function enabled, access is only possible with entry of the established password. • Password for Authentication With authentication enabled a password can be established with the parameter HTTP-Webserver | password for autentification. The access to the integrated WEB server is only possible after successful authentication. • Username for Authentication The Username for the authentication can be defined with the parameter HTTP-Webserver | username for autentification. Note: In the current protocol firmware the username is longer used for the authentication! • Warning Web browser logged on For logging in the system a warning can be generated with logged on user. The generation of this warning can be activated with the parameter HTTP-Webserver | warning webbrowser logged on. Functions Protocol Elements DC0-023-2.01 8-47 LAN-Communikation (104) HyperText Transfer Protocol - HTTP The HyperText Transfer Protocol (HTTP) is a protocol for the transmission of data over a network. It is used mainly to load web pages and other data from the World Wide Web (WWW) or from a Web Browser integrated in a system. In the automation technique, parameter settings or diagnostic information of systems are realized more and more frequently with WEB technology. With this technique a WEB server is implemented in the device – the data are displayed on WEB pages. The HTTP forms the so-called application layer, over which the models provide no other layers. The application layer is addressed by the user programs, in the case of HTTP, in most cases this is the Web Browser, the normal user is therefore presented with this layer when he enters a web address. In the ISO/OSI layer model, the application layer corresponds with layer 7. The TCP/IP reference models implemented in the Internet sees the application layer in layer 4. In the core, HTTP is a stateless protocol. That also means, that after successful data transmission, the connection between the two communication partners does not need to be maintained. If then further data are to be transmitted, firstly another connection must be established. However through expansion of its interrogation methods, header information and status codes, the HTTP is not restricted to HyperText, rather is used increasingly for the exchange of any arbitrary data. For the communication, HTTP is dependent on a reliable transport protocol. In all practical cases, TCP is used for this. 8-48 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (104) 8.6. Coupling of the SICAM TOOLBOX II over LAN/WAN (remote connection) The remote maintenance of Ax 1703 components can be performed using a "remote connection" over LAN/WAN. The remote connection can be carried out with the following methods: • • 8.6.1. Remote connection over external Terminal Server (connection to M-CPU with TIAX00) Remote connection over integrated Terminal Server (Telnet) Remote Connection over external Terminal Server (connection to M-CPU with TIAX00) For the remote maintenance of Ax 1703 components using remote connection over external terminal server, the serial interface of the SICAM TOOLBOX II is connected with a selected SICAM 1703 component over ethernet. An external terminal server (=serial to ethernet converter) is thereby implemented at the SICAM TOOLBOX II side and at the SICAM 1703 component side. The IP address of the selected SICAM 1703 component and the SICAM TOOLBOX II are to be parameterized in the external terminal servers. All components that can be reached via the selected SICAM 1703 component can thus be reached for the remote maintenance. In the SICAM 1703 component and in the SICAM TOOLBOX II, no special parameter settings are required. If SICAM 1703 components are used in different LAN/WAN networks, a specific external terminal server must be used at the SICAM TOOLBOX II side for each LAN/WAN network or the external terminal server must be reparameterized accordingly with the programs provided for this purpose. A communications protocol firmware based on IEC 60870-5-1 and IEC 60870-5-2 "Balanced" is used between the SICAM TOOLBOX II and the LAN/WAN communications protocol firmware. Here, the remote connection over external terminal server is only mentioned for the sake of completeness, it is not however any special functionality of the LAN/WAN communications protocol firmware. In addition, this solution is now rarely implemented (or is only in use on older plants). In new plants, now in most cases the remote connection is carried out over Telnet with the integrated terminal server of the SICAM TOOLBOX II and the LAN/WAN communications protocol firmware. Functions Protocol Elements DC0-023-2.01 8-49 LAN-Communikation (104) 8.6.2. Remote Connection over integrated Terminal Server (Telnet) For the remote maintenance of SICAM 1703 components using remote connection with Telnet, a transparent connection is established over ethernet between the SICAM TOOLBOX II and the integrated terminal server of the LAN/WAN communications firmware. The Telnet protocol is based on TCP/IP and is a Client-Server protocol. The SICAM TOOLBOX II thereby always takes over the client function, the SICAM 1703 component always the server function. The remote connection using Telnet is always established by the SICAM TOOLBOX II. For Telnet a TCP/IP connection must be set up. With the Toolbox interfacing, the Toolbox is Connector and the NIP is Listener. The Listener-Port number to be used is 2001. If several Toolboxes attempt to setup a connection at the same time, the first Toolbox wins, the rest are rejected. If an error is detected during the remote maintenance of SICAM 1703 components using remote connection, then the TCP/IP connection is terminated. For the remote connection, a connection is to be set up on the Toolbox for every remote station with the following parameters: • • • • Transmission medium = terminal server, TCP/IP (TELNET) IP address of the remote station (IP address or Host ID of the terminal server of the remote station) Port number = 2001 Delay time For security reasons the remote connection can be deactivated with the parameter advanced parameters | remote operation . With remote connection deactivated, the Telnet protocol over Port 2001 is no longer handled. With connection established for the remote maintenance, a warning is generated in the SICAM 1703 component. If necessary, this warning can be deactivated with the parameter advanced parameters | warning remote operation. Functionally, the remote connection over Telnet thereby corresponds with the interfacing with external terminal server (and TIAX00), only with this solution the functionality of the terminal server is integrated in the SICAM TOOLBOX II and in the LAN/WAN communications protocol firmware. So that a secure point-to-point connection over Telnet is ensured, a communications protocol based on IEC 608705-1 and IEC 60870-5-2 "Balanced" is implemented between the SICAM TOOLBOX II and the LAN/WAN communications protocol firmware on the application layer. Telnet is thereby used as transport protocol. The service message formats between SICAM TOOLBOX II and the SICAM 1703 component are prepared accordingly on the LAN/WAN communications protocol firmware (conversion from SICAM 1703 internal format and format for SICAM TOOLBOX II) and transferred to the master service function of the SICAM 1703 component for further processing. Telnet - Protocol Telnet (Telecommunication Network Protocol) is the name of a network protocol widespread in the Internet. Telnet is a Client-Server protocol, it uses TCP and the clients mostly connect with the destination computer over Port 23, however, as with most internet protocols, this port can also be changed. The Telnet protocol specifies the interfacing of terminals over TCP/IP. 8-50 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9. LAN Communication (61850) IEC 61850 is a general, network-based transmission protocol for the protection and control in electrical switchgear of the medium and high-voltage technique (station automation). The standard series mainly defines: • • • • • General definitions for switchgear The most important information for functions and devices, The exchange of information for protection, monitoring, control and measurement A digital interface for primary data A configuration language The protocol uses TCP/IP as basic transmission protocol and the MMS protocol (Manufacturing Messaging Specification) as classic Client-Server communication (defined in the standard part IEC 61850-8-1). In addition, two so-called Peer-to-Peer services are described for the realtime-capable communication, which sit directly on the ethernet protocol: • Transmission of fast scanned values according to standard part IEC 61850-9-1 (is presently not supported by the protocol element Server + Client!) • Transmission of GOOSE messages according to standard part IEC 61850-9-2 The 61850 Client actively establishes the connection and fetches data from a 61850 Server or sends data to a 61850 Server. The 61850 Server waits passively for a connection established by a 61850 Client and is data source and data recipient. In contrast to IEC 60870-5-104, which is based on a signal-orientated data model, the data model of the IEC 61850 interface is strictly object-orientated. The name of the object in plain text serves as identification. The objects are self-descriptive, i.e. the structure of the objects is transmitted with the object itself in the message. In contrast to IEC 60870-5-104, IEC 61850 is only defined for the station bus and therefore cannot be used for the process data transmission between the stations and the power system control. For the interfacing of the power network control centre, the data must be mapped to e.g. IEC 60870-5-101/104. Master station-1 Master station-2 Master station-n LAN-Interface LAN-Interface LAN-Interface Switch Switch Station bus Ethernet TCP/IP with IEC61850 Station bus Ethernet TCP/IP with IEC61850 Switch Station bus Ethernet TCP/IP with IEC61850 Switch Switch Switch LAN-Interface LAN-Interface LAN-Interface LAN-Interface LAN-Interface Remote station (IED) #1 Remote station (IED) #2 Remote station (IED) #3 Remote station (IED) #4 Remote station (IED) #n max. 100 connections per LAN-Interface Functions Protocol Elements DC0-023-2.01 9-1 LAN-Communikation (61850) One major peculiarity of the IEC 61850 protocol is the decoupling of the object-orientated technological representation of the data from the communication. The 61850 defines the appearance of the functions based on the data to outside. The functions are indeed described but not defined. For each connection, the SICAM 1703 protocol element supports either 61850-Server function or 61850-Client function. General functions IEC 61850 Client Communication of a client with one or several servers (IEC 61850) • LAN Communication over Ethernet TCP/IP according to IEC 61850 ─ Supported functionality according to − PICS (Protocol Implementation Conformance Statement) − PIXIT (Protocol Implementation Extra Information) − Supported Logical Nodes and their Attributes ─ Server Client − Acquisition of events ∗ Static data sets, dynamic data sets ∗ Unbuffered reports, buffered reports ∗ Change monitoring for measured values ∗ Monitoring of intermediate and faulty position for double-point binary informations − Transmission of files ∗ Disturbance records to SICAM DISTO − Transmission of integrated totals ─ Client Server − General interrogation − Command transmission ∗ Set control location, check control location ∗ Command interlocking ∗ Direct control with normal security, direct control with enhanced security, SBO control with enhanced security − Setting groups • Clock synchronization ─ Clock synchronization with one or more NTP servers − Server synchronized via GPS (DCF77 upon inquiry) − One NTP server can serve several automation units − NTP (network time protocol) according to RFC 1305 − Up to 4 different NTP servers can be interrogated (redundancy) − Cyclic, can be set in a seconds grid; self-adapting ─ Clock synchronization with one or more NTP servers − NTP (network time protocol) according to RFC 1305 • • Functions for supporting redundant communication routes SICAM TOOLBOX II connection over LAN/WAN ("remote connection") ─ Connection is made via TELNET (Port 2001) according to RFC 854 ─ At one time, exactly one SICAM TOOLBOX II can be served • 9-2 Diagnosis via webserver DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) General functions IEC 61850 Server Communication of a server with one client (IEC 61850) • LAN Communication via Ethernet TCP/IP according to IEC 61850 ─ Supported functionality according to: − PICS (Protocol Implementation Conformance Statement) − PIXIT (Protocol Implementation Extra Information) − MICS (Model Implementation Conformance Statement) − Supported Logical Nodes and their Attributes ─ Client Server − Acquisition of events ∗ Static Data Sets, Dynamic Data Sets ∗ Unbuffered Reports, Buffered Reports ∗ Change monitoring for measured values ∗ Monitoring of intermediate and faulty position for double-point binary informations − Transmission of files ∗ Disturbance records to SICAM DISTO − Transmission of integrated totals ─ Server Client − General Interrogation − Command Transmission ∗ Set control location, check control location ∗ Command interlocking ∗ Direct Control with normal security, direct control with enhanced security, SBO control with enhanced security − Setting groups • Clock synchronization ─ Clock synchronization with one or more NTP servers − Server synchronized via GPS (DCF77 upon inquiry) − One NTP server can serve several automation units − NTP (network time protocol) according to RFC 1305 − Up to 4 different NTP servers can be interrogated (redundancy) − Cyclic, can be set in a seconds grid; self-adapting ─ Clock synchronization with one or more NTP servers − NTP (network time protocol) according to RFC 1305 • Functions for supporting redundant communication routes • SICAM TOOLBOX II connection over LAN/WAN ("remote connection") ─ Connection is made via TELNET (Port 2001) according to RFC 854 ─ At one time, exactly one SICAM TOOLBOX II can be served • Diagnosis via webserver Functions Protocol Elements DC0-023-2.01 9-3 LAN-Communikation (61850) 9.1. LAN Communication over Ethernet TCP/IP according to IEC 61850 The 61850 standard series essentially defines: Standardized Information - for circuit breakers, measured value unit, measured values, status, control, Meta data etc. with self-description (IEC 61850-7-4) - standardized information are based on a set of about 20 general basic types "CDC = Common Data Classes" (status, measured value, count,…) (IEC 61850-7-3) - some of the standardized information are switchgear-specific, others are general - the definition of new information models by reusing the standardized information is explicitly supported • Standardized Services - for unrestricted access to values, signaling of values and archiving/interrogation of values, …, controlling devices (IEC 61850-7-2) - the standardized services can be applied both to the standardized information (EC 61850-7-4) as well as to any expanded or new information models. • Standardized Networks - for the exchange of messages in a narrower sense, suitable standards are selected. The standardized services, the standardized information and all other information are communicated over standardized communication systems (IEC 61850-8-1/ -9-1/ -9-2). • Standardized Configurations - devices and the entire switchgear are described completely formal. The IEC 61850-6 standard provides an XML-based system description language (Substation Configuration Language, SCL) with which the standardized configuration files are created. Logical node & Data objects Information models IEC61850-7-4/...7-3 „Signals“ (labeled Informations) Services „Interface“ Information exchange (IEC61850-7-2) Publish/subscribe read/write switch signal/archive Communication profiles Mapping on e.g. MMS and TCP/IP/Ethernet (IEC61850-8-1) Ethernet, TCP/IP Command values Answer Device Network 9-4 DC0-023-2.01 Functions Protocol Elements Configuration file according IEC61850-6 describes all layers • LAN-Communikation (61850) Protocols according to the IEC 61870-5 standard are based on the OSI layer model IEC 60870-5-5 Application Procedures Mapping IEC 60870-5-101 IEC 61850 7 IEC61850 ACSI-Services 6 4 3 2 1 Priority Tagging (IEEE 802.1Q + IEEE 802.1p) Layer Client Server MMS GOOSE 5 Sampled Value Exchange Peer-to-Peer Diagnostics with WEB HTTP TCP T-Profile Remote connection for TOOLBOX II Time Sync. TELNET NTP TCP UDP Legende: ARP ……...….. Address Resolution Protocol HTTP ….....….. Hyper Text Transfer Protocol ICMP …..…….. Internet Control Message Protocol IP …………….. Internet Protocol NTP ………….. Network Time Protocol TCP …….……. Transmission Control Protocol UDP ……….…. User Datagram Protocol MMS ……….… Manufacturing Message Specification GOOSE ……… Generic Object Oriented Substation Events IP ARP Ethernet …. IEC 61850 Task Functions, Characteristics, Comments 7 - Application Application • Transmit handling • Receive handling • Management of multiple connections 6 - Presentation Data format • IEC 61850 ACSI to Ax 1703 / ACP 1703 and compatible systems In the "private range" according to IEC 60870-5-104, Ax 1703 / ACP 1703-specific system messages and some user data are implemented (e.g. transmission of disturbance records to SICAM DISTO) 5 - Session Interface between data format and communication protocol • • • • • 4 - Transport 3 - Network Communication protocol • TCP/IP according to RFC 791 and RFC 793; GOOSE • ICMP according to RFC 792; GOOSE 2 - Data Link 1 - Physical LAN interface • Ethernet 10/100 Mbps according to IEEE 802.3; GOOSE • Medium and transmission rate can be selected with SICAM TOOLBOX II • Connection technique (on the master control or communication element) RJ45 for copper and MT-RJ connector for FO • ARP according to RFC 826 • IP Encapsulation according to RFC 894 Functions Protocol Elements GOOSE MMS HTTP TELNET according to RFC 854 NTP according to RFC 1305 DC0-023-2.01 9-5 LAN-Communikation (61850) Relevant Standards Standard IEC 61850-1 IEC 61850-2 Note Introduction and Overview - Introduction and overview of the standards of the IEC 61850 series Dictionary - Collection of terms IEC 61850-3 General Requirements (… especially on the network components) - Quality requirements (reliability), maintainability, system availability, portability, IT security) - Environmental conditions - Auxiliary services - Other standards and other rules of engineering IEC 61850-4 System and Project Management - Engineering service requirements (classification of parameters, technical work tools, documentation) - System utilization cycle (product versions, production setting, support after production setting) - Quality control (responsibilities, test equipment, type tests, system tests, factory acceptance tests "FAT" and location acceptance tests "SAT“) IEC 61850-5 Communication Requirements for Functions and Device Models - Principle of the logical nodes - Logical communication links - Concept of assigned information elements for the communication (PICOM) - Logical nodes and assigned PICOM - Functions - Performance requirements (response times etc.) - „Dynamic Scenarios“ (requirements on the information flow under various operating conditions) IEC 61850-6 Language for the configuration of station automation systems ("Engineering") - formal description of the single-pole scheme, of devices and system structure and their assignment to the single-pole scheme IEC 61850-7-1 Basic communication structure for station and bay-related secondary technology equipment – principles and models - Introduction in IEC 61850-7 - Communication principles and models IEC 61850-7-2 Basic communication structure for station and bay-related secondary technology equipment – Abstract Communication Services Interface (ACSI) - Description of the abstract communication service interface (ACSI) - Specification of the abstract communication services - Model of the server database IEC 61850-7-3 Basic communication structure for station and bay-related secondary technology equipment – Common Data Classes - Abstract common data classes and attribute definitions IEC 61850-7-4 Basic communication structure for station and bay-related secondary technology equipment – Compatible Logic Nodes and Data Classes - Definition of logical nodes, data objects and their logical addressing IEC 61850-8-1 Specific Communication Services Modeling (SCSM) – Modeling on MMS (acc. to ISO/IEC 9501-1 and -2) and ISO/IEC 9501-3 - Illustration for the communication within the entire station (Client-Server communication and "GOOSE" messages) Note: … The underlined standards contain essential information for the implementation of the 61850 functions in the protocol element. 9-6 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Relevant Standards (continued) Standard Note IEC 61850-9-1 Specific Communication Services Modeling (SCSM) – Scanned values over serial Simplex-MultiplePoint-to-Point connection - Model for the Point-to-Point-like, unidirectional communication of scanned values of the transformer (with and without Merging Unit) IEC 61850-9-2 Specific Communication Services Modeling (SCSM) – Scanned values over ISO/IEC 8802-3 - Model for the bus-type, flexible communication of scanned values of the transformer (with and without Merging Unit) IEC 61850-10 Conformity Check - Procedure for the conformity check IEC 60255-24 IEEE COMTRADE IEC 61850 Definition of Terms Designation Abbreviation ACSI ACSI Abstract Communication Service Interface The protocol-independent user interface 'ACSI' decouples the applications from the underlying communication protocols and bus physics. Common Data Class CDC The IEC 61850 defines different Common Data Classes. Common Data Classes are e.g. single-point information, double-point information, single command (incl. the CSI), double command (incl. the return information), setpoint value, … Data D Data Class Data Set DS GOOSE Selection from the object-orientated data model (selective data of the hierarchical attributes) Dynamic data sets are generated (created) per RUN-Time from the parameters. Different Data Sets are created for each Physical Device. Note: SICAM 1703 components presently only support "Dynamic Data Sets" ! FC Static Data Set Directory Data are e.g. commands, binary information, status, time, … Data Class is also called Common Data Class (CDC) Dynamic Data Set Functional Constraint Note All data which changes spontaneously are described with Functional Constraint e.g. status of the binary information, counts, measured value, … The Static Data Set is fixed predefined and is either (a) determined automatically by the device per Functional Constraint (fixed) in SICAM 1703 Server (b) specified with parameterization tool e.g: for ABB devices the Static Data Set is generated by a configurator and loaded in the device. DIR The Directory (=MMS-Director) contains all data that can be transmitted in transmit direction or receive direction. The Generic Object Oriented Substation Events (GOOSE) is a transmission service of IEC 61850 for generic status events, that can be sent simultaneously per Multicast to multiple devices in order to satisfy high real-time requirements. Typical cases of application are the spontaneous transmission of switching device settings in the decentral interlocking of switching commands in substations. GOOSE messages use the ether-type specification for VLAN, the prioritization and are represented directly on the ethernet layer. Functions Protocol Elements DC0-023-2.01 9-7 LAN-Communikation (61850) IEC 61850 Definition of Terms (continued) Designation Abbreviation Logical Device LD A Logical Device is one function in a device (Physical Device). A Physical Device can contain several functions (Logical Devices). Logical Devices are e.g. protection functions, control functions, disturbance recording, measured value acquisition, … The designation of the Logical Devices is not fixed and can therefore be freely defined. Note: Siemens uses e.g. the following designations for Logical Devices: CTRL … Control DR ….… Disturbance Recording EXT …… Extras MEAS … Measuring (measured value acquisition) PROT … Protection (protection function) Logical Node LN A Logical Node is a subfunction of a Logical Device. Every subfunction is represented by data objects, which essentially represent the process information. Logical Nodes are e.g. switches, protection functions (KU, DTL, distance calculation), … LOG Note Archive function – similar to the decentral archive "DEAR" …but is presently not supported! MMS MMS Manufacturing Message Specification The Manufacturing Message Specification (MMS) standardizes the exchange of messages in the production area. MMS provides functions that can be used for the observation, inspection and control of device operations and technical processes. Physical Device IED The Physical Device (also called IED; IED = Intelligent Electronical Device) is a device usually with 1 ethernet interface – but can also be equipped for redundant configurations with several ethernet interfaces. Report Spontaneous transmission from ServerClient takes place using Reports Buffered Reports: [FC = BR] - spontaneous data remain stored with interface fault Unbuffered Reports: [FC = RP] - spontaneous data are deleted with interface fault Report Control Block Every Report (in the server) has its own Report Control Block The characteristics of the respective Report are entered in the Report Control Block e.g. - Reference to the Data Set - Trigger for the transmission (spontaneous, general interrogation, …) - DataSet Name (optional) -… The Report Control Block can be read and written by the client. ICD ICD IED Configuration Description Description file of one individual device (IED). SCD-File SCD System Configuration Description Description file for the system configuration – this is normally created with a system configurator and contains the Engineering for the entire plant. SCL SCL Substation Configuration Language PICS PICS Protocol Implementation Conformance Statement PIXIT PIXIT Protocol Implementation Extra Information MICS MICS SCSM SCSM Specific Communication Service Mapping PICOM PICOM Pieces of Communication 1) … The IEC 61850 Interoperability is documented in the documents PICS and PIXIT 9-8 DC0-023-2.01 Functions Protocol Elements 1) 1) LAN-Communikation (61850) 9.1.1. Objects and Data The data models for 61850 describe the real data of a device, that can be read or written over the communication. The data models are strictly object-orientated. The objects are functions that the user of the substation requires and knows. Every object defines mandatory or optional data. Physical Device [IED] The physical device is also called IED [Intelligent Electronical Device]. The physical device is a device normally with 1 ethernet interface. For redundant configurations the physical device can also be equipped with several ethernet interfaces. The IED-Name can be parameterized with the parameter IEC61850 Server | IED Name. However, this IED-Name is not used by the protocol firmware and is only displayed on the main page of the WEB server. The IED-Name required for IEC 61850 is only taken by the protocol element from the data of the SIP message address conversion in transmit/receive direction. Logical Device [LD] A logical device is one function in a physical device. A physical device can contain several functions (logical devices). Logical devices are e.g. protection functions, control functions, disturbance recording, measured value acquisition. The designation of the logical devices is not fixed and can thus be freely defined. Note: Siemens uses e.g. the following designations for logical devices: CTRL … Control DR ….… Disturbance Recording EXT …… Extras MEAS … Measurement PROT … Protection Functions Protocol Elements DC0-023-2.01 9-9 LAN-Communikation (61850) Logical Nodes [LN] A logical node is a subfunction of a logical device. Every subfunction is represented by data objects, which essentially represent the process information. IEC 61850-7-4 presently defines 92 logical nodes – these largely cover all areas of a modern substation. Designation (first letter) Logical Node Categories Number of defined Logical Nodes A Automatic Control 4 C Supervisory Control 5 G Generic References 3 I Interfacing and Archiving 4 L System Logical Node 3 M Meetering and Measurement 8 P Protection Functions 28 R Protection Related Functions 10 S Sensors and Monitoring 4 T Instrument Transformer 2 X Switchgear 2 Y Power Transformers 4 Z Further Power System Equipment 15 The IEC 61850 standard series also contains clear rules for the expansion of the information models. Included among these are supplements to the logical nodes, new logical nodes, expanded and new data and new data attributes. 9-10 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) The following logical nodes are supported by SICAM 1703 Client/Server: Logical Nodes A ANCR ARCO ATCC AVCO C CALH CCGR CILO CPOW CSWI G GAPC GGIO GSAL I IARC IHMI ITCI ITMI L LLN0 LPHD M MDIF MHAI MHAN MMTR MMXN MMXU MSQI MSTA P PDIF PDIR PDIS PDOP PDUP PFRC PHAR PHIZ PIOC PMRI PMSS POPF PPAM PSCH PSDE PTEF Functions Protocol Elements Description S C - - Automatic Control Neutral Current Regulator Relative Power Control Automatic Tap Changer Controller Voltage Control Supervisory Control Alarm Handling Cooling Group Control Interlocking Point-On-Wave Switching Switch Controller Generic References Generic Automatic Process Control Generic Process I/O Generic Security Application - - - - - - Generic References Archiving Human Machine Interface Telecontrol Interface Telemonitoring Interface System Logical Node Logical Node Zero Physical Device Information Meetering and Measurement Differential Measurements Harmonics Or Interharmonics Non Phase Related Harmonics Or Interharmonics Metering Non Phase Related Measurement Measurement Sequence & Imbalance Metering Statistics Protection Functions Differential Direction Comparsion Distance Directional Overpower Directional Underpower Rate Of Change Of Frequency Harmonic Restraint Ground Detector Instantaneous Overcurrent Motor Restart Inhibition Motor Starting Time Supervision Over Power Factor Phase Angle Measuring Protection Scheme Sensitive Directional Earthfault Transient Eart Fault DC0-023-2.01 9-11 LAN-Communikation (61850) The following logical nodes are supported by SICAM 1703 Client/Server: (continued) Logical Nodes P PTOC PTOF PTOV PTRC PTTR PTUC PTUF PTUV PUPF PVOC PVPH PZSU R RADR RBDR RBRF RDIR RDRE RDRS RFLO RPSB RREC RSYN S SARC SIMG SIML SPDC T TCTR TVTR X XCBR XSWI Y YEFN YLTC YPSH YPTR 9-12 Description S C - - - - Protection Functions continued Time Overcurrent Over Frequency Overvoltage Protection Trip Conditioning Thermal Overload Undercurrent Under Frequency Undervoltage Under Power Factor Voltage Controlled Time Overcurrent Volts per Hz Zero Speed Or Underspeed Protection Related Functions Disturbance Recorder Channel Analogue Disturbance Recorder Channel Binary Breaker Failure Directional Element Disturbance Recorder Function Disturbance Record handling Fault Locator Power Swing Detection / Blocking Autoreclosing Synchronism-Check or Synchronising Sensors and Monitoring Monitoring And Diagnostic For Arcs Insulation Medium Supervision (Gas) Insulation Medium Supervision (Liquid) Monitoring And Diagnostics For Partial Discharges Instrument Transformer Current Transformer Voltage Transformer Switchgear Circuit Breaker Circuit Switch Power Transformers Earth Fault Neutralizer (Petersen Oil) Tap Changer Power Shunt Power Transformer DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) The following logical nodes are supported by SICAM 1703 Client/Server: (continued) Logical Nodes Z ZAXN ZBAT ZBSH ZCAB ZCAP ZCON ZGEN ZGIL ZLIN ZMOT ZREA ZRRC ZSAR ZTCF ZTCR Description S C - - Further Power System Equipment Auxiliary Network Battery Bushing Power Cable Capacitor Bank Converter Generator Gas Insulated Line Power Overhead Line Motor Reactor Rotating Reactive Component Surge Arrestor Thyristor Controlled Frequency Converter Thyristor Controlled Reactive Component The logical nodes "LLN0" and "LPHD0" must always be present in every logical device. The logical nodes "LLN0" and "LPHD1" are created automatically by the protocol element for every logical device, insofar as these have not already been defined through the parameterization (SIP message address conversion). The logical node "LLN0" contains data which apply for all logical nodes of the logical device (e.g. revision status of the parameters). The logical node LPHD1 contains data of the IED's [IED = Intelligent Electronical Device = Physical Device] – these are applicable for all logical nodes of the physical device (e.g. rating plate,…). Functions Protocol Elements DC0-023-2.01 9-13 LAN-Communikation (61850) Basic data types [CDC = Common Data Class] All standardized information according to IEC 61850-7-4 (e.g.: circuit breaker, measured value unit, measured values, status, control, Meta data,… ) are based on a set of about 30 general basic data types (status, measured value, count,…). The basic data types are known as Common Data Classes [CDC] and are defined in the IEC 61850-7-3 standard. CDC Ss (1) Se Common Data Class Specification for Ss Se GO GO Cs Ce (2) (2) [abbreviation ] Status Information SPS DPS INS ACT ACD SEC BCR Single Point Status Double Point Status Integer Status Protection Activation Information Directional Protection Activation Information Security Violation Counting Binary Counter Reading - - - - - - - - - - - - - - |- |- ||- - - -| -| -| -| -| |- |- |- -| -| -| -| -| - - - - - - - - - - - - - - - - - - - - - - - - Measurand Information MV CMV SAV WYE DEL SEQ HMV HWYE HDEL Measured Value Complex Measured Value Sampled Value Collection Of Measurands (Phase to ground related measured value of a three phase system) Delta (Phase to phase related measured value of a three phase system) Sequence Harmonic Value Harmonic Value for WYE Harmonic Value for DEL Controllable Status Information SPC DPC INC BSC ISC [ST|CO] [ST|CO] [ST|CO] [ST|CO] [ST|CO] Controllable Single Point Controllable Double Point Controllable Integer Status Binary Controlled Step Position Information Integer Controlled Step Position Information |||- ||||- Controllable Analogue Information APC Controllable analogue set point information Status Settings SPG ING Single Point Setting Integer Status Setting Analogue Settings ASG CURVE Analogue Setting Setting Curve Description Information DPL LPL CSD SGCB Device Name Plate Logical Node Name Plate Curve Shape Description Setting Group Control Block Note: SGCB is a Control Block and not a Common Data Class, but is handled as a CDC by the protocol element! 9-14 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) For commands, the “Extended Common Data Classes” defined in the IEC 61850-8-1 standard are used. These "Extended Common Data Classes" consist of several attributes that are used differently according to IEC 61850 Control Model. CDC Ss (1) Se Ss Se GO GO Cs Ce (2) (2) |- ||- - - -| -| -| -| |- |- |- -| -| -| -| |- -| - - -| |- - - - - - - Extended Common Data Class Specification for [abbreviation ] Controllable Status Information SPC DPC INC BSC [ST|CO] ISC [ST|CO] [ST|CO] [ST|CO] [ST|CO] Extended Common Data Class Controllable Single Point Extended Common Data ClassControllable Double Point Extended Common Data Class Controllable Integer Status Extended Common Data Class Binary Controlled Step Position Information Extended Common Data Class Integer Controlled Step Position Information |||- |||- Controllable Analogue Information APC Extended Common Data Class Controllable Analogue Set Point Information (1) Common Data Classes with the additional designation [ ST|CO] are supported differently by the Server/Client for the Functional Constraints "ST" (Status Information) and "CO" (Control)! (2) In the protocol element with 61850-Client function, for data (attributes) in transmit/receive direction that are not contained in the 61850 standard, the Common Data Class (CDC) can be parameterized. Devices of different manufacturers utilize the possibility in order to expand the logical nodes defined in the standard with additional attributes for data in the private range. For the expansion in the private range, only Common Data Classes can be selected that are already defined in the standard and are supported by the protocol element. The expansions are only supported at the logical node level and with the parameterization the highest value Common Data Class in the hierarchy must be parameterized. Examples: VL.C01/CSWI1.SPos.ctlVal ………………….. (SPos = DPC) VL.C01/XCBR1.SPos.ctlVal …. …………..… (SPos = DPC) VL.C01/MMXU1.STotW..mag.f …………….. (STotW = MV) VL.C01/MMXU1.AS.phsA.cVal.mag.f ………(AS = WYE) Legend: Functions Protocol Elements Ss …….. Server transmitting Se …….. Server receiving Cs ......... Client transmitting Ce ......... Client receiving SsGO … Server transmitting GOOSE (Publish) SeGO … Server receiving GOOSE (Subscribe) DC0-023-2.01 9-15 LAN-Communikation (61850) Logical nodes are structured hierarchically and contain different groups of information: • • • • • • Common Logical Node Information Optional Logical Node Information Status Information Settings Measured Values Controls Example: Logical Node XCBR1 Logical Node: Circuit Breaker [ XCBR ] Common Logical Node Information Mode …………..……………………. [Mod] Behavior ……...………..…………… [Beh] Health ……………………………….. [Health] Name Plate ……………………...…..[NamePlt] … information independent from the dedicated function represented by the LN. E.g. mode, health, name plate, ... Optional Logical Node Information Local Operation ……………………. [Loc] External Equipment Health ……….. [EEHealth] External Equipment Name Plate …. [EEname] Operation Counter ……………...…..[OpCnt] Controls Switch Position ..…………………… [Pos] Block Opening ……….…………….. [BlkOpn] Block Closing ………………………..[BlkCls] Charger Motor Enabled ………..….. [ChaMotEna] Metered Values (Measured Values) Sum of Switched Amperes…. (resetable) [SumSwARs] … are data, which are changed by commands like switchgear state (ON/OFF), tap changer position or resetable counters. E.g. total active power, total reactive power, frequency, net real energy since last reset, ... … are analogue data measured from the process or calculated in the functions like currents, voltages, power etc. e.g. total active power, total reactive power, frequency, net real energy since last reset, … Status Information Circuit Breaker Operating ………….[CBOpCap] Capability Point On Wave Switching ………... [POWCap] Capability Circuit Breaker Operating. ………... [MaxOpCap] Capability When Fully Charged 9-16 DC0-023-2.01 … information representing either the status of the process or of the function allocated to the LN . e.g. switch type, switch operating capability,... Functions Protocol Elements LAN-Communikation (61850) The precise structure of the logical nodes is documented in the IEC 61850-7-4 standard. In the following example, the structure of the logical node for the circuit breaker [XCBR] is documented schematically with designation of the fields. Phsyical Device IED Locical Device #1 LD#1 Locical Device #2 LD#2 Logical Node LHPD These logical nodes must be created on each logical device LLN0 LN Reference Logical Node e.g. XCBR1 XCBR1 Logical Node Attribute [LLName] ………….... Common Logical Node Information [LOC] ………………... [EEHealth] ………….. Data Logical Node Attribute „POS“ CDC = „Controllable Double Point“ (DPC) [EEName] …………… Data Reference [OpCnt] ……………… [Pos] ……………….… Position Controls XCBR1.Pos Data Attribute Data Attribute Reference XCBR1.Pos.ctlVal Attribute Type = BOOLEAN 0 = OFF 1 = ON Attribute Type [operTim] … Operate Time XCBR1.Pos.operTim [origIn] ……. Originator XCBR1.Pos.orIgin [ctlNum] ….. Control Number XCBR1.Pos.ctlNum Attribute XCBR1.Pos.stVal [q] ……..….. Quality XCBR1.Pos.q [t] ……….... Time Stamp XCBR1.Pos.t XCBR1.Pos.stSeld [subEna] ..… Substit. Enable XCBR1.Pos.subEna [subVal] ...… Substit. Value XCBR1.Pos.subVal [subID] ….… Substit. ID XCBR1.Pos.subQ [pulseConfig] ..… Pulse Configuration XCBR1.Pos.pulseConfig [ctlModel] …...…. Control Model XCBR1.Pos.ctlModel [sboTimeout] ….. SBO Timeout XCBR1.Pos.sboTimeout [sboClass] …..… SBO Class XCBR1.Pos.sboClass [d] ………………. Textual desc. of data XCBR1.Pos.d [dataNs] ……..… Data Name Space XCBR1.Pos.dataNs [cdcNs] ……...… CDC Name Space XCBR1.Pos.cdcNs [subQ] …..… Substit. Q XCBR1.Pos.subID SUBSTITUTION [stSeld] ….... Selected STATUS Attribute Type CONFIGURATION, DESCRIPTION and EXTENSION Attribute Type = CODED ENUM 0 = intermediate-state 1 = off 2 = on 3 = bad-state XCBR Common Data Class: „Controllable Double Point“ (DPC) Status Value [stVal] ….…. Status Value Logical Node CONTROL [ctlVal] ……. Control Value [BlkOpn], [BlkCls], [ChaMotEna] [SumSwArs] Metered Values [CpOpCap], []POWCap], [MaxOpCap] e.g. XCBRn Locical Device #2 LD#n Functions Protocol Elements Status Information … The controllable data is in the status „selected“ … Value used to substitute the data attribute „q“ … Shows the address of the device that made the substitution. The value of null shall be used if subEna is false of if the device is not known DC0-023-2.01 9-17 LAN-Communikation (61850) The following example shows the representation of the logical node in the IEC 61850-7-4 standard for the circuit breaker (XCBR). Legend: M/O ……. M = Mandatory (these attributes must be mandatorily supported) O = Optional (these attributes can be optionally supported) The Common Data Class [CDC] is visible in the field "Attr. Type". The following example shows the representation of the basic data types [CDC] in the IEC 61850-7-3 standard for the Common Data Class "Controllable Double Point (DPC)". 9-18 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) IEC 61850 Address The IEC 61850 address is represented as readable text (ASCII-characters) and is presently limited to max. 62 characters. The syntax of the 61850 variable names [Data Attribute Reference] is defined by the 61850 standard. Every object is unambiguously identified by its address (name of the object) in plain text. Due to the address, the objects are self-descriptive. Structure (principle): IED001.MEAS / Q1MMXU1 . Mod . ctVal LDName LNName DataName DataAttributeName LDName/LNName.DataName.DataAttributeName LDName ………Logical Device Name LNName .…….. Logical Node Name Data and data attributes can thereby occur several times in the structure. IED001.MEAS / Q1MMXU1 . PhV . phsA . cVal . Mag . f LDName LNName DataName DataName DataAttributeName DataComponentName DataComponentName 61850 address: FCD: LDName: LNName: Lnclassname: DataName: LDName + "/" + FCD = 32 + 1 + 29 = max. 62 characters LNName + DataName + DataAttributeName + DataComponentName = max. 29 characters IEDName + LDName = max. 32 characters LN_prefix + LN_classname + LN_instanceID = max. 11 characters = max. 4 characters = max. 10 characters The address must not contain any special characters (excluded from this are the established separating characters "/" and ".") and no umlauts. Note: The use of the special character "_" is possible in principle, but should not be used due to the compatibility with other devices! The structure of the IEC 61850 address is explained with the help of the following example. Functions Protocol Elements DC0-023-2.01 9-19 LAN-Communikation (61850) IEC61850-Adresse (Example): BC1703CTRL/Q00XCBR1.Pos.stVal Data Attribute Reference Data Reference Logical Node Reference Functional Constraint Data (FCD) (max. 29 signs) BC1703 CTRL / Q00 XCBR 1 . Pos . stVal Data Attribute Name - the name is standardized (61850) Data Name (Data Object Name) Logical Node Name „Suffix“ - only numbers are allowed Logical Node Name „Class“ - the name is standardized (61850) 4 signs fixed Logical Node Name „Prefix“ Logical Node Name „LNName“ (max. 11 signs) - the name is standardized (61850) Logical Device Name [optional] - the name is freely definable IED Name (physical device) - the name is freely definable (the 1st sign must be a character) Logical Device Name „LDName“ (max. 32 signs) [optional] - the name is freely definable … The seperators at these positionens are defined by norm IEC 61850 optional fields (all other fields are mandatory!) Examples for the valid syntax of 61650 addresses: BC1703CTRL/Q00XCBR1.Pos.stVal VL.C01/Q0XCBR1.Mod.stVal T403B1CTRL/GGIO10.SPCSO0.stVal IED001MEAS/Q1MMXU1.Mod.ctVal System information module failed: Reference voltage U4: BC1703CTRL/SYSGGIO1.SPCS01.stVal BC1703MEAS/GGIO1.AnInU4.mag.f Examples for a 61850 address with max. recursion depth: IED001.MEAS/Q1MMXU1.PhV.phsA.cVal.mag.f BC1703_E17CTRL/GO_E07GGIO1.DPCSOQ1.stVal 9-20 DC0-023-2.01 Functions Protocol Elements max. 62 signs according IEC61850-8-1 (Ed.1) LAN-Communikation (61850) MMS Address For the transmission the IEC 61850 address is converted by the protocol element on the line to the defined format of the MMS address. The MMS address is presently used with max. 65 characters. Of the 65 bytes, 3 characters are fixed reserved through the FCD (Functional Constraint Data) and 1 separating character by the MMS address structure. As a result, the present implementation produces a max. possible length for the 61850 address of 62 characters. MMS-Adresse (Example): BC1703CTRL/Q00XCBR1$ST$Pos$stVal Functional Constraint Data (FCD) BC1703 CTRL / Q00 XCBR 1 $ ST $ Pos $ stVal Functional Constraint - built by the protocol element (2 signs fixed) The separators at these positions are defined by the MMS -Norm The field "Functional Constraint [FC]" of the MMS address is inserted by the protocol element itself. One IEC 61850 Common Data Class [CDC] consists of various Functional Constraints. Note: A Common Data Class is e.g. single-point information, double-point information,… FC Functional Constraint CF Attribute used for configuration CO Control DC Attribute used for description EX Attribute used for extensions of common data classes MX Measurands (analogue values) SE Attribute used for edit parameter group SG Attribute used for active parameter group SP Setpoint ST Status Information SV Attribute used for substitution Examples for the valid syntax of MMS addresses: BC1703CTRL/Q00XCBR1$Pos$stVal VL.C01/Q0XCBR1$Mod$stVal T403B1CTRL$GGIO10$CO$SPCSO0$stVal BC1703_E17CTRL/GO_E07GGIO1$ST$DPCSOQ1$stVal Examples for MMS addresses with max. recursion depth: VL.C01/MMXU1$MX$A$phsA$cVal$mag$f Functions Protocol Elements DC0-023-2.01 9-21 LAN-Communikation (61850) Data Class, Data Attributes are those data objects which contain real information. The attributes are assigned to the common data classes. The common data classes [CDC's] are documented in the IEC 61850-7-3 standard. The elements "Physical Device", "Logical Device", "Logical Node" and "Data Class" are only used for the structuring of the data. The CDC's are structural elements with attribute-types that contain (apart from a few exceptions) no further substructures. Attribute types (without SUB-structure): e.g.: BOOLEAN, INT8U, INT32U,… Attribute types (with SUB-structure): e.g.: TimeStamp, Quality, Originator,… Note: - Attribute types in upper case / lower case (e.g. TimeStamp) have a further sub-structure. - Attribute types in upper case (e.g. BOOLEAN) have no further sub-structure. 9-22 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.1.2. Definition of the Connections IP Addresses Every device which is connected to a TCP/IP network has an unambiguous IP address. 32 The protocol firmware supports only IP addresses in the format IPv4 (=32 Bit). With that, 2 , in other words 4,294,967,296 addresses can be represented. The IP address is mostly represented in the dotted decimal notation. Example: 130. 94.122.195 The IP address of the own station is to be parameterized in the system-technical parameters with the parameter IP-address | own IP-address. The IP address of the remote station is to be parameterized for each connection in the system-technical parameters Connection definition. Port Number Every IP connection is defined by the IP address of the own station and the remote station and the port number. The port numbers are defined by the IANA (Internet Assigned Numbers Authority). Port numbers used in the LAN protocol firmware: Port Number Protocol Standard 102 IEC 61850 IEC 61850 80 HTTP (Hypertext Transfer Protocol) RFC 2616 (HTTP/1.1) 123 NTP V3 (Network Time Protocol) RFC 1305 Telnet RFC 854 2001 1) Legend: RFC .. Request for Comments 1) this port number is not registered with IANA! Default Router (Default Gateway) If the own network is connected by means of a router, then the IP address of the default router is to be set in the system-technical parameters of the protocol firmware with the parameter IP-address | Default-Router (Default-Gateway). Functions Protocol Elements DC0-023-2.01 9-23 LAN-Communikation (61850) Subnet Mask The subnet mask is a bit mask, which splits up an IP address into a network part and a device part (host part). It is used in IP networks to make routing decisions. The subnet mask is to be set in the system-technical parameters of the protocol firmware with the parameter IPaddress | Subnet mask. The subnet mask is exactly as long as the IP address on which it is applied (therefore 32 Bit for IPv4). All bits of the network part are set to "1" and all bits of the device part to "0". Predominantly, the notation of a network mask is not performed binary, rather (as for IP addresses too) frequently in decimal notation (dotted decimal notation). Consequently, the IPv4 network mask for a 27 bit network part reads 255.255.255.224. The usable address space of a network is defined by the subnet mask. For a 27 bit network part, the first 27 places of the IP address of the network part are identical and for all hosts of the network. The network part is continuous in all practical cases of application (without zeros in between). Example: Calculation of network and host section IPv4 address = 130.94.122.195 Network part = 27 Bit Subnet mask = 255 . 255 . 255 . 224 11111111 11111111 11111111 11100000 IP Address Network mask Network part Decimal 130.094.122.195 255.255.255.224 130.094.122.192 Binary 10000010 01011110 01111010 11000011 11111111 11111111 11111111 11100000 10000010 01011110 01111010 11000000 Calculation IP address AND Subnet mask = Network part IP Address Network mask Device part 130.094.122.195 255.255.255.224 3 10000010 01011110 01111010 11000011 11111111 11111111 11111111 11100000 00000000 00000000 00000000 00000011 IP address AND (NOT subnet mask) = Device part A network mask with 27 bits set produces a network part of 130.94.122.192. 5 bits, and therefore 32 addresses, remain for the device part. In the example above, the smallest host address ends with 11000000 (decimal: 192), the largest possible host address with the octet 11011111 (decimal: 223). The address range for the subnet in the example is therefore 130.094.122.192 to 130.094.122.223. The largest address is by definition reserved for the IP broadcast and the smallest address describes the network itself. They are therefore not included among the freely usable addresses. In practice, the default gateway is often assigned to the smallest (in the example, binary: 11000001, decimal: 193) or the largest (in the example, binary: 11011110, decimal: 222) usable IP address in the network. 9-24 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Connection-specific parameters In the master station and in the remote terminal unit(s), the required settings are to be carried out in the parameters of the Connection definition for every connection. The following parameters can be set per connection: • Parameter "Station Number" The station number is used SICAM 1703 internal for the routing of the data, diagnostic treatment and failure management. The station number is the SICAM 1703 internal reference for that connection to which an IP address is assigned. During the data transmission, only the IP address assigned to the station number is transmitted, the station number is not transmitted. For the data flow routing, the data to be transmitted are routed to a "station number" (connection number = destination station number). The station number is to be entered for each connection in the parameters Connection definition | Station number. • Parameter "Enable" A parameterized connection can be activated/deactivated with the parameter Connection definition | Enable. e.g. this way connections can be prepared, that are first activated at a later time by means of parameterization. • Parameter "Station Failure" For certain redundancy configurations or operating modes, for the SICAM 1703 internal diagnostics, the failure of a connection can be suppressed with the parameter Connection definition | Station failure. If the failure is suppressed, the connection is never signaled in the diagnostic as failed and all messages in transmit direction (also INIT-End) are discarded until the connection is established! Note: As a result a ring overflow is avoided with non-connected remote stations. • Parameter "Own Mode" For every TCP/IP connection one party is either "Server (Listener)" or "Client (Connector)". The TCP/IP connection is always only established by the "Client (Connector)". With the parameter Connection definition | Own mode the role of the own station is to be parameterized for every connection. • Parameter "IP-addr" [only ETA2] For every connection the IP address of the remote station is to be parameterized. The IP address (Internet-Protocol) is a number, which permits the addressing of parties in LAN IP networks. This address must always be unambiguous in one network. The IP address is to be parameterized as follows: Example: 130. 94.122.195 The IP address of the remote station is to be parameterized for every connection with the parameters Connection definition | IP-addr. The settings of the variable elements of the message in the IEC 60870-5-101/104 parameter block of the basic system element are not evaluated by the 61850 protocol element. Functions Protocol Elements DC0-023-2.01 9-25 LAN-Communikation (61850) 9.1.2.1. Data Transmission Procedure The transmission of data ready to be sent from the master station (61850-Client) to the remote terminal unit (61850Server) takes place spontaneously with connection established and for each connection. The transmission of data ready to be sent from the remote terminal unit (61850-Server) to the master station (61850-Client) takes place either spontaneous by means of 61850-Reports or interrogated by the master station. For each LAN connection, the Client-Server data transmission is comparable with that between 2 stations over a virtual point-to-point connection. In addition, with 61850, for the transmission of data between servers the Multicast transmission procedure "GOOSE" (Generic Object Oriented Substation Events) is used. The transmission rate (10/100 Mbit/s) and the method of transmission (full duplex/half duplex) on the ethernet is determined with the parameter advanced parameters | Ethernet-speed and -duplex. In the default setting this parameter is set to "autosense" (=automatic detection) and only needs to be specifically adjusted in exceptional cases. Note: If problems occur with the default setting when coupling other systems directly with cross-over cables or when using HUB's or other network components, here "half duplex" is to be used. The data storage on the basic system element is managed individually for every LAN connection. Data messages "to all" are already split up selectively for every LAN connection by the communications function on the basic system element (BSE). The prioritization of the data to be sent to the protocol element takes place on the basic system element (BSE). System data are processed with high priority by the communications function on the basic system element and transferred to the protocol element for transmission as fast as possible. This prioritization is of no significance for the protocol element with 61850-Server function. The data are received from the basic system element by the protocol element, entered in the IEC 61850 organized process image on the protocol element and prepared for transmission according to IEC 61850. The possible 104-blocking for the data transmission between basic system element protocol element is not used. In the SICAM 1703 protocol element with 61850-Client function, with the parameter IEC61850 | Client | Timeout 61850 Services the monitoring time for 61850 Services (e.g.: Read/Write) can be set. For commands, this monitoring time is extended to the time that can be set with the parameter IEC61850 | Timeout Confirmation -> Termination. 9-26 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.1.2.2. Failure Monitoring The monitoring of every connection by the master station (Client) and by the remote terminal unit (Server) is carried by means of cyclic transmitted messages (TCP Keep Alive Frames). The failure monitoring can be carried out independently by both participating stations of a connection. The "TCP Keep Alive Frames" are generated and monitored by the TCP/IP-Stack of the protocol firmware itself and are not transferred to the basic system element. The time scale for the cyclic transmission of the "TCP Keep Alive Frames" is determined with the parameter advanced parameters | TCP Keep Alive Raster. If with connection established, the cyclic reception of the "TCP Keep Alive Frames" is missing, the failure of the connection is signaled by the TCP/IP-Stack of the protocol firmware. The failure of a connection is signaled immediately by the protocol element to the basic system element, insofar as this is not disabled in the parameters of the Connection definition with the parameter Station failure. With connection failed, the client attempts to re-establish a connection to the assigned server in a cyclic time-scale. The time-scale can be set with the parameter IEC61850 | Client | Timeout IEC61850 connection setup. No further data are sent from the connections with Client-functionality to failed remote stations until successful establishment of the connection and the initialization of the connection. The data are stored in the data storage of the communication function on the basic system element (BSE) until these are deleted by the dwell time monitoring or can be transmitted to the re-reachable remote station. From the connections with Server-functionality, further data are sent from the basic system element and entered in the internal IEC 61850 data model, even with failed connection to the remote station. Functions Protocol Elements DC0-023-2.01 9-27 LAN-Communikation (61850) 9.1.3. Station Initialization Initialization of the Connections [Client] After startup, the connection is established for every connection at TCP/IP level by the 61850-Client. For failed or unreachable remote stations, a connection setup (attempt) for the connection is performed cyclic by the 61850-Client. After complete initialization of a connection, the protocol element with 61850-Client function starts the data pick-up from the basic system element and triggers a general interrogation to the basic system element. Initialization of the Connections [Server] After startup, all parameterized connections with 61850-Client function are reported by the protocol element as failed (insofar as this is not disabled in the parameters of the connection definitions). For each connection with 61850-Server function, the protocol element waits for an establishment of the connection at TCP/IP level by the 61850 Client. 9-28 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.1.4. Acquisition of Events (transmission of data ready to be sent) With connection established, the transmission from the master station (Client) to the remote terminal unit (Server) takes place spontaneously. The transmission from the remote terminal unit (Server) to the master station (Client) takes place either spontaneous by means of reports or interrogated by the master station. For the transmission of data between servers, the "GOOSE" transmission procedure can be implemented. 9.1.4.1. Data Transmission Server Client The transmission of data ready to be sent from the master station (61850-Client) to the remote terminal unit (61850Server) takes place spontaneously with connection established and for each connection. The transmission of data ready to be sent from the remote terminal unit (61850-Server) to the master station (61850-Client) takes place either spontaneous by means of 61850-Reports or interrogated by the master station. With the parameter IEC61850 | Client | advanced parameters | IEC61850 Service für Abfrage it is determined, whether the transmission of the data from the remote terminal unit (61850-Server) master station (61850 Client) is carried out spontaneously by means of reports or through cyclic interrogation by the master station. With spontaneous transmission using reports, the spontaneous transmission is activated in the Report Control Block of the 61850-Server by the protocol element with 61850-Client function. With transmission of the data through cyclic interrogation, the data attributes are interrogated selectively by the protocol element with 61850-Client function (Report Control Block, Reports and Data Sets are not used here). The time-scale for the cyclic interrogation of the individual values can be parameterized with the parameter IEC61850 | Client | advanced parameters | acquisition grid for "single read requests". The possible 104-blocking for the data transmission between basic system element protocol element is not used. The prioritization of the data ready to be sent by the basic system element (BSE) is of no significance for the protocol element with 61850-Server function. The data are transferred from the basic system element, entered in the IEC 61850 organized process image on the protocol element and prepared for transmission according to IEC 61850. The prioritization of the data ready to be sent by the basic system element (BSE) is only of significance for the protocol element with 61850-Client function. Functions Protocol Elements DC0-023-2.01 9-29 LAN-Communikation (61850) Reports / Report Control Block The spontaneous transmission of data from 61850-Server 61850-Client takes place by means of reports. The reports are created permanently in the servers and every report has its own Report Control Block. The characteristics of the respective report are entered in the Report Control Block. The Report Control Block can be read as well as written by the 61850-Server. The following information are stored in the Report Control Block: (extract-wise) • • • • Reference to the associated DataSet Trigger for the transmission (spontaneous, general interrogation,…) DataSet Name (optional) … Buffered Reports, Unbuffered Reports For the reports, a distinction is made between "Buffered Reports" and "Unbuffered Reports". This function is determined by the 61850 device. With the "Buffered Reports", changes are stored after a connection failure. In the handling of the reports, on reception no distinction is made between Buffered/Unbuffered reports by the SICAM 1703 protocol element with 61850-Client function. The SICAM 1703 protocol element with 61850-Server function only supports Unbuffered Reports. Static / Dynamic Data Sets In the datasets, all information is contained that can be transmitted spontaneously from the 61850-Server to the 61850-Client. Required values that are not contained in the datasets, must be read out from the 61850-Client by cyclic interrogation of the attributes. Static datasets are predefined by the 61850-device and are created in the device by the 61850-Server function itself. In SICAM 1703 devices, the static datasets are generated by the protocol element with 61850-Server function from the data of the SIP message address conversion in transmit direction. Dynamic datasets must be created by the 61850-Client in the 61850-Server. In the initialization phase, the protocol element with 61850-Server function reads out the information from those devices with 61850-Client function, whether dynamic datasets are supported. Dynamic datasets are generated by the protocol element with 61850-Server function from the data of the SIP message address conversion in receive direction and created in the devices with 61850-Server function. With the parameter IEC61850 | Client | advanced parameters | dataset it is determined how the dynamic datasets are to be created. The datasets can be created as follows: • • For each logical node For each logical device Hints: - Siemens protection equipment of the Siprotec series support only dynamic datasets. - Protection equipment of other manufacturers mostly support only static datasets 9-30 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.1.4.2. Data Transmission Server Server with "GOOSE" [only server] The Generic Object Oriented Substation Events (GOOSE) is a transmission service of IEC 61850 for generic status events, that can be sent simultaneously per Multicast to multiple devices in order to satisfy high real-time requirements. Typical cases of application are the spontaneous transmission of switching device settings in the decentral interlocking of switching commands in substations. GOOSE messages use the ether-type specification for VLAN, the prioritization and are represented directly on the ethernet layer. With GOOSE messages according to standard part IEC 61850-9-2, data are exchanged between 61850 devices (servers). Range for the Multicast address (MAC address) for GOOSE: From Multicast Address 01-0C-CD-01-00-00 To 01-0C-CD-01-01-FF For the GOOSE data transmission, the IEC 61850 protocol element supports only basic types (single elements) – data structures are not supported! The GOOSE data transmission is supported by the server function of the protocol element in transmit direction "Publisher" (transmitter) and also in receive direction "Subscriber" (receiver). The datasets to be transmitted are defined with the process-technical parameterization of the SIP message address conversion. The datasets must consist of data of the MMS directories. GOOSE messages are transmitted with high priority by the switches implemented in 61850 networks. For this the switches must support the standard IEEE802.1Q (prioritization of messages). GOOSE Transmission Procedure The GOOSE data transmission is a cyclic multicast transmission. A GOOSE message is thereby transmitted from one device as "Publisher" (transmitter) and received by multiple devices "Subscribers" (receivers). With the GOOSE data transmission, the GOOSE message is transmitted spontaneously immediately with change and then cyclic with changed cycle time (repeat time). The data transmission is not acknowledged, the reception of the current state is ensured through the repeat procedure. The initial repeat time after a spontaneous GOOSE data transmission is 20ms. This time is doubled with each transmission until the parameterized maximum repeat time is reached. The maximum repeat time for GOOSE messages is to be parameterized with the parameter IEC61850 | Server | Goose | max. Wiederholzeit für GOOSE Telegramme. 20ms 40ms 80ms 160ms Settable time scale Time scale Send GOOSE Change Spontaneous data change #1 in GOOSE data set Functions Protocol Elements DC0-023-2.01 9-31 Settable time scale LAN-Communikation (61850) 20ms 40ms 80ms xx ms 20ms 40ms 80ms Settable time scale Settable time scale Time scale Send GOOSE Change Spontaneous data change #1 in GOOSE data set Spontaneous data change #2 im GOOSE Dataset Failure Monitoring The failure monitoring for GOOSE messages in receive direction (Subscriber) is derived from the current HOLDTime (repeat time) per GOOSE application. The current HOLD-Time is also included in every message of a GOOSE message. The time for the failure monitoring is the current HOLD-Time multiplied by the parameterized maximum number of retries for GOOSE. The maximum number of retries for GOOSE messages is to be parameterized with the parameter IEC61850 | Server | Goose | Retry count for GOOSE. After a failure is detected, the data concerned can be emulated by the protocol element to the basic system element as failed ("not topical"). The selection of whether the data are to be emulated as failed, is set with the parameter IEC61850 | Server | Goose | Mark data invalid after GOOSE failure. Note: If the emulation of the data concerned is deactivated on failure, the monitoring by the user function must be ensured. 9-32 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Parameters for GOOSE Data Data of the process-technical parameter setting (SIP message address conversion in transmit/receive direction) can be selected for the GOOSE data transmission. All data with the same "Goose-Index" are assigned to one GOOSE application. The detail parameters for each GOOSE application (GOOSE-Index) are to be parameterized in the systemtechnical parameters in the spreadsheet IEC61850 | Server | Goose | Goose Definition. All data of a GOOSE application are transmitted with the parameterized multicast address. The following parameters can be set in the goose definitions: • Parameter "Enable" A parameterized GOOSE application can be activated/deactivated with the parameter IEC61850 | Server | Goose | Goosedefinition | Enable. e.g. this way GOOSE applications can be prepared, that are first activated at a later time by means of parameterization. • Parameter "Goose Index" With the GOOSE Index, the data of the SIP message address conversion are assigned to the GOOSE application. The GOOSE Index is only used SICAM 1703 internal and is parameterized for each GOOSE application with the parameter IEC61850 | Server | Goose | Goosedefinition | Goose Index. • Parameter "Goose Control Block (gocbref)" With the parameter IEC61850 | Server | Goose | Goosedefinition | Goose Control Block (gocbref) the reference to the GOOSE Control Block is parameterized. The GOOSE Control Block is generated by the protocol element for each GOOSE application from the parameters of the goose definitions and can be read by the Client. With the integrated WEB server, the GOOSE Control Block can be read out in the directory of the server under the Functional Constraint "GO". • Parameter "Goose Id (goid) With the parameter IEC61850 | Server | Goose | Goosedefinition | Goose Id (goid) an unambiguous GOOSE identification is parameterized. The GOOSE identification must be unambiguous in the network and is transmitted with the GOOSE message. • Parameter "Dataset Reference" For every GOOSE application a specific dataset is created in the SICAM 1703 Server. With the parameter IEC61850 | Server | Goose | Goosedefinition | Dataset Reference the reference to the dataset is to be parameterized for each GOOSE application. • Parameter "MAC Address" Every GOOSE application is transmitted with Multicast to multiple devices as GOOSE message. With the parameter IEC61850 | Server | Goose | Goosedefinition | MAC Address the multicast address (=MAC address) is to be parameterized for each GOOSE application. The MAC address is to be parameterized as character string without separating character. Example: The multicast address 01-0C-CD-01-01-FF is to be parameterized with the character string 010CCD0101FF. • Parameter "AppId" With the parameter IEC61850 | Server | Goose | Goosedefinition | AppId the application identification (AppId) of the GOOSE application is to be parameterized. • Parameter "configRev" With the parameter IEC61850 | Server | Goose | Goosedefinition | configRev an unambiguous revision identifier of the GOOSE application is to be parameterized. This revision identifier should be changed when the dataset of the GOOSE application changes, so that no malfunction occurs in connected devices with incompatible parameter setting. Note: The revision identifier of the GOOSE application is generally not used presently and is parameterized with a fixed value! Functions Protocol Elements DC0-023-2.01 9-33 LAN-Communikation (61850) • Parameter "VLAN Vid" With the parameter IEC61850 | Server | Goose | Goosedefinition | VLAN Vid the VLAN-ID (unambiguous number of the virtual LAN’s) is to be parameterized. With virtual LAN's (VLAN's), on a physical LAN several virtual LAN’s are defined, which do not mutually hinder each other and which also cannot receive or listen to the data traffic of the other respective VLANs on the physical ethernet phase. To be able to screen and if necessary prioritize the data traffic of a virtual LAN against the other network parties, the data packets must have a corresponding identification. For this, the MAC-Frames are expanded with an additional feature (a “Tag”). The corresponding procedure is therefore also called “Frame-Tagging”. The Tagging is realized with an additional field in the MAC-Frame. In this field, two items of information essential for the virtual LAN are contained: VLAN-ID: The virtual LAN is identified with an unambiguous number. This ID determines the association of a data packet to a logical (virtual) LAN. With this 12-bit value, up to 4094 different VLAN's can be defined (the VLAN-IDs “0” and “4095” are reserved or not allowed). Priority: The priority of a VLAN-identified data packet is flagged with a 3-bit value. Thereby “0” stands for the lowest priority, the “7” for highest priority. Data packets without VLAN-Tag are handled with the priority “0”. • 9-34 Parameter "VLAN priority" With the parameter IEC61850 | Server | Goose | Goosedefinition | VLAN priority the priority for the data packets in the VLAN is to be parameterized. DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.1.5. General Interrogation, Outstation Interrogation The general interrogation (outstation interrogation) function is used to update the master station after the internal connection initialization or after the master station has detected a loss of information. A general interrogation command "to all" triggered in the system is always transferred by the communications function on the basic system element (BSE) station-selective (per connection) to the protocol element (server or client) and replied to by this directly from the internal process image of the protocol element with the current time. Handling of the General Interrogation in the Protocol Element with 61850 Client Function A general interrogation is only sent to the server by the protocol element with 61850 Client function after startup or after going communication failure (connection failure) (GI-Bit in Unbuffered Control Block). Handling of the General Interrogation in the Protocol Element with 61850 Server Function The protocol element with 61850 Server function does not perform any general interrogation towards the basic system element. A general interrogation triggered by the 61850 Client is replied to by the protocol element with 61850 Server function directly from the internal process image of the protocol element by means of "Unbuffered Reports". Functions Protocol Elements DC0-023-2.01 9-35 LAN-Communikation (61850) 9.1.6. Clock Synchronization In networks and in systems with time-critical tasks, a precise time is essential. The clock synchronization for IEC 61850 can be performed in the following ways: • Network Time Protocol (NTP) according to RFC 1305 Messages that are transmitted after a startup, but before the station has the correct time, contain the relative time from startup (reference day for ACP 1703: 1.1.2001; for Ax 1703: 1.1.1997) with the flagging of the time stamp as invalid. 9.1.6.1. Clock Synchronization with Network Time Protocol (NTP) The Network Time Protocol (NTP) is a standard for the synchronization of clocks in systems over IP communication networks. NTP is a hierarchical protocol over which time servers can determine a common time amongst each other. The NTP protocol determines the delay of packets in the network and compensates these for the clock synchronization. The NTP protocol uses port number 123. The NTP protocol is a Client/Server protocol. NTP clients can request the time from NTP servers. The Network Time Protocol (NTP) uses the connectionless network protocol UDP. The NTP protocol has been developed especially to enable a reliable time tagging over networks with variable packet delay. The NTP protocol is defined in the standard "RFC 1305: NTP V3". The time stamps in NTP are 64 bits long. 32 bits encode the seconds since the 1st January 1900 00:00:00 hours, 32 the other 32 bits the seconds fraction. In this way, a time period of 2 seconds (about 136 years) can be −32 represented with a resolution of 2 seconds (about 0.25 nanoseconds). NTP uses a UTC time scale and supports switching seconds, but not daylight-saving time and winter time. NTP uses a hierarchical system of different levels. The level specifies how far the NTP server is from an external time source. As time source an atomic clock, a DCF77 receiver or a GPS receiver can be used. A Layer-1 server is connected directly with a time source and uses this as reference for its time. A Layer-2 server uses a Layer-1 server as reference and synchronizes itself with other servers on its level if the connection to the higher level fails. The highest level is 16 and signifies, that this NTP server has not yet calibrated itself with other servers. As a rule no more than 4 levels exist, since otherwise the time would deviate too much. 9-36 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.1.6.1.1. Clock Synchronization with one or several NTP Servers For the clock synchronization of a component, the time information can be requested from one or several NTP servers in the network. The NTP servers themselves are synchronized either directly with DCF77 or GPS receiver, or by interrogating the time information from other NTP servers. Clock synchronization over LAN: • • • • • Clock synchronization with one or several NTP servers - Server synchronized over GPS (DCF77 on request) - One server can service several automation units Protocol: NTP V3 (Network Time Protocol) according to RFC 1305 Up to 4 different NTP servers can be interrogated (redundancy) Cyclic time interrogation of the NTP servers, settable in seconds grid, self-adapting Achievable accuracy: approx. 3ms (dependent on the quality of the IP network) Parameters for NTP time synchronization (NTP Client): • NTP Time Synchronization The time synchronization by means of NTP is enabled with the parameter NTP-time synchronisation client | NTP-time synchronisation. The other parameters for NTP time synchronization are only displayed after the function has been enabled. • NTP Maximum Time Deviation If the deviation of the time between the own component and the NTP server is greater than the parameterized value, an error is signaled. The maximum time deviation is to be parameterized with the parameter NTP-time synchronisation client | NTP optimization | NTP maximum time deviation. • NTP Server 1 IP address NTP Server 2 IP address NTP Server 3 IP address NTP Server 4 IP address The protocol firmware supports max. 4 different redundant NTP servers. The time is always requested from all parameterized NTP servers. The time for the synchronization is determined by means of a defined algorithm from the times received from the NTP servers. For every NTP server the unambiguous IP address of the NTP server is to be parameterized in the format IPv4 (32 Bit) in dotted decimal notation. Example: 130. 94.122.200 The IP addresses of the NTP servers are to be parameterized with the parameters NTP-time synchronisation client | NTP-Server 1 IP-address, … NTP-Server 4 IP-address. Functions Protocol Elements DC0-023-2.01 9-37 LAN-Communikation (61850) 9.1.6.1.2. Clock Synchronization for one or several NTP Clients In configurations with less demand on the accuracy for time synchronization, the LAN protocol firmware in the SICAM 1703 component with 61850 Client functionality provides an integrated NTP server for other systems. This function is then helpful if the clock synchronization of the remote terminal unit is carried out by means of DCF77 receiver or over a serial interface, and in this remote terminal unit other devices are connected over LAN, which require a time synchronization with NTP. Through this the additional procurement of an NTP server for the subnet in the remote terminal unit is not necessary! The time of the integrated NTP server is controlled by the local time of the component. The accuracy is therefore dependent on the accuracy of the clock synchronization of the component itself. Clock synchronization over LAN: (NTP Server) • • • • • • Protocol: NTP V4 (for NTP V4 there is presently no public specification) Level 14 (… based on the achievable accuracy with remote synchronization over serial communication line) The achievable accuracy is dependent on the accuracy of the clock synchronization of the component The NTP server supports only the request of the time (BROADCAST transmission of the time is not supported by the integrated NTP server) max. 100 clients with a time request 1x per minute Comment: This limit is an experimental value (the limit results from the system load utilization) Reaction time (transmission of the requested time by the protocol firmware): Typically 300-900us Parameters for NTP time synchronization (Server): 9-38 • NTP Server The integrated NTP server function of the LAN communications firmware is enabled with the parameter NTPtime synchronisation server | NTP-Server. • Synchronization with invalid time With function enabled with the parameter NTP-time synchronisation server | synchronisation with invalid time NTP reply messages are also sent when the time of the SICAM 1703 component is not yet set. DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.1.7. Command Transmission For the transmission of commands, the Common Data Classes expanded in the IEC 61850-8-1 standard are used. These expanded Common Data Classes consist of several attributes that are all transmitted in one 61850 message. The protocol element with 61850-Client function describes the attribute "Check" as last attribute during the preparation of the command. The protocol element with 61850-Server function only then processes the command further if the attribute "Check" is set. Exception: With abortion of the command ("Cancel"), instead of the attribute "Check" the attribute "Test" is used. At the same time a maximum of 10 different commands can be executed simultaneously by the protocol element with 61850 Client or Server function. The transmission of commands for IEC 61850 is defined in the "Control Models": IEC 61850 Control Model Data Attributes without TimeActivatedOperate Direct with normal security Direct with enhanced security Select Before Operate with normal security 1) Select Before Operate with enhanced security Note 2) Oper Only EXECUTE-command Oper Only EXECUTE-command Select Before Operate (SBO) Oper Cancel Only SELECT/EXECUTE-commands Select Before Operate (SBOw) Oper Cancel Only SELECT/EXECUTE-commands 1) … is not supported by the SICAM 1703 protocol element! 2) … "Data Attributes with Time Activated Operate" are not supported by the protocol element! The "Control Model" is determined by the 61850-Server and read out by the 61850-Client in the startup phase. With the Control Models "Direct With Enhanced Security" and "SBO With Enhanced Security" the Termination is also transmitted and the Termination for IEC 60870-5-101/104 is derived from this. With the other Control Models the Termination for IEC 60870-5-101/104 is derived from the return information. IEC 61850-7-2 Model/Services: IEC 61850-7-2 Model IEC 61850-7-2 Service Control Select Note SelectWithValue Cancel Operate CommandTermination TimeActivatedOperate 1) 1) … is not supported by the SICAM 1703 protocol element! Functions Protocol Elements DC0-023-2.01 9-39 LAN-Communikation (61850) The SICAM 1703 protocol element for 61850 performs the adaptation ("Mapping") of the various command modes from IEC 60870-5-101/104 IEC 61850. SICAM 1703 internal, the protocol element with 61850-Server function requests the information ACTCON, ACTTERM and the return information with the cause of transmission = "Return information caused by a remote command" for every command. "1 out of n" Check [Server only] With "1 out of n" check activated, only 1 command output procedure may be performed at one time. The SICAM 1703 protocol element with 61850-Server function can perform a "1 out of n" check either per connection (=station-selective) or per LAN interface (= globally for the LAN interface). The "1 out of n" check is activated on the protocol element with 61850-Server function with the parameter IEC61850 | server | 1 aus N Kontrolle. Command Termination For commands with "Enhanced Security", for the transmission of the information "Command Termination" of the temporary information report "Command Termination" is used. In the SICAM 1703 protocol element with 61850-Client function, with the parameter IEC61850 | client | advanced parameters | termination for commands it can be selected whether the "Termination of Activation" is to be derived from the "Command Termination" of 61850 or from the return information itself for the conversion to IEC 60870-5-101/104. For the evaluation/generation of the termination, a correlation is established by the protocol element between command and return information via the 61850 address from the parameters of the SIP message address conversion (stVal, ctlVal). In the SICAM 1703 protocol element with 61850-Client function, with the parameter IEC61850 | client | Timeout 61850 Services the monitoring time for 61850 Services (e.g.: Read/Write) can be set. For commands, this monitoring time is extended to the time that can be set with the parameter IEC61850 | Timeout Confirmation -> Termination. Converting EXECUTE(104) SELECT/EXECUTE (61850) [Client only] The protocol element with 61850-Client function can convert IEC 60870-5-101/104 commands with "direct command transmission" (Execute only) for the transmission to the 61850 remote station to a "Select Before Operate with enhanced security" command. This function is activated on the protocol element with the parameter IEC61850 | client | Convert commands EXE to SEL/EXE. With function activated the SELECT-command is transmitted immediately to the remote station. After reception of the confirmation for the SELECT-command, the EXECUTE-command is transmitted to the remote station after a settable delay. The delay time can be set with the parameter IEC61850 | client | Delay between SEL CON – EXE ACT. Note: - SELECT/EXECUTE-commands (IEC 60870-5-101/104) cannot be converted to "Direct with normal security" or "Direct with enhanced security" by the protocol element for the transmission to IEC 61850! 9-40 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Monitoring [Client only] The protocol element with 61850-Client function performs the following checks and monitoring during the conversion of the commands from IEC 60870-5-101/104 IEC 61850. • Timeout SELECT – EXECUTE For SELECT/EXECUTE-commands, the protocol element with IEC 61850 Client function monitors the time between IEC 60870-5-101/104 SELECT-command and the IEC 60870-5-101/104 EXECUTE-command at the interface from the basic system element. The monitoring time can be set with the parameter IEC61850 | Timeout Select -> Execute. If the monitoring time expires, a "negative confirmation of activation" (ACTCON-) is transmitted to the basic system element by the protocol element for the IEC 60870-5-101/104 EXECUTE-command and the command is not transmitted. • Timeout ACTIVATION – CONFIRMATION For commands, the protocol element with IEC 61850 Client function monitors the time between the command transmitted to the 61850 remote station [Server] and the CONFIRMATION received from the 61650 remote station. The monitoring time can be set with the parameter IEC61850 | Timeout Activation -> Confirmation. If the monitoring time expires, a "negative confirmation of activation" (ACTCON-) is transmitted to the basic system element by the protocol element. • Timeout CONFIRMATION – TERMINATION For commands, the protocol element with IEC 61850 Client function monitors the time between the CONFIRMATION received from the 61850 remote station [Server] for the transmitted command and the TERMINATION received from the 61650 remote station. The monitoring time can be set with the parameter IEC61850 | Timeout Confirmation -> Termination. If the monitoring time expires, a "negative termination of activation" (ACTTERM-) is transmitted to the basic system element by the protocol element. Functions Protocol Elements DC0-023-2.01 9-41 LAN-Communikation (61850) Monitoring [Server only] The protocol element with 61850-Server function performs the following checks and monitoring during the conversion of the commands from IEC 61850 IEC 60870-5-101/104. • Timeout SELECT – EXECUTE For "Select Before Operate" commands, the protocol element with IEC 61850 Server function monitors the time between the SELECT-command received via IEC 61850 and converted to IEC 60870-5-101/104 and the IEC 60870-5-101/104 EXECUTE (Operate)-command. The monitoring time can be set with the parameter IEC61850 | Timeout Select -> Execute. If the monitoring time expires, the EXECUTE-command is discarded by the protocol element and a "negative confirmation of activation" (ACTCON-) is transmitted to the 61850 server. • Timeout ACTIVATION – CONFIRMATION For commands that have been converted from IEC 61850 to IEC 60870-5-101/104, the protocol element with IEC 61850 Server function monitors that time between the "Activation" (ACT) and the "Confirmation of Activation" (ACTCON) at the interface to/from the basic system element. The monitoring time can be set with the parameter IEC61850 | Timeout Activation -> Confirmation. If the monitoring time expires, a "negative confirmation of activation" (ACTCON-) is transmitted to the 61850 client by the protocol element. • Timeout CONFIRMATION - TERMINATION For commands that have been converted from IEC 61850 to IEC 60870-5-101/104, the protocol element with IEC 61850 Server function monitors that time between the "Confirmation of Activation" (ACTCON+) and the "Termination of Activation" (ACTTERM+) at the interface from the basic system element. The monitoring time can be set with the parameter IEC61850 | Timeout Confirmation -> Termination. If the monitoring time expires, a "negative termination of activation" (ACTTERM-) is transmitted to the 61850 client by the protocol element. 9-42 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.1.7.1. Control Location [Client only] If the function "control location" is activated, commands from the protocol element of the master station are only then transmitted to the addressed remote terminal unit if the command has been sent from an enabled control location (originator address). The setting of the control location itself takes place with a command message in single command format <TI=45> which is converted on the basic system element to a PRE control message (function: set control location) by the protocol control function. A command received with an originator address not enabled as control location is not transmitted from the protocol element of the master station and is discarded. For these commands a negative confirmation of activation (ACTCON-) is sent back immediately by the protocol element to the originator address. 9.1.7.1.1. Control Location Check The control location check is used to check whether the control location, specified with the originator address in the spontaneous information object "Command", has command authority. The originator address specified in the spontaneous information object "Command" must correspond with one of the control locations previously set. If the originator address in the spontaneous information object "Command" does not match with one of the control locations previously set or if no control location has been preset: • • the command is rejected a negative confirmation of the activation is sent (ACTCON-) The control location check is activated as soon as a PRE control message of the type "Set control location" is entered in the PST detailed routing on the basic system element (BSE) for a protocol element (PRE). After startup of the PRE, the BSE sends a PRE control message "Set control location" to the PRE. As a result the control location check function is activated on the PRE. Functions Protocol Elements DC0-023-2.01 9-43 LAN-Communikation (61850) 9.1.7.1.2. Set Control Location The control location is set on the PRE with a PRE-control message (Function = Set control location) either globally for all stations or station-selective. The control location can be set or deleted and is applicable for all commands of a protocol element. On the BSE the control location is set by the spontaneous information object "control location" and is valid for all commands of a protocol element. The assignment of this message takes place in the OPM of the Toolbox II with the category ACP 1703 Systemfunktionen / protocol element control message. For the derivation of the control location, the following values in the spontaneous information object "Command" signify the originator address: Note: Originator Address Control Location 0 Not defined 1 ... 127 remote command 128 ... 255 local command The selection of the control location and the generation of the spontaneous information object "Control location" must be programmed in an application program of the open-/closed-loop control function. With the spontaneous information object "Control location" in "single command" format, up to 256 control locations can be set at the same time. The information object "Control location" is converted on the basic system element (BSE) to a PRE-control message and passed on to the protocol element. Due to an information object "Control location" with the single command state "ON", the originator address is added to the list of enabled control locations (="Control location enabled"). Due to an information object "Control location" with the single command state "OFF", the originator address is deleted from the list of enabled control locations (="control location not enabled"). The deleting of the control locations can be carried out either station-selective for each control location individually or globally for all stations and all control locations. No confirmation (ACTCON) and no termination (ACTTERM) of the command initiation is created for the information object "Control location". With each startup of the protocol element, all enabled control locations are reset. The control locations are to be set again after every startup of the protocol element. 9-44 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.1.7.2. Transmission of Integrated Totals IEC 61850 does not define any counter concepts like IEC 60870-5-101/104. With IEC 61850 integrated totals can be transmitted as measured values. The transmission can be performed either spontaneously with reports or through interrogation of the selective attributes. Functions Protocol Elements DC0-023-2.01 9-45 LAN-Communikation (61850) 9.1.8. File Transfer (disturbance records) In 61850 protection equipment [Server] disturbance records are recorded and stored in the protection equipment as files in IEEE-Comtrade format. These files can be read out by the protocol element of the master station [Client] with the procedures defined in IEC 61850 (ASCI-Service: File Transfer Model) and transferred to SICAM DISTO for storage/evaluation. The protocol element of the master function supports the following possibilities for reading out and transferring disturbance records: • Transfer of disturbance records to SICAM DISTO Attention: A transmission of the disturbance records from the protocol element of the master station to a central control system according to IEC 60870-5-101/104 "Transmission of files in monitoring direction (disturbance record transmission of one protective device)" is presently not supported! According to IEC 61850 the disturbance records are stored in the server in the file directory "COMTRADE". For each disturbance record the following files are created in this directory: • • • Header-File (File-Extension = .HDR) ………… general information about the station (ASCII) Configuration-File (File-Extension = .CFG) ..... general info about the disturbance record (ASCII) Data-File (File-Extension = .DAT) ………...….. Information of analog, digital channels (BINARY) or optionally • ZIP-File (File-Extension = .ZIP) ………...…….. all files of a disturbance record as ZIP-File Optionally, the disturbance records can also be stored in the 61850 Server as "zipped" file, whereby then a separate ZIP-file is created for every disturbance event. The filename of the disturbance record file is not fixed, but normally contains the fault number and possibly additional information for the identification of the fault or the station. IEC 61850-7-2 Model IEC 61850-7-2 Service FILE transfer GetFile Note SetFile DeleteFile GetFileAttributeValues 9-46 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.1.8.1. Transfer of Disturbance Records to SICAM DISTO With the 61850 protocol element [Client] disturbance records can be read out from 61850 devices [Server] and transferred to SICAM DISTO for storage/evaluation. Disturbance records are stored by SICAM DISTO in the format transmitted by the protocol element either as single files in IEEE Comtrade format (*.HDR, *,CFG, *.DAT) or as file in zipped format (*.ZIP). The data transmission between the protocol element and SICAM DISTO is carried out with a proprietary procedure for the transmission of files. The transmission of all necessary information takes place with SICAM 1703 user data containers <TI:=142> in the private range of IEC 60870-5-101/104. For the transmission of disturbance records, a separate "channel“ is defined between the protocol element and SICAM DISTO for every client with SICAM 1703 user data containers (="disturbance record containers"). For each channel a SICAM 1703 user data container (disturbance record container) in transmit direction (to SICAM DISTO) and a SICAM 1703 user data container (disturbance record container) in receive direction (from SICAM DISTO) is to be defined. The assignment of the IEC 60870-5-101/104 message address for the spontaneous information object "disturbance record container" is carried out in the OPM II in the master station in the process-technical parameterization in transmit direction (to SICAM DISTO) with the category firmware / Fault_record_Trans_IEC61850 and in receive direction (from SICAM_DISTO) with the category firmware / Fault_record_Rec_IEC61850. Attention: Redundant configurations with SICAM DISTO are not supported! Sequence of the disturbance record transmission (between Client / Server) The file directory in the server is interrogated cyclic (every 3 minutes) by the protocol element [Client] or spontaneously with a request from SICAM DISTO (e.g. with restart of SICAM DISTO). If the attribute "RcdMade" (RecordMade = "disturbance record has been created") of the Logical Node "RDRE" (Disturbance Recorder Function) is available in the server, this can be entered in the SIP message address conversion in receive direction. With a change of the attribute to "TRUE" or with a change of the time, the protocol element spontaneously executes an interrogation of the file directories of the server – as a result newly stored disturbance records can be interrogated quickly and transmitted. So that the transmission of spontaneous information is not delayed during a fault by the transmission of disturbances records, the interrogation of the file directories by the protocol element first takes place after a delay of 10 seconds. Functions Protocol Elements DC0-023-2.01 9-47 LAN-Communikation (61850) After the transmission of a disturbance record has concluded or with cancelation of the disturbance record transmission to SICAM DISTO, a renewed interrogation of the file directories is performed automatically by the protocol element. IEC 61850 Protocol element [Client] Communication services SAT DISTO … cyclic or spontaneous query of the file directory in the server … in case of a change in the file directory of the server Directory (Ty pe=0) Fetch file (Ty File segment is read out from the server File ready for transmission Fetch selected file pe=4) File segment (Type=1) File segment (Type=1) Last segment „Segment en d“ (Type=2) Acknowledg Next file segment is read out from ther server ement segm ) ent (Type=5 File segment (Type=1) File segment (Type=1) Last segment „Segment end “ (Type=2) nt ment segme Acknowledge Last file segment is read out from ther server (Type=5) File segment (Type=1) File segment (Type=1) Last segmen t „Segment en d“ (Type=3) t ment segmen Acknowledge (Type=5) File completely transmitted File transfer between protocol element and SAT DISTO 9.1.8.2. Transmission of Disturbance Records [SICAM 1703 = Server] Attention: records The protocol element for 61850 [Server] does not presently support any transfer of disturbance according to IEC 61850! Note: The parameters prepared for this function • • IEC61850 | Server | Comtrade Störschriebe | Kanaldefinitionen (CFG) IEC61850 | Server | Comtrade Störschriebe | Headerfile (HDR) are presently not evaluated! 9-48 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.2. Function for the Support of Redundant Communication Routes To increase the availability both master stations as well as remote terminal units can be designed redundant. In this chapter, not the possible redundancy concepts themselves that can be realized are described, rather only those functions supported by the protocol element for the support of redundant systems or communication routes. The following redundancy modes are supported: • • • 9.2.1. Redundancy Mode "1703-Redundancy" Server Redundancy GOOSE Redundancy Redundancy Mode "1703-Redundancy" With the redundancy mode “1703-redundancy”, one remote terminal unit (Controlled Station) is connected with one or several master stations (Controlling Stations) over several logical connections. The data transmission takes place over all connections. The switchover of the redundancy state ("ACTIVE" "PASSIVE") takes place system-internal through redundancy control messages. Redundancy function of the standard redundancy mode: • The data transmission is carried out on all connections independent of the other connections • All data transferred from the basic system element to the LAN protocol element for transmission are also transmitted to the remote station with the redundancy state "PASSIVE". • The 61850 Client + Server functionality is performed unchanged in the redundancy state "ACTIVE" and "PASSIVE" • When using GOOSE in transmit direction (Publisher) special functions can be executed during redundancy switchover to avoid failures in the connected devices (Subscriber). (see chapter GOOSE Data Transmission [Server only] / GOOSE Redundancy) • All data received from the LAN protocol element in the redundancy state "PASSIVE" are marked by the basic system element in the message status with the redundancy status "passive". • The switchover to "PASSIVE" takes place globally per LAN protocol element and not selectively per connection Attention: Redundant configurations with SICAM DISTO are not supported! Functions Protocol Elements DC0-023-2.01 9-49 LAN-Communikation (61850) 9.2.2. Server Redundancy Special functions are implemented in the protocol element for the support of redundant configurations of SICAM 1703 devices with 61850 Server function. So that a fast switchover between the servers can be performed during redundancy switchover from "PASSIVE ACTIVE", the connection to both 61850-Servers must be established and the 61850-communication must be completely initialized. The 61850-Client has no information about which 61850-Server is "ACTIVE". The transmission of spontaneous data (Reports) is only carried out by the "ACTIVE" 61850-Server. After initialization is complete, the spontaneous transmission of data (Reports) is deactivated by the protocol element of the "PASSIVE" 61850-Server. The switchover of the redundancy state ("ACTIVE" "PASSIVE") takes place system-internal through redundancy control messages. Functions in the redundancy state "PASSIVE": • • • Data in transmit direction continue to be received from the basic system and are entered into the internal process image of the protocol element Spontaneous data and GI-data in transmit direction (Reports) are no longer transmitted by the protocol element Data in receive direction continue to be passed on from the protocol element to the basic system element and identified by this with the "PASSIVE-Bit". Functions during the switchover from the redundancy state "PASSIVE" "ACTIVE": • • The spontaneous transmission of data in transmit direction (Reports) is activated A general interrogation is carried out to the basic system element Limitation: - The cyclic interrogation of attributes must not be used with server redundancy ! (this can lead to inconsistent states in the client) The server redundancy is to be activated in the protocol element of the SICAM 1703 component with 61850-Server function with the parameter IEC61850 | Server | Redundancy for Server. 9-50 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.2.3. GOOSE Redundancy For the support of redundant configurations of SICAM 1703 components with 61850 Server function, special functions are implemented in the protocol element for the GOOSE message transfer during transmission (Publisher), which prevent a possible failure of the GOOSE messages at the receivers (Subscriber) in the connected devices during redundancy switchover. These functions are then required, if the same GOOSE applications are sent in the redundant SICAM 1703 components. For redundant devices with GOOSE Publisher function and the same parameterized GOOSE applications (i.e. same MAC address is used by different devices) always only 1 device may be active at one time. The passive device stops the transmission of GOOSE messages. The special functions for GOOSE redundancy are to be enabled with the parameter IEC61850 | Server | Goose | Redundancy for goose (Publish). The switchover of the redundancy state takes place system-internal through redundancy control messages. Functions during the switchover from the redundancy state "ACTIVE" "PASSIVE": • All GOOSE applications are transmitted again by the server (Publisher) before the switchover with the "HOLDTime in the message = 10 seconds". as a result the failure monitoring time for GOOSE applications is retriggered again in the connected devices before the switchover. Functions in the redundancy state "PASSIVE": • • Transmission of GOOSE messages is stopped. 61850 Server + Client functions continue to be executed. Functions during the switchover from the redundancy state "PASSIVE" "ACTIVE": • After switchover, all GOOSE applications are only transmitted by the "ACTIVE" Server (Publisher) after a delay time of 2 seconds. Hints: - The "State Number" in the GOOSE message (change counter) is not synchronized between the redundant devices. As a result, during redundancy switchover (without change of the data state) a change in connected devices can be detected. - The "State Number" is not evaluated by the SICAM 1703 protocol element! Functions Protocol Elements DC0-023-2.01 9-51 LAN-Communikation (61850) 9.3. Protocol Element Control and Return Information This function is used for the user-specific influencing of the functions of the protocol elements. This function contains two separate independent parts: • • Protocol element control Protocol element return information The Protocol Element Control enables: • Setting control location The Protocol Element Return Information enables: • --- Internal distribution for messages with process information Block Diagram Protocol element control Internal function Transmission route Protocol element return information Protocol element Messages with process information Messages with system information 9-52 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.3.1. Protocol Element Control With the help of messages with process information, the protocol element control on the basic system element enables specific functions of the protocol elements to be controlled. The specific functions are determined by the protocol element implemented. The assignment of the messages with process information to the functions is carried out with the help of processtechnical parameters of the ACP 1703 system data protocol element control message. The messages for protocol control are transmitted immediately from the basic system element to the protocol element, regardless of the user data to be sent and the priority control. For messages with process information which are used in ACP 1703 as protocol element control message, an unused CASDU is to be used! All CASDU´s for process information are distributed automatically to the corresponding remote terminal unit. Possible Client functions: Parameter Function Set control location Legend: SF **) Station Z-Par 125 65535 SCS=<ON>: Set control location (HKA) (global) SCS=<OFF>: Delete all control locations (HKA's) (global) 0 – 99 65535 SCS=<ON>: Set control location (HKA) SCS=<OFF>: Reset control location (HKA) 242 Note SF..............Control function_(PRE) Station .......Station number 0 - 99...... Station 0 - 99 of the selected protocol element 125......... Station 0 - 99 of the selected protocol element (=BROADCAST) Z-Par .........Additional parameter_(PRE) SCS...........single command state HKA...........Originator address (HKA) = 0 – 255 The setting of the control location can only be performed with a single command <TK=45>! In the PRE-control message to the protocol element the additional parameter is set as follows. SCS = <OFF> ...........Additional parameter = HKA+256 SCS = <ON>.............Additional parameter = HKA **) If a PRE-control message is entered in the PST-detailed routing on the BSE, after startup of the PRE the BSE sends a PRE-control message "Set control location" to the PRE. As a result the function for evaluating the control location is activated on the PRE. Functions Protocol Elements DC0-023-2.01 9-53 LAN-Communikation (61850) 9.3.2. Protocol Element Return Information Presently the LAN protocol element does not support any protocol return information messages! 9-54 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.4. Message Conversion Data in control direction are transferred from the basic system element to the protocol element in the SICAM 1703 internal IEC 60870-5-101/104 format (unblocked). These are entered by the protocol element in the internal IEC 61850 data model. The data transmission from this data model takes place according to IEC 61850. Data in monitoring direction are received by the protocol element according to the IEC 61850 transmission procedure and converted by the protocol element to the internal IEC 60870-5-101-/104 format and then passed on to the basic system element. The parameterization of the address conversion from IEC 60870-5-101/104 IEC 61850 address and message format takes place in the Toolbox II with the "SIP Message Address Conversion". The "Mapping" of IEC 61850 attributes to IEC 60870-5-101/104 type identifications takes place through the parameterization of the address conversion. In the SIP message address conversion the following categories are available: Categories: SICAM 1703 Protocol Element with 61850 Client Function firmware / ET03/Client_Rec_IEC61850 firmware / ET03/Client_Trans_IEC61850 firmware / ET03/Fault_record_Rec_IEC61850 firmware / ET03/Fault_record_Trans_IEC61850 Categories: SICAM 1703 Protocol Element with 61850 Server Function firmware / ET03/Server_Rec_IEC61850 firmware / ET03/Server_Trans_IEC61850 firmware / ET03/Server_Rec_Goose_IEC61850 firmware / ET03/Server_Trans_Goose_IEC61850 firmware / ET03/Server_Trans_Defaultwert_IEC61850 Functions Protocol Elements DC0-023-2.01 9-55 LAN-Communikation (61850) When data change, with 61850 all attributes of the same Functional Constraint group are always transmitted. If, for example, the binary information state "stVal" changes from Pos, then the other data attributes of the same Functional Constraint (ST = Status Information) such as e.g. "q" and "t" are also transmitted, even if these have not changed. In receive direction, with a change of state / time / quality, data are converted from 61850 to IEC 60870-5-101/104 and transferred to the basic system element. On reception of data, the following time information is taken for the message conversion: • Time of the ".t" attribute has changed since the last transmission Time of the ".t" attribute is applied • Time of the ".t" attribute has not changed since the last transmission, time of the report is available (=time of the creation of the report in the server) Time of the report is applied • Time of the ".t" attribute has not changed since the last transmission, time of the report is not available (=time of the creation of the report in the server) Current time is applied Note: A general interrogation is always replied to by the protocol element from the internal process image of the protocol element with the last received time. 9-56 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Message Conversion in Control Direction (Client Server) (Client transmit direction, Server receive direction) IEC 60870-5-101/104 2) IEC 61850 Common Data Class [CDC] FC Cs Se <TI=47> Regulating step command <TI=30> <TI=31> Single-point information with time stamp Double-point information with time stamp <TI=45> <TI=46> single command double command <TI=30> <TI=31> Single-point information with time stamp Double-point information with time stamp - <TI=45> Single command - <TI=46> Double command 1) 1) Setpoint command, scaled value Setpoint command, short floating point number <TI=49> <TI=50> 1) 1) Setpoint command, scaled value Setpoint command, short floating point number <TI=30> <TI=31> Single-point information with time stamp Double-point information with time stamp <TI=45> <TI=46> single command double command 1) 1) Binary Controlled Step Position CO DPC Controllable Double Point CO INC <TI=49> <TI=50> <TI=49> <TI=50> BSC ISC SGCB Controllable Integer Status CO Integer Controlled Step Position Setting Group SP Setpoint command, scaled value Setpoint command, short floating point number <TI=30> <TI=31> Single-point information with time stamp Double-point information with time stamp <TI=45> <TI=46> single command double command SPC Controllable Single Point CO 1) for these values no adaptation (scaling) is supported! 2) all with CP56Time2a time stamp Legend: Functions Protocol Elements CO Cs …. Client transmitting Se …. Server receiving FC … Functional Constraint DC0-023-2.01 9-57 LAN-Communikation (61850) Message Conversion in Monitoring Direction (Client Server) (Server transmit direction, Client receive direction) IEC 60870-5-101/104 1) <TI=30> Single-point information with time stamp <TI=31> Double-point Information with time stamp <TI=38> <TI=39> Protection event with time stamp Blocked activation of protection with time stamp Blocked tripping of protection with time stamp <TI=40> <TI=30> <TI=38> <TI=39> <TI=40> <TI=37> FC Ce Ss ACD Directional Protection Activation Information ST Single-point information with time stamp Protection event with time stamp Blocked activation of protection with time stamp Blocked tripping of protection with time stamp ACT Protection Activation Information ST Counts with time stamp BCR Binary Counter Reading ST Step position information with time stamp BSC Binary Controlled Step Position ST <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp CMV Complex Measured Value MX <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp DEL Delta MX <TI=30> <TI=31> Single-point information with time stamp Double-point information with time stamp DPC Controllable Double Point ST <TI=32> 1) - DPL Device Name Plate - <TI=31> Double-point Information with time stamp DPS Double Point Status ST <TI=30> <TI=31> <TI=35> <TI=36> 1) 1) Single-point information with time stamp Double-point information with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp INC Controllable Integer Status ST <TI=30> <TI=31> <TI=35> <TI=36> 1) 1) Single-point information with time stamp Double-point information with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp INS Integer Status ST <TI=32> 1) Step position information with time stamp ISC Integer Controlled Step Position ST - LPL Logical Node Name Plate - MV Measured Value - <TI=34> <TI=35> <TI=36> 9-58 IEC 61850 Common Data Class [CDC] Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp DC0-023-2.01 Functions Protocol Elements MX LAN-Communikation (61850) <TI=34> <TI=35> <TI=36> Functions Protocol Elements Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp DC0-023-2.01 SAV Sampled Value MX 9-59 LAN-Communikation (61850) Message Conversion in Monitoring Direction (Client Server) "continued” (Server transmit direction, Client receive direction) IEC 60870-5-101/104 1) IEC 61850 Common Data Class [CDC] SEQ FC Ce Ss Sequences MX Setting Group SP <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp <TI=30> <TI=31> <TI=35> <TI=36> Single-point information with time stamp Double-point information with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp SGCB <TI=30> <TI=31> Single-point information with time stamp Double-point information with time stamp SPC Controllable Single Point ST <TI=30> Single-point information with time stamp SPS Single Point Status ST <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp WYE Collections Of Measurands MX 1) 1) 1) for these values no adaptation (scaling) is supported! 2) all with CP56Time2a time stamp Legend: 9-60 Ss …. Server transmitting Ce ... Client receiving FC … Functional Constraint DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Message Conversion GOOSE (Server Server) (Server transmit direction, Server receive direction) IEC 60870-5-101/104 2) IEC 61850 Common Data Class [CDC] FC Ss Se Single-point information with time stamp Protection event with time stamp Blocked activation of protection with time stamp Blocked tripping of protection with time stamp ACD Directional Protection Activation Information ST Single-point information with time stamp Protection event with time stamp Blocked activation of protection with time stamp Blocked tripping of protection with time stamp ACT Protection Activation Information ST <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp CMV Complex Measured Value MX <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp DEL Delta MX <TI=30> <TI=31> Single-point information with time stamp Double-point information with time stamp DPC Controllable Double Point ST <TI=31> Double-point Information with time stamp DPS Double Point Status ST <TI=30> <TI=31> <TI=35> <TI=36> INC Controllable Integer Status ST - 1) 1) Single-point information with time stamp Double-point information with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp INS Integer Status ST - 1) 1) Single-point information with time stamp Double-point information with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp MV Measured Value ST <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp SAV Sampled Value ST <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp SEQ Sequences ST <TI=30> <TI=38> <TI=39> <TI=40> <TI=30> <TI=38> <TI=39> <TI=40> <TI=30> <TI=31> <TI=35> <TI=36> Functions Protocol Elements DC0-023-2.01 9-61 LAN-Communikation (61850) 9-62 <TI=30> <TI=31> Single-point information with time stamp Double-point information with time stamp SPC Controllable Single Point ST <TI=30> Single-point information with time stamp SPS Single Point Status ST DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Message Conversion GOOSE (Server Server) “continued” (Server transmit direction, Server receive direction) IEC 60870-5-101/104 2) <TI=34> <TI=35> <TI=36> Measured value, normalized value with time stamp Measured value, scaled value with time stamp Measured value, short floating point number with time stamp IEC 61850 Common Data Class [CDC] WYE Collections Of Measurands 1) for these values no adaptation (scaling) is supported! 2) all with CP56Time2a time stamp Legend: Functions Protocol Elements Ss …. Server transmitting Se .. . Server receiving FC … Functional Constraint DC0-023-2.01 9-63 FC Ss Se ST LAN-Communikation (61850) 9.4.1. Special Functions For the coupling of devices with the IEC 61850 protocol, if necessary the following special functions can be activated for the adaptation of the message conversion: • • • • • • • • • Conversion of the time information Signaling / measured value disabling Emulation of the going binary information Emulation of the data on reception of the attribute Beh.stVal="OFF" Technological adaptation for measured values Measured value change monitoring Monitoring intermediate and faulty positions of double-point information Logging of the remote commands at the local control centre Remote parameterization/diagnostic of SICAM 1703 components via 61850 9.4.1.1. Conversion of the Time Information As time format, as standard IEC 61850 defines the UTC-Format (Universal Time Coordinated = "coordinated universal time"). For the message conversion, the SICAM 1703 internal time format can be determined with the parameter advanced parameters | time format in transmit direction and with the parameter advanced parameters | time format in receive direction. Possible time formats: 9-64 IEC 61850 Time Format (on the line) IEC 60870-5-101/104 Time Format (SICAM 1703 internal) UTC (Universal Time Coordinated) Local time with daylight-saving / normal time UTC (Universal Time Coordinated) Local time with normal time (winter time) UTC (Universal Time Coordinated) UTC (Universal Time Coordinated) Local time Local time DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.4.1.2. Signaling / Measured Value Disabling [Client only] The signaling / measured value disabling is a function of the protection equipment and can be activated globally (for binary information and measured values together) for example by means of a keylock switch or by means of a control input in the protection equipment. Through the signaling / measured value disabling function the spontaneous transmission (Reporting) is deactivated. With activation/deactivation of the signaling / measured value disabling, for each logical device the binary information "Behavior" is transmitted spontaneously to the client. The signaling / measured value disabling is transmitted as last signal with activation and as first signal with deactivation. So that the functions for the emulation of the data can be executed by the protocol element with signaling / measured value disabling, the attribute "Beh.stVal" for signaling / measured value disabling of the affected logical node or the logical node LLN0 must be entered in the SIP message address conversion in receive direction. The protocol element evaluates the attribute of the respective logical node with higher priority than the attribute of the logical node LLN0. If only the attribute "Beh.stVal" of the logical node LLN0 is entered, on reception of the attribute "Beh.stVal = BLOCKED" the data of all affected logical nodes is emulated. If the attribute "Beh.stVal" of a selective logical node is entered, on reception of the attribute "Beh.stVal = BLOCKED" only the data of the selective logical node is emulated. The emulation of the data concerned (with activation of the signaling / measured value disabling) by the protocol element with 61850 Server function to the internal IEC 60870-5-101/104 format can be selected with the parameter IEC61850 | Client | advanced parameters | behavior of Beh.stVal=5 (OFF). Possible emulation of the data with Beh.stVal = BLOCKED: • • No emulation Emulation of the data with "BL=1" (blocked) On deactivation of the signaling / measured value disabling, in the following cases all data concerned are read out again by the SICAM 1703 protocol element with 61850 Server function from the 61850 clients and the data transferred spontaneously: • • • Change of the attribute Beh.StVal from "BLOCKED" "ON" Change of the attribute Beh.StVal from "BLOCKED" "TEST" Change of the attribute Beh.StVal from "BLOCKED" "TEST-BLOCKED" Hints: - In the SICAM 1703 protocol element with 61850 Server function, no special functionality is implemented for the signaling / measured value disabling! - For counts that are transmitted as measured values, no emulation is performed! - With signaling / measured value disabling activated, also no (possible) parameterized cyclic interrogation of the data points concerned is performed. - SICAM 1703 internal, on activation of the signaling / measured value disabling, all signals/measured values are generated with the status "spontaneous + blocked" and transmitted via 61850 to the client. On deactivation of the signaling / measured value disabling, all signals/measured values are transmitted spontaneously with the status "spontaneous". Functions Protocol Elements DC0-023-2.01 9-65 LAN-Communikation (61850) 9.4.1.3. Emulation of the Going Binary Information [Client only] With IEC 61850, protection signals are only transmitted with the state "ON" (coming). For IEC 60870-5-101/104, the "coming/going state" is always required for every signal. The protocol element with 61850 Client function can emulate the "Going Signal" automatically for selected signals in receive direction. The "Going Signal" is fixed emulated with the time of the coming signal + 1 millisecond. The emulation of the going signal can be parameterized in the SIP message address conversion in receive direction in the category firmware / ET03/Client_Rec_IEC61850 for each signal in the field Meldungsart. 9.4.1.4. Emulation of the Data on Reception of the Attribute Beh.stVal="OFF" [Client only] On reception of the attribute "Beh.stVal" with the state "OFF" for a selective logical node or the logical node LLN0 (per logical device), the emulation of the data concerned by the protocol element with 61850 Server function to the internal IEC 60870-5-101/104 format can be selected with the parameter IEC61850 | Client | advanced parameters | behavior of Beh.stVal=5 (OFF). Possible emulation of the data with Beh.stVal = OFF: • • • No emulation Emulation of the data with "NT=1" (not topical) Emulation of the data with "IV=1" (invalid) So that the functions for the emulation of the data can be performed by the protocol element, the attribute "Beh.stVal" must be entered in the SIP message address conversion in receive direction. The protocol element evaluates the attribute of the respective logical node with higher priority than the attribute of the logical node LLN0. If only the attribute "Beh.stVal" of the logical node LLN0 is entered, on reception of the attribute "Beh.stVal = OFF" the data of all affected logical nodes is emulated. If the attribute "Beh.stVal" of a selective logical node is entered, on reception of the attribute "Beh.stVal = OFF" only the data of the selective logical node is emulated. Note: For counts that are transmitted as measured values, no emulation is performed! On reception of the attribute Behavior (Beh.stVal) with the state <> "OFF", in the following cases all affected data points are read out again by the SICAM 1703 protocol element with 61850 Server function from the 61850 clients and the data transferred spontaneously: • • • 9-66 Change of the attribute Beh.StVal from "OFF" "ON" Change of the attribute Beh.StVal from "OFF" "TEST" Change of the attribute Beh.StVal from "OFF" "TEST-BLOCKED" DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.4.1.5. Technological Adaptation for Measured Values The technological adaptation enables the measured value supplied by the connected devices to be transformed into a technological or normalized value. Into which value conversion can take place, is dependent on the format of the spontaneous information object to be transferred. Type Identification (IEC 60870-5-104) Spontaneous Information Object Value Range -15 - 1 ... + 1-2 <TI:=34> Measured value, normalized value <TI:=35> Measured value, scaled value - 32768 ... + 32767 <TI:=36> Measured value, short floating point - 8,43 * 10-37 ... + 3,37 * 1038 Meaning normalized, percental representation technological, integer technological, floating point The parameters for the technological adaptation are parameterized for each measured value as • adaptation line with 2 interpolation points (X_0%, X_100%, Y_0%, Y_100%) . The received measured value is adapted linear according to the parameter setting by the protocol element before transfer to the basic system element. The adaptation line with 2 interpolation points is to be parameterized for each measured value with the parameters Measured value adaptation_X_0% , Measured value adaptation_X_100% , Measured value adaptation_Y_0% and Measured value adaptation_Y_100%. For this, the technological value Y0 is parameterized for the lower limit of the measuring range X0 and the technological value Y100 for the upper limit of the measuring range X100. Functions Protocol Elements DC0-023-2.01 9-67 LAN-Communikation (61850) Bipolar measured values without zero-range suppression and plausibility check Example: Value Meaning Parameter X0 -2000 lower boundary of the measuring range (set by parameter) Measured value adaptation_X_0% X100 +2000 upper boundary of the measuring range (set by parameter) Measured value adaptation_X_100% Y0 -1 technological value at X0 Measured value adaptation_Y_0% Y100 +1 technological value at X100 Measured value adaptation_Y_100% Y100 X0 Normalized value X100 Y0 Data point quality descriptor IV OV 0 9-68 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.4.1.6. Measured Value Change Monitoring Measured values are transmitted from some protection equipment with the smallest changes in measured value or even cyclic. So as not to load the following transmission facilities unnecessarily, the measured value is monitored for change in accordance with the following rules: • The first value received after startup is transmitted immediately • Every change of the quality descriptors blocked, invalid or overflow triggers an immediate transmission • Change monitoring in accordance with the method of the additive threshold value procedure Additive threshold value procedure In the parameterized processing grid the measured value is monitored for change. If the deviation from the last spontaneously transmitted measured value is greater than the parameter-settable thresh_uncond, the new measured value is transmitted immediately. Otherwise, in the parameterized processing grid the deviations from the last spontaneously transmitted measured value are totalled according to the polarity sign. Only when the amount of this total exceeds the parameter-settable thresh_additive is the current measured value spontaneously transmitted. A transmission of the measured value due to a general interrogation does not influence the threshold value procedure. By means of parameterization it is established: ─ Processing grid ─ Thresh_Uncond ─ Thresh_Additive 0.1s - 25.5s -37 38 - 8.43 * 10 … + 3.37 * 10 -37 38 - 8.43 * 10 … + 3.37 * 10 The values for the parameters thresh_additive and thresh_uncond are absolute values and always refer to the received non-linearized value. The processing grid is parameterized for all measured values together with the parameter IEC61850 | Grid for measurands change monitoring. The thresholds are to be parameterized for every measured value with the parameter thresh_additive and the parameter Schwelle_unbedingt. Functions Protocol Elements DC0-023-2.01 9-69 LAN-Communikation (61850) The following example describes a standard case, in which the adaptation line goes through the zero point (origin) (Yat X=0 = 0). Examples Technological value Y100 Processing grid Thresh_uncond Thresh_additive Example 1: (represents a change of the received value by 80) (represents an additive sum of 6000) After transmission due to the exceeding of the large threshold, the value has changed once by 79 (< the large threshold) and subsequently remains constant. The measured value is transmitted after 7.5 seconds. 0.0s 0.1s 0.2s 0.3s 0.4s 0.5s 0.6s 0.7s 0.8s ... 7.4s 7.5s Measured value 300 379 379 379 379 379 379 379 379 ... 379 379 Difference >80 79 79 79 79 79 79 79 79 ... 79 79 Additive total 0 79 158 237 316 395 474 553 632 ... 5925 6004 Transmission x Example 2: x After transmission due to the exceeding of the large threshold, the value has changed once by 1 (< the large threshold) and subsequently remains constant. The measured value is transmitted after 10 minutes. 0.0s 0.1s 0.2s 0.3s 0.4s 0.5s 0.6s 0.7s 0.8s ... 599.9 600s Measured value 300 301 301 301 301 301 301 301 301 ... 301 301 Difference >80 1 1 1 1 1 1 1 1 ... 1 1 Additive total 0 1 2 3 4 5 6 7 8 ... 5999 6000 Transmission x Example 3: 9-70 4000 0.1s 80.00 6000.00 x After transmission due to the exceeding of the large threshold, the value continually changes by ±1. The measured value is not transmitted. 0.0s 0.1s 0.2s 0.3s 0.4s 0.5s 0.6s 0.7s 0.8s ... 7.4s 7.5s Measured value 300 301 300 299 300 301 300 301 299 ... 300 301 Difference >80 1 0 -1 0 1 0 1 -1 ... 0 1 Additive total 0 1 0 1 0 1 0 1 1 ... 0 1 Transmission x DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.4.1.7. Monitoring Intermediate and Faulty Positions of Double-Point Information [Client only] Double-point information that are transmitted from the connected 61850 devices, or single-point information that are transmitted from the connected 61850 devices and converted to double-point information on the protocol element, can be monitored by the protocol element for intermediate and faulty position. (in most cases protection equipment do not have any monitoring for intermediate and faulty position implemented) Thereby, the transfer of an intermediate position (neither ON- nor OFF binary information exists) or a faulty position (both ON- as well as OFF binary information exists) is suppressed by the protocol element for a parameter-settable time. On reception of a double-point information with intermediate or faulty position, a monitoring time is started and the double-point information is not transferred. If during the monitoring time the double-point information is received with valid binary information state (ON or OFF), the monitoring time is stopped and the double-point information is transferred with the valid binary information state. On expiry of the monitoring time, the double-point information with the state "intermediate or faulty position" is transferred with the received time. The assignment of the message address for the spontaneous information object "Double-point information" is carried out in the OPM II with the category SIP-Telegrammadressumrechnung /... / firmware / .... For the suppression of the intermediate and faulty position, a suppression time for intermediate position and a suppression time for faulty position is to be parameterized for all double-point information together. The suppression time for intermediate position is to be parameterized with the parameter IEC61850 | Client | intermediate position suppression time. The suppression time for faulty position is to be parameterized with the parameter IEC61850 | Client | faulty position suppression time. Functions Protocol Elements DC0-023-2.01 9-71 LAN-Communikation (61850) 9.4.1.8. Logging of the Remote Commands at the Local Control Centre [Server only] For documentation or traceability, a logging of operator inputs to an existing local control centre is often required. So that remote commands can be logged at a local control centre connected in the 61850 network, the remote commands must also be sent to the local control centre. However with IEC 61850, due to the Server/Client communication this is not possible without additional measures! For configurations with SICAM 1703 components as 61850-Client and the control centre system SICAM 230 as local control centre, the logging of remote commands via IEC 61850 is possible by means of a proprietary (noncompatible) procedure, if an unambiguously assigned return information is available for every remote command (assignment: ctlVal stVal). With function activated, the protocol element with 61850 Server function sends the return information to the control point and to the local control centre with the information required for the logging in the attribute "orIdent" (Originator Identification). The following items of information are entered in the attribute "orIdent" as ASCII-Text (max. 64 characters): • • • • • • • IP Address Region number Component number Cause of transmission Positive/Negative identifier Data (On/Off, Lower/Higher,…) Originator address The function can be activated with the parameter IEC61850 | Server | advanced parameters | log remote commands on local SCADA system. 9.4.1.9. Remote Parameterization/Diagnostic of SICAM 1703 Components via 61850 If SICAM 1703 components are used as 61850-Client and as 61850-Server, then a remote parameterization/diagnostic of the SICAM 1703 components can be performed over the LAN connection and the 61850 protocol element. The remote parameterization/diagnostic is activated automatically by the 61850 protocol element, as soon as the connection is established and a SICAM 1703 component with 61850 protocol element has been detected as remote station. For this a proprietary procedure is implemented over the TCP/IP connection of the LAN-link, which can only be used between SICAM 1703 components and is not defined in IEC 61850 or IEC 60870-5-104 respectively. The automatic detection/activation and the transmission of all messages required for the remote parameterization/diagnostic takes place over TCP/IP with messages defined especially for this purpose. 9-72 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.5. WEB Server A WEB server is integrated into the protocol firmware for internal diagnostic information. This information can be read out comfortably with a common WEB Browser (e.g. Microsoft Internet Explorer). For the access to the WEB server the communications protocol "HTTP (Hyper Text Transfer Protocol)" is used with the port number 80. The integrated WEB server is addressed by means of direct specification of the IP address of the ethernet interface of the automation unit. Via the integrated WEB server the following information can be read out: • General information (IP address, default gateway, subnet mask) • Diagnostic information ("Diagnosis") - Triggering a Ping command ("Send Ping") - Display of the connection information ("Connections") - Display of the "Detail Routing Parameters" for the server function in transmit direction ("Detail rout. Server TRA") - Display of the "Detail Routing Parameters" for the server function in receive direction ("Detail rout. Server REC") - Display of the "Detail Routing Parameters" for the client function in transmit direction ("Detail rout. Client TRA") - Display of the "Detail Routing Parameters" for the client function in receive direction ("Detail rout. Client REC") - Display of the control locations with command authority ("Control location") - Display of the directories in SICAM 1703 components with server function ("Directories Server") • Display of system-internal data for development specialists ("Developer Information") - Display memory content ("Stack | Task Stack", "Memory | Heap, Read Memory, Read Register") Note: The values displayed on the WEB pages indicate the current status when the WEB page is started. The values of a WEB page are not updated automatically! An updating of the WEB page displayed in Internet Explorer can be performed e.g. by means of the Internet Explorer function (Update or Refresh). Functions Protocol Elements DC0-023-2.01 9-73 LAN-Communikation (61850) General Information On the Start page of the WEB Server, general information about the protocol element and the network-specific settings are displayed. General Information: • Reg#, Comp#, BSE#, SSE#, IP Address, Subnet Mask, Default Router, Actual Link, Speed, Duplex The parameterized or current values are displayed next to the respective fields. • "IED Name" [Server only] The displayed "IED Name" (= Intelligent Electronical Device Name or Physical Device Name) is parameterized with the parameter IEC61850 Server | IED Name. This IED Name is not however used by the protocol firmware. The IED Name required for IEC 61850 is only taken by the protocol element from the data of the SIP message address conversion in transmit/receive direction. • "Firmware" The status of the firmware is displayed next to the field "Firmware". OK ……………………..…… Firmware running error-free KILL, No: #### (0x####)…. A serious error has occurred notify manufacturer! The number displayed (decimal, and HEX) supply the developer with more specific information about the cause of the error. • "Redundancy" The current redundancy state of the protocol element is displayed next to the field "Redundancy". Firmware active ……..…… Firmware passive …..…… 9-74 The redundancy state of the protocol element is "ACTIVE" The redundancy state of the protocol element is "PASSIVE" DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) • "LLN0.configRev" The current revision of the SICAM 1703 internal IEC 61850 specific parameters is displayed here. This revision can parameterized either with the parameter IEC61850 | Server | advanced parameters | LLN0.configRev or with corresponding setting of the parameter IEC61850 | Server | advanced parameters | LLN0.configRev setting the parameter revision generated automatically by the Toolbox II is displayed for the relevant parameter blocks. Note: The "configRev" is the unambiguous identifier of the parameter status of a 61850 device and for SICAM 1703 components is listed for each Physical Device. Attention: 61850 devices of some manufacturers check that revision of the parameter status (ConfigRev) imported from the ICD-File for connected 61850 devices with that parameter status used in the connected 61850 device (ConfigRev is read out and compared). 81850 devices of some manufacturers terminate the complete function if the ConfigRev no longer corresponds! Note: The SICAM 1703 protocol element for 61850 does not terminate the function with different ConfigRev's – correctly parameterized data are converted, the remaining data are not converted. Functions Protocol Elements DC0-023-2.01 9-75 LAN-Communikation (61850) Triggering a Ping command ("Send Ping") On the WEB page Diagnosis | Send Ping a PING command can be transmitted from the LAN protocol element to the remote station. This function can be used by the user in order to be able to check the reachability of a connected 61850 remote station. The advantage of this function is that the PING command is really transmitted from the protocol element, thus from the source. The results of the PING command are displayed in a separate window. 9-76 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Connection Information ("Connections") On the WEB page Diagnosis | Connections the status information of the parameterized connections is displayed. Connection-specific status information: • "Station" (SICAM 1703 internal station number) The station number is used SICAM 1703 internal for the routing of the data, diagnostic treatment and failure management. The station number is the SICAM 1703 internal reference for that connection to which an IP address is assigned. • "IP Address" The field "IP Address" displays the IP address of the remote station parameterized in the parameters for Connection definition. An IP address marked red signifies that this is presently not reachable. By clicking the mouse button on the IP address, via a link the WEB page of a WEB server possibly implemented in the remote station is displayed. • "Dir Ind." [Server only] The field "Dir Ind." (Directory Index) is only used for SICAM 1703 components with 61850-Server function and is an unambiguous index number for a directory created in the server (data model). The "Dir Ind" is unambiguous within a device. By clicking the mouse button on the registered "Dir Ind." of a station, the assigned data model of the 61850Station (remote station) is displayed. • "Dir ID" [Server only] The field "Dir ID" (Directory ID) is only used for SICAM 1703 components with 61850-Server function and is an unambiguous identification number for a directory created in the server (data model). The "Dir ID" is unambiguous within a device. By clicking the mouse button on the registered "Dir ID" of a station, the assigned data model of the 61850Station (remote station) is displayed. • "TCP Conn." [Client only] The field "TCP Conn." (TCP connection) indicates the status of the connected at TCP level. (OK … Connected established at TCP level) Functions Protocol Elements DC0-023-2.01 9-77 LAN-Communikation (61850) 9-78 • "MMS Conn." [Client only] Indicates the status of the connection at MMS level. (OK … Connection is established at TCP level and MMS level, datasets are created and spontaneous transmission is possible) • "Data" [Client only] The field "Data" is OK if all 61850-Data (transmit/receive direction) parameterized in the SIP message address conversion also exist in the remote station. • "ET03 is" This field displays the set parameters Connection definition | own mode as the role of the own station for every connection. • "Server (Vendor/Model/Version)" [Client only] This field displays the manufacturer information of the connected 61850 device (Server) read out by the Client. • "Req. Dir. (NV)" (Request Directory Named Variables) [Client only] By clicking the mouse button on the link "Request’ registered in the field "Req. Dir. (NV)", the Directory (data model) of all "Named Variables" is read out and displayed. • "File Dir." [Client only] By clicking the mouse button on the link "Request" registered in the field "File Dir.", the File Directory is read out and displayed. Displayed are e.g. files of recorded disturbance records in IEEE Comtrade format. DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Named Variables Directory of the Station [Client only] Via the WEB page Diagnosis | Connections | Req. Dir. (NV) of the 61850-Client, the Named Variables Directory of the 61850 remote station (Server) can be read out and displayed. The NV Directory contains the following information: • "Domains (Logical Devices)" Listing of all Logical Devices of the 61850-Station. e.g. CTRL …Control, DR …Disturbance Recording, EXT … Extras, MEAS … Measured Value Acquisition, PROT … Protection. • NVL (Datasets) Listing of the NVL (Named Variable Lists) per Logical Device. • NV Data Listing of all NV (Named Variables) per Logical Device. The current states of the data attributes of the Named Variables ("Data Attribute Reference") can be read out directly from the 61850 remote station (Server) with "Read" via the WEB page in the 61850 Client. The readout is only supported for basic types! (the readout of higher-level structures "Data References" is not supported) With an attempt to read out a higher-level structure, the error message "structure. please use a single leaf" is displayed! Functions Protocol Elements DC0-023-2.01 9-79 LAN-Communikation (61850) The current state of the selected data attribute is displayed in the window (below). Through the readout, data in the 61850 device cannot be deleted unintentionally. File Directory of the Station [Client only] On the WEB page Diagnosis | Connections | File Dir. the File Directory of the 61850 remote station (Server) can be displayed in the 61850-Client. A file can be displayed by clicking the left mouse button on the link stored in the filename or saved on the local PC by clicking the right mouse button and selecting the function "Save file as…". The readout and saving of the file is controlled by the protocol firmware. The files read out via the WEB server are not deleted in the 61850 remote station. 9-80 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Detail Routing Client TRA [Client only] Detail Routing Client REC [Client only] The address conversion from SICAM 1703 internal IEC 60870-5-101/104 format to the IEC 61850 format in transmit direction and the address conversion from IEC 61850 format to the SICAM 1703 internal IEC 60870-5101/104 format in receive direction is parameterized with the Toolbox-II in the OPM and generated with the function SIP message address conversion. On the WEB page Diagnosis | Detail Routing Client TRA all routing information generated for the protocol element in transmit direction are displayed. Functions Protocol Elements DC0-023-2.01 9-81 LAN-Communikation (61850) On the WEB page Diagnosis | Detail Routing Client REC all routing information converted for the protocol element in receive direction are displayed. A separate line is created in the routing information for every IEC 60870-5-101/104 data point. Routing entries with incorrect parameter setting are indicated with the color red. (e.g. wrong type identification,…) Routing entries with data points that do not exist in the server are indicated with the color blue. With incorrect IEC 61850 address an error message is displayed in the field "Error". The 61850 address is checked by the protocol firmware after startup for all routing information from the designation "Logical Node" on. 9-82 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Connection-specific status information: • "Type" SICAM 1703 internal defined/unambiguous number for the detailed routing record type. • "TI, CASDU1, CASDU2, IOA1, IOA2, IOA3" 5-stage address and type identification according to IEC 60870-5-101/104. • "Station" (SICAM 1703 internal station number) The station number is used SICAM 1703 internal for the routing of the data, diagnostic treatment and failure management. The station number is the SICAM 1703 internal reference for that connection to which an IP address is assigned. • "Value" • "Ctrltype" [Client only] In this field, the Control Type (Ctrltype) for the data point read out from the 61850 Server is displayed. The possible Control Types are also displayed on the WEB page. • "Internal" In the field "Internal" an internal status information is displayed for every data point. The internal status information is formed from individual internal binary states and displayed as a number. The following status numbers are of significance for the user: 01 … Data point exists in directory / no spontaneous transmission (is interrogated cyclic) 05 … Data point exists in directory / spontaneous transmission 09 … Data point exists in directory / spontaneous transmission • "IM" In the field "IM" (Interlocking Messaging) the current state of the command enabling for this data point is displayed. The command enabling can be controlled by binary information and is used for "overlapping command interlocks". • "Attrib" In the field "Attrib", internal information is displayed which is only of significance for the software development experts. • "IEC61850 Address" In this field the parameterized IEC 61850 address of the data point is displayed. A basic type ("Data Attribute Reference") must always be specified as IEC 61850 address. • "Error" In the field "Error" an error information is displayed for incorrectly parameterized IEC 61850 address. • "Data" In this field the current status of the IEC 60870-5-101/104 data point including the quality bits and the time information is displayed. Functions Protocol Elements DC0-023-2.01 9-83 LAN-Communikation (61850) Detail Routing Server TRA [Server only] Detail Routing Server REC [Server only] The address conversion from SICAM 1703 internal IEC 60870-5-101/104 format to the IEC 61850 format in transmit direction and the address conversion from IEC 61850 format to the SICAM 1703 internal IEC 60870-5101/104 format in receive direction is parameterized with the Toolbox-II in the OPM and generated with the function SIP message address conversion. On the WEB page Diagnosis | Detail Routing Server TRA all routing information converted for the protocol element in transmit direction are displayed. On the WEB page Diagnosis | Detail Routing Server REC all routing information converted for the protocol element in receive direction are displayed. A separate line is created in the routing information for every IEC 60870-5-101/104 data point. Routing entries with incorrect parameter setting are indicated with the color red. (e.g. wrong type identification,…) Routing entries with data points that do not exist in the server are indicated with the color blue. With incorrect IEC 61850 address an error message is displayed in the field "Error". The 61850 address is checked by the protocol firmware after startup for all routing information from the designation "Logical Node" on. 9-84 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Connection-specific status information: • "Type" SICAM 1703 internal defined/unambiguous number for the detailed routing record type. • "TI, CASDU1, CASDU2, IOA1, IOA2, IOA3" 5-stage address and type identification according to IEC 60870-5-101/104. • "Sel." (Station-selective/Global) In the field "Sel." (selective) it is displayed whether the routing of the data point is applicable for selected selective stations (Connections) or globally for all connections with server function. (Sel: 0=global / 1=selective). With selective assignment, up to 10 different station numbers can be specified for each data point. • "SA", "SB", "SC", "SD", "SE", "SF" "SG", "SH", "SI", "SJ" (SICAM 1703 internal station number) In the fields "SA", .. "SJ" for each data point the selected station numbers (connections) are displayed to which the data point has been assigned. The station number is used SICAM 1703 internal for the routing of the data, diagnostic treatment and failure management. The station number is the SICAM 1703 internal reference for that connection to which an IP address is assigned. • "IEC61850 Address" In this field the parameterized IEC 61850 address of the data point is displayed. A basic type ("Data Attribute Reference") must always be specified as IEC 61850 address. • "Error" In the field "Error" an error information is displayed for incorrectly parameterized IEC 61850 address. • "Data" In this field the current status of the IEC 60870-5-101/104 data point is displayed. Functions Protocol Elements DC0-023-2.01 9-85 LAN-Communikation (61850) Control Location [Client only] On this WEB page the control locations set for the client are displayed. If the function "control location" is activated, commands from the protocol element with the “Client” function are only then transmitted to the addressed station (61850 remote station) if the command has been sent from an enabled control location (originator address). The control location can be set globally for all connections or selectively per connection by means of protocol control messages. The control location (originator address) is a definition according to IEC 60870-5-101/104 and is supported by the protocol element. (for details about the function "Control Location" refer to chapter "Command Transmission / Control Location". 9-86 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Directories Server [Server only] On this WEB page the directories created in the server are displayed. The directories for the 61850 Server are generated by the protocol element from the process-technical parameters (=SIP message address conversion) for the 61850 interface. The time required by the protocol element for the generation and checking of the directories is displayed on the WEB page in the field "Time to check/create Directory (mm:ss)“. The measurement of the time begins after startup of the protocol element. The data in the directories can be displayed in the following ways: • "Plain Directories" In this directory all data are displayed in sorted order. • "Hierarchical Directories" In this directory all data are displayed in "Hierarchically" structured form. Directory-specific Information: • "Directory Index" The field "Directory Index" is only displayed for SICAM 1703 components with 61850-Server function and is an index number to a directory created in the server (data model). Index numbers with the same value point to the same directory. By clicking the mouse button on the registered "Directory Index" the data model of the selected directories is displayed. • "Directory ID" The field "Directory ID" (directory identification number) is only displayed for SICAM 1703 components with 61850-Server function and is an unambiguous identification number for a directory created in the server (data model). The "Directory ID" is unambiguous within a device. By clicking the mouse button on the registered "Directory ID", the assigned data model of the 61850-Station (remote station) is displayed. • "Directory Info" The field "Directory Info" (Directory Information) is only displayed for SICAM 1703 components with 61850Server function. By clicking the mouse button on "Show" in the field "Directory Info", detailed information of the 61850 server is displayed for the generated data model of the selected directories. Functions Protocol Elements DC0-023-2.01 9-87 LAN-Communikation (61850) 9-88 • "Station" The field "Station" displays all internal station numbers (connection numbers) which use this directory. Note: If several remote stations use exactly the same data model (in transmit and in receive direction), internally only 1 directory is created for this by the protocol element. • "Error" During the generation of the directories, the protocol element performs extensive checks. In the field "Error", an error information is entered for fatal errors (e.g. no memory available). Here "Success" must always be entered – otherwise the protocol element does not run! In the event of an error, the parameters of the plant must be transferred to the protocol experts for analysis. DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Directory Server "Plain" [Server only] On this WEB page the selected directory of the server is displayed in "Plain Format". In Plain Format, the data are displayed in alphabetical order. Directory-specific Information: • "Named Variable Lists (NVL)" In the list "Named Variable Lists (NVL)" all datasets generated for the selected server directory are displayed. Datasets are only created for those data, that are to be transmitted from one 61850 Server to one 61850 Client. For data in the direction 61850-Server 61850-Client, no data sets are created. • "Named Variables (NV)" In the list "Named Variables (NV)" all attributes of the entire directories are displayed. The directory (=MMS Directory) contains the assigned datasets (data from Server Client) and all data from Client Server. Functions Protocol Elements DC0-023-2.01 9-89 LAN-Communikation (61850) Directory Server "Hierarchical" [Server only] On this WEB page, the selected server directory is displayed in "Hierarchically" structured form. 9-90 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) Directory Information [Server only] On this WEB page, detailed information of the data model generated for the selected directory of the 61850 server are displayed. The data model is generated during startup by the protocol element from the process-technical parameters (SIP message address conversion). The data model forms the directory (=MMS Directory) for the communication according to IEC 61850. The following information is displayed: • • • • Number of logical devices created - Count Domains (Logical Devices) Number of logical nodes created - Count Logical Nodes Number of NVL's created – Count Named Variable Lists (Datasets) Number of attributes created – Count Named Variables (Attributes) The following information is displayed for each "Logical Device": • "Index" The field displays only a consecutive number that is assigned by the protocol element for the parameterized logical devices and is of no further significance. • "Domain (LD)" In the field "Domain (LD)" (Domain Logical Device) the logical devices created in the server directory are displayed. • "CntLN" In the field "CntLN" (Count Logical Nodes) the number of logical nodes generated per logical device is displayed. • "Cnt NVL (Datasets)" In the field "Cnt NVL (Datasets)" (Count Named Variable Lists) the number of "Named Variable Lists (Dataset)" generated per logical device is displayed. • "Cnt Attrib" In the field "Cnt Attrib" (Count Attributes) the number of attributes generated per logical device is displayed. Functions Protocol Elements DC0-023-2.01 9-91 LAN-Communikation (61850) GOOSE [Server only] On this WEB page, detail information of the GOOSE-Header information are displayed. The datasets for the GOOSE applications are generated from the process-technical parameters (SIP message address conversion) during startup. The sum of the transmitted/received GOOSE applications from startup of the protocol element are displayed on the WEB page. The following information is displayed for each GOOSE application: • "Index" The field "Index" displays the parameterized number for the respective GOOSE application. This index is only required for the SICAM 1703 protocol element and is not transmitted. • "Error" In the field "Error" a detailed error information is displayed for each Goose application (since startup of the own device). Possible error information: Blank field ………… OK Timeout …………….. GOOSE application has already been received once, but presently this is no longer received Data Set Wrong …… The structure of the dataset received for the GOOSE application does not correspond with the parameter setting in the own device Never Received …… The dataset for the parameterized GOOSE application has never been received • 9-92 "Dir" In the field "Dir" (Direction) the transmission direction of the respective GOOSE application is displayed. REC = Subscriber (receiver) TRA = Publisher (transmitter) DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) • "GoCBRef" In the field "GoCBref" the GOOSE Control Block Reference is displayed. This is unambiguous in the device and the network. • "goID" In the field "goID" an unambiguous GOOSE identification reference is displayed. This identifier is unambiguous for each device and for each network and is also transmitted with GOOSE. • "dsRef" A specific dataset is created in the SICAM 1703 server for every GOOSE application. In the field "dsRef" the Dataset Reference per device is displayed. • "MAC Goose" In the field "MAC Goose" (MAC address) the parameterized MAC address of the GOOSE application is displayed. The MAC address is a "UNICAST MAC address" – several different remote stations can receive data from one MAC address. • "MAC Source" In the field "MAC Source" (MAC address) the unambiguous MAC address of that device which has transmitted the GOOSE application is displayed. Note: If due to an incorrect parameter setting, an unambiguous GOOSE application is to be transmitted from several devices (e.g. through the copying of parameters), the MAC addresses of the devices are displayed alternating in the field "MAC Source". • "configRev" In the field "configRev" an unambiguous revision identifier of the GOOSE application is entered. Note: The revision identifier is generally not used presently and by default is assigned with "1" ! • "VLAN_VID" In the field "VLAN_VID" the parameterized VLAN identification is displayed. • "VLAN_Prio" In the field "VLAN-Prio" the parameterized VLAN priority is displayed. • "Cnt TRA/REC" In the field "CntTRA/REC" it is displayed how often the GOOSE application has been received or transmitted by the protocol element since startup. • "Cnt DS wrong" In the field "Cnt DS wrong" it is displayed how often a GOOSE application has been received with wrong data set by the protocol element since startup. • "Cnt timeout" In the field "Cnt timeout" it is displayed how often a timeout has been detected by the protocol element during reception of a GOOSE application since startup. • "Max timeout" In the field "Max timeout", the maximum TIMEOUT presently applicable for the expected reception of the respective GOOSE application is displayed. Functions Protocol Elements DC0-023-2.01 9-93 LAN-Communikation (61850) In the field, the structure of the GOOSE datasets is displayed for each GOOSE-Index (GOOSE application) as follows: Example "GOOSE Application Index-1,2,4": GOOSE Application Index-1,2,4: 9-94 DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) In the field "GoCBRef" the parameterized GOOSE Control Block Reference (=MMS address) is displayed. The GOOSE Control Block is generated by the protocol element for each GOOSE application from the parameters of the goose definitions and can be read by the Client but not written. With the integrated WEB server, the GOOSE Control Block can be read out in the directory of the server under the Functional Constraint "GO". Example: "GoCBRef" = MEAS/LLN0$GO$gcb01 GOOSE Control Block Functions Protocol Elements DC0-023-2.01 9-95 LAN-Communikation (61850) Developer Information On these WEB pages, system-internal data of the protocol firmware for the software development specialists can be read out for troubleshooting. The following information can be displayed: 9-96 • Task Stack (internal operating system memory information) • Memory - HEAP …….……. Read out of the statistical information about the free/occupied memory - Read Memory … Display of the selected memory range - Read Register … Display of the CPU Register (Ethernet Controller Configuration, ENI-Controller Configuration, SER-/GEN-/MEM-Module Configuration) • EEPROM - Mac EEPROM … Display of the memory content of the Mac EEPROM - User EEPROM … Display of the memory content of the User EEPROM (presently not used) DC0-023-2.01 Functions Protocol Elements LAN-Communikation (61850) 9.6. Coupling of the SICAM TOOLBOX II over LAN (remote connection) The remote maintenance of Ax 1703 components can be performed over LAN using a "remote connection". The remote connection can be carried out with the following methods: • • 9.6.1. Remote connection over external Terminal Server (connection to M-CPU with TIAX00) Remote connection over integrated Terminal Server (Telnet) Remote Connection over external Terminal Server (connection to M-CPU with TIAX00) For the remote maintenance of Ax 1703 components using remote connection over external terminal server, the serial interface of the SICAM TOOLBOX II is connected with a selected SICAM 1703 component over ethernet. An external terminal server (=serial to ethernet converter) is thereby implemented at the SICAM TOOLBOX II side and at the SICAM 1703 component side. The IP address of the selected SICAM 1703 component and the SICAM TOOLBOX II are to be parameterized in the external terminal servers. All components that can be reached via the selected SICAM 1703 component can thus be reached for the remote maintenance. In the SICAM 1703 component and in the SICAM TOOLBOX II, no special parameter settings are required. If SICAM 1703 components are used in different LAN networks, a specific external terminal server must be used at the SICAM TOOLBOX II side for each LAN network or the external terminal server must be re-parameterized accordingly with the programs provided for this purpose. A communications protocol based on IEC 60870-5-1 and IEC 60870-5-2 "Balanced" is used between the SICAM TOOLBOX II and the LAN communications protocol firmware. Here, the remote connection over external terminal server is only mentioned for the sake of completeness, it is not however any special functionality of the LAN communications protocol firmware. In addition, this solution is now rarely implemented (or is only in use on older plants). In new plants, now in most cases the remote connection is carried out over Telnet with the integrated terminal server of the SICAM TOOLBOX II and the LAN communications protocol firmware. Functions Protocol Elements DC0-023-2.01 9-97 LAN-Communikation (61850) 9.6.2. Remote Connection over integrated Terminal Server (Telnet) For the remote maintenance of SICAM 1703 components using remote connection with Telnet, a transparent connection is established over ethernet between the SICAM TOOLBOX II and the integrated terminal server of the LAN communications firmware. The Telnet protocol is based on TCP/IP and is a Client-Server protocol. The SICAM TOOLBOX II thereby always takes over the client function, the SICAM 1703 component always the server function. The remote connection using Telnet is always established by the SICAM TOOLBOX II. For Telnet a TCP/IP connection must be set up. With the Toolbox interfacing, the Toolbox is Connector and the NIP is Listener. The Listener-Port number to be used is 2001. If several Toolboxes attempt to setup a connection at the same time, the first Toolbox wins, the rest are rejected. If an error is detected during the remote maintenance of SICAM 1703 components using remote connection, then the TCP/IP connection is terminated. For the remote connection, a connection is to be set up on the Toolbox for every remote station with the following parameters: • • • • Transmission medium = terminal server, TCP/IP (TELNET) IP address of the remote station (IP address or Host ID of the terminal server of the remote station) Port number = 2001 Delay time Functionally, the remote connection over Telnet thereby corresponds with the interfacing with external terminal server (and TIAX00), only with this solution the functionality of the terminal server is integrated in the SICAM TOOLBOX II and in the LAN communications protocol firmware. So that a secure point-to-point connection over Telnet is ensured, a communications protocol based on IEC 608705-1 and IEC 60870-5-2 "Balanced" is implemented between the SICAM TOOLBOX II and the LAN communications protocol firmware on the application layer. Telnet is thereby used as transport protocol. The service message formats between SICAM TOOLBOX II and the SICAM 1703 component are prepared accordingly on the LAN communications protocol firmware (conversion of SICAM 1703 internal format and format for SICAM TOOLBOX II) and transferred to the master service function of the SICAM 1703 component for further processing. 9-98 DC0-023-2.01 Functions Protocol Elements Appendix Appendix Internet Protocol - IP The Internet Protocol (IP) is that network protocol used almost exclusively in computer networks. With the protocol, single packets are transmitted throughout the entire network. IP forms the first layer of the Internet protocol family independent of the transmission medium. That means, that using IP address and subnet mask computers within a network can be grouped into logical units, so-called subnets. On this basis it is possible to address computers in larger networks and establish connections to them, since logical addressing is the basis for routing (route selection and transfer of network packets). The Internet Protocol represents the basis of the Internet. Transmission Control Protocol – TCP The Transmission Control Protocol (TCP) is a reliable, connection-orientated transport protocol in computer networks and is supported by all operating systems for modern computers. It is part of the Internet protocol family, the basis of the Internet, and is located in layer 4 of the OSI reference model. The protocol can be implemented on networks from 1200Bit/s up to several Gbit/s. In contrast to the connectionless UDP (User Datagram Protocol), TCP establishes a virtual channel (connection) between two terminals of a network connection (Sockets). On this channel, data can be transmitted in both directions. In all practical cases, TCP is based on the IP (Internet Protocol), which is why one also speaks of „TCP/IP Protocol“. Due to its many pleasing characteristics – data losses are detected and remedied automatically, data transmission is possible in both directions, can be used on many different media – the TCP/IP is a widespread protocol for data transmission. TCP is basically a point-to-point connection in full duplex, which permits the transmission of the information in both directions at the same time. The data in the reverse direction can thereby contain additional control information. The management of this connection as well as the data transmission is carried out by the TCP Software. Every TCP connection is identified unambiguously by two terminals. A terminal represents an assigned pair consisting of IP address and port. Such a pair forms a bidirectional software interface, and is known as a Socket. With the help of the IP addresses, the systems participating on the connection are identified; with the help of the ports, the two programs communicating with each other on the two participating systems are then identified. By using port numbers at both sides of the connection, it is possible for example, that one Web server on one port (normally Port 80) can have several connections open to another system at the same time. The ports are 16-Bit numbers (port numbers) and range from 0 to 65535. Ports from 0 to 1023 are reserved (English: well known ports[1]) and are assigned by the IANA, e.g. Port 80 is reserved for the HTTP protocol used in the WWW. A typical TCP packet has a maximum size of 1500 Bytes. It may only be so large, that it fits in the transmission layer situated below, the Internet protocol IP. The IP packet is specified theoretically up to 65535 Bytes (64 kB), but this is mostly transmitted over ethernet, and there the frame size is fixed at 1500 Bytes. TCP and IP protocols each define a header of 20 Bytes size. Therefore 1460 bytes are left over for the user data in a TCP/IP packet. Functions Protocol Elements DC0-023-2.01 1 Appendix Connection Setup A Web server which offers its service generates a terminal with the port number assigned to the application and its IP address. This is known as passive open or also as listen. If a client wishes to establish a connection, it generates its own terminal from its IP address and a still free port number. With the help of the port number of the application and the IP address of the server, a connection can then be set up. During the data transmission phase (active open) the roles of Client and Server (from TCP perspective) are completely symmetrical. In particular, each of the two participating systems can initiate a connection setup. For the establishment of a TCP connection, the so-called three-way handshake is implemented. The system which wishes to establish the connection sends the other a SYN packet (from the English word synchronize) with a sequence number x. The sequence numbers are thereby important for the assurance of a complete transmission in the correct order and without duplicates. It therefore concerns a packet, whose SYN-Bit is set in the packet header (see TCP-Header). The start sequence number is optional and is generated by the respective operating system according to a random algorithm. TCP/IP – Communication services Client TCP/IP – Initiate connection setup Server syn seq=x 1, seq=y syn ack = x+ ack = y+1, se q=x+1 TCP/IP – connection setup [data] TCP/IP Handshake The remote station (see sketch) receives the packet and as counter move sends its start sequence number y in its own SYN packet. At the same time, it confirms the reception of the first SYN packet, by increasing the sequence number x by one and sending it back in the ACK part (from the English word acknowledgement = confirmation) of the header. The client finally confirms the reception of the SYN/ACK packet by sending its own ACK packet with the sequence number y+1. This procedure is also called `Forward Acknowledgement´. The server receives this ACK segment, the ACK segment is identified by the set ACK-Flag. The connection is thereby established. SYN-SENT SYN/ACK-SENT ACK-SENT 2 <SEQ=100><CTL=SYN> <SEQ=300><ACK=101><CTL=SYN,ACK> <ACK=301><CTL=ACK> DC0-023-2.01 SYN-RECEIVED SYN/ACK-RECEIVED ESTABLISHED Functions Protocol Elements Appendix Connection release The controlled connection release takes place similar to the connection setup. Instead of the SYN-Bit, the FIN-Bit (from the English word finish = end, conclusion) is used, which indicates that no more data are coming from the transmitter. The reception of the packet is again confirmed with ACK. The recipient of the FIN packet finally sends its FIN packet, which is also confirmed to it. Client or Server TCP/IP – Initiate connection release TCP/IP – Communication services fin, seq=x ack = x+1 TCP/IP – connection released Remote station fin, seq=y ack =y+1 TCP/IP Teardown TCP/IP – Initiate connection release TCP/IP – connection released Although four ways are actually used, with connection release it also concerns a three-way handshake, since the ACK and FIN operations from the server to the client are evaluated as one way. In addition, a shortened procedure is possible, in which the FIN and ACK are accommodated in the same packet just as with the connection setup. The maximum segment lifetime (MSL) is the maximum time that a segment can stay in the network before it is discarded. After sending the last ACK's, the client switches to a waitstate lasting two MSL in which all delayed segments are discarded. As a result it is ensured, that no delayed segments can be wrongly interpreted as part of a new connection. Apart from this a correct connection termination is ensured. If ACK y+1 is lost, the timer at the server expires and the LAST_ACK segment is transmitted again. SICAM 1703 protocol elements do not however use the controlled connection release. A connection is normally only released with a Link failure, consequently an acknowledgement at TCP/IP level cannot be expected. The SICAM 1703 protocol firmware therefore uses the RST-bit in the RST packet for the immediate release of the connection. No acknowledgement is expected for this packet. Functions Protocol Elements DC0-023-2.01 3 Appendix User Datagram Protocol - UDP The User Datagram Protocol (UDP) is a minimal, connectionless (unacknowledged) network protocol, which belongs to the transport layer of the Internet protocol family. It provides no guarantee that transmitted packets also arrive or that packets arrive in the same order in which they have been sent. An application that uses the UDP must therefore be insensitive to lost, unsorted or duplicated packets or itself contain corresponding correction measures. The task of UDP is to allow data that are transmitted over the Internet to reach the correct application. In order to allow the data that are sent with UDP to reach the correct program on the destination system, ports are used for UDP, just as for TCP. For this, with UDP the port number of the service which is to receive the data is also sent. Since a connection does not have to be established first before the beginning of transmission, the hosts can begin faster with the exchange of data. 4 DC0-023-2.01 Functions Protocol Elements Appendix HyperText Transfer Protocol - HTTP The HyperText Transfer Protocol (HTTP) is a protocol for the transmission of data over a network. It is used mainly to load web pages and other data from the World Wide Web (WWW) or from a Web Browser integrated in a system. In the automation technique, parameter settings or diagnostic information of systems are realized more and more frequently with WEB technology. With this technique a WEB server is implemented in the device – the data are displayed on WEB pages. The HTTP forms the so-called application layer, over which the models provide no other layers. The application layer is addressed by the user programs, in the case of HTTP, in most cases this is the Web Browser, the normal user is therefore presented with this layer when he enters a web address. In the ISO/OSI layer model, the application layer corresponds with layer 7. The TCP/IP reference models implemented in the Internet sees the application layer in layer 4. In the core, HTTP is a stateless protocol. That also means, that after successful data transmission, the connection between the two communication partners does not need to be maintained. If then further data are to be transmitted, firstly another connection must be established. However through expansion of its interrogation methods, header information and status codes, the HTTP is not restricted to HyperText, rather is used increasingly for the exchange of any arbitrary data. For the communication, HTTP is dependent on a reliable transport protocol. In all practical cases, TCP is used for this. Functions Protocol Elements DC0-023-2.01 5 Appendix Telnet - Protocol Telnet (Telecommunication Network Protocol) is the name of a network protocol widespread in the Internet. Telnet is a Client-Server protocol, it uses TCP and the clients mostly connect with the destination computer over Port 23, however, as with most internet protocols, this port can also be changed. The Telnet protocol specifies the interfacing of terminals over TCP/IP. Network Time Protocol (NTP) The Network Time Protocol (NTP) is a standard for the synchronization of clocks in systems over IP communication networks. NTP is a hierarchical protocol over which time servers can determine a common time amongst each other. The NTP protocol determines the delay of packets in the network and compensates these for the clock synchronization. The NTP protocol uses port number 123. The NTP protocol is a Client/Server protocol. NTP clients can request the time from NTP servers. The Network Time Protocol (NTP) uses the connectionless network protocol UDP. The NTP protocol has been developed especially to enable a reliable time tagging over networks with variable packet delay. The NTP protocol is defined in the standard "RFC 1305: NTP V3". The time stamps in NTP are 64 bits long. 32 bits encode the seconds since the 1st January 1900 00:00:00 hours, 32 the other 32 bits the seconds fraction. In this way, a time period of 2 seconds (about 136 years) can be −32 represented with a resolution of 2 seconds (about 0.25 nanoseconds). NTP uses a UTC time scale and supports switching seconds, but not daylight-saving time and winter time. NTP uses a hierarchical system of different levels. The level specifies how far the NTP server is from an external time source. As time source an atomic clock, a DCF77 receiver or a GPS receiver can be used. A Layer-1 server is connected directly with a time source and uses this as reference for its time. A Layer-2 server uses a Layer-1 server as reference and synchronizes itself with other servers on its level if the connection to the higher level fails. The highest level is 16 and signifies, that this NTP server has not yet calibrated itself with other servers. As a rule no more than 4 levels exist, since otherwise the time would deviate too much. 6 DC0-023-2.01 Functions Protocol Elements Literature Literature ACP 1703 • Ax 1703 Common Functions Protocol Elements DC0-023-1 ACP 1703 Platforms Configuration Automation Units and Automation Networks DC0-021-1 Documents on Interoperability Ax 1703 Interoperability IEC 60870-5-101/104 DA0-046-1 ACP 1703 Interoperability IEC 60870-5-101/104 DC0-013-1 Ax 1703 Interoperability IEC 60870-5-103 DA0-063-1 ACP 1703 Interoperability IEC 60870-5-103 DC0-026-1 International standards IEC 60870-5-101 Telecontrol Equipment and Systems Part 5: Transmission Protocols Main section 101: Application-related standard for basic telecontrol tasks IEC 60870-5-103 Telecontrol Equipment and Systems Part 5: Transmission Protocols Main section 103: Application-related standard for the information interface of protection equipment IEC 60870-5-104 Telecontrol equipment and systems Part 5: Transmission protocols Section 104: Network access for IEC 60870-5-101 using standard transport profiles Functions Protocol Elements DC0-023-2.01 1 Literature International standards (continued) IEC 61850-1 Introduction and Overview - Introduction and overview of the standards of the IEC 61850 series IEC 61850-2 Dictionary - Collection of terms IEC 61850-3 General Requirements - Quality requirements (reliability), maintainability, system availability, portability, IT security) - Environmental conditions - Auxiliary services - Other standards and other rules of engineering IEC 61850-4 System and Project Management - Engineering service requirements (classification of parameters, technical work tools, documentation) - System utilization cycle (product versions, production settings, support after production setting) - Quality control (responsibilities, test equipment, type tests, system tests, factory acceptance tests "FAT" and location acceptance tests "SAT) IEC 61850-5 Communication Requirements for Functions and Device Models - Principle of the logical nodes - Logical communication links - Concept of assigned information elements for the communication (PICOM) - Logical nodes and assigned PICOM - Functions - Performance requirements (response times etc.) - „Dynamic Scenarios“ (requirements on the information flow under various operating conditions) IEC 61850-6 Language for the configuration of station automation systems - formal description of the single-pole scheme, of devices and system structure and their assignment to the single-pole scheme IEC 61850-7-1 Basic communication structure for station and bay-related secondary technology equipment – principles and models - Introduction into IEC 61850-7 - Communication principles and models IEC 61850-7-2 Basic communication structure for station and bay-related secondary technology equipment – Abstract Communication Services Interface (ACSI) - Description of the abstract communication services interface (ACSI) - Specification of the abstract communication services - Model of the server database IEC 61850-7-3 basic communication structure for station and bay-related secondary technology equipment – Common Data Classes - Abstract common data classes and attribute definitions IEC 61850-7-4 Basic communication structure for station and bay-related secondary technology equipment – Compatible Logical Nodes and Data Classes - Definition of logical nodes, data objects and their logical addressing 2 DC0-023-2.01 Functions Protocol Elements Literature International standards (continued) IEC 61850-8-1 Specific Communication Services Modeling (SCSM) – Modeling for MMS (according to ISO/IEC 9501-1 and -2) and ISO/IEC 9501-3 - Modeling for the communication within the entire station (Client-Server communication and "GOOSE" messages) IEC 61850-9-1 Specific Communication Services Modeling (SCSM) – Scanned values over serial Simplex-Multiple-Point-to-Point connection - Modeling for the Point-to-Point-type, unidirectional communication of scanned values of the transformer (with and without Merging Unit) IEC 61850-9-2 Specific Communication Services Modeling (SCSM) – Scanned values over ISO/IEC 8802-3 - Modeling for the bus-type, flexible communication of scanned values of the transformer (with and without Merging Unit) IEC 61850-10 Conformity check - Procedure for the conformity check Functions Protocol Elements DC0-023-2.01 3