User's Manual

RTM Elster AMCO applicative PFS Coronis Systems
5.7.4.“leak event table” reading management
RTM Elster AMCO stores in an internal table, the pieces of information relative to the occurrence, or the
disappearance of the leaks.
 Reading request data format
Applicative command
1 byte
0x04
 Reading acknowledgment data format
The total length is 74 Bytes
Applicative
acknowledgment
command
Generic header
Leak Event
0
(most recent)
Leak Event
1
Leak Event
2
Leak Event
3
Leak Event
4
1 byte
23 bytes 10 bytes 10 bytes 10 bytes 10 bytes 10 bytes
0x84
(*) (*) (*) (*) (*)
(*) : when no event has been detected, the table is filled with 0x00.
when only one event has been detected, only “Leak Event 0” field is filled with the corresponding leak
detected event.
If a second leak is detected, then the previous one moved in “Leak Event 1” field and the second one
filled “Leak Event 0” field.
The table is a circular buffer which can store up to 5 events, and has the following structure:
Status Consumption-rate Date
1 byte 2 bytes 7 bytes
Leak Event
0
Status_Evt 0 ConsRate_Evt 0 Date_Evt 0
Leak Event
1
Status_Evt 1 ConsRate_Evt 1 Date_Evt 1
Leak Event
2
Status_Evt 2 ConsRate_Evt 2 Date_Evt 2
Leak Event
3
Status_Evt 3 ConsRate_Evt 3 Date_Evt 3
Leak Event
4
Status_Evt 4 ConsRate_Evt 4 Date_Evt 4
EVO RTM-UserMan 51