File: P2LPC User's Manual Version: 1.0.0 Datum: 20.4.2007

© 2000 ISKRAEMECO d.d.

UK DISTRIBUTOR:SMS Metering LtdTEL: 0845 6047244EMAIL: sales@smsmetering.co.uk

ISKRAEMECO

Users Manual

P2LPC

P2LPC Documents: P2LPC_Technical_description.doc P2LPC Users Manual.doc P2LPC File Formats.doc P2LPC WebService Specification.doc

ISKRAEMECO P2LPC

Page 2 of 34

PREFACE 4 P2LPC HARDWARE DESIGN 4

Single Board Computer (SBC) 5 FRONT PANEL LED DESCRIPTION 5 SOFTWARE DESCRIPTION 6

Platform 6 AutoLaunch application 7 Remote networking setup 7 RASServer application 7 Restart application 7 KillProcCE application 7

P2LPC APPLICATION 8 P2LPC.xml file 9 DLCMeters.xml file - DLC network 9 SerialMeters.xml file - RS485 network 9 Results files 10 Profile files 11 Statistic and log files 12

UPLOAD NEW APPLICATION TO THE P2LPC 14 Upload new zipped application and definition files to the P2LPC: »P2LPCUpgrade.zip« 14 Upload SW tool module to the P2LPC: P2LPCUpgrade.exe 14 Reset application P2LPC 14

PREPARE FILE P2LPCRESTART.TXT AND ZIPPED FILE IN “P2LPCUPGRADE.ZIP”. 14 “P2LPCRESTART.TXT” FILE HAS ONE LINE WITH TEXT: 14 “P2LPCRESTART”START REMOTE DISPLAY APPLICATION ON THE P2LPC 14 START REMOTE DISPLAY APPLICATION ON THE P2LPC 15 CONNECT CONCENTRATOR USING ETHERNET 16 SETTING GPRS ON P2LPC 17

1. »Modem COM4.ras« file 17 2. »Startup.dat« file 17 3. »P2LPC.xml« file 17 4. Restart P2LPC 17

SETTING TIME ZONE, DATE AND TIME ON P2LPC 18 USING NTP SERVICE ON P2LPC AS NTP CLIENT 19 DLC NETWORK 20 SERIAL NETWORK 21

CONSERETH 22 DATA CONCENTRATOR SCHEDULING AND MONITORING 23

Schedule 23 Monitoring 24

DEMAND READING 25 P2LPC Demand Reading method 25 Demand reading delay 25

P2LPC_TRANSACTION 26 P2LPC_SNMP AGENT FUNCTIONALITY 28

SNMP MIB 28 P2LPC WEB SERVICE 29

ISKRAEMECO P2LPC

Page 3 of 34

Web service 29 Standards used 29 P2LPC Web Service implementation list 29

APPENDIX: P2LPC EVENTS CODES AND STRINGS 31 APPENDIX: TRANSACTIONS SAMPLES 33

•••••••

•••••

••

ISKRAEMECO P2LPC

Page 7 of 34

AutoLaunch application

For automatic start of P2LPC application after boot, ISKRAEMECO creates special application named “AutoLaunch”, which is integrated into Windows CE image. AutoLaunch application starts other applications listed under Windows Registry key (HKEY_CURRENT_USER\Software\ISKRAEMECO\AutoLaunch). Applications are started automatically, if full path and application name is written as registry item. You can start up to 10 applications (0 to 9). Example : "2=str:Storage Card\P2LPC_WINCE.exe". AutoLaunch application also checks for newer version of P2LPC application (see “Upload new application to the P2LPC”).

Remote networking setup

For using remote networking in P2LPC application, network connections should be created. Network connections are created by application RasEntry2.exe (stored on CompactFlash card). If we want to use it we should put this application to AutoLaunch application settings in Registry. It creates two network connections, one for modem and one for direct serial port. Data parameters for each connection are stored in Modem COM4.ras and Serial COM2.ras.

RASServer application

RASServer application is used to enable and startup RAS server on P2LPC. It is called automatically when P2LPC application starts, if “server” mode is selected (see explanation of “P2LPC.xml” file).

Restart application

Restart application is used to restart P2LPC and is integrated into Windows CE image. Command can be executed from command prompt or by Telnet command. Syntax is following: “restart [N]”, where N is time in seconds before restart occur, this gives time to gracefully complete some other actions. If N is omitted, delay is 30 seconds. Value for N is between 30 to 120, if N exceeds this limits N is rounded to nearest limit value.

KillProcCE application

KillProcCE application is used to list and kill processes on P2LPC. Command can be executed from command prompt or by Telnet command. Syntax is following: “KillProcCE [program_name.exe]”, where “program_name.exe” is the name of application to terminate. If “program_name.exe” is omitted, program lists currently running processes. For this application “Toolhelp.dll” library is needed.

•

•

•

•

•

•

ISKRAEMECO P2LPC

Page 9 of 34

P2LPC.xml file

P2LPC application behavior is controlled by P2LPC.xml file. P2LPC.xml file is detailed explained in “P2LPC File Formats” document. The P2LPC.xml file is processed when the currently active schedule is finished.

DLCMeters.xml file - DLC network

DLCMeters.xml file is the list file of found DLC meters on DLC network. File is dynamically created or updated when new DLC meter is found on DLC network and it is also output file. It stores DLC address, number of credits and phase for each DLC meter fount by P2LPC on DLC network and meters device id number. DLC meters are listed from first found to last found (not by value of DLC address). DLCMeters.xml file is detailed explained in “P2LPC File Formats” document.

SerialMeters.xml file - RS485 network

SerialMeters.xml file is the list file contains information on the used HDLC addresses and as input file is transferred to folder P2LPCFiles. SerialMeters.xml file is detailed explained in “P2LPC File Formats” document After file is accepted by application, it is dynamically completed or updated with founded serial meters on RS485 network meters and renamed to SerialMeters.old . File is dynamically updated when new serial meter is found on DLC network and it is also output file. P2LPC application schedule Id=90 is default schedule for RS485 meters. .

ISKRAEMECO P2LPC

Page 10 of 34

Results files

Once the meter is read by the concentrator, the concentrator generates three different types of result files per each meter (result file, load profile file and event file). The form is as follows: Sub_meterID_YYYYMM.pl?(?)

