Expected IntervalEDW LPEX V2.0 communication protocol

Description
Communication line configuration
Communication station configuration
I/O tag configuration
I/O tag address
Error indication
Literature
Changes and modifications
Document revisions

Description

EDW LPEX V2.0 protocol is a simple text file protocol. Its implementation is based on a sequential processing of file rows. Two types of files are supported:

• LPEX file
• MPX file

The LPEX file consists of a header and part with data. The header contains a description of data, that are separated by a defined separator. This separator is used to separate also data in each row of a document.

An example of LPEX file body:

One row of table corresponds to one row in a text file. As a separator there is used a symbol ";", which may be defined in the station parameters - parameter "Column Delimiter".

For better visibility, the data is displayed in a table below. The header columns are described in Protocol parameters in the section Communication station configuration.

The MPX file is an even more primitive text file protocol that has only a data portion. The body of the MPX file may look as follows:

For better visibility, the data is displayed in a table below. The header columns are described in Protocol parameters in the section Communication station configuration.

When MPX files are analyzed, the column order is fixed, and the protocol parameters that specify the column names in the LPEX header as well as the maximum number of columns (Date Column Name, Time Column Name .. Interval Name and Max. Columns Number)  are ignored. Parameters Date Conversion Mask and Time Conversion Mask, specifying the date and time format, are also ignored, and format yymmddhhmi is assumed.

Communication line configuration

• Communication line category: FILE I/O.

• The parameter "Input File" is used only if the parameters Primary FTP Server and/or Secondary FTP Server are specified and by parameter ZIP File Mask specifies, that input files are in ZIP format (*.zip) - the input files are downloaded from the specified FTP servers and the ZIP files are searched for in the directory specified by the "Input File" parameter.

• The parameter "Archive" specifies a folder for storing processed files.

Communication station configuration

Communication station - configuration dialog box, Protocol parameters.
They influence some of the optional protocol parameters. A user may define the following station protocol parameters:

I/O tag configuration

Permitted I/O tags: Ai

I/O tag address

I/O tag address consists of three parts.

First one defines the type of value:

• P - Power (calculated from Energy read from the input file)
• W - Work (calculated by integrating Power within current hour)
• E - Energy (directly from the input file with possible recalculations due to size of Interval -  see the parameter Expected Interval)

The second one - "Primary EAN Code" and "BackupEAN Code" are used as a unique identifier of value, which is placed in "Address Column Name" of source file.

The third part represents the value type (AP+,AP-,AQ+,AQ-), which is in the "Value Type Column Name".

Note: configuration of two I/O tags which are of types Power and Energy and next two parts of their address is identical, is not currently supported. Only one of these I/O tags will work. Combinations Power + Work or Work + Energy are supported.

Following special addresses exist:

• I/O tag with the address TRIGGER will be set to a value equal to the number of processed LPEX or MPX files immediately after the processing is done
• I/O tag with the address INVALIDS will be set to a value equal to the number of I/O tags the data for which were not found in a file that was just processed

Error indication

The flags FA and FB are used to indicate the situations, when data processing was not done as expected. FB flag is set only for the performance values on condition that the files comes from other server, i.e. they are transmitted through FTP. It relates to the following situations:

• time in the file is older than "Maximum File Age" and the parameter "Send Old Values" is enabled at the same time,
• data are not processed during the current hour, for example, if the record with time stamp 13:45 comes in the time 14:03,
• older data, as already processed, come for I/O tag.

In these cases, the values are archived without flag. The most recent valid value will have FB flag.

• There were received data with the same time stamp as current time stamp of I/O tag, but with the different value. FB flag is set for this particular value.
• The name of each processed file contains also the information about time. If this time is different from time stamp of value stored in the file, this data has also FB flag, in case of both archival and current value.

The performance values will be preprocessed before sending to D2000 Server. If the values are received in N-minutes intervals, the value from the file will be divided by a number (N* 60), which ensures that from the integral value of work will be average performance. The time stamp of this artificial performance value will be moved to the beginning of interval.

If the protocol is configured so that data are downloaded from FTP servers, user may set the primary and secondary FTP server. If data downloading from primary server failed, the secondary one is used. Data processed in such a way have FA flag.
These value flags are displayed in the archival dialog box of I/O tag, column "Value flag".

Literature

Changes and modifications

-

Document revisions

• Ver. 1.0 - April 23, 2014 - New document.
• Ver. 1.1 - May 17, 2018 - Support for MPX files.