LogData V23 Examples Description V111 3ADR023043M9901

  • View
    217

  • Download
    0

Embed Size (px)

Text of LogData V23 Examples Description V111 3ADR023043M9901

  • 8/18/2019 LogData V23 Examples Description V111 3ADR023043M9901

    1/27

    Example Description V01

    PS563-WATER Library Package LogData_AC500_V23 Data Logging Library Application Examples

  • 8/18/2019 LogData V23 Examples Description V111 3ADR023043M9901

    2/27

    LogData - Water Library Introduction and Examples Description 1  AC500 / Issue: 08.2015

    Content

    1. INTRODUCTION TO DOCUMENT ............................................................................. 2

    1.1 Scope of the document ................................................................................................... 2

    1.2 Overview of the Content ................................................................................................. 2

    1.3 Compatibi lity ................................................................................................................... 2

    1.4 Safety Instruct ions .......................................................................................................... 2

    2. Logger Overview ............................................................................................................ 3

    2.1 Operat ing Modes of the Logger ......................................................................................... 5

    2.1.1 Mode 0/1: Buffer and disposal in chronologic order ....................................................... 5

    2.1.2 Mode 2: Buffer and disposal via FTP ............................................................................ 6

    2.1.3 Mode 3: Events Recorder.............................................................................................. 6

    3. Generic Example program ............................................................................................ 8

    3.1 Preparat ion ......................................................................................................................... 8

    3.2 Use Mode 0/1 Buf fer and disposal in chronolog ic order ............................................... 10

    3.2 Use mode 2: Buffer and d isposal via FTP ....................................................................... 15

    3.3 Use mode 3: Event recorder ............................................................................................ 17

    4. IEC60870 Example program ........................................................................................ 19

    4.1 Preparat ion ....................................................................................................................... 19

    4.2 Use Mode 0/1: Buffer and disposal in chronologic order .............................................. 23

    5. REVISION HISTORY ................................................................................................ 25

  • 8/18/2019 LogData V23 Examples Description V111 3ADR023043M9901

    3/27

    LogData - Water Library Introduction and Examples Description 2  AC500 / Issue: 08.2015

    1. INTRODUCTION TO DOCUMENT

    1.1 Scope of the document

    This document is intended for explaining the first use of the LogData AC500 library, with the provided example projects, to directly log data of remote communication connections of the AC500 or as standalone data logger.

    1.2 Overview of the Content

    There are two example projects provided for the two different use cases of the logger.

    In chapter 3 the Example for logging of generic protocols is described, while the logging for IEC 60870 protocol is described in chapter 4.

    The necessary preparation of the AC500 is explained at the beginning of each of these example chapters.

    In the ready to run application programs Ethernet communication is assumed to transfer and receive data between AC500 acting as a substation (logging data in case of interruptions in communication) and a control station (receiving then e.g. logged historical data after a communication is there again after an outage).

    1.3 Compatibility The example programs explained in this document has been used with the below engineering system versions. It should also work with other versions; nevertheless some small adaptations may be necessary, for future versions.

    ·  AC500 Control Builder Plus CBP V2.3., as delivered with Automation Builder V 1.0 Suite of Engineering programs.

    1.4 Safety Instructions

    The user must follow all applicable safety instructions and the guidelines mentioned in the user documents of  the ABB products used in the example program

    ·  Read the complete safety instructions for the AC500 before installation and commissioning.

    ·  Read all safety instructions of your control station system manuals..

  • 8/18/2019 LogData V23 Examples Description V111 3ADR023043M9901

    4/27

    LogData - Water Library Introduction and Examples Description 3  AC500 / Issue: 08.2015

    2. Logger Overview

    The AC500 Datalogging Function Block Library contains five Function Blocks for the purpose of advanced time-stamped data logging for different use cases. In typical use cases the AC500 application program generates data which are normally transmitted to a telecontrol system for storage and further processing or  displaying to the end user. Typically, these may be remote applications like water pumping stations or solar  power plants where the connection between the remote station (AC500) and a central SCADA/telecontrol station is not always stable or only sporadically connected. Sporadically connected can be by intention e.g. to save communication costs or open ports/connections to be handled by a control station. Then the Datalogging Function Blocks can store data in case of a broken or intentionally interrupted connection between AC500 and the telecontrol system.

    1 AC500 application

    2 telecontrol

    Fig. 1: Overview

     Alternatively

    ·  The Datalogging Library can be used as an event recorder. In this special mode data is continuously recorded in a ring buffer which can be read out after a certain event x (e.g. outage) in order to analyze the values especially before but also after the event x.

    ·  Data can be logged only and on command transferred to the ftp area to be analyzed offline or taken out via the SD card.

    The following figure 2 gives an overview of the described interaction of the Datalogging Function Blocks.There is always an input Function Block needed which transfers the input data into data sets with timestamp for use by the Datalogger. An output Function Block receives the current or retrieved data from the Datalogger in case of communication or further processing. The input Function Blocks "LOG_xxx_INPUT", the Function Block "LOG_HANDLING" and the output Function Blocks "LOG_xxx_OUTPUT" communicate via SRAM FIFOin and FIFOout areas in the memory. This SRAM FIFOs are intermediate buffers and help in decoupling time wise and speeding up the necessary write/read operations on the logging file structures significantly. These read/write operations on the files are done in blocks of datasets, enabling a comparably fast interaction with the otherwise slow file system.

  • 8/18/2019 LogData V23 Examples Description V111 3ADR023043M9901

    5/27

    LogData - Water Library Introduction and Examples Description 4  AC500 / Issue: 08.2015

    Fig. 2: Overview Function Blocks

    Each Datalogging application requires the main Function Block LOG_HANDLING , one of the input Function Blocks to provide data to be logged and one output Function Block to retrieve the data.

     As input and output Function Blocks two different types exist:

    ·  For logging data of an interrupted IEC60870 communication, the Function Blocks LOG_IEC60870_INPUT and LOG_IEC60870_OUTPUT are provided. The IEC60870 Datalogging

    Function Blocks support the IEC data types and work internally with the standard AC500 IEC60870 Library. The IEC Datalogger output Function Block does not need special handling or control/inputs.

    ·  For other types of general data LOG_GENERIC_INPUT and LOG_GENERIC_OUTPUT are provided. The generic Datalogging Function Blocks support an even larger variety of data types. The generic output Function Block needs to be hand-shaked with for each data set, in order to retrieve the data from the Datalogging files. Therefore the generic Function Blocks can also be used to integrate the data logging into any other protocol, e.g. Modbus.

    The Function Block LOG_HANDLING ensures that also several consecutive and fast interruptions can be handled without losing data. While the log file is replayed, arriving new data is stored in the SRAM FIFOin and added to the Datalogging files (File FIFO) if the SRAM FIFOin becomes full - during that short time the log file replay is paused. Nevertheless any data send to a control station via a communication is always with the oldest data first (FIFIO = “First In First Out”).

     As it takes up to 30 seconds before a communication break is detected (e.g. with TCP/IP protocols by the  AC500 hardware/firmware), the data rate at which data should be logged in case of a communication break has to be calculated and limited.

     As an improvement a ping mechanism can be implemented in the Substation. This was done in the example program for the IEC logger. With this ping the interruption is already detected after 1-2 seconds (can be configured in the example program).

     As the SRAM FIFOin has to store data during this time, its size limits the data rate. The SRAM FIFO size is 160 datasets. This means the data rate should be lower than approximately max. datarate = 1