Extension File Explanation plr file containing results plrz zipped file containing results ple file containing events plez zipped file containing events plp file containing profile readout plpz zipped file containing profile readout

P2LPC generate one (plr/plp/ple) file per meter per month. For example, if the concentrator reads results from meter 12345678 just after midnight on the 1.1.2004, a file named Sub_12345678_200401.plr(z) will be generated. All the results read from this meter until 23:59:59 on the 31st of January 2004 will be appended into this file. The concentrator’s settings in P2LPC.xml: UseZipFiles="1 ; result files is zipped UseZipFiles="0" ; result files is not zipped Results files are the results of reading meters on DLC network. Each meter has own readout file. Readout files names are in following format:

Sub_12345678_200401.plr

New readout file is created for a new month. When RAS operation mode is “server” or “GPRS”, only files, which are requested, are transferred to center. Files remain on P2LPC storage. When transfer to collecting center occurs (in the case “client” mode of RAS operation), all readout files are transferred to data collecting center. After that all files, which are not from current month, are deleted (after successful transfer). Typical contents of readout file are following: <Device DeviceID="33320881" P2LPCIdent="00000000" > <Results> <Register Ident="96.1.0" Value="33320881" DateTime="2003-05-09T22:15:50" Status="0" /> <Register Ident="1.0.0" Value="2003-05-09T22:17:37" DateTime="2003-05-09T22:15:54" Status="0" /> <Register Ident="1.8.0" Value="00023412" DateTime="2003-05-09T22:15:57" Status="0" /> <Register Ident="2.8.0" Value="00000000" DateTime="2003-05-09T22:16:00" Status="0" /> </Results> </Device>

Device ID (8 places) Year and month of results

Extension P2LPC Results Prefix »Sub_«

ISKRAEMECO P2LPC

Page 11 of 34

Profile files

Profile files are the results of reading profile of meters on DLC network. Each meter has own profile file. Profile files names are in following format:

Sub_12345678_200401.plp

New profile file is created for a new month. When RAS operation mode is “server” or “GPRS”, only files, which are requested, are transferred to center. Files remain on P2LPC storage. When transfer to collecting center occurs (in the case “client” mode of RAS operation), all profile files are transferred to data collecting center. After that all files, which are not from current month, are deleted (after successful transfer). Typical contents of profile file are following: <Device DeviceID="33320881" P2LPCIdent="00000000"> <Profile Ident="99.1.0" Period="3600"> <Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T00:00:00" Status="0" /> <Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T01:00:00" Status="0" /> <Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T02:00:00" Status="0" /> <Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T03:00:00" Status="0" /> <Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T04:00:00" Status="0" /> <Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T05:00:00" Status="0" /> . . . </Profile> </Device>

Device ID (8 places) Year and month of results

Extension P2LPC Profile Prefix »Sub_«

ISKRAEMECO P2LPC

Page 12 of 34

Statistic and log files

Statistic and log files help to monitor P2LPC application working. Log file has P2LPCLog.txt name. It logs various information, warnings and errors’ occurring while P2LPC application is working. It is simple text file, limited to 512kB. When size limit is reached, file is truncated by 128kB. Excerpt from P2LPCLog.txt:

LogTraceLevel="3" ----extended . 6.3.2003 13:16:27.000 Information DocThread : Thread started OK 6.3.2003 13:16:27.000 Information Substations count = 0 6.3.2003 13:16:28.000 Information Schedule ID = 1 Schedule thread (0008C948) 6.3.2003 13:16:28.000 Information Schedules Add index = 0 6.3.2003 13:21:05.000 Information TAPI Line[0] = Hayes Compatible on COM1: 6.3.2003 13:21:05.000 Information TAPI Line[1] = Iskraemeco Modem 6.3.2003 13:26:06.000 Information TAPI Line[5] = Serial Cable on COM1: 6.3.2003 13:31:00.000 Information Start Communication with 21 [0x015] 6.3.2003 13:31:03.000 Information DoExecuteConnect OK 6.3.2003 13:31:09.000 Information DoExecuteAARQ OK 6.3.2003 13:31:26.000 Information Stop Communication with 21 [0x015] 6.3.2003 13:31:29.000 Information DoExecuteDisconnect OK 6.3.2003 13:31:29.000 Information Start Communication with 96 [0x060] 6.3.2003 13:31:50.000 Information DoExecuteConnect FAILED 6.3.2003 13:31:50.000 Information Start Communication with 22 [0x016] 6.3.2003 13:31:53.000 Information DoExecuteConnect OK 6.3.2003 13:32:03.000 Information DoExecuteAARQ OK . . . 6.3.2003 13:33:39.000 Information Stop Communication with 25 [0x019] 6.3.2003 13:33:42.000 Information DoExecuteDisconnect OK 6.3.2003 13:33:42.000 Information Start Communication with 23 [0x017] 6.3.2003 13:33:45.000 Information DoExecuteConnect OK 6.3.2003 13:33:55.000 Information DoExecuteAARQ OK 6.3.2003 13:34:11.000 Information Stop Communication with 23 [0x017] 6.3.2003 13:34:28.000 Information DoExecuteDisconnect OK 6.3.2003 13:34:28.000 Information Start Communication with 97 [0x061] 6.3.2003 13:34:56.000 Information DoExecuteConnect FAILED 6.3.2003 13:34:56.000 Information Start Communication with 98 [0x062] 6.3.2003 13:35:29.000 Information DoExecuteConnect FAILED 6.3.2003 13:35:29.000 Information Find DLC slaves START (3 phases) 6.3.2003 13:35:30.000 Information Finding DLC slaves COMPLETE (All phases) . . . LogTraceLevel="0" ----short . 3.10. 12:47:18 - Info - SchedID=1 retry=6 - DevID[198]="11901692" 23.10. 12:47:22 - Info - Fork DLC 869 [0x365] OK 23.10. 12:47:58 - Info - Finish SchedID=1 - DevID[198]="11901692" OK 23.10. 12:47:58 - Info - SchedID=1 retry=6 - DevID[199]="11901697" 23.10. 12:48:02 - Info - Fork DLC 874 [0x36A] OK 23.10. 12:48:38 - Info - Finish SchedID=1 - DevID[199]="11901697" OK 23.10. 12:48:40 - Info - SchedID=1 retry=6 - DevID[200]="35400072" 23.10. 12:48:44 - Info - Fork DLC 395 [0x18B] OK 23.10. 12:49:19 - Info - Finish SchedID=1 - DevID[200]="35400072" OK 23.10. 12:49:19 - Info - SchedID=1 retry=6 - DevID[201]="11901671" 23.10. 12:49:22 - Info - Fork DLC 848 [0x350] OK 23.10. 12:50:19 - Info - Finish SchedID=1 - DevID[201]="11901671" OK .

