You are on page 1of 34

ISKRAEMECO

Users Manual
P2LPC

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

File:
P2LPC User's Manual
Version:
1.0.0
Datum:
20.4.2007
2000 ISKRAEMECO d.d.
UK DISTRIBUTOR:
SMS Metering Ltd
TEL: 0845 6047244
EMAIL: sales@smsmetering.co.uk

ISKRAEMECO

P2LPC

PREFACE

P2LPC HARDWARE DESIGN

Single Board Computer (SBC)

FRONT PANEL LED DESCRIPTION

SOFTWARE DESCRIPTION

Platform
AutoLaunch application
Remote networking setup
RASServer application
Restart application
KillProcCE application
P2LPC APPLICATION
P2LPC.xml file
DLCMeters.xml file
SerialMeters.xml file
Results files
Profile files
Statistic and log files

6
7
7
7
7
7
8
9
9
9
10
11
12

- DLC network
- RS485 network

UPLOAD NEW APPLICATION TO THE P2LPC


Upload new zipped application and definition files to the P2LPC:
Upload SW tool module to the P2LPC:
P2LPCUpgrade.exe
Reset application P2LPC

P2LPCUpgrade.zip

14
14
14
14

PREPARE FILE P2LPCRESTART.TXT AND ZIPPED FILE IN P2LPCUPGRADE.ZIP.

14

P2LPCRESTART.TXT FILE HAS ONE LINE WITH TEXT:

14

P2LPCRESTARTSTART REMOTE DISPLAY APPLICATION ON THE P2LPC

14

START REMOTE DISPLAY APPLICATION ON THE P2LPC

15

CONNECT CONCENTRATOR USING ETHERNET

16

SETTING GPRS ON P2LPC


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

17
17
17
17
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
P2LPC Demand Reading method
Demand reading delay

25
25
25

P2LPC_TRANSACTION

26

P2LPC_SNMP AGENT FUNCTIONALITY


SNMP MIB

28
28

P2LPC WEB SERVICE

29
Page 2 of 34

ISKRAEMECO
Web service
Standards used
P2LPC Web Service implementation list

P2LPC
29
29
29

APPENDIX:

P2LPC EVENTS CODES AND STRINGS

31

APPENDIX:

TRANSACTIONS SAMPLES

33

Page 3 of 34