••••••

•

ISKRAEMECO P2LPC

Page 14 of 34

Upload new application to the P2LPC

Upload new zipped application and definition files to the P2LPC: »P2LPCUpgrade.zip«

From P2LPC version 1.10 Build 20070420 is possible to send new application and or definition files in compressed (zip) file. This is procedure to upload new compressed version of P2LPC from center to the P2LPC concentrator.

1. On desktop computer prepare new application and/or other new P2LPC definitions file and compress (zip)all files into “P2LPCUpgrade.zip”; rename file to “P2LPCUpgrade.tmp”;

2. Make RAS connection with the P2LPC,3. When RAS connection is made start FTP session with the P2LPC and upload “P2LPCUpgrade.tmp” to

P2LPC, after successful upload rename “P2LPCUpgrade.tmp” into “P2LPCUpgrade.zip”.4. Close FTP session,5. P2LPC will restart automatically.

Note: If P2LPC version 1.10 Build 20070420 (DLCMeters.xml) is older then

Upload SW tool module to the P2LPC: P2LPCUpgrade.exe

This module have to be uploaded only once. This is procedure to upload upgrade SW module to the P2LPC concentrator. SW module “P2LPCUpgrade.exe” is SW tool to upgrade of P2LPC application and/or other setting file automatic. This module copy and unzipped file »P2LPCUpgrade.zip« in root directory. This tool copy all existing file to new files in folder »Storage card\P2LPCFiles *.old« and restart application of P2LPC.

1. On desktop computer prepare new application and/or other new P2LPC definitions file and compress (zip)all files into “P2LPCUpgrade.zip”; rename file to “P2LPCUpgrade.tmp”;

2. Make RAS connection with the P2LPC,3. Start FTP session with the P2LPC and upload SW tool “P2LPCUpgrade.exe” to P2LPC and upload

“P2LPCUpgrade.tmp” to P2LPC, after successful upload,4. Close FTP session,5. Start Telnet session,6. Move file “P2LPCUpgrade.exe” from FTP root directory (“\Storage card\P2LPCFiles”) into “\Storage card”

directory7. execute in directory “\Storage card”: start wdttrigger.exe and killprocce P2LPC_WinCE.exe 8. rename in directory “\Storage card\P2LPCFiles” “P2LPCUpgrade.tmp” into “P2LPCUpgrade.zip”.,9. Execute command “Start P2LPCUpgrade.exe” from command prompt to force upgrade tool executed,10. Close Telnet session,11. P2LPC will restart automatically.

Reset application P2LPC

From P2LPC version 1.10 Build 20070420 upload zipped file to the P2LPC: »P2LPCUpgrade.zip«

Prepare file P2LPCrestart.txt and zipped file in “P2LPCUpgrade.zip”.

“P2LPCrestart.txt” file has one line with text:

“P2LPCrestart”

ISKRAEMECO P2LPC

Page 15 of 34

Start remote display application on the P2LPC This is procedure to start remote display application (CERDISP.exe) on P2LPC. This feature allows you to get P2LPC screen picture on remote desktop computer. This feature gives you possibility to control P2LPC application from desktop computer with mouse and keyboard. On desktop computer, CERHOST.exe application should run (peer application of CERDISP.exe).

1. On desktop computer from connection to P2LPC will be established, start program CERHOST.exe. 2. Make RAS connection with the P2LPC, 3. When RAS connection is made, start Telnet session and check if application CERDISP.exe exists on

P2LPC (“\Windows” or “\Storage Card” directory). If not exists put CERDISP.exe from desktop computer to P2LPC (use FTP session to upload application),

4. In Telnet session(GSM/GPRS), execute command “start cerdisp -c” from command prompt. If remote desktop computer is connect to P2LPC to Ethernet port, execute command “start cerdisp IPaddress” from command prompt. IPaddress is IP of remote desktop computer. This command will start remote display application,

5. Optionally you can close Telnet session, 6. If CERDISP.exe on P2LPC is started and connection with CERHOST.exe application is made, you will

see P2LPC desktop in CERHOST window on desktop computer. Now you are able to control P2LPC application from desktop.

Note: Due to slow communication rate (modem) screen update can take few seconds.

•

•••••

•

ISKRAEMECO P2LPC

Page 17 of 34

Setting GPRS on P2LPC For passage from GSM to GPRS communication is needed to decide suitable contract with mobile operator. Offer to VPN of connection to APN is important to this. Radius server is necessary for simplification of administration. It must be configured so, that is unchangeable connection between SIM card and IP address - without binding on username and password. Mobile operator ensures safety needs so, that allows only traffic from VPN on GPRS terminals of belonging APN. At such configuration, also switch is possible on GSM back. When »Modem« LED on the front panel of the concentrator is pulsing with slow symmetrical pulses, the GPRS login was performed successfully. The LED on the GSM terminal should be blinking wit quick double blinks. To set GPRS mode on P2LPC following files should be modified: 1. »Modem COM4.ras« file Bold and red items should be set to appropriate value used for GPRS mobile operator:

Name=Modem Connection UseCountryAndAreaCodes=N SpecificIpAddr=N SpecificNameServers=N DeviceType=modem DeviceName=Iskraemeco Modem IpHeaderCompression=Y SwCompression=Y RequireEncryptedPw=N RequireMsEncryptedPw=N UserName= Password= BaudRate=19200 CountryCode=386 AreaCode=4 Phone=*99***1#

2. »Startup.dat« file

Modification of “Startup.dat” file is needed to configure correct GPRS context on GSM/GPRS modem using AT-commands. To set GPRS mobile operator context find following registry key "HKEY_LOCAL_MACHINE\ExtModems\Iskraemeco Modem\Init". Modify following registry settings in “Startup.dat” file for GPRS mobile operator:

.. "[HKEY_LOCAL_MACHINE\ExtModems\Iskraemeco Modem\Init]" "3=str:ATL0M0X3<cr>" "4=str:AT+CGDCONT=1,ip,maingatelan.telia.se<cr>" ..

To support longer modem configuration strings look for following registry key in “Startup.dat” "HKEY_LOCAL_MACHINE\Drivers\Unimodem\Settings". If this registry key does not exists, add following lines to “Startup.dat”

.. "[HKEY_LOCAL_MACHINE\Drivers\Unimodem\Settings]" "MaxCmd=dword:50" ..

3. »P2LPC.xml« file

Set GPRS mode. This is done by modifying attribute »Mode« from value »server« to »GPRS« in element »RAS« .. <RAS

StartTime="00:05:00" Period="86400" RemoteDirectory="\\\\REMOTE_COMPUTER\\RAS_TEST" PhoneNumber="123456" AreaCode="4" CountryCode="386" Mode="GPRS"

/> ..

4. Restart P2LPC

New settings will be in affect after restart of P2LPC.

••

•

•••••

•

•••

•

•

•••••

•

ISKRAEMECO P2LPC

Page 20 of 34

DLC network P2LPC is data concentrator for automatic data collection from MT/ME351 and MT/ME371 family system meters. Communication with the MT/E371 system meter is established by means of the integrated DLC modem with DLMS/COSEM communication protocol. Software application in P2LPC is responsible for reading, finding and managing communications with system meters over DLC network, storing data and transferring data to data collection centre on demand Change some of defaults parameters in “P2LPC.xml” file in specific DLC network conditions can have result in better reading performance.

<P2LPC> <Info Version="1.10" Producer="ISKRAEMECO d.d." /> . .

<Readout SchedulePeriod="1800" RetryCount="5" /> ; retry 5 times in default schedule unread meters . . <DLC

InitialCredits="3" ; is used to increase performance in specific bad DLC network condition – group of meters

FindSlavesCount="20" ; 20 meters will be installed in P2LPC in one install schedule (forced installation)

MaxSessionFailsToDeinstall="10" ; is used to quick split DLC network if it is mixed through crosstalk settable from 1 up to 20. /> . . </P2LPC>

ISKRAEMECO P2LPC

Page 21 of 34

Serial network P2LPC is data concentrator for automatic data collection from MT/ME372 RS485 family system meters. Communication with the MT/E372 RS485 meter is established by means of the integrated serial interface with DLMS/COSEM communication protocol. Software application in P2LPC is responsible for reading, finding and managing communications with system meters over RS485 network, storing data and transferring data to data collection centre on demand.

Activation Serial interface: P2LPC application schedule Id=90 is default schedule for RS485 meters. Schedule Id=90 is created automatically, if SerialMeters.xml file exists. User can set baud rate and timeout for serial interface in P2LPC.xml file. Serial interface is activated by setting parameters in “P2LPC.xml” file and transferred SerialMeters.xml file to folder P2LPCFiles.

P2LPC.xml parameter setting <P2LPC>

<Info Version="1.00" Producer="ISKRAEMECO d.d." /> <SerialPort Baudrate="9600" Timeout="1000" />" ; define baud rate 9600 and timeout 1second.…

SerialMeters.xml file is the file of founded serial meters on RS485 network. This file contains information on the used HDLC addresses and as input file is transferred to folder P2LPCFiles . Initial file is as follow:

<SerialMeters> <SerialMeter Address="17"/> <SerialMeter Address="18"/>

. . <SerialMeter Address="65"/>

<SerialMeter Address="66"/> </SerialMeters>

After file is accepted by application, it is dynamically completed or updated with meters renamed to SerialMeters.old and is as follow:

<SerialMeters P2LPCVersion=" 1.10" P2LPCBuild="20061013"> <SerialMeter Address="17" DeviceId="40371144" /> <SerialMeter Address="18" DeviceId="40371142" />

. . <SerialMeter Address="65" DeviceId="40371179" />

<SerialMeter Address="66" DeviceId="40371180" /> </SerialMeters>

Deactivation Serial interface: Delete or comments lines in “P2LPC.xml” file:

<SerialPort Baudrate="9600" … />" <Schedule Ident="90" … /> <Transaction Type= … ScheduleId="90" /> and

Delete SerialMeters.xml file.

Note: P2LPC application can run only Serial meter schedule or Consereth-IP. Deactivation and activation have to be performed to switch serial functionality.

ISKRAEMECO P2LPC

Page 22 of 34

CONSERETH Meters can be included in IP networks by means of the P2LPC communicator to which IEC 1107 meters are connected at the RS485 interface. A number of meters are limited with the RS485 standard. The P2LPC concentrator implements the CONSERETH-IP protocol enabling transparent serial data transfer to IP network. All unchanged IEC1107 messages of the meter are transferred to the IP over GPRS/Eth network. The meters are accessible from the centre at IP address by means of the CONSERETH-IP protocol enabling tunneling of IEC 1107 messages to the TCP transport. CONSERETH-IP Protocol Layers CONSERETH-IP protocol is intended for data transfer of serial interfaces to IP transport. The so-called data tunneling is performed. Serial interface data are transparently transferred to TCP transport layer by means of CONSERETH application layer which implements the CONSERETH-IP Protocol. CONSERETH-IP Protocol can be activated if files consereth.exe and consereth.xml is present in folder Storage Card. Activation CONSERETH-IP interface: CONSERETH interface is activated by setting parameters in “startup.dat” file. "[HKEY_CURRENT_USER\Software\ISKRAEMECO\AutoLaunch]" … "6=str:Storage Card\CONSERETH.exe" … File consereth.xml contains setup information for CONSERETH serial interface and TCP/IP interface. Initial file is as follow:

<CONSERETH> <SerialPort Name="COM2:" Baudrate="9600" Databits="7" Parity="EVEN" Stopbits="1" Handshake="NONE" /> <TCPIP Address="127.0.0.1" Port="2000" /> </CONSERETH>

Deactivation CONSERETH-IP: Delete or comments lines in “startup.dat” file: … "6=str:Storage Card\CONSERETH.exe" … New Activation and Deactivation CONSERETH-IP: Parameter for consereth In “startup.dat” file is not set. Activation is follow definition in file AutoLaunch.ini present in folder Storage Card. "\Storage Card\ CONSERETH.exe " Note: P2LPC application can run only Serial meter schedule or Consereth-IP. Deactivation and activation have to be performed to switch serial functionality.