,6.5$(0(&2

3/3&

3UHIDFH

7KLVPDQXDOLVLQFRPSOHWHDQGSUHOLPLQDU\XVHUVPDQXDOIRU3/3&7KLVPDQXDOLVEULHIGHVFULSWLRQRI
FRQWUROOLQJ3/3&RSHUDWLQJ6FUHHQVKRWVDUHWDNHQIURPGHVNWRS3&HPXODWRUQRWIURPDFWXDO:LQGRZV&(
DSSOLFDWLRQ:LQGRZV&(GRFXPHQWDWLRQVKRXOGEHUHDGIRUEHWWHUXQGHUVWDQGLQJRI3/3&

3/3&+DUGZDUHGHVLJQ
3/3&FRQVLVWVRIWKHIROORZLQJPRGXOHVDQGFRPSRQHQWV
 3RZHUVXSSO\
 6LQJOHERDUGFRPSXWHU
 0DLQERDUG
 ,QWHJUDWHG'/&PRGHP
 0RGHPPRGXOHIRUFRPPXQLFDWLRQZLWKGDWDFROOHFWLQJFHQWHU
 6HULDO56FRPPXQLFDWLRQSRUW
 3/3&FDVH

3/3&EORFNGLDJUDP



3RZHUVXSSO\

SURYLGHVPDQ\YROWDJHVQHHGHGE\HDFKEORFN 






6%&



(WKHUQHWDGDSWHU

6LQJOHERDUGFRPSXWHU



ELWEDVHGDQG


ZLWKLQWHJUDWHG

SHULSKHUDO





0RGHPPRGXOH

SRZHUHGE\0LFURVRIW
'/&0RGHP
*60*356 

:LQGRZV&(RSHUDWLQJ

V\VWHP







.H\ERDUG
56

9*$PRQLWRU
PRXVH
6HULDOSRUW
RSWLRQDO
RSWLRQDO

3DJHRI

,6.5$(0(&2

3/3&

6LQJOH%RDUG&RPSXWHU 6%& 
3/3&LVEDVHGRQDVLQJOHERDUGFRPSXWHU6%&6%&LVEDVHGRQELWSURFHVVRUDUFKLWHFWXUHFDSDEOHRI
UXQQLQJ 0LFURVRIW :LQGRZV &( RSHUDWLQJ V\VWHP 6%& LV PDGH LQ WKH IRUP RI PRGXOH DQG KDV WKH IROORZLQJ
FRPSRQHQWV
 ELW&38
 0%5$0
 %RRW)ODVK
 )ODVKGDWDVWRUDJH0%IRUORDGLQJRSHUDWLQJV\VWHPLPDJHDQGGDWDVWRUDJH
 5HDOWLPHFORFNZLWKEDWWHU\RUVXSHUFDSEDFNXS


2Q6%&:LQGRZV&(RSHUDWLQJV\VWHPLVUXQQLQJ2SHUDWLQJV\VWHPLVVWDUWHGIURP&RPSDFW)ODVKFDUGZKLFK
FRQWDLQVLPDJHRIRSHUDWLQJV\VWHP$IWHU3/3&ERRWVDQGRSHUDWLQJV\VWHPLVUXQQLQJ3/3&DSSOLFDWLRQLV
VWDUWHGDXWRPDWLFDOO\ XQGHUVSHFLDOFRQGLWLRQGHVFULEHGODWHU 


)URQWSDQHO/('GHVFULSWLRQ

)URQWSDQHORI3/3&KDVVHYHQJUHHQOLJKWHPLWWLQJGLRGHV/('WRLQGLFDWHRSHUDWLRQDQGVWDWXVRI3/3&
DSSOLFDWLRQ













581 
LVDOZD\VRQZKHQDSSOLFDWLRQLVVWDUWHGDQGUXQQLQJ
$/$50
LVRQZKHQDSSOLFDWLRQLVQRWUXQQLQJ VKRXOGEHRIIDOOWLPH 
/(9(/ 
EOLQNVZKHQGDWDIUDPHVDUHWUDQVIHUUHGWKURXJK'/&RU5)PRGHP
02'(0
LVRQZKHQVHUYHU5$6PRGHLVVHOHFWHGZKHQGDWDFRQQHFWLRQLVPDGHLWEOLQNVIDVW
LI5$6PRGHLV*356LWEOLQNVZLWKDSSUR[+]IUHTXHQF\ZKHQFRQQHFWHGWR*356QHWZRUNLI5$6
PRGHLVFOLHQWLWLVRQGXULQJGDWDFRQQHFWLRQZLWKFHQWHURWKHUZLVHLVRII
'/& 
LVRQZKHQ'/&PRGHPLVLQXVH
5)

QRWXVHG
(7+(51(7
LVRQZKHQ(WKHUQHWFDUULHULVSUHVHQW

3DJHRI

,6.5$(0(&2

3/3&

6RIWZDUHGHVFULSWLRQ
:HFDQGLYLGH3/3&VRIWZDUHLQWRWZRSLHFHV
3ODWIRUPLHRSHUDWLQJV\VWHPZKHUHDOOFRPSRQHQWVH[LVWRUDUHFUHDWHGIRU3/3&DSSOLFDWLRQWRUXQ
3/3&DSSOLFDWLRQDFWXDOO\SHUIRUPGDWDFRQFHQWUDWRUIXQFWLRQDOLW\
(DFKSLHFHVRIVRIWZDUHKDVLWVRZQVHWWLQJVDQGFRQILJXUDWLRQVILOHV

3ODWIRUP
3ODWIRUPRURSHUDWLQJV\VWHPLV:LQGRZV&(EDVHG:HXVHFRPSOHWH*8,LQWHUIDFHDQGDOOVRIWZDUH
FRPSRQHQWVRIIHUHGE\RSHUDWLQJV\VWHP7KLVFRPSOHWHIXQFWLRQDOLW\LVQRWQHHGHGQRZEXWPD\EHXVHGLQWKH
IXWXUH*8,LQWHUIDFHLVDOVRPRUHXVHUVIULHQGO\DQGRIIHUVHDV\VHWWLQJHGLWLQJDQGWHVWLQJRI3/3&RSHUDWLRQV
:HKDYHSRVVLELOLW\WRVHWVRPHRSHUDWLQJV\VWHPVHWWLQJVGXULQJERRWWLPH7KHVHVHWWLQJVDUHVWRUHGRQ
&RPSDFW)ODVKFDUGILOH4UBSUVQEBU9DOXHVIURPILOH4UBSUVQEBUDUHVWRUHGLQ:LQGRZV&(5HJLVWU\
&RPSDFW)ODVKFDUGLVLQ:LQGRZV&(RSHUDWLQJV\VWHPUHIHUHQFHGDV6WRUDJH&DUG7KHGHVFULSWLRQRI
4UBSUVQEBU RQO\,6.5$(0(&2VH[WHQVLRQV LVLQWKHIROORZLQJWDEOH
"EEFECZ*4,3"&.&$0
<),&:@$633&/5@64&3=4PGUXBSF=*4,3"&.&$0=1-1$@8*/$&>
1SPEVDFSTUS*4,3"&.&$0
1SPHSBN1-1$@8*/$&
7FSTJPO

6RPHLQIRUPDWLRQVWULQJV

<),&:@$633&/5@64&3=4PGUXBSF=*4,3"&.&$0="VUP-BVODI>
TUS8JOEPXT=&YQMPSFSFYF
TUS4UPSBHF$BSE=3BT&OUSZFYF
TUS4UPSBHF$BSE=1-1$@8*/$&FYF

+HUH\RXFDQVHWZKLFK
DSSOLFDWLRQVDUHVWDUWHG
DXWRPDWLFO\ZKHQ:LQGRZV
&(VWDUWV)XOOSDWKWR(;(
ILOHLVQHHGHG

<),&:@-0$"-@."$)*/&=&YU.PEFNT=*TLSBFNFDP.PEFN=*OJU>
"5-.DS
"59DS
"5,%$DS
<),&:@$-"44&4@3005=JOJ>
%FGBVMUTUSEPDGJMF
<),&:@$-"44&4@3005=EBU>
%FGBVMUTUSEPDGJMF
<),&:@$-"44&4@3005=SBT>
%FGBVMUTUSEPDGJMF

+HUHVRPHH[WUDPRGHP
VHWWLQJVDUHSRVVLEOH
GHSHQGLQJRIPRGHPW\SH
3671*60*356 

<RXFDQDVVRFLDWHVRPHILOH
H[WHQVLRQWR3RFNHW:RUG
DSSOLFDWLRQIRUHDV\HGLWLQJ
ILOHVFRQWHQWV

<),&:@$-"44&4@3005=QMS>
%FGBVMUTUSEPDGJMF
<),&:@-0$"-@."$)*/&=5JNF;POFT>
%FGBVMUTUS3PNBODF4UBOEBSE5JNF
<),&:@-0$"-@."$)*/&=OMT=PWFSSJEFT>
45JNFTUS=
*5-;SEXPSE
*5JNFEXPSE
45'NUTUS))NNTT

<RXFDQFRPPHQWOLQHFRQWHQWVE\SXWWLQJDWWKHEHJLQQLQJRIOLQH
1RWH4UBSUVQEBUILOHKDVDOVRSDUDPHWHUVWRFRQWURO6%&

3DJHRI

ISKRAEMECO

P2LPC

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.

Page 7 of 34

,6.5$(0(&2

3/3&

3/3&$SSOLFDWLRQ

8VHUFDQFRQWUROEHKDYLRURI3/3&DSSOLFDWLRQLQWHUDFWLYHO\$OOFRPPDQGVDUHVWRUHGXQGHU&RPPDQGPHQX
+HUHLVGHVFULSWLRQRI&RPPDQGPHQXLWHPV


)RUHFH
)RUFH)RUN
)LQG,QVWDOO
SURFHVVRQ'/&
SURFHVVRQ'/&
QHWZRUN
QHWZRUN
)RUFH*OREDO
'HLQVWDOSURFHVV
RQ'/&QHWZRUN

)RUFH
'HLQVWDOO
SURFHVVRQ'/&
QHWZRUN

)RUFHWRH[HFXWH
GDWDUHDGRXWIURP
VXEVWDWLRQV
PHWHUV

6FURROEHWZHHQ
YLHZV
)RUFHWRPDNH
5$6FRQQHFWLRQ
WRVHQGGDWDWR
FROOHFWLQJFHQWHU

5HORDGVRPH
SDUDPHWHUVIURP
3/3&LQLILOHOLNH
SHULRGV



3/3&DSSOLFDWLRQXVHVILOHVIRUSDUDPHWHUL]DWLRQVDQGIRUVWRULQJPHWHUVUHDGLQJVORJJLQJDQGVWDWLVWLF3/3&
XVHV;0/IRUPDWWRVWRUHRUUHDGLQIRUPDWLRQVLQWRRUIURPILOHV3/3&ILOHVDUHGHWDLOHGH[SODLQHGLQ3/3&
)LOH)RUPDWVGRFXPHQW3/3&DSSOLFDWLRQUHDGVDQGZULWHVILOHVRQ&RPSDFW)ODVKFDUG 3/3&)LOHVIROGHULQ
:LQGRZV&(HQYLURQPHQW 
3/3&)LOHVGLUHFWRU\LVFRQQHFWHGZKHQORJRQXVLQJWKHILOHWUDQVIHUSURWRFRO

7KLVLVSHUVLVWHQWPHGLXPZKLFKKROGVGDWDGXULQJSRZHURII)LOHVRQ3/3&DUHGLYLGHGLQWRIROORZLQJJURXSV
 &RQILJXUDWLRQILOHVLQWKLVJURXSDUH
 1-1$YNMLQSXWVHWXSILOHIRU3/3&DSSOLFDWLRQ
 %-$.FUFSTYNMILOHFRQVLVWVOLVWRIIRXQG'/&PHWHUVE\3/3&
 4FSJBM.FUFSTYNMILOHLVWKHILOHRIIRXQGHGVHULDOPHWHUVRQ56QHWZRUNE\3/3&
 5HVXOWVILOHVVWRUHVUHVXOWVRIPHWHUVUHDGLQJV ILOHQDPHIRUPDWLV6XEB;;;;;;;;B<<<<00SOU
ZKHUH;;;;;;;;LVPHWHUGHYLFHLGQXPEHU<<<<LVFXUUHQW\HDUDQG00LVFXUUHQWPRQWK 3/3&
LWVHOIKDVDOVRUHVXOWILOHZKHUHLWVWRUHVUHVXOWVRIZULWHWUDQVDFWLRQVWRPHWHUV ILOHQDPHIRUPDWLV
3/3&B;;;;;;;;B<<<<00SOUZKHUH;;;;;;;;LV3/3&GHYLFHLGQXPEHU<<<<LVFXUUHQW
\HDUDQG00LVFXUUHQWPRQWK 
 3URILOHILOHVVLPLODUWRUHVXOWVILOHVRQO\ORDGSURILOHUHVXOWVDUHVWRUHG ILOHQDPHIRUPDWLV
6XEB;;;;;;;;B<<<<00SOSZKHUH;;;;;;;;LVPHWHUGHYLFHLGQXPEHU<<<<LVFXUUHQW\HDU
DQG00LVFXUUHQWPRQWK 
 (YHQWVILOHVVLPLODUWRSURILOHILOHVRQO\HYHQWV VLPLODUWRSURILOH DUHVWRUHG ILOHQDPHIRUPDWLV
6XEB;;;;;;;;B<<<<00SOHZKHUH;;;;;;;;LVPHWHUGHYLFHLGQXPEHU<<<<LVFXUUHQW\HDU
DQG00LVFXUUHQWPRQWK 
 &RPPDQGILOHVLQWKLVJURXSDUH
 1-1$5BSJGGYNMWDULIIVHWWLQJVILOH3/3&DSSOLFDWLRQGLVWULEXWHVWDULIIVHWWLQJVIURPWKLV
ILOHWR'/&PHWHUV
 1-1$%FNBOE3FBEJOHYNM3/3&SHUIRUPVUHDGLQJRIPHWHUVVSHFLILHGLQWKLVILOH7KLV
ILOHLVVHQGIURPFHQWHUWR3/3&WRSHUIRUPRQGHPDQGUHDGLQJ
 6WDWLVWLFDQGORJILOHVWKLVILOHVDUHLQWH[WIRUPDWDQGVWRUHV'/&VWDWLVWLFDQGDSSOLFDWLRQORJ)LOH
QDPHVVWDUWZLWK1-1$4UBU UYURU1-1$-PH UYU

5HVXOWVSURILOHDQGHYHQWVILOHVFRXOGEHFRPSUHVVHGLI3/3&LVFRQILJXUHGIRUXVLQJFRPSUHVVLRQ:KHQ
FRPSUHVVLRQLVXVHGOHWWHU]LVDGGHGWRILOHH[WHQVLRQ SOU] SOS] SOH] 


3DJHRI

ISKRAEMECO
P2LPC.xml file

P2LPC

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.
.

Page 9 of 34

ISKRAEMECO
Results files

P2LPC

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
plr
plrz
ple
plez
plp
plpz

File Explanation
file containing results
zipped file containing results
file containing events
zipped file containing events
file containing profile readout
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 concentrators 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
Prefix Sub_

Extension P2LPC Results


Device ID (8 places)

Year and month of results

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>

Page 10 of 34

ISKRAEMECO
Profile files

P2LPC

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
Prefix Sub_

Extension P2LPC Profile


Device ID (8 places)

Year and month of results

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"
<Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T01:00:00"
<Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T02:00:00"
<Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T03:00:00"
<Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T04:00:00"
<Register Ident="1.8.0" Value="00029.355" DateTime="2004-01-01T05:00:00"
.
.
.
</Profile>
</Device>

Status="0"
Status="0"
Status="0"
Status="0"
Status="0"
Status="0"

Page 11 of 34

/>
/>
/>
/>
/>
/>

ISKRAEMECO
Statistic and log files

P2LPC

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"
.
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
.
.
.
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
6.3.2003
.
.
.

----extended

13:16:27.000
13:16:27.000
13:16:28.000
13:16:28.000
13:21:05.000
13:21:05.000
13:26:06.000
13:31:00.000
13:31:03.000
13:31:09.000
13:31:26.000
13:31:29.000
13:31:29.000
13:31:50.000
13:31:50.000
13:31:53.000
13:32:03.000

Information
Information
Information
Information
Information
Information
Information
Information
Information
Information
Information
Information
Information
Information
Information
Information
Information

DocThread : Thread started OK


Substations count = 0
Schedule ID = 1 Schedule thread (0008C948)
Schedules Add index = 0
TAPI Line[0] = Hayes Compatible on COM1:
TAPI Line[1] = Iskraemeco Modem
TAPI Line[5] = Serial Cable on COM1:
Start Communication with 21 [0x015]
DoExecuteConnect OK
DoExecuteAARQ OK
Stop Communication with 21 [0x015]
DoExecuteDisconnect OK
Start Communication with 96 [0x060]
DoExecuteConnect FAILED
Start Communication with 22 [0x016]
DoExecuteConnect OK
DoExecuteAARQ OK

13:33:39.000
13:33:42.000
13:33:42.000
13:33:45.000
13:33:55.000
13:34:11.000
13:34:28.000
13:34:28.000
13:34:56.000
13:34:56.000
13:35:29.000
13:35:29.000
13:35:30.000

Information
Information
Information
Information
Information
Information
Information
Information
Information
Information
Information
Information
Information

Stop Communication with 25 [0x019]


DoExecuteDisconnect OK
Start Communication with 23 [0x017]
DoExecuteConnect OK
DoExecuteAARQ OK
Stop Communication with 23 [0x017]
DoExecuteDisconnect OK
Start Communication with 97 [0x061]
DoExecuteConnect FAILED
Start Communication with 98 [0x062]
DoExecuteConnect FAILED
Find DLC slaves START (3 phases)
Finding DLC slaves COMPLETE (All phases)

LogTraceLevel="0"
.
3.10. 12:47:18 - Info
23.10. 12:47:22 - Info
23.10. 12:47:58 - Info
23.10. 12:47:58 - Info
23.10. 12:48:02 - Info
23.10. 12:48:38 - Info
23.10. 12:48:40 - Info
23.10. 12:48:44 - Info
23.10. 12:49:19 - Info
23.10. 12:49:19 - Info
23.10. 12:49:22 - Info
23.10. 12:50:19 - Info
.

----short
-

SchedID=1 retry=6 - DevID[198]="11901692"


Fork DLC 869 [0x365] OK
Finish SchedID=1 - DevID[198]="11901692"
SchedID=1 retry=6 - DevID[199]="11901697"
Fork DLC 874 [0x36A] OK
Finish SchedID=1 - DevID[199]="11901697"
SchedID=1 retry=6 - DevID[200]="35400072"
Fork DLC 395 [0x18B] OK
Finish SchedID=1 - DevID[200]="35400072"
SchedID=1 retry=6 - DevID[201]="11901671"
Fork DLC 848 [0x350] OK
Finish SchedID=1 - DevID[201]="11901671"

OK
OK
OK
OK

Page 12 of 34

,6.5$(0(&2

3/3&
6WDWLVWLFILOHVDUHXVHGIRUPRQLWRULQJFRPPXQLFDWLRQVFRQGLWLRQVRQ'/&QHWZRUN8VHUFDQVHHVXFFHVVUDWH
RIFRPPXQLFDWLRQEHWZHHQ3/3&DQGSDUWLFXODUPHWHUDQGDYDLODELOLW\RISDUWLFXODUPHWHUWR3/3&(YHU\
DFWLRQSHUIRUPHGE\3/3&DQGPHWHUVLVUHFRUGHGLQVWDWLVWLFILOH$IWHUUHDGRXWRU'/&QHWZRUNLQJVHVVLRQ
UHVXOWVDUHXSGDWHGDQGDSSHQGHGWRVWDWLVWLFILOH6WDWLVWLFILOHKDV1-1$4UBUUYUQDPH)RUHYHU\QHZGD\
1-1$4UBUUYUILOHLVUHQDPHGWR3/3&6WDWB<<<<B00B''W[WIRUPDWQDPH:KHQWUDQVIHUWRFROOHFWLQJ
FHQWHURFFXUVDOOVWDWLVWLFVILOHVDUHWUDQVIHUUHGWRGDWDFROOHFWLQJFHQWHU$IWHUWKDWDOOVWDWLVWLFVILOHVDUHGHOHWHG
H[FHSW1-1$4UBUUYU 1-1$4UBUUYUILOHLVUHQDPHGWR3/3&6WDWB<<<<B00B''B++B00B66W[W
IRUPDWQDPHLI3/3&DSSOLFDWLRQLVFORVHG

1-1$4UBUUYUKDVWKHIROORZLQJIRUPDW

1-1$4UBUJTUJD *%1-1$

1-1$4UBSUVQ5JNF
4UBUJTUJDUZQF%-$'JOE
4DIFEVMFTDPVOU


4DIFEVMF*%4DIFEVMF5JNF$PVOU




%-$.BTUFS"EESFTT<Y$>

%-$4MBWFTDPVOU


%-$"EESFTT*OTUBMM-PTU5JNF'PSL5JNF$SFEJUT3451IBTF4VDDFT3BUF"WBJMBCJM

<Y">
<Y>
<Y%>
<Y">3
<Y#>
<Y'>
<Y>
<Y>3
<Y">3
<Y">
<Y>-PTU
<Y">
<Y>-PTU
<Y>
<Y>
<Y>-PTU
<Y>


1-1$4UBUJTUJD&OE


6WDWLVWLFILOHKDVIROORZLQJLQIRUPDWLRQ
 'DWHDQGWLPHRI'/&GDWD
 'DWHDQGWLPHRI3/3&DSSOLFDWLRQVWDUW
 /LVWRIUXQQLQJVFKHGXOHV
 '/&DGGUHVVRI3/3&PDVWHUDGGUHVV
 &RXQWRI'/&VODYHVPHWHUV
 /LVWRI'/&VODYHVZLWKGHFLPDODQGKH[DGGUHVVLQVWDOOORVWWLPHIRUNWLPHFUHGLWV567SKDVH
VXFFHVVUDWHDQGDYDLODELOLW\
 5HSHDWHUVWDWXVRIVODYHVPHWHUV

/LVWRI'/&VODYHVFRQVLVWVRIDOOPHWHUVIRXQGRQ'/&QHWZRUNE\3/3&,IWKHPHWHUGRHVQRWUHVSRQGRQ
'/&IRUNUHTXHVWWKHPHWHULVPDUNHGDVORVW&UHGLWLVWKHQXPEHURIUHSHWLWLRQVRQ'/&PHGLXP3RVVLEOH
YDOXHVIRUFUHGLWVDUHRU/RZHUQXPEHUPHDQVEHWWHUFRQGLWLRQVIRUFRPPXQLFDWLRQZLWKPHWHU
&UHGLWFDQFKDQJHLIFRQGLWLRQVDUHFKDQJHGDIWHU'/&IRUNUHTXHVW
6XFFHVVUDWHLVUDWLREHWZHHQUHDGRXWUHTXHVWVDQGUHDGRXWUHVSRQVHVLQUHDGRXWVHVVLRQ HDFKUHDGRXW
VHVVLRQIRUQRZLVFRQVLVWVRIUHTXHVWUHVSRQVHSDLUV $YDLODELOLW\LVUDWLREHWZHHQQXPEHURIUHDGRXWVHVVLRQV
VWDUWHGRQSDUWLFXODUPHWHUDQGVXFFHVVIXOUHVSRQVHVWRVHVVLRQVWDUW5HDGRXWVHVVLRQZLWKSDUWLFXODUPHWHULV
VWDUWHGRQO\LISDUWLFXODUPHWHUUHVSRQVHVWR'/&QHWZRUNLQJIRUNUHTXHVWV,IPHWHUGRHVQRWUHVSRQGWRIRUN
UHTXHVWLWLVQRWLQFOXGHGWRUHDGRXWVHVVLRQ1XPEHURIUHDGRXWVHVVLRQVIRUSDUWLFXODUPHWHULVHTXDORUORZHU
WKDQWRWDOVFKHGXOHFRXQW

3DJHRI

ISKRAEMECO

P2LPC

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
directory
7. 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

Page 14 of 34

ISKRAEMECO

P2LPC

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.

Page 15 of 34

,6.5$(0(&2

3/3&

&RQQHFWFRQFHQWUDWRUXVLQJ(WKHUQHW
,IFRQFHQWUDWRULVFRQQHFWLQJGLUHFWO\WRFRPSXWHUDFURVVRYHUFDEOHLVXVHG
1H[WWKLQJLVWKHW\SHRIH[LVWLQJQHWZRUN IL[HG,3RU'+&3 ,I'+&3LVXVHGGHIDXOWVHWWLQJVKRXOGVXIILFH7KH
GHIDXOWVHWWLQJVDUHVXFKWKDWWKHFRQFHQWUDWRULVZDLWLQJIRUDVHUYHUWRDVVLJQLWDQDGGUHVV,IWKHUHLVQR'+&3
WKHQDFRQFHQWUDWRUFKRRVHVDQDGGUHVVIURPDSUHGHILQHGUDQJH

7RXVHIL[HG,3DGGUHVVLQJVWDUWXSGDWILOHKDVWREHPRGLILHG

>+.(<B/2&$/B0$&+,1(?&RPP?(1'6,6$?3DUPV?7FSLS@
$XWR0DVN VWU
$XWR6XEQHW VWU
,S$GGUHVV VWU
'HIDXOW*DWHZD\ VWU
6XEQHWPDVN VWU
(QDEOH'+&3 GZRUG

%HFDUHIXOWRFRPPHQWWKHILUVWWZROLQHV,WLVQHHGWRUHVWDUWWKHFRQFHQWUDWRU7KLVFDQEHDFKLHYHGXVLQJWKH
IROORZLQJVHTXHQFHRIFRPPDQGV DIWHUORJJLQJYLD7HOQHW 
VWDUWUHVWDUW


+RZWRPRGLI\6WDUWXSGDWE\UHPRWHFRQQHFWLRQ

6WDUWXSGDWILOHVKRXOGEHSODFHGLQ?6WRUDJH&DUGEXWWKLVGLUHFWRU\LVQRWVHHQE\)73FOLHQW )73URRWLV
ORFDWHGLQ?6WRUDJH&DUG?3/3&)LOHV IROORZLQJSURFHGXUHVKRXOGEHGRQH
 0DNHWHOQHWVHVVLRQWR3/3&FRS\DQGUHQDPH6WDUWXSGDWILOHWR)73URRWGLUHFWRU\
DPQZ=4UPSBHF$BSE=4UBSUVQEBU=4UPSBHF$BSE=1-1$'JMFT=4UBSUVQUNQ

 0DNHIWSVHVVLRQWR3/3&DQGJHW6WDUWXSWPSILOH
 0RGLI\6WDUWXSWPS
 3XWPRGLILHG6WDUWXSWPSILOHEDFNWR3/3&E\IWSSXWFRPPDQG
 5HQDPH6WDUWXSWPSILOHWR6WDUWXSGDWRQ3/3&E\IWSUHQDPHFRPPDQG
 ,I3/3&B:,1&(DSSOLFDWLRQLVUXQQLQJLWDXWRPDWLFDOO\FRS\6WDUWXSGDWILOHLQWR?6WRUDJH&DUG
GLUHFWRU\LIQRWXVHWHOQHWWRFRS\ILOH
 &ORVHRSHQIWSDQGWHOQHWVHVVLRQV


)URP3/3&YHUVLRQ%XLOGXSORDG]LSSHGILOHWRWKH3/3&3/3&8SJUDGH]LS

0DNHIWSVHVVLRQWR3/3&DQGJHW6WDUWXSROGILOH
2QGHVNWRSFRPSXWHUSUHSDUHQHZVWDUWXSGDWDQGRURWKHUQHZ3/3&GHILQLWLRQVILOHDQGFRPSUHVV ]LS DOO
ILOHVLQWR3/3&8SJUDGH]LS5HVWDUWRI3/3&LVGRQHDXWRPDWLFDOO\
'HWDLOVLQWKLVGRFXPHQW8SORDGQHZDSSOLFDWLRQWRWKH3/3&





3DJHRI

ISKRAEMECO

P2LPC

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 ATcommands. 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.
Page 17 of 34

,6.5$(0(&2

3/3&

6HWWLQJWLPH]RQHGDWHDQGWLPHRQ3/3&

7LPH]RQHVHWWLQJVKRXOGEHGRQHE\FKDQJLQJUHJLVWU\VHWWLQJV8VHUFDQFKDQJHRUDGGDGGLWLRQDOUHJLVWU\
VHWWLQJVWURXJKPRGLI\LQJ6WDUWXSGDWILOHRQ3/3&'HIDXOWWLPH]RQHDOUHDG\H[LVWVLQ6WDUWXSGDWXQGHU
+.(<B/2&$/B0$&+,1(?7LPH=RQHVUHJLVWU\NH\7KLVYDOXHVKRXOGEHFKDQJHWRDSSURSULDWHYDOXH

<),&:@-0$"-@."$)*/&=5JNF;POFT>
%FGBVMUTUS3PNBODF4UBOEBSE5JNF

7RVHW3/3&WRXVHWLPH]RQH87&DQGZLWKRXW'67XVHIROORZLQJUHJLVWU\VHWWLQJLQ6WDUWXSGDW

<),&:@-0$"-@."$)*/&=5JNF;POFT>
%FGBVMUTUS8$FOUSBM"GSJDB4UBOEBSE5JNF


1RWHV
 6WDUWXSGDWILOHVKRXOGEHLQ?6WRUDJHFDUGGLUHFWRU\+RZWRPRGLI\6WDUWXSGDWILOHLVH[SODLQHGODWHU
 &KDQJHVLQ6WDUWXSGDWILOHZLOOEHXVHGDIWHUUHVWDUWRI3/3&


+RZWRPRGLI\6WDUWXSGDWE\UHPRWHFRQQHFWLRQ

6WDUWXSGDWILOHVKRXOGEHSODFHGLQ?6WRUDJH&DUGEXWWKLVGLUHFWRU\LVQRWVHHQE\)73FOLHQW )73URRWLV
ORFDWHGLQ?6WRUDJH&DUG?3/3&)LOHV IROORZLQJSURFHGXUHVKRXOGEHGRQH
 0DNHWHOQHWVHVVLRQWR3/3&FRS\DQGUHQDPH6WDUWXSGDWILOHWR)73URRWGLUHFWRU\
DPQZ=4UPSBHF$BSE=4UBSUVQEBU=4UPSBHF$BSE=1-1$'JMFT=4UBSUVQUNQ

 0DNHIWSVHVVLRQWR3/3&DQGJHW6WDUWXSWPSILOH
 0RGLI\6WDUWXSWPS
 3XWPRGLILHG6WDUWXSWPSILOHEDFNWR3/3&E\IWSSXWFRPPDQG
 5HQDPH6WDUWXSWPSILOHWR6WDUWXSGDWRQ3/3&E\IWSUHQDPHFRPPDQG
 ,I3/3&B:,1&(DSSOLFDWLRQLVUXQQLQJLWDXWRPDWLFDOO\FRS\6WDUWXSGDWILOHLQWR?6WRUDJH&DUG
GLUHFWRU\LIQRWXVHWHOQHWWRFRS\ILOH
 &ORVHRSHQIWSDQGWHOQHWVHVVLRQV


)URP3/3&YHUVLRQ%XLOGXSORDG]LSSHGILOHWRWKH3/3&3/3&8SJUDGH]LS

0DNHIWSVHVVLRQWR3/3&DQGJHW6WDUWXSROGILOH
2QGHVNWRSFRPSXWHUSUHSDUHQHZVWDUWXSGDWDQGRURWKHUQHZ3/3&GHILQLWLRQVILOHDQGFRPSUHVV ]LS DOO
ILOHVLQWR3/3&8SJUDGH]LS5HVWDUWRI3/3&LVGRQHDXWRPDWLFDOO\
'HWDLOVLQWKLVGRFXPHQW8SORDGQHZDSSOLFDWLRQWRWKH3/3&