ISKRAEMECO P2LPC

Page 23 of 34

Data concentrator scheduling and monitoring This item describes how processes of scheduling and monitoring are implemented in the P2LPC data concentrator.

Schedule Schedule is basic readout entity, which actually performs meter data collection. Schedule is implemented as an operating system thread. The data concentrator can have up to 16 schedules running as independent threads. Schedules are created and started when the application is started and executed after start condition is reached (schedule time). Schedules are identified by Id number. Schedules with Id=1 is a default schedule for PLC meters and schedule with Id=90 is a default schedule for using serial data communication. The schedule with Id=1 is created automatically (if not already exists) when first meters are found on the PLC network. For adding and/or removing schedules, configuration file (P2LPC.xml) is used. Data which are collected by a schedule are defined by a configuration file (P2LPC.xml) as “Transaction” elements. “Transaction” element has attribute “Schedule” which defines schedule Id in which transaction is executed. If value for schedule Id=0, then transaction is executed in every defined schedule. Schedules share single communication resource – a PLC modem among them. Due to the fact that schedules have no priority, any schedule waiting for a resource can get this single resource (as soon as this resource is released from the active schedule). Picture below illustrates behavior of three running schedules, schedule 1 is in execution. In between, schedule 2 becomes ready for the execution but does not have free resources. Later on schedule 3 also becomes ready for the execution. When schedule 1 finishes execution, it releases resource thus making it available for other schedules. Internal operating system functionality assigns free resource to the one of pending schedules. In our case schedule 3 obtains resource before schedule 2, even schedule 2 was ready for execution before schedule 3. Beside regular schedules, PLC networking (finding and installing new meters) also use shared resource PLC modem. PLC networking process is also an operating system thread. Schedules and PLC networking have no priority, so operating system gives shared resource to the one of pending schedules or to the PLC networking. Demand reading request is the only operation that can interrupt currently running schedule or the PLC networking thread. If a demand reading occurs during communication to the particular meter, this communication transaction is finished. The active schedule is interrupted and the current execution point is saved. Other pending schedules are also disabled. After that point, a demand reading is performed. When demand reading is finished, interrupted active schedule continues while other schedules are enabled.

Schedule 2, ready to execute, waiting for free resource

Schedule 3, ready to execute, waiting for free resource

Schedule 1, execute, and free resource

Schedule 1, release resource, schedule 3 start to execute

Schedule 3, release resource, schedule 2 start to execute

1 2 3

ISKRAEMECO P2LPC

Page 24 of 34

Monitoring Monitoring and logging are supported in the P2LPC data concentrator. Running operations are logged into the “P2LPCLog.txt” file. The file is limited up to 512kB. If this limit is exceeded, 128kB cut-off is performed. To improve overall system performances, writings to the log file are buffered (FIFO principle). After every 25 buffered items, the amount of the buffer is written into the log file. The amount of logged data can be controlled by a setting of “LogTraceLevel” attribute of the “P2LPC.xml” file; value can be from 0 to 3. Beside the log file, PLC network statistic is written after each PLC networking operation and after each schedule is finished. PLC statistic is written into the “P2LPCStatBrief.txt” file. If the “LogTraceLevel” attribute is set to 3, then each PLC statistic is written into the “P2LPCStat.txt” file. By inspecting “P2LPCStat.txt” file, a user can monitor PLC communication quality. Third method to log and monitor P2LPC concentrator, are events. Concentrator events are stored into “P2LPC_xxxxxxxx_yyyymm.ple” file. Each month a new file is created. For details about concentrator events see “P2LPC File Formats” document.

••••

ISKRAEMECO P2LPC

Page 26 of 34

P2LPC_Transaction P2LPC transactions determine which COSEM objects will be read or write from meter. Transactions are set in “P2LPC.xml” file and can be added and/or removed. COSEM object access type is set for each transaction. Access type is defined by “Type” attribute of “Transaction” element. Possible values are “get” for read COSEM object and “set” for write to COSEM object. Each COSEM object is described by class id; instance id and attribute id (see DLMS UA document for details about COSEM objects). This COSEM object properties are defined by “Transaction” element attributes “ClassId”, “InstanceId” and “AttributeId”. These four attributes of “Transaction” element are mandatory, following attributes are optional. Attribute “ScheduleId” determine in which schedule transaction executes. If “ScheduleId” has value 0, transaction is executed in all existing schedules. Attributes “DaysAgo” and “HoursAgo” determine for how many days and hours ago data is requested from meter. These attributes apply only to COSEM profile objects. Attribute “ExactTime” determine exact time of data requested from meter. These attributes apply only to COSEM profile objects. For “set” type of access to COSEM object, value for write shall be provided. Additional element “Parameter” with attributes “Type” and “Value”. Attribute “Type” determine COSEM object value type (like short, long, unsigned …, see DLMS UA document for details about COSEM objects value type). Attribute “Value” is value to be writing to COSEM object. By this way numeric types can be set. For setting strings or complex values, attribute “HexValue” is used instead of “Value”. In that case attribute “Type” is set to value 99 and value of attribute “HexValue” is hexadecimal coded string of bytes separated by space. Note: certain knowledge of meter COSEM objects data types and structures are needed to prepare write transactions. P2LPC does not validate parameter type and value! Sample: <Transactions> <Transaction Type="set" ClassId="1" AttributeId="2" InstanceId="0.0.128.0.2.255" ScheduleId="0"> <Parameters> <Parameter Type="17" Value="1" /> </Parameters> <Transaction Type="set" ClassId="8" AttributeId="2" InstanceId="0.0.1.0.0.255" ScheduleId="2"> <Parameters> <Parameter Type="99" Value="09 0C 07 D7 02 15 03 0A 2E 17 00 FD A8 00" /> </Parameters> <!--Daily and hourly values / --> <Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.99.2.0.255" ScheduleId="1"/> <Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.99.1.0.255" ScheduleId="1"/> <Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.98.1.0.255" ScheduleId="1"/> <Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.98.2.0.255" ScheduleId="1"/> …… </Transactions>

ISKRAEMECO P2LPC

Page 27 of 34

P2LPC meters firmware upgrade P2LPC concentrator supports upgrade of meters firmware. Upgrade procedure is performed by web service calls. Following steps should be taken to upgrade meters firmware:

1. Send new firmware binary file to concentrator. Use web service calls “UploadFileChunk” or use FTP service to upload file to concentrator.

2. When file is uploaded, start upgrade procedure by web service call “UpgradeMeters”, with full name of the firmware binary file (from step 1 - located on concentrator) as call parameter.

3. Concentrator starts to upgrade the meters by activating “upgrade start” action for each meter. Activate information is send only to the meters which will be upgraded, depending on meter type (i.e. if upgrade binary file is for three-phase meters, only three-phase meters will be activated for upgrade).

4. After activate “upgrade start” is sent to all involved meters, firmware binary blocks are sent to the meters. Firmware is dividing in blocks. These blocks are sent by broadcast command.

5. After all blocks of upgrade binary file are transferred, upgrade check is performed on each upgraded meter. Upgrade check is made by reading “Image_Free_Block_Address” object from particular meter. Until this object value points to lower address than firmware image end address, concentrator resends firmware upgrade block pointed by value of “Image_Free_Block_Address” object. By this mechanism concentrator fills-up missing blocks inside meter firmware image.

6. When “Image_Free_Block_Address” object points to address bigger than firmware image end address, activate “upgrade stop” command is sent to meter. After that, meter is upgraded and it restarts itself.

7. Events during upgrade process are written into concentrator events file and present success of upgrade.

ISKRAEMECO P2LPC

Page 28 of 34

P2LPC_SNMP agent functionality Concentrators P2LPC are equipped with SNMP agent functionality, based on standardized SNMP network management protocol. This SW package enables the concentrator to be manageable by the SNMP-based management systems. This SW module support AMR specific MIB variable and traps, defined in AMR MIB definition document “iskraemeco_amr_v2_12.mib”. P2LPC device status, communications link status and status of meters controlled by the P2LPC device are published via MIB variables. SNMP version which is supported is SNMPv2. Concentrator P2LPC AMR SNMP agent transforms information into SNMP formatted output and sends it to the management center. Concentrator P2LPC generates SNMP traps and immediately sends them to AMR control center and answer to SNMP queries. P2LPC AMR SNMP functionality and its components are detailed explained in separate documents which are part P2LPC SNMP module documentation. Activation AMR SNMP Agent: AMR SNMP Agent is activated by setting parameters in “startup.dat” file. "[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SNMP\Parameters\ExtensionAgents]" "3=str:Software\\Iskraemeco\\AMRAgent\\CurrentVersion" "[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SNMP\Parameters\TrapConfiguration\public]" "1=str:10.2.5.242" "[HKEY_LOCAL_MACHINE\Software\Iskraemeco\AMRAGENT\CurrentVersion]" "Pathname=str:\\Storage Card\\amragent.dll"

SNMP MIB

Provides a detailed insight into the operational status of concentrator and attached meters Complete MIB definition is available in document “iskraemeco_amr_v2_12.mib”.

•

•

•

•

•

••

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

ISKRAEMECO P2LPC

Page 31 of 34

Appendix: P2LPC events codes and strings Current list of concentrator events codes and strings: // Event groups #define EVENT_GROUP_SYSTEM 1 #define EVENT_GROUP_DLC 2 #define EVENT_GROUP_COMMUNICATION 3 #define EVENT_GROUP_SUBSTATION 4 // Event types #define EVENT_TYPE_SYS_STARTUP 1 #define EVENT_TYPE_SYS_EXIT 2 #define EVENT_TYPE_SYS_RESTART 3 #define EVENT_TYPE_SYS_DEVICE_ID 4 #define EVENT_TYPE_SYS_PARAMS_OK 5 #define EVENT_TYPE_SYS_CONFIG_OK 6 #define EVENT_TYPE_SYS_PARAMS_ERROR 7 #define EVENT_TYPE_SYS_CONFIG_ERROR 8 #define EVENT_TYPE_SYS_READING_ERROR 9 #define EVENT_TYPE_SYS_READING_SESSION_ERROR 10 #define EVENT_TYPE_SYS_READING_TRANS_ERROR 11 #define EVENT_TYPE_SYS_DEMAND_READING_ERROR 12 #define EVENT_TYPE_SYS_DEMAND_READING_SESSION_ERROR 13 #define EVENT_TYPE_SYS_DEMAND_READING_TRANS_ERROR 14 #define EVENT_TYPE_SYS_DEMAND_READING_XML_OK 15 #define EVENT_TYPE_SYS_DEMAND_READING_XML_ERROR 16 #define EVENT_TYPE_SYS_TARIFF_XML_OK 17 #define EVENT_TYPE_SYS_TARIFF_XML_ERROR 18 #define EVENT_TYPE_SYS_DLC_METERS_XML_ERROR 19 #define EVENT_TYPE_SYS_THREAD_START_ERROR 20 #define EVENT_TYPE_SYS_HDLC_ERROR 21 #define EVENT_TYPE_SYS_MEMORY_ERROR 22 #define EVENT_TYPE_SYS_SERIAL_METERS_XML_ERROR 23 #define EVENT_TYPE_SYS_SAVE_THREAD_ERROR 24 #define EVENT_TYPE_SYS_TIME_SYNC 25 #define EVENT_TYPE_SYS_CODE_RED 26 #define EVENT_TYPE_SYS_UPGRADE_START 27 #define EVENT_TYPE_SYS_UPGRADE_START_SECTION 28 #define EVENT_TYPE_SYS_UPGRADE_FILE_ERROR 29 #define EVENT_TYPE_SYS_UPGRADE_START_MISSING 30 #define EVENT_TYPE_SYS_UPGRADE_FINISH 31 #define EVENT_TYPE_SYS_UPGRADE_FINISH_SECTION 32 #define EVENT_TYPE_SYS_KEYS_FILE_OK 33 #define EVENT_TYPE_SYS_KEYS_FILE_ERROR 34 #define EVENT_TYPE_SYS_RESULTS_FILE_ERROR 35 #define EVENT_TYPE_SYS_UPGRADE_START_ACTIVATE 36 #define EVENT_TYPE_DLC_INSTALL 1 #define EVENT_TYPE_DLC_DEINSTALL 2 #define EVENT_TYPE_DLC_GLOBAL_DEINSTALL 3 #define EVENT_TYPE_DLC_DOUBLE_ADDRESS 4 #define EVENT_TYPE_DLC_ADD_SUBSTATION 5 #define EVENT_TYPE_DLC_NETWORK_ERROR 6 // DLC general error #define EVENT_TYPE_DLC_NEW_ADDRESS 7 // DLC new address assigned to slave (dynamic DLC addressing) #define EVENT_TYPE_DLC_SLAVE_LOST 8 // DLC slave not responds to fork #define EVENT_TYPE_DLC_SLAVE_DELETE 9 // DLC slave delete due to not responding to master #define EVENT_TYPE_DLC_SLAVE_EXISTS 10 // DLC slave address already exists (old DLC addressing) #define EVENT_TYPE_COM_OPEN_PORT_ERROR 1 #define EVENT_TYPE_COM_PHY_LAYER_ERROR 2 #define EVENT_TYPE_COM_GSM_MODEM_ERROR 3 #define EVENT_TYPE_COM_RAS_SERVER_ERROR 4 #define EVENT_TYPE_COM_PPP_CONNECT 5 #define EVENT_TYPE_COM_PPP_DISCONNECT 6 #define EVENT_TYPE_SUB_TARIFF_WRITE_OK 1 #define EVENT_TYPE_SUB_TARIFF_WRITE_ERROR 2 #define EVENT_TYPE_SUB_TARIFF_ACTIVATE_OK 3 #define EVENT_TYPE_SUB_TARIFF_ACTIVATE_ERROR 4 #define EVENT_TYPE_SUB_SET_ENCRYPTION_KEY_OK 5 #define EVENT_TYPE_SUB_SET_ENCRYPTION_KEY_ERROR 6