3DJHRI

,6.5$(0(&2

3/3&

8VLQJ173VHUYLFHRQ3/3&DV173FOLHQW

7KLVGRFXPHQWGHVFULEHVKRZWRXVH173VHUYLFHRQ3/3&173VHUYLFHLVUXQQLQJRQ3/3&RQO\IHZ
VHWWLQJVVKRXOGEHGRQHWRVHWDSSURSULDWHSDUDPHWHUV7KHVHSDUDPHWHUVDUHUHJLVWU\YDOXHVXVHGWRFRQWURO
173VHUYLFH7RVHWWKLVUHJLVWU\YDOXHV6WDUWXSGDWILOHVKRXOGEHPRGLILHGE\DGGLQJIROORZLQJ

<),&:@-0$"-@."$)*/&=4FSWJDFT=5JNFTWD>
4FSWFSTUSHPPEUJNFJKTTJ
3FGSFTIEXPSE&
3FDPWFSZ3FGSFTIEXPSE&
$MJFOUPOMZEXPSE

1RWHV
 5HJLVWU\YDOXH6HUYHULV85/WR173VHUYHUXVHGIRUWLPHV\QFKURQL]DWLRQ
 173VHUYHUQDPHVKRXOGEHXVHG QRW,3DGGUHVV 
 5HIUHVKDQG5HFRYHU\5HIUHVKYDOXHVDUHKH[DGHFLPDOLQPLOOLVHFRQGVVPDOOHVWWLPHLVPLQXWHV
PV [( 
 &KDQJHVLQ6WDUWXSGDWILOHZLOOEHXVHGDIWHUUHVWDUWRI3/3&

8VHUFDQFKHFNLI173VHUYLFHLVUXQQLQJE\VHUYLFHVOLVWFRPPDQGIURP7HOQHWRUFRPPDQGSURPSW

TFSWJDFTMJTU
)51Y)551%%--3VOOJOH
5&-YGB5&-/&5%%MM3VOOJOH
'51YGCF'51%%MM3VOOJOH
/51YUJNFTWDEMM3VOOJOH



+RZWRPRGLI\6WDUWXSGDWE\UHPRWHFRQQHFWLRQ

6WDUWXSGDWILOHVKRXOGEHSODFHGLQ?6WRUDJH&DUGEXWWKLVGLUHFWRU\LVQRWVHHQE\)73FOLHQW )73URRWLV
ORFDWHGLQ?6WRUDJH&DUG?3/3&)LOHV IROORZLQJSURFHGXUHVKRXOGEHGRQH
 0DNHWHOQHWVHVVLRQWR3/3&FRS\DQGUHQDPH6WDUWXSGDWILOHWR)73URRWGLUHFWRU\