ISKRAEMECO P2LPC

Page 32 of 34

// Event group strings #define EVENT_GROUP_STRING_NONE (_T("NON.")) #define EVENT_GROUP_STRING_SYSTEM (_T("SYS.")) #define EVENT_GROUP_STRING_DLC (_T("DLC.")) #define EVENT_GROUP_STRING_COMMUNICATION (_T("COM.")) #define EVENT_GROUP_STRING_SUBSTATION (_T("SUB.")) // Event type strings #define EVENT_TYPE_STRING_UNKNOWN (_T("Unknown")) #define EVENT_TYPE_SYS_STRING_STARTUP (_T("Startup")) #define EVENT_TYPE_SYS_STRING_EXIT (_T("Exit")) #define EVENT_TYPE_SYS_STRING_RESTART (_T("Restart")) #define EVENT_TYPE_SYS_STRING_DEVICE_ID (_T("DeviceId")) #define EVENT_TYPE_SYS_STRING_PARAMS_OK (_T("ParamsOK")) #define EVENT_TYPE_SYS_STRING_CONFIG_OK (_T("ConfigOK")) #define EVENT_TYPE_SYS_STRING_PARAMS_ERROR (_T("ParamsError")) #define EVENT_TYPE_SYS_STRING_CONFIG_ERROR (_T("ConfigError")) #define EVENT_TYPE_SYS_STRING_READING_ERROR (_T("ReadingError")) #define EVENT_TYPE_SYS_STRING_READING_SESSION_ERROR (_T("ReadingSessionError")) #define EVENT_TYPE_SYS_STRING_READING_TRANS_ERROR (_T("ReadingTransError")) #define EVENT_TYPE_SYS_STRING_DEMAND_READING_ERROR (_T("DemandReadingError")) #define EVENT_TYPE_SYS_STRING_DEMAND_READING_SESSION_ERROR (_T("DemandReadingSessionError")) #define EVENT_TYPE_SYS_STRING_DEMAND_READING_TRANS_ERROR (_T("DemandReadingTransError")) #define EVENT_TYPE_SYS_STRING_DEMAND_READING_XML_OK (_T("DemandReadingXMLOK")) #define EVENT_TYPE_SYS_STRING_DEMAND_READING_XML_ERROR (_T("DemandReadingXMLError")) #define EVENT_TYPE_SYS_STRING_TARIFF_XML_OK (_T("TariffXMLOK")) #define EVENT_TYPE_SYS_STRING_TARIFF_XML_ERROR (_T("TariffXMLError")) #define EVENT_TYPE_SYS_STRING_DLC_METERS_XML_ERROR (_T("DLCMetersXMLError")) #define EVENT_TYPE_SYS_STRING_THREAD_START_ERROR (_T("ThreadStartError")) #define EVENT_TYPE_SYS_STRING_HDLC_ERROR (_T("HDLCError")) #define EVENT_TYPE_SYS_STRING_MEMORY_ERROR (_T("MemoryError")) #define EVENT_TYPE_SYS_STRING_SERIAL_METERS_XML_ERROR (_T("SerialMetersXMLError")) #define EVENT_TYPE_SYS_STRING_SAVE_THREAD_ERROR (_T("SaveThreadError")) #define EVENT_TYPE_SYS_STRING_TIME_SYNC (_T("TimeSync")) #define EVENT_TYPE_SYS_STRING_CODE_RED (_T("CodeRed")) #define EVENT_TYPE_SYS_STRING_UPGRADE_START (_T("UpgradeStart")) #define EVENT_TYPE_SYS_STRING_UPGRADE_START_SECTION (_T("UpgradeStartSection")) #define EVENT_TYPE_SYS_STRING_UPGRADE_FILE_ERROR (_T("UpgradeFileError")) #define EVENT_TYPE_SYS_STRING_UPGRADE_START_ACTIVATE (_T("UpgradeStartActivate")) #define EVENT_TYPE_SYS_STRING_UPGRADE_START_MISSING (_T("UpgradeStartMissing")) #define EVENT_TYPE_SYS_STRING_UPGRADE_FINISH (_T("UpgradeFinish")) #define EVENT_TYPE_SYS_STRING_UPGRADE_FINISH_SECTION (_T("UpgradeFinishSection")) #define EVENT_TYPE_SYS_STRING_KEYS_FILE_OK (_T("P2LPCKeysOK")) #define EVENT_TYPE_SYS_STRING_KEYS_FILE_ERROR (_T("P2LPCKeysError")) #define EVENT_TYPE_SYS_STRING_RESULTS_FILE_ERROR (_T("ResultsFileError")) #define EVENT_TYPE_DLC_STRING_INSTALL (_T("Install")) #define EVENT_TYPE_DLC_STRING_DEINSTALL (_T("Deinstall")) #define EVENT_TYPE_DLC_STRING_GLOBAL_DEINSTALL (_T("GlobalDeinstall")) #define EVENT_TYPE_DLC_STRING_DOUBLE_ADDRESS (_T("DoubleAddress")) #define EVENT_TYPE_DLC_STRING_ADD_SUBSTATION (_T("AddSubstation")) #define EVENT_TYPE_DLC_STRING_NETWORK_ERROR (_T("NetworkError")) #define EVENT_TYPE_DLC_STRING_NEW_ADDRESS (_T("NewAddress")) #define EVENT_TYPE_DLC_STRING_SLAVE_LOST (_T("SlaveLost")) #define EVENT_TYPE_DLC_STRING_SLAVE_DELETE (_T("SlaveDelete")) #define EVENT_TYPE_DLC_STRING_SLAVE_EXISTS (_T("SlaveExists")) #define EVENT_TYPE_COM_STRING_OPEN_PORT_ERROR (_T("OpenPortError")) #define EVENT_TYPE_COM_STRING_PHY_LAYER_ERROR (_T("PhyLayerError")) #define EVENT_TYPE_COM_STRING_GSM_MODEM_ERROR (_T("GSMModemError")) #define EVENT_TYPE_COM_STRING_RAS_SERVER_ERROR (_T("RASServerError")) #define EVENT_TYPE_COM_STRING_PPP_CONNECT (_T("PPPConnect")) #define EVENT_TYPE_COM_STRING_PPP_DISCONNECT (_T("PPPDisconnect")) #define EVENT_TYPE_SUB_STRING_TARIFF_WRITE_OK (_T("TariffWriteOK")) #define EVENT_TYPE_SUB_STRING_TARIFF_WRITE_ERROR (_T("TariffWriteError")) #define EVENT_TYPE_SUB_STRING_TARIFF_ACTIVATE_OK (_T("TariffActivateOK")) #define EVENT_TYPE_SUB_STRING_TARIFF_ACTIVATE_ERROR (_T("TariffActivateError")) #define EVENT_TYPE_SUB_STRING_SET_ENCRYPTION_KEY_OK (_T("SetEncryptionKeyOK")) #define EVENT_TYPE_SUB_STRING_SET_ENCRYPTION_KEY_ERROR (_T("SetEncryptionKeyError"))

ISKRAEMECO P2LPC

Page 33 of 34

Appendix: transactions samples Default transaction (implicitly included) <Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.96.1.0.255" ScheduleId="1"/> read device id <Transaction Type="get" ClassId="8" AttributeId="2" InstanceId="0.0.1.0.0.255" ScheduleId="1"/> read current time <Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.42.0.0.255" ScheduleId="1"/> read logical device name

Current values <Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.0.255" ScheduleId="1"/> read meter register value, T0 <Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.1.255" ScheduleId="1"/> read meter register value, T1 <Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.2.255" ScheduleId="1"/> read meter register value, T2 <Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.3.255" ScheduleId="1"/> read meter register value, T3 <Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.4.255" ScheduleId="1"/> read meter register value, T4

Maximum Demand <Transaction Type="get" ClassId="4" AttributeId="2" InstanceId="1.0.1.6.0.255" ScheduleId="2"/> read maximum demand value, T0, current billing period <Transaction Type="get" ClassId="4" AttributeId="2" InstanceId="1.0.1.6.1.255" ScheduleId="2"/> read maximum demand value, T1, current billing period <Transaction Type="get" ClassId="4" AttributeId="2" InstanceId="1.0.1.6.2.255" ScheduleId="2"/> read maximum demand value, T2, current billing period

Power Outage <Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.128.6.1.255" ScheduleId="3"/> Read short power failure counter value

Load profile <Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.99.1.0.255" ScheduleId="4"/> read Load Profile 1 values (1.8.0 register profile) <Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.99.2.0.255" ScheduleId="4"/> read Load Profile 2 values (midnight values registers profile

Billing profile <Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.98.1.0.255" ScheduleId="4" /> read Billing Profile 1 <Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.98.2.0.255" ScheduleId="4" /> read Billing Profile 2

Load profile period <Transaction Type="set" ClassId="7" AttributeId="4" InstanceId="1.0.99.1.0.255" ScheduleId="3"/> change Load Profile 1 profiling perod ….

<Parameters> <Parameter Type="6" Value="3600"/>

</Parameters> … to 3600 seconds (1 hour)<Transaction Type="set" ClassId="7" AttributeId="4" InstanceId="1.0.99.2.0.255" ScheduleId="3"/> change Load Profile 2 profiling perod ….

ISKRAEMECO P2LPC

Page 34 of 34

<Parameters> <Parameter Type="6" Value="86400"/> </Parameters> … to 86400 seconds (1 day) Impulse input registers <Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.2.1.8.0.255" ScheduleId="3"/> read meter register value, impulse input 1 <Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.3.1.8.0.255" ScheduleId="3"/> read meter register value, impulse input 2 Tariff <Transaction Type="get" ClassId="20" AttributeId="2" InstanceId="0.0.13.0.0.255" ScheduleId="3"/> read name of active tariff program <Transaction Type="get" ClassId="20" AttributeId="6" InstanceId="0.0.13.0.0.255" ScheduleId="3"/> read name of passive tariff program <Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.128.10.3.255" ScheduleId="3"/> read current active tariff <Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.128.10.0.255" ScheduleId="3"/> read tariff control register <Transaction Type="set" ClassId="1" AttributeId="2" InstanceId="0.0.128.10.0.255" ScheduleId="3"/> change tariff control register to … <Parameters> <Parameter Type="17" Value="1"/> </Parameters> …1 (external tariff inputs). 0 - internal tariff program Events <Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.99.98.0.255" ScheduleId="3"/> read logbook (event log) <Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.99.97.0.255" ScheduleId="3"/> read long power failures log <Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.97.97.0.255" ScheduleId="3"/> read Fatal Fault register

Exclusion of default reading transactions ScheduleId="0" : all SsceduleID

<ExcludeTransaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.0.255" ScheduleId="0"/> these are transactions performed without any user definitions

<ExcludeTransaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.1.255" ScheduleId="0"/> if LP2 is used they should be excluded <ExcludeTransaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.2.255" ScheduleId="0"/>