DPQZ=4UPSBHF$BSE=4UBSUVQEBU=4UPSBHF$BSE=1-1$'JMFT=4UBSUVQUNQ

 0DNHIWSVHVVLRQWR3/3&DQGJHW6WDUWXSWPSILOH
 0RGLI\6WDUWXSWPS
 3XWPRGLILHG6WDUWXSWPSILOHEDFNWR3/3&E\IWSSXWFRPPDQG
 5HQDPH6WDUWXSWPSILOHWR6WDUWXSGDWRQ3/3&E\IWSUHQDPHFRPPDQG
 ,I3/3&B:,1&(DSSOLFDWLRQLVUXQQLQJLWDXWRPDWLFDOO\FRS\6WDUWXSGDWILOHLQWR?6WRUDJH&DUG
GLUHFWRU\LIQRWXVHWHOQHWWRFRS\ILOH
 &ORVHRSHQIWSDQGWHOQHWVHVVLRQV


)URP3/3&YHUVLRQ%XLOGXSORDG]LSSHGILOHWRWKH3/3&3/3&8SJUDGH]LS

0DNHIWSVHVVLRQWR3/3&DQGJHW6WDUWXSROGILOH
2QGHVNWRSFRPSXWHUSUHSDUHQHZVWDUWXSGDWDQGRURWKHUQHZ3/3&GHILQLWLRQVILOHDQGFRPSUHVV ]LS DOO
ILOHVLQWR3/3&8SJUDGH]LS5HVWDUWRI3/3&LVGRQHDXWRPDWLFDOO\
'HWDLOVLQWKLVGRFXPHQW8SORDGQHZDSSOLFDWLRQWRWKH3/3&

3DJHRI

ISKRAEMECO

P2LPC

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" />
.
.
<DLC

; retry 5 times in default schedule unread meters

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"
/>
.
.
</P2LPC>

; is used to quick split DLC network if it is mixed through crosstalk


settable from 1 up to 20.

Page 20 of 34

ISKRAEMECO

P2LPC

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
<SerialMeter
.
.
<SerialMeter
<SerialMeter
</SerialMeters>

Address="17"/>
Address="18"/>
Address="65"/>
Address="66"/>

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.

Page 21 of 34

ISKRAEMECO

P2LPC

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.

Page 22 of 34

ISKRAEMECO

P2LPC

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.

1
2
3
Schedule 1, release
resource, schedule 3
start to execute

Schedule 3, release
resource, schedule 2
start to execute

Schedule 3, ready to
execute, waiting for
free resource
Schedule 2, ready to
execute, waiting for
free resource
Schedule 1, execute,
and free resource

Page 23 of 34

ISKRAEMECO

P2LPC

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.

Page 24 of 34

,6.5$(0(&2

3/3&

'HPDQGUHDGLQJ
3/3&'HPDQG5HDGLQJPHWKRG
'HPDQGUHDGLQJLVDFDSDELOLW\RIWKH3/3&GDWDFRQFHQWUDWRUDSSOLFDWLRQWRDFFHSWGHPDQGVIURPWKH&HQWUH
HQGH[HFXWHWKHPDVVRRQDVSRVVLEOH7KHGHPDQGUHDGLQJPHWKRGLVEDVHGRQWKHSULQFLSOHRISURFHVVLQJWKH
3/3&'HPDQG5HDGLQJ[PO  ILOH 7KLV ILOH FRQWDLQV LQIRUPDWLRQ RQ WKH ,' RI WKH UHTXHVWHG PHWHU DQG WKH
WUDQVDFWLRQVZKLFKQHHGWREHSHUIRUPHGE\WKHGDWDFRQFHQWUDWRU$IWHUWKH3/3&'HPDQG5HDGLQJ[POILOHLV
DFFHSWHGE\WKHDSSOLFDWLRQLWLVUHQDPHGLQWRWKH3/3&'HPDQG5HDGLQJROG
$VVRRQDVWKHDSSOLFDWLRQUXQQLQJRQWKHGDWDFRQFHQWUDWRUGHWHFWVVXFKDILOHLWZLOODWWHPSWILOHSURFHVVLQJ
DQGVWDUWH[HFXWLQJWKHGHVLUHGWUDQVDFWLRQVRQWKHUHTXHVWHGPHWHU+RZHYHUWKHWLPHEHWZHHQDSSHDUDQFHRI
WKH 3/3&'HPDQG5HDGLQJ[PO ILOH DQG LWV GHWHFWLRQ PD\ YDU\ VXEVWDQWLDOLW\ 7KLV LV GXH WR WKH IDFW WKDW WKH
DSSOLFDWLRQFKHFNVIRUWKLVILOHDSSHDUDQFHHYHU\WLPHZKHQLWFRQFOXGHVWKHDFWLYHWUDQVDFWLRQRQWKHFXUUHQWO\
DFWLYH PHWHU WKH WUDQVDFWLRQ GHILQHG LQ WKH 3/3&[PO ILOH EHLQJ SHUIRUPHG RQ WKH HQWLUH PHWHU SRSXODWLRQ 
%HIRUH WKH WUDQVDFWLRQ LV VWDUWHG RQ WKH QH[W PHWHU IURP WKH OLVW WKH DSSOLFDWLRQ FKHFNV LI D GHPDQG UHDGLQJ
QHHGVWREHSHUIRUPHG,IQRWLWFRQWLQXHVZLWKWKHUHDGRXWVFKHGXOHRQWKHQH[WPHWHUIURPWKHOLVW,IWKHUHLVQR
FXUUHQWO\UXQQLQJVFKHGXOHVGHPDQGUHDGLQJVWDUWVLPPHGLDWHO\
'HPDQGUHDGLQJGHOD\
)ROORZLQJ SLFWXUH EHORZ LOOXVWUDWLRQ RI D GHPDQG UHDGLQJ GHOD\ LV VKRZQ ZKHQ GHPDQG UHDGLQJ UHTXHVW LV
UHFHLYHG LQ WKH PLGGOH RI D FXUUHQW VFKHGXOH H[HFXWLRQ )HZ DFWLRQV DUH WDNHQ EHIRUH DFWXDO GHPDQG UHDGLQJ
VWDUWV
GHPDQGUHDGLQJUHTXHVWLVDFFHSWHG
UXQQLQJDFWLYHVFKHGXOHLVLQWHUUXSWHG RWKHUSHQGLQJVFKHGXOHVDUHGLVDEOHG
FXUUHQWPHWHUWUDQVDFWLRQLVILQLVKHG
GHPDQGUHDGLQJVHVVLRQVVWDUWV
,I WKH 3/3& GDWD FRQFHQWUDWRU LV QRW H[HFXWLQJ DQ\ VFKHGXOH GXULQJ UHFHLYLQJ D GHPDQG UHDGLQJ UHTXHVW D
GHPDQGUHDGLQJVHVVLRQVWDUWVLPPHGLDWHO\

1RUPDOVFKHGXOHH[HFXWLRQ
&RQQHFW

6WDUWVHVVLRQ 7UDQVDFWLRQ

7UDQVDFWLRQ

7UDQVDFWLRQ1

'LVFRQQHFW

 'HPDQGUHDGLQJUHTXHVW

 ILQLVKFXUUHQWWUDQVDFWLRQ
JRWRGLVFRQQHFW

 ILQLVKFXUUHQWWUDQVDFWLRQ
VWDUWGHPDQGUHDGLQJ

'HPDQGUHDGLQJ

&RQQHFW

6WDUWVHVVLRQ 7UDQVDFWLRQ

7UDQVDFWLRQ1

'LVFRQQHFW

7LPHEHWZHHQ  DQG  LVGHPDQGUHDGLQJODWHQF\DQGLWWDNHVDERXWVHFRQGV JRRG'/&QHWZRUN


FRQGLWLRQVQRUHWULHV 'HPDQGUHDGLQJLWVHOIIRURQHPHWHUDQGRQHYDOXH LHUHJLVWHU WDNHVDERXWVHFRQGV
JRRG'/&QHWZRUNFRQGLWLRQVQRUHWU\ 7KLVWDEOHVKRZVDSSUR[LPDWHWLPHVIRUGHPDQGUHDGLQJWUDQVDFWLRQV
FRPSOHWLRQ UHDGLQJRQHPHWHUDQGRQHYDOXH 
'/&QHWZRUNFRQGLWLRQV
1RUHWU\
6XFFHVVDIWHUWKLUGUHWU\
9HU\JRRG
VHF
VHF
0HGLXP
VHF
VHF
9HU\EDG
VHF
VHF
3DJHRI

ISKRAEMECO

P2LPC

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
<Transaction
<Transaction
<Transaction
<Transaction

</Transactions>

hourly values / -->


Type="get" ClassId="7"
Type="get" ClassId="7"
Type="get" ClassId="7"
Type="get" ClassId="7"

AttributeId="2"
AttributeId="2"
AttributeId="2"
AttributeId="2"

InstanceId="1.0.99.2.0.255"
InstanceId="1.0.99.1.0.255"
InstanceId="1.0.98.1.0.255"
InstanceId="1.0.98.2.0.255"

ScheduleId="1"/>
ScheduleId="1"/>
ScheduleId="1"/>
ScheduleId="1"/>

Page 26 of 34

ISKRAEMECO

P2LPC

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.

Page 27 of 34

ISKRAEMECO

P2LPC

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\ExtensionAg
ents]"
"3=str:Software\\Iskraemeco\\AMRAgent\\CurrentVersion"
"[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SNMP\Parameters\TrapConfigu
ration\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.

Page 28 of 34

,6.5$(0(&2

3/3&

3/3&:HE6HUYLFH
3/3&:HE6HUYLFHRIIHUVDGLIIHUHQWDSSURDFKIRUKDQGOLQJ3/3&ILOHV3/3&GDWDFRQFHQWUDWRUFROOHFWVGDWD
IURPDWWDFKHGPHWHUVVWRUHVGDWDDQGVHUYHVFROOHFWHGGDWDWRSURFHVVLQJ$00FHQWHU

:HEVHUYLFHLPSOHPHQWHGRQ3/3&GDWDFRQFHQWUDWRUHQDEOHVDFFHVVWRGDWDVWRUHGRQ3/3&GDWD
FRQFHQWUDWRUXVLQJVWDQGDUGZLGHO\DFFHSWHGDQGVLPSOHWHFKQRORJ\ ;0/62$3 3/3&GDWDFRQFHQWUDWRU
VHUYHVUHTXHVWVIURPGDWD$00FHQWHU 6HS: :HEVHUYLFHSURYLGHVPRUHIOH[LEOHDQGRSWLPL]HGDFFHVVWR
GDWDVWRUHGRQ3/3&,QFRQWUDVWWR)73WUDQVIHUZKHUHDOOILOHVDUHWUDQVIHUUHGZHEVHUYLFHH[WUDFWVRQO\
UHTXHVWHGGDWD7KLVUHGXFHVWUDIILFDQGFRVWUHVXOWLQJEHWWHUSHUIRUPDQFHDQGPRUHRSWLPL]HGV\VWHP

$FWLYDWLRQ:HE6HUYLFHLQ3/3&
:HEVHUYLFHLVDFWLYDWHGE\VHWWLQJSDUDPHWHUVLQTUBSUVQEBUILOH
+RZWRPRGLI\6WDUWXSGDWE\UHPRWHFRQQHFWLRQVHH6HWWLQJWLPH]RQHGDWHDQGWLPHRQ3/3&

<),&:@$633&/5@64&3=4PGUXBSF=*4,3"&.&$0="VUP-BVODI>
TUS4UPSBHF$BSE=*OTUBMM8FC4FSWJDFFYF

7RRO 
3/3&:HE6HUYLFH&OLHQW
:HEVHUYLFHFOLHQWLV6:WRROWRFRPPXQLFDWHZLWK3/3&:HE6HUYLFH
&OLHQWLVUXQZLWKVWDUW3/3&:HE6HUYLFH&OLHQWH[H
6SMIUUQ*1@1-1$XFCTFSWJDFXTEM
:HEVHUYLFH
$ZHEVHUYLFHLVDFROOHFWLRQRISURWRFROVDQGVWDQGDUGVXVHGIRUH[FKDQJLQJGDWDEHWZHHQDSSOLFDWLRQV
6RIWZDUHDSSOLFDWLRQVZULWWHQLQYDULRXVSURJUDPPLQJODQJXDJHVDQGUXQQLQJRQYDULRXVSODWIRUPVFDQXVHZHE
VHUYLFHVWRH[FKDQJHGDWDRYHUFRPSXWHUQHWZRUNVOLNHWKH,QWHUQHW7KLVLQWHURSHUDELOLW\LVGXHWRWKHXVHRI
RSHQVWDQGDUGV2$6,6DQGWKH:&DUHWKHVWHHULQJFRPPLWWHHVUHVSRQVLEOHIRUWKHDUFKLWHFWXUHDQG
VWDQGDUGL]DWLRQRIZHEVHUYLFHV7RLPSURYHLQWHURSHUDELOLW\EHWZHHQZHEVHUYLFHLPSOHPHQWDWLRQVWKH:6,
RUJDQL]DWLRQKDVEHHQGHYHORSLQJDVHULHVRISURILOHVWRIXUWKHUGHILQHWKHVWDQGDUGVLQYROYHG
6WDQGDUGVXVHG






:HE6HUYLFHV3URWRFRO6WDFN7RUHLWHUDWHZHE
VHUYLFHVFRQVLVWRIDFROOHFWLRQRIVWDQGDUGVDQG
SURWRFROV7KLVFROOHFWLRQLVNQRZQDVWKHZHE
VHUYLFHVSURWRFROVWDFN
;0/$OOGDWDWREHH[FKDQJHGLVIRUPDWWHGZLWK
;0/WDJV7KLVHQFRGLQJFDQEHSHUIRUPHGE\
62$3RU;0/53&
&RPPRQSURWRFROV;0/GDWDFDQEHWUDQVSRUWHG
EHWZHHQDSSOLFDWLRQVXVLQJFRPPRQSURWRFROV
VXFKDV+773)73DQG6073
:6'/7KHSXEOLFLQWHUIDFHWRWKHZHEVHUYLFHLV
GHVFULEHGE\:HE6HUYLFHV'HVFULSWLRQ
/DQJXDJHRU:6'/7KLVLVDQ;0/EDVHG
VHUYLFHGHVFULSWLRQRQKRZWRFRPPXQLFDWHXVLQJ
WKHZHEVHUYLFH
8'',7KHZHEVHUYLFHLQIRUPDWLRQLVSXEOLVKHG
XVLQJWKLVSURWRFRO,WHQDEOHVDSSOLFDWLRQVWRORRN
XSZHEVHUYLFHVLQIRUPDWLRQLQRUGHUWRGHWHUPLQH
ZKHWKHUWRXVHWKHP

3/3&:HE6HUYLFHLPSOHPHQWDWLRQOLVW
3/3&:HE6HUYLFHDQGLWVFRPSRQHQWVDUHGHWDLOHGH[SODLQHGLQ6SHFLILFDWLRQ3/3&:HE6HUYLFHGRF
GRFXPHQW

3/3&:HE6HUYLFHLVDFRPSRQHQWRI3/3&GDWDFRQFHQWUDWRURIIHULQJDGLIIHUHQWDSSURDFKIRUKDQGOLQJILOHV
3/3&GDWDFRQFHQWUDWRUXVHVDQGJHQHUDWHV,WVIXQFWLRQDOLW\LVYLVLEOHWRXVHUDVDVHWRIIROORZLQJPHWKRGV

 *HW*URXSV
 *HW0HWHUV/LVW


3DJHRI

,6.5$(0(&2
 *HW0HWHUV/LVW%\*URXS
 *HW0HWHU5HVXOWV
 *HW0HWHU3URILOH
 *HW0HWHU6WDWXV
 *HW0HWHU7DULII6HWWLQJV
 6HW0HWHU7DULII6HWWLQJV
 *HW0HWHU(YHQWV
 *HW0HWHU3RZHU)DLOXUHV
 *HW0HWHU2Q'HPDQG5HVXOWV
 *HW&RQFHQWUDWRU5HVXOWV
 *HW&RQFHQWUDWRU6WDWXV
 *HW&RQFHQWUDWRU(YHQWV
 *HW&RQFHQWUDWRU6\VWHP7LPH
 6HW&RQFHQWUDWRU6\VWHP7LPH
 *HW9HUVLRQ
 *HW0HWHU/RDG&RQWURO
 6HW0HWHU/RDG&RQWURO
 *HW0HWHU6HUYLFH&RQWURO
 6HW0HWHU6HUYLFH&RQWURO
 *HW0HWHU'LVFRQQHFW&RQWURO
 6HW0HWHU'LVFRQQHFW&RQWURO
 6HW7UDQVSRUW.H\
 6HW(QFU\SWLRQ.H\
 6HW0HWHU(QFU\SWLRQ.H\
 6HW0HWHU3XUFKDVH
 *HW0HWHU3XUFKDVH7UDQVDFWLRQV
 *HW&RQFHQWUDWRU&RQILJ,G
 6HW&RGH5HG
 *HW0HWHU&RGH5HG6WDWXV
 *HW0HWHU&RGH5HG3RZHU/LPLW
 6HW0HWHU&RGH5HG3RZHU/LPLW
 7LPH6\QF
 8SJUDGH0HWHUV
 *HW'LUHFWRULHV
 *HW)LOHV
 *HW)LOH6L]H
 'RZQORDG)LOH&KXQN
 8SORDG)LOH&KXQN
 'HOHWH)LOH
 ([HFXWH$FWLRQ
 &RVHP*HW5HTXHVW
 &RVHP*HW5HTXHVW([
 &RVHP6HW5HTXHVW
 &RVHP$FWLRQ5HTXHVW
 *HW([FOXGH0HWHU/LVW
 6HW([FOXGH0HWHU/LVW
 *HW0HWHU'LVSOD\/LVW
 6HW0HWHU'LVSOD\/LVW
 *HW0HWHU3RZHU/LPLW
 6HW0HWHU3RZHU/LPLW
 *HW0HWHU3URILOH&RQILJ
 6HW0HWHU3URILOH&RQILJ
 *HW0HWHU/RDG3URILOH3HULRG
 6HW0HWHU/RDG3URILOH3HULRG
 *HW0HWHU%LOOLQJ5HDG7LPH
 6HW0HWHU%LOOLQJ5HDG7LPH
 *HW0HWHU6FKHGXOHG5HDG7LPHV
 6HW0HWHU6FKHGXOHG5HDG7LPH


3/3&

3DJHRI

ISKRAEMECO

Appendix:

P2LPC

P2LPC events codes and strings

Current list of concentrator events codes and strings:


// Event groups
#define EVENT_GROUP_SYSTEM
#define EVENT_GROUP_DLC
#define EVENT_GROUP_COMMUNICATION
#define EVENT_GROUP_SUBSTATION

1
2
3
4

// Event types
#define EVENT_TYPE_SYS_STARTUP
#define EVENT_TYPE_SYS_EXIT
#define EVENT_TYPE_SYS_RESTART
#define EVENT_TYPE_SYS_DEVICE_ID
#define EVENT_TYPE_SYS_PARAMS_OK
#define EVENT_TYPE_SYS_CONFIG_OK
#define EVENT_TYPE_SYS_PARAMS_ERROR
#define EVENT_TYPE_SYS_CONFIG_ERROR
#define EVENT_TYPE_SYS_READING_ERROR
#define EVENT_TYPE_SYS_READING_SESSION_ERROR
#define EVENT_TYPE_SYS_READING_TRANS_ERROR
#define EVENT_TYPE_SYS_DEMAND_READING_ERROR
#define EVENT_TYPE_SYS_DEMAND_READING_SESSION_ERROR
#define EVENT_TYPE_SYS_DEMAND_READING_TRANS_ERROR
#define EVENT_TYPE_SYS_DEMAND_READING_XML_OK
#define EVENT_TYPE_SYS_DEMAND_READING_XML_ERROR
#define EVENT_TYPE_SYS_TARIFF_XML_OK
#define EVENT_TYPE_SYS_TARIFF_XML_ERROR
#define EVENT_TYPE_SYS_DLC_METERS_XML_ERROR
#define EVENT_TYPE_SYS_THREAD_START_ERROR
#define EVENT_TYPE_SYS_HDLC_ERROR
#define EVENT_TYPE_SYS_MEMORY_ERROR
#define EVENT_TYPE_SYS_SERIAL_METERS_XML_ERROR
#define EVENT_TYPE_SYS_SAVE_THREAD_ERROR

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define

25
26
27
28
29
30
31
32
33
34
35
36

EVENT_TYPE_SYS_TIME_SYNC
EVENT_TYPE_SYS_CODE_RED
EVENT_TYPE_SYS_UPGRADE_START
EVENT_TYPE_SYS_UPGRADE_START_SECTION
EVENT_TYPE_SYS_UPGRADE_FILE_ERROR
EVENT_TYPE_SYS_UPGRADE_START_MISSING
EVENT_TYPE_SYS_UPGRADE_FINISH
EVENT_TYPE_SYS_UPGRADE_FINISH_SECTION
EVENT_TYPE_SYS_KEYS_FILE_OK
EVENT_TYPE_SYS_KEYS_FILE_ERROR
EVENT_TYPE_SYS_RESULTS_FILE_ERROR
EVENT_TYPE_SYS_UPGRADE_START_ACTIVATE

#define EVENT_TYPE_DLC_INSTALL
#define EVENT_TYPE_DLC_DEINSTALL
#define EVENT_TYPE_DLC_GLOBAL_DEINSTALL
#define EVENT_TYPE_DLC_DOUBLE_ADDRESS
#define EVENT_TYPE_DLC_ADD_SUBSTATION
#define EVENT_TYPE_DLC_NETWORK_ERROR
#define EVENT_TYPE_DLC_NEW_ADDRESS
addressing)
#define EVENT_TYPE_DLC_SLAVE_LOST
#define EVENT_TYPE_DLC_SLAVE_DELETE
#define EVENT_TYPE_DLC_SLAVE_EXISTS
addressing)

1
2
3
4
5
6
7

// DLC general error


// DLC new address assigned to slave (dynamic DLC

8
9
10

// DLC slave not responds to fork


// DLC slave delete due to not responding to master
// DLC slave address already exists (old DLC

#define
#define
#define
#define
#define
#define

EVENT_TYPE_COM_OPEN_PORT_ERROR
EVENT_TYPE_COM_PHY_LAYER_ERROR
EVENT_TYPE_COM_GSM_MODEM_ERROR
EVENT_TYPE_COM_RAS_SERVER_ERROR
EVENT_TYPE_COM_PPP_CONNECT
EVENT_TYPE_COM_PPP_DISCONNECT

1
2
3
4
5
6

#define
#define
#define
#define

EVENT_TYPE_SUB_TARIFF_WRITE_OK
EVENT_TYPE_SUB_TARIFF_WRITE_ERROR
EVENT_TYPE_SUB_TARIFF_ACTIVATE_OK
EVENT_TYPE_SUB_TARIFF_ACTIVATE_ERROR

1
2
3
4

#define EVENT_TYPE_SUB_SET_ENCRYPTION_KEY_OK
#define EVENT_TYPE_SUB_SET_ENCRYPTION_KEY_ERROR

5
6

Page 31 of 34

ISKRAEMECO
// Event group strings
#define EVENT_GROUP_STRING_NONE
#define EVENT_GROUP_STRING_SYSTEM
#define EVENT_GROUP_STRING_DLC
#define EVENT_GROUP_STRING_COMMUNICATION
#define EVENT_GROUP_STRING_SUBSTATION

P2LPC
(_T("NON."))
(_T("SYS."))
(_T("DLC."))
(_T("COM."))
(_T("SUB."))

// Event type strings


#define EVENT_TYPE_STRING_UNKNOWN

(_T("Unknown"))

#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define

EVENT_TYPE_SYS_STRING_STARTUP
EVENT_TYPE_SYS_STRING_EXIT
EVENT_TYPE_SYS_STRING_RESTART
EVENT_TYPE_SYS_STRING_DEVICE_ID
EVENT_TYPE_SYS_STRING_PARAMS_OK
EVENT_TYPE_SYS_STRING_CONFIG_OK
EVENT_TYPE_SYS_STRING_PARAMS_ERROR
EVENT_TYPE_SYS_STRING_CONFIG_ERROR
EVENT_TYPE_SYS_STRING_READING_ERROR
EVENT_TYPE_SYS_STRING_READING_SESSION_ERROR
EVENT_TYPE_SYS_STRING_READING_TRANS_ERROR
EVENT_TYPE_SYS_STRING_DEMAND_READING_ERROR
EVENT_TYPE_SYS_STRING_DEMAND_READING_SESSION_ERROR
EVENT_TYPE_SYS_STRING_DEMAND_READING_TRANS_ERROR
EVENT_TYPE_SYS_STRING_DEMAND_READING_XML_OK
EVENT_TYPE_SYS_STRING_DEMAND_READING_XML_ERROR
EVENT_TYPE_SYS_STRING_TARIFF_XML_OK
EVENT_TYPE_SYS_STRING_TARIFF_XML_ERROR
EVENT_TYPE_SYS_STRING_DLC_METERS_XML_ERROR
EVENT_TYPE_SYS_STRING_THREAD_START_ERROR
EVENT_TYPE_SYS_STRING_HDLC_ERROR
EVENT_TYPE_SYS_STRING_MEMORY_ERROR
EVENT_TYPE_SYS_STRING_SERIAL_METERS_XML_ERROR
EVENT_TYPE_SYS_STRING_SAVE_THREAD_ERROR

(_T("Startup"))
(_T("Exit"))
(_T("Restart"))
(_T("DeviceId"))
(_T("ParamsOK"))
(_T("ConfigOK"))
(_T("ParamsError"))
(_T("ConfigError"))
(_T("ReadingError"))
(_T("ReadingSessionError"))
(_T("ReadingTransError"))
(_T("DemandReadingError"))
(_T("DemandReadingSessionError"))
(_T("DemandReadingTransError"))
(_T("DemandReadingXMLOK"))
(_T("DemandReadingXMLError"))
(_T("TariffXMLOK"))
(_T("TariffXMLError"))
(_T("DLCMetersXMLError"))
(_T("ThreadStartError"))
(_T("HDLCError"))
(_T("MemoryError"))
(_T("SerialMetersXMLError"))
(_T("SaveThreadError"))

#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define
#define

EVENT_TYPE_SYS_STRING_TIME_SYNC
EVENT_TYPE_SYS_STRING_CODE_RED
EVENT_TYPE_SYS_STRING_UPGRADE_START
EVENT_TYPE_SYS_STRING_UPGRADE_START_SECTION
EVENT_TYPE_SYS_STRING_UPGRADE_FILE_ERROR
EVENT_TYPE_SYS_STRING_UPGRADE_START_ACTIVATE
EVENT_TYPE_SYS_STRING_UPGRADE_START_MISSING
EVENT_TYPE_SYS_STRING_UPGRADE_FINISH
EVENT_TYPE_SYS_STRING_UPGRADE_FINISH_SECTION
EVENT_TYPE_SYS_STRING_KEYS_FILE_OK
EVENT_TYPE_SYS_STRING_KEYS_FILE_ERROR
EVENT_TYPE_SYS_STRING_RESULTS_FILE_ERROR

(_T("TimeSync"))
(_T("CodeRed"))
(_T("UpgradeStart"))
(_T("UpgradeStartSection"))
(_T("UpgradeFileError"))
(_T("UpgradeStartActivate"))
(_T("UpgradeStartMissing"))
(_T("UpgradeFinish"))
(_T("UpgradeFinishSection"))
(_T("P2LPCKeysOK"))
(_T("P2LPCKeysError"))
(_T("ResultsFileError"))

#define
#define
#define
#define
#define
#define
#define
#define
#define
#define

EVENT_TYPE_DLC_STRING_INSTALL
EVENT_TYPE_DLC_STRING_DEINSTALL
EVENT_TYPE_DLC_STRING_GLOBAL_DEINSTALL
EVENT_TYPE_DLC_STRING_DOUBLE_ADDRESS
EVENT_TYPE_DLC_STRING_ADD_SUBSTATION
EVENT_TYPE_DLC_STRING_NETWORK_ERROR
EVENT_TYPE_DLC_STRING_NEW_ADDRESS
EVENT_TYPE_DLC_STRING_SLAVE_LOST
EVENT_TYPE_DLC_STRING_SLAVE_DELETE
EVENT_TYPE_DLC_STRING_SLAVE_EXISTS

(_T("Install"))
(_T("Deinstall"))
(_T("GlobalDeinstall"))
(_T("DoubleAddress"))
(_T("AddSubstation"))
(_T("NetworkError"))
(_T("NewAddress"))
(_T("SlaveLost"))
(_T("SlaveDelete"))
(_T("SlaveExists"))

#define
#define
#define
#define
#define
#define

EVENT_TYPE_COM_STRING_OPEN_PORT_ERROR
EVENT_TYPE_COM_STRING_PHY_LAYER_ERROR
EVENT_TYPE_COM_STRING_GSM_MODEM_ERROR
EVENT_TYPE_COM_STRING_RAS_SERVER_ERROR
EVENT_TYPE_COM_STRING_PPP_CONNECT
EVENT_TYPE_COM_STRING_PPP_DISCONNECT

(_T("OpenPortError"))
(_T("PhyLayerError"))
(_T("GSMModemError"))
(_T("RASServerError"))
(_T("PPPConnect"))
(_T("PPPDisconnect"))

#define
#define
#define
#define

EVENT_TYPE_SUB_STRING_TARIFF_WRITE_OK
EVENT_TYPE_SUB_STRING_TARIFF_WRITE_ERROR
EVENT_TYPE_SUB_STRING_TARIFF_ACTIVATE_OK
EVENT_TYPE_SUB_STRING_TARIFF_ACTIVATE_ERROR

(_T("TariffWriteOK"))
(_T("TariffWriteError"))
(_T("TariffActivateOK"))
(_T("TariffActivateError"))

#define EVENT_TYPE_SUB_STRING_SET_ENCRYPTION_KEY_OK
#define EVENT_TYPE_SUB_STRING_SET_ENCRYPTION_KEY_ERROR

(_T("SetEncryptionKeyOK"))
(_T("SetEncryptionKeyError"))

Page 32 of 34

ISKRAEMECO

Appendix:

P2LPC

transactions samples

Default transaction (implicitly included)


<Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.96.1.0.255" ScheduleId="1"/>
<Transaction Type="get" ClassId="8" AttributeId="2" InstanceId="0.0.1.0.0.255" ScheduleId="1"/>
<Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.42.0.0.255" ScheduleId="1"/>

read device id
read current time
read logical device name

Current values
<Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.0.255" ScheduleId="1"/>
<Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.1.255" ScheduleId="1"/>
<Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.2.255" ScheduleId="1"/>
<Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.3.255" ScheduleId="1"/>
<Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.4.255" ScheduleId="1"/>

read meter register value, T0


read meter register value, T1
read meter register value, T2
read meter register value, T3
read meter register value, T4

Maximum Demand
<Transaction Type="get" ClassId="4" AttributeId="2" InstanceId="1.0.1.6.0.255" ScheduleId="2"/>
<Transaction Type="get" ClassId="4" AttributeId="2" InstanceId="1.0.1.6.1.255" ScheduleId="2"/>
<Transaction Type="get" ClassId="4" AttributeId="2" InstanceId="1.0.1.6.2.255" ScheduleId="2"/>

read maximum demand value, T0, current billing period


read maximum demand value, T1, current billing period
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"/>
<Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.99.2.0.255" ScheduleId="4"/>

read Load Profile 1 values (1.8.0 register profile)


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" />
<Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.98.2.0.255" ScheduleId="4" />

read Billing Profile 1


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>
<Transaction Type="set" ClassId="7" AttributeId="4" InstanceId="1.0.99.2.0.255" ScheduleId="3"/>

to 3600 seconds (1 hour)


change Load Profile 2 profiling perod .

Page 33 of 34

ISKRAEMECO

P2LPC

<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"/>
<Transaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.3.1.8.0.255" ScheduleId="3"/>

read meter register value, impulse input 1


read meter register value, impulse input 2

Tariff
<Transaction Type="get" ClassId="20" AttributeId="2" InstanceId="0.0.13.0.0.255" ScheduleId="3"/>
<Transaction Type="get" ClassId="20" AttributeId="6" InstanceId="0.0.13.0.0.255" ScheduleId="3"/>
<Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.128.10.3.255" ScheduleId="3"/>
<Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.128.10.0.255" ScheduleId="3"/>
<Transaction Type="set" ClassId="1" AttributeId="2" InstanceId="0.0.128.10.0.255" ScheduleId="3"/>

read name of active tariff program


read name of passive tariff program
read current active tariff
read tariff control register
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"/>
<Transaction Type="get" ClassId="7" AttributeId="2" InstanceId="1.0.99.97.0.255" ScheduleId="3"/>
<Transaction Type="get" ClassId="1" AttributeId="2" InstanceId="0.0.97.97.0.255" ScheduleId="3"/>

read logbook (event log)


read long power failures log
read Fatal Fault register

Exclusion of default reading transactions


<ExcludeTransaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.0.255" ScheduleId="0"/>
<ExcludeTransaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.1.255" ScheduleId="0"/>
<ExcludeTransaction Type="get" ClassId="3" AttributeId="2" InstanceId="1.0.1.8.2.255" ScheduleId="0"/>

Page 34 of 34

ScheduleId="0" : all SsceduleID


these are transactions performed without any user
definitions
if LP2 is used they should be excluded