Coronis Systems EVO MODULE WHICH ALLOWS DATA COLLECTION OF WATER User Manual RTM Elster AMCO applicative PFS

Coronis Systems MODULE WHICH ALLOWS DATA COLLECTION OF WATER RTM Elster AMCO applicative PFS

USERS MANUAL

Download: Coronis Systems EVO MODULE WHICH ALLOWS DATA COLLECTION OF WATER User Manual RTM Elster AMCO applicative PFS
Mirror Download [FCC.gov]Coronis Systems EVO MODULE WHICH ALLOWS DATA COLLECTION OF WATER User Manual RTM Elster AMCO applicative PFS
Document ID877545
Application IDCk4O9/lT0CTx2HWKYc6lFQ==
Document DescriptionUSERS MANUAL
Short Term ConfidentialNo
Permanent ConfidentialNo
SupercedeNo
Document TypeUser Manual
Display FormatAdobe Acrobat PDF - pdf
Filesize47.1kB (588690 bits)
Date Submitted2007-12-10 00:00:00
Date Available2007-12-11 00:00:00
Creation Date2007-11-13 17:28:57
Producing SoftwareStarOffice 7
Document Lastmod0000-00-00 00:00:00
Document TitleRTM Elster AMCO applicative PFS

RTM Elster AMCO applicative PFS
Coronis Systems
EVO RTM Applicative Reference
Guide
Users Manual
EVO RTM-UserMan
RTM Elster AMCO applicative PFS
Coronis Systems
Coronis Systems
RTM Elster AMCO Products,
EVO RTM-UserMan
RTM Elster AMCO applicative PFS
Coronis Systems
Revision History
Rev.
Description
Author
Date
Comments
Original document
AMR
15 Sept 2006
Draft
Updated document
AMR
21 Sept 2006
Correspondence with
CDS Sections added
Updated document
AMR
06 Oct 2006
Modifications following meeting between
Elster AMCO & CORONIS in OCALA from
25th to 27th of September 2006
Updated document
AMR
19 Oct 2006
Coronis internal revision only
not distributed
Updated document
AMR
13 Nov 2006
Approval form added
Updated document
AMR
15 Nov 2006
Update concerning RTM limitations in Drive
By and Walk By operating mode
Updated document
AMR
04 Dec 2006
Update based on Bruce A. Bharat comments
on revision 6 of the document
Updated document
AMR
24 Jan 2007
Update based on Bruce A. Bharat comments
on revision 7 of the document
22 Feb 2007
1) Update based on Elster AMCO comments
on revision 8 of the document
2) Filtering algorithm added with
activation/deactivation capabilities
08 Mar 2007
Corrections added :
- parameters ID were false in
Appendix A (encoder unit A & B),
- Radio address description added and
sRTM reference added (§6)
- Frame length correction in §5.5.5
(TOU Buckets readings with 4 port
connected)
- Datalogging parameter description
added in section §5.5.3
22 Mar 2007
Corrections added :
- Several default value ( in chapters and
appendix A ),
- Several parameters size ( in chapters
and appendix A ),
- Several access right in appendix A,
- Definition of the offset in records
datalogging table in §5.5.4,
- Wrong command examples in §5.6.3,
- Acknowledgment in §5.12.2.
23 Mar 2007
Corrections added :
- Restriction on the index sampling period
when TOU Buckets function is activated
(§5.5.5)
26 Mar 2007
Corrections added :
- Default value corrected for TOU
Buckets parameter (0x60), alarm
frame path (0x5A,0x5B,0x5C,0x5D) and
Step time of pseudo bubble up
transmission
03 Apr 2007
Corrections added :
- Default filled value corrected for leak
event table in §5.7.4
- Restriction on the 2 LSB bits of step
time bubble up (§5.6.1).
10
11
12
13
14
EVO RTM-UserMan
Updated document
Updated document
Updated document
Updated document
Updated document
Updated document
AMR
AMR
SDA
SDA
SDA
SDA
RTM Elster AMCO applicative PFS
Rev.
15
Description
Updated document
Coronis Systems
Author
AMR
Date
26 Jul 2007
Comments
Corrections added :
- §4.1: Data max length correction (173
instead of 174),
- §4.2.2: comments added when writing
only operating mode,
- §5.4.6: error corrected in Encoder Unit
LSB Byte description,
- §5.4.7: details on encoder data returned
- §5.12: added part for alarm window
configuration (new feature) that permits to
enable alarm frames even if pseudo bubbleup is activated without generating possible
collisions.
16
Updated document
SDA/AMR
15 Oct 2007
Corrections added :
- Completely remove from document the
“Sampling activation type parameter”
- Few other corrections
17
Updated document
AMR
18 Oct 2007
Appendix C added:
related to Wavenis products Service
Commands
EVO RTM-UserMan
RTM Elster AMCO applicative PFS
Coronis Systems
DOCUMENT CONTROL AND APPROVAL
Document Name
Revision
Author
Date
EVO RTM-UserMan
17
Adam Molnar
18 October 2007
Name
Title
Company
Bruce A. Bharat
Product/Project
Manager
Elster AMCO
Name
Title
Company
John Rouse
VP Sales - North
America
Coronis Systems
Victor Razanatsimba
Project Manager
Coronis Systems
Adam Molnar
Project Technical
Manager
Coronis Systems
Date
Sign off approval
Date
Sign off approval
This device complies with part 15 of the FCC rules. Operation is subject to
the following two conditions: This device may not cause harmful
interference, and this device must accept any interference received
including interference that may cause undesired operation.
Caution: Any changes or modification not expressly approved by
CORONIS-SYSTEMS could void the user's authority to operate the
equipment.
EVO RTM-UserMan
RTM Elster AMCO applicative PFS
Coronis Systems
TABLE OF CONTENTS
1.DEFINITIONS...................................................................................................................................................7
2.INTRODUCTION............................................................................................................................................10
3.REFERENCE DOCUMENTS.........................................................................................................................10
4.RTM ELSTER AMCO CONFIGURATION ACCESS......................................................................................11
4.1.Radio exchange principle............................................................................................................................11
4.2.Internal parameters access.........................................................................................................................13
4.2.1.Reading internal parameters..........................................................................................................13
4.2.2.Writing internal parameters............................................................................................................14
4.3.Control bytes description.............................................................................................................................15
4.3.1.Profile selection..............................................................................................................................15
4.3.2.Operating Mode..............................................................................................................................16
4.3.3. Alarm Configuration.......................................................................................................................17
4.3.4.Application Status...........................................................................................................................18
4.3.5.Leakage Detection Status..............................................................................................................19
4.4.Writing RTC parameter...............................................................................................................................20
4.5.Meter reading sampling period configuration..............................................................................................21
4.5.1.Reading sampling period parameter..............................................................................................21
4.5.2.Sampling activation type parameter...............................................................................................21
5.RTM ELSTER AMCO FUNCTIONALITIES...................................................................................................22
5.1.Fixed Network/Walk By/ Drive By switching method...................................................................................22
5.2.Datalogging management...........................................................................................................................22
5.2.1.Datalogging parameters access....................................................................................................23
5.2.2.Datalogging mode activation..........................................................................................................24
5.2.3.Datalogging in time steps...............................................................................................................24
5.2.4.Datalogging once a week...............................................................................................................24
5.2.5.Datalogging once a month.............................................................................................................25
5.3.RTM-Register interface...............................................................................................................................26
5.3.1.Pulse register three wire interface..................................................................................................26
5.3.2.Encoder three wire interface..........................................................................................................27
5.4.RTM-register pairing....................................................................................................................................29
5.4.1.Programming current register reading (pulse register only)..........................................................29
5.4.2.Programming pulse value (pulse register only)..............................................................................30
5.4.3.Definition of the pulse value parameters........................................................................................30
5.4.4.Programming meter model (pulse register only)............................................................................31
5.4.5.Encoder model detection...............................................................................................................33
5.4.6.Encoder Unit (Encoder register only).............................................................................................34
5.4.7.Reading encoder internal data (Encoder only)...............................................................................35
5.5.RTM reading management..........................................................................................................................36
5.5.1.Generic header structure...............................................................................................................36
5.5.2.Current register reading.................................................................................................................37
5.5.3.Daily consumption profile reading..................................................................................................38
5.5.4.Datalogging table reading..............................................................................................................40
EVO RTM-UserMan
RTM Elster AMCO applicative PFS
Coronis Systems
5.5.5.Time Of Use (TOU) buckets configuration and readings...............................................................43
5.6.Automatic Radio transmission
(pseudo bubble up mode - Fixed Network Only)...........................45
5.6.1.Pseudo bubble up parameters list..................................................................................................45
5.6.2.Pseudo bubble up allowed commands list.....................................................................................45
5.6.3.Example.........................................................................................................................................46
5.7.Leak detection management.......................................................................................................................47
5.7.1.Residual leak detection..................................................................................................................47
5.7.2.Extreme leak detection...................................................................................................................48
5.7.3.Leak detection parameters list.......................................................................................................49
5.7.4.“leak event table” reading management........................................................................................50
5.8.back flow detection management (encoder only)........................................................................................52
5.8.1.back flow detection parameters list................................................................................................52
5.8.2.Reading back flow detection..........................................................................................................53
5.9.Tamper detection (pulse register only)........................................................................................................54
5.9.1.Tamper detection parameters list...................................................................................................54
5.9.2.Reading Tamper detection date.....................................................................................................54
5.10.Communication and reading error detection (encoder only).....................................................................55
5.10.1.Encoder communication error......................................................................................................55
5.10.2.Encoder reading error detection...................................................................................................55
5.10.3.Communication and reading error detection parameters list.......................................................56
5.11.Low Battery Warning detection..................................................................................................................56
5.11.1.Low Battery Warning detection parameters list............................................................................56
5.12.Faults or Flow Problems automatic transmission......................................................................................57
5.12.1.Time windows dedicated to alarm sending..................................................................................57
5.12.2.Parameter list...............................................................................................................................57
5.12.3. Automatic configuration of the destination route (via SDP).........................................................58
5.12.4.Radio command for the configuration of the route.......................................................................58
5.12.5.Triggering an alarm frame............................................................................................................59
5.12.6.alarm frame acknowledgment......................................................................................................61
6.RADIO ADDRESS DESCRIPTION................................................................................................................62
APPENDIX A : RTM ELSTER AMCO INTERNAL PARAMETERS LIST.........................................................63
APPENDIX B : RTM ELSTER AMCO RADIO COMMANDS LIST..................................................................67
APPENDIX C : SERVICE COMMANDS...........................................................................................................68
Wavecard Serial Link Service Request Command description.........................................................................68
Request types....................................................................................................................................................69
EVO RTM-UserMan
RTM Elster AMCO applicative PFS
Coronis Systems
1.Definitions
Absolute Encoder: A meter register, that when queried by the Radio Transmitter module, will reply back to
the Radio Transmitter module with the exact reading of the register odometer reading.
Automatic Frequency Control: AFC guarantees top performance over the full lifetime of devices, keeping
Rx carrier frequencies aligned to Tx. AFC compensates frequency shift introduced by component aging
(discrete,quartz), but also by temperature drift and even by ambient temperature differences between
communicating devices.
Automatic Sensitivity Control: ASC operates like the squelch function in audio systems (ambient noise
filtering) to avoid “false” wake-up when RF environment is noisy. This is a serious factor for saving power.
Back flow: A reverse flow condition, created by a difference in water pressures or tampering of the meter
(i.e. reversing the physical meter), which causes water to flow back into the distribution pipes of a potable
water supply from any source or sources other than an intended source.
Bubble-Up Technology: Radio Transmitter module communications technique in which the radio transmitter
module automatically transmits, at pre-determined intervals, without having received a command to do so,
the information it has acquired from the meter register
Datalogging: Storage of consumption data over time, so that usage may be tracked. This is achieved by the
Radio transmitter module interrogating the water meter register at programmable time intervals and saving
the obtained reading together with time and date in memory for later retrieval.
Link budget: A link budget is the accounting of all of the gains and losses from the transmitter, through the
medium (free space, cable, waveguide, fiber, etc.) to the receiver in a telecommunication system. It takes into
account the attenuation of the transmitted signal due to propagation, as well as the loss, or gain, due to the
antenna. Random attenuations such as fading are not taken into account in link budget calculations with the
assumption that fading will be handled with diversity techniques. It is given by the following equation:
Pout (dBm) + Gtx (dBi) - Att-Max (dB) + Grx (dBi) - Sensi (dBm) = 0
Where:
Pout (dBm) output power on the TX side
Gtx (dBi) antenna gain on the TX side
AttMax (dB) Maximum possible attenuation. It includes LOS attenuation that
depends on distance and carrier frequency. It also includes signal
attenuation through obstacles.
Grx (dBi) Antenna gain on the RX side
Sensi (dBm) Receiver sensitivity on the RX side
Leak Detection Algorithm: An algorithm in the radio transmitter module which uses consumption
information acquired from the meter register to determine whether or not a leak is present on a specific
account
Overhearing: Overhearing is when a given, unintended device, within radio range, receives another device’s
transmission frequency, forcing the unintended device’s receiver to power up.
Pit Mount Interface: An adapter which allows the Radio Transmitter module antenna to rest above the pit lid
for better reception and transmission reliability in a pit environment.
Pseudo-bubble up: A feature which was developed in order to counter systems that specifies X amount of
readings a day via a bubble up system (see “bubble-Up Technology”). The pseudo bubble up feature will
automatically send a daily profile acquired from the datalogging table to the end user in one transmission
rather than via 6 transmissions. To the end user, who is receiving the data, there is no difference, other than
the means in which the data was received. Hence, “pseudo bubble up”.
Pulse Register: Meter register that sends an electrical pulse at a pre-defined interval (i.e. 1 pulse equals 1
gallon). The interval is usually a volume of consumption (gallons, cubic feet, cubic meters, etc).
EVO RTM-UserMan
RTM Elster AMCO applicative PFS
Coronis Systems
Quality of Service (QoS): Quality of Service (QoS) is an empirical, relative gauge of communications in a
network derived by an algorithm which is balanced to minimize RF communications while finding the best
communications path. Quality of Service is determined by a “balance” of 4 parameters: Device Class
(application dependent: sensor, valve, actuator, gateway…), Remaining energy (no limit if powered by
mains), RSSI, Number of “attached” children.
Radio Transceiver Module (Radio Transmitter module): Also known as endpoint, a radio transmitter
device is attached to the water meter register and transmits vital information about the meter and
consumption characteristics.
Received Signal Strength Indication (RSSI): RSSI is a measurement of the received radio signal strength
(energy integral, not the quality).RSSI is generic radio receiver technology metric, which usually is invisible to
the user of device containing the receiver, but is directly known to users of wireless networking of IEEE
802.11 protocol family.
Time of Use (TOU) Pricing: A tariff method in which a given utility charges different rates based on usage
during different times of day.
Two Way Communications: Two-way communications is radio technology terms which refers to a device
which can both transmit and receive (a transceiver) information on demand.
Wake-up preamble: A wake-up sequence used by the radio transmitter module, which is sent prior to data,
as communication is initiated.
WaveBox: Elster AMCO specified collector, which has many forms of communication ability to the head end
computer, including WiFI, GPRS, and Ethernet.
Wavecell: Current Coronis Wavenis/cellular network gateway. Offers full 2-way communications for
automated monitoring and remote network administration.
Waveflow: Current Coronis Low-cost, battery powered utility meter monitor with ultra-long battery life.
Wavehub: Mini Network concentrator or dedicated repeater
WYSIWYG – “What You See Is What You Get”: An acronym for What You See Is What You Get, used in
computing to describe a system in which content during editing appears very similar to the final product. It is
commonly used for word processors, but has other applications, such as Web (HTML) authoring.
Acronyms
AFC - Automatic Frequency Control
AFH – Automatic Frequency Hopping
ASC - Automatic Sensitivity Control
CPU - Central Processing Unit
DSSS - Direct Sequence Spread Spectrum
FHSS - Frequency Hopping Spread Spectrum
HCI - Host Controller Interface
IEEE – Institute of Electrical and Electronics Engineers
LLC - Logical Link Control
MAC - Medium Access Control
PAN - Personal Area Network
PDK - Product Development Kit
PHY – Refers to the physical layer of a integrated circuit
QoS – Quality of Service
RSSI – Received Signal Strength Indication
EVO RTM-UserMan
RTM Elster AMCO applicative PFS
Coronis Systems
RTC - Real Time Clock
RTM – Radio Transceiver Module
SDP - Service Discovery Protocol
TOU – Time of Use
ULP - Ultra-Low-Power
WBX – Wavebox (Collector)
WF – Waveflow (Radio Transmitter module)
WNM – Wavenet Manager
EVO RTM-UserMan
10
RTM Elster AMCO applicative PFS
Coronis Systems
2.Introduction
This document specifies all the features embedded in the RTM Elster AMCO radio module. A part of these
features are compatible with Coronis Standard RTM. Functionalities added specifically for Elster AMCO are
based on last “Statement of Conformance” document provided to CORONIS listed below :
–
–
–
“Coronis Conformance Doc - Fixed - 09.28.06 AMCO v11_revised_by_AMCO.xls”,
“Coronis Conformance Doc - Walk-by 10.2.06 v4 revised by AMCO.xls”,
“Coronis Conformance Doc - Drive By - 10.1.06 v4 revised by AMCO.xls”.
The aim of this document is to describe functional aspects of each feature embedded into the RTM Elster
AMCO radio module.
Each feature is fully configurable using radio signal bidirectional exchange.
3.Reference documents
Ref
Title
Version
Release Date
DR[1]
Project Thor – Product Specification.doc
03/05/05
DR[2]
cs-sup-muti-wflowapp-e02.pdf
03/31/05
DR[3]
Coronis Conformance Doc - Fixed - 09.28.06
AMCO v11_revised_by_AMCO.xls
11
09/28/06
DR[4]
Coronis Conformance Doc - Walk-by 10.2.06 v4
revised by AMCO.xls
02/10/06
DR[5]
Coronis Conformance Doc - Drive By - 10.1.06 v4
revised by AMCO.xls
01/10/06
DR[6]
Encoder Back flow Detection Spec r1
10.24.06.pdf
10/24/06
DR[7]
Wavecard User Handbook
Note :
For each section of this document a correspondence is made with DR[1] to DR[6], in order to
give Elster AMCO the ability to verify conformance between their Commercial Specifications (CDS)
and Coronis RTM Elster AMCO Product Functional specifications (PFS).
EVO RTM-UserMan
11
RTM Elster AMCO applicative PFS
Coronis Systems
4.RTM Elster AMCO Configuration access
RTM Elster AMCO as several embedded features, each one detailed later in this document, that are fully
configurable using radio frames. This section describes radio frame generic format and explains how to
access to the configuration of each embedded feature.
4.1.Radio exchange principle
Figure 1 below shows a point-to-point radio exchange principle between a USB Waveport (Waveport is a
Coronis radio modem generally used as the initiator of the radio exchange) and a Standard Coronis RTM.
RTM
Elster
AMCO
Figure 1
EVO RTM-UserMan
12
RTM Elster AMCO applicative PFS
Coronis Systems
Note : point-to-point exchange commands have the following format: (all exchanges modes are
described in document DR[7])
CMD
NAME
DESCRIPTION
0x20
REQ_SEND_FRAME
Request to send a radio frame with the waiting for the radio
response.
0x30
RECEIVED_FRAME
Received radio frame by the radio board.
The data field of each command must be formatted according to the following table:
DATA
CMD
6 bytes
variable ( max : 174 bytes)
0x20
Remote equipment “Radio Address”
Data to Transmit
0x30
Remote equipment “Radio Address”
Received Data
The first byte of the field “Data to Transmit” contains an “applicative command” that allows the recipient of
the radio frame to identify the corresponding action to process.
The first byte of the field “Received Data” contains an “applicative command acknowledgment” indicating
that the remote equipment has processed the requested action.
1 byte
173 bytes max
Data to Transmit
Applicative command
Data relating to the request
Received Data
Applicative command
Acknowledgment
Data relating to the response
ATTENTION :
Following sections of this document describe only “Data to Transmit” and “Received Data” fields
format. These fields are the only ones relevant when accessing to RTM Elster AMCO embedded features.
Other fields of the radio frame depend on the exchange mode chosen, and are detailed in document DR
[7].
EVO RTM-UserMan
13
RTM Elster AMCO applicative PFS
Coronis Systems
4.2.Internal parameters access
This chapter details the applicative data field used for reading or writing RTM Elster AMCO internal
parameters.
The complete list of accessible parameters is described in Appendix A at the end of this document.
Commands to use for accessing RTM Elster AMCO internal parameters :
Applicative
Commands
Description
0x18
Request to read parameter(s)
0x98
Request to read parameter(s) acknowledgment
0x19
Request to write parameter(s)
0x99
Request to write parameter(s) Acknowledgment
It is possible to access up to 10 parameters simultaneously either in writing or reading access
4.2.1.Reading internal parameters
 Reading request data format
Applicative
command
Number of
param to read
1st param ID
1st param size
...
...
nnd param ID
nnd param size
0x18
1 byte
1 byte
1 byte
...
...
1 byte
1 byte
nmax = 10
 Reading acknowledgment data format
Applicative
acknowledgment
command
0x98
Operating Number of
Mode
param
(1)
read
2 bytes
1 byte
1stparam
ID
1st param
size
1st param
value
...
1 byte
1 byte
variable
...
nth param nth param nth param
ID
size
value
1 byte
1 byte
variable
(1) Operating mode is systematically sent in the reading parameter request acknowledgment frame.
Remark :When a parameter is not a valid parameter of RTM Elster AMCO, or the size is configured with a
wrong value, the corresponding field “size” is set to “0x00” in the response frame and the corresponding
parameter value is not significant in this case.
EVO RTM-UserMan
14
RTM Elster AMCO applicative PFS
Coronis Systems
4.2.2.Writing internal parameters
 Writing request data format
Operating
Applicative
Mode
command
(1)
Mask on Operating
mode (indicate the
bits that must be
updated)
(1)
Number of
param to
write
(2)
1st
param
ID
1st
param
size
1st
param
new
value
2 bytes
1 byte
1 byte
1 byte
variable
2 bytes
0x19
...
nth
param
ID
nth
param
size
nth
param
new
value
...
1 byte
1 byte
variable
(1) These two fields has to be included in each writing command request. These 4 bytes are used to update
partially or entirely the operating mode parameter fields (See section §4.3.2.).
Indeed, the operating mode mask is used in the RTM Elster AMCO embedded software to reinitialize the
internal feature associated to these fields. With this method the application software don't need to take into
account the previous value of operating mode parameter.
It is recommended to use the writing command to initialize all parameters relative to a functionality like
datalogging in addition with positioning at “1” the concerned mask on operating mode. In this case the
internal function will be initialized with the parameters included in the frame.
(2) the maximum number of parameters to write must not be higher than nmax = 10
It is possible to write only the operation mode using the writing parameter command. In this case the frame
format is as follows:
 Writing acknowledgment data format
Applicative
acknowledgment
command
Operating
Mode
Number of
param written
1st param
ID
1st param
update status
(1)
...
...
nnd
param ID
nnd param
update status
0x99
2 bytes
1 byte
1 byte
1 byte
...
...
1 byte
1 byte
(1) 'Update Status' possible value: 0x00 : param update ok
0xFF : param update error
ATTENTION : some of the parameters are limited, i.e. their values should not be written out of their limits.
If a value is written out of the limits, the value will not be written and the parameter value will remain
unchanged. The status of writing will be NOK.
Example: An hour parameter should be set up from 0 to 23. Thus if value 40 is set, the update status
relative to this parameter will be equal to “0xFF”.
 Writing request data format with only operating mode
Applicative
command
Operating
Mode
Mask on Operating
mode (indicate the bits
that must be updated)
Number of param to
write
1 byte
2 bytes
2 bytes
1 byte
0x19
EVO RTM-UserMan
0x00
15
RTM Elster AMCO applicative PFS
Coronis Systems
 Writing acknowledgment data format in case of frame format error
Applicative
acknowledgment
command
Operating Mode
Status of writing
1 byte
2 bytes
1 byte
0x99
Operating Mode
current value
0x00 --> update Operating Mode OK
0xFF --> Syntax error (not enough bytes in the request)
4.3.Control bytes description
Some internal parameters are very useful to configure RTM Elster AMCO module and verify its state. These
control bytes are:
 Profile selection (1 byte),
 Operating Mode (2 bytes),
 Alarm Configuration (1 byte),
 Application Status (1 byte),
 Leakage detection Status (1 byte),
Depending on the selected profile or the type of connected meter, the meaning of each field could be
different. All these differences are defined below.
4.3.1.Profile selection
Profile selection (internal parameter ID = 0x05)
Value
RTM Elster AMCO profile
0x01
1 to 4 Digital Ports
0x02
1 or 2 Encoder Ports
ATTENTION :
RTM Elster AMCO initializes all the features on profile parameter programming. Also, programming the
“Encoder” profile causes an encoder automatic detection.
EVO RTM-UserMan
16
RTM Elster AMCO applicative PFS
Coronis Systems
4.3.2.Operating Mode
The “Operating Mode” is used to activate/deactivate each RTM Elster AMCO feature. This parameter is
accessible through the command write parameters (described in section 4.2.2).
“Operating Mode” parameter is systematically returned in generic header present in almost each response
frame of the RTM Elster AMCO.
 RTM Elster AMCO pulse
Operating Mode (no ID for this internal parameter)
bit 15
bit 14
bit 13
bit 12
Network
configuration
Not
used
Not
used
00:
01:
10:
11:
Fixed Network
Drive by/ Walk by
Drive By (only)
Walk By (only)
bit 11
bit 10
Bubble-Up
management
TOU Buckets
management
bit 9
bit 8
Not used
Not used
0 : deactivated 0 : deactivated
1 : activated
1 : activated
Operating Mode (no ID for this parameter)
Bit 7
Not used
Bit 6
Bit 5
Bit 4
Bit 3
Extreme leak
detection
Residual leak
detection
Tamper
detection
Bit 2
Datalogging
00 : deactivated
01 : time steps mngt
10 : once a week mngt
11 : once a month mngt
0 : deactivated 0 : deactivated 0 : deactivated
1 : activated
1 : activated
1 : activated
Bit 1
Bit 0
Ports management
00 : 1 Port (A)
01 : 2 Ports (A,B)
10 : 3 Ports (A, B, C)
11 : 4 Ports (A, B, C, D)
 RTM Elster AMCO encoder
Operating Mode (no ID for this internal parameter)
bit 15
bit 14
bit 13
bit 12
Network
configuration
Not
used
Not
used
00:
01:
10:
11:
Fixed Network
Drive by/ Walk by
Drive By (only)
Walk By (only)
bit 11
bit 10
bit 9
bit 8
Bubble-Up
management
TOU Buckets
management
Encoder
filtering algorithm
management
Back flow
detection
0 : deactivated 0 : deactivated
1 : activated
1 : activated
0 : deactivated
1 : activated
0 : deactivated
1 : activated
Operating Mode (no ID for this internal parameter)
Bit 7
Encoder
misread
detection
Bit 6
Bit 5
Extreme leak Residual leak
Encoder
detection
detection
communication
fault detection
0 : deactivated 0 : deactivated 0 : deactivated
1 : activated
1 : activated
1 : activated
EVO RTM-UserMan
Bit 4
0 : deactivated
1 : activated
Bit 3
Bit 2
Datalogging
00 : deactivated
01 : time steps mngt
10 : once a week mngt
11 : once a month mngt
Bit 1
Bit 0
Ports management
00 : one Port (A)
01 :2 Ports (A & B)
17
RTM Elster AMCO applicative PFS
Coronis Systems
4.3.3. Alarm Configuration
“Alarm Configuration” parameter is used to enable automatically alarm transmission on fault or other
anomaly independently.
Some internals features can be associated to an alarm configuration bit. To be sure that the Alarm frame will
be sent after fault or problem detection, the user must take care that the corresponding “Operating Mode”
bit is correctly set.
In case of manual network installation, Some other important information have to be configured in RTM
Elster AMCO such as the path to reach the root of the network.
 RTM Elster AMCO pulse
Alarm Configuration (internal parameter ID = 0x58)
Bit Number
Bit 7
(MSB)
bit 6
bit 5
bit 4
bit 3
bit 2
bit 1
Bit 0
(LSB)
Bit Definition
Not used
Not used
Not used
Not used
High
threshold
(Extreme
leak)
Low
threshold
(Residual
leak)
Low Battery
Warning
Cut cable
Pulse profile
0 : alarm frames disabled
1 : alarm frames enabled
 RTM Elster AMCO encoder
Alarm Configuration (internal parameter ID = 0x58)
Bit Number
Bit 7
(MSB)
bit 6
bit 5
bit 4
bit 3
bit 2
bit 1
Bit 0
(LSB)
High
threshold
(Extreme
leak)
Low
threshold
(Residual
leak)
Low
Battery
Warning
Encoder
communication
failure
Bit Definition
Not used
Not used
Back flow
Encoder
misread
Encoder profile
0 : alarm frames disabled
1 : alarm frames enabled
ATTENTION :
When RTM Elster AMCO is programmed to send information periodically using Pseudo bubble
up feature, enabling alarm frames is not recommended. Indeed, in such a case alarm frame
management can generate collisions on the radio medium . However, information returned in
pseudo bubble up mode include RTM Elster AMCO Status bytes (Application Status & Leakage
Detection Status) allowing the user software to monitor default detection on the RTM without any
other necessary radio exchange.
EVO RTM-UserMan
18
RTM Elster AMCO applicative PFS
Coronis Systems
4.3.4.Application Status
“ Application Status” parameter give at any time RTM Elster AMCO fault, or consumption-rate, status.
Each RTM Elster AMCO internal feature that can be activated or deactivated through its corresponding bit in
“Operating Mode” has an associated status bit in “Application status” parameter.
User has to reset each bit by writing the “Application Status” parameter once the default has been handled.
If a fault detection is not handled properly the corresponding bit in “Application Status” parameter will be
set once again.

RTM Elster AMCO pulse
Application Status (internal parameter ID = 0x01)
Bit Number
Bit 7
(MSB)
bit 6
bit 5
Bit Definition
Leak detection
(extreme or
residual)
Not used
Not used
Pulse profile
bit 4
bit 3
bit 2
bit 1
Tamper
Tamper
Tamper
Tamper
detection on detection on detection on detection on
Port D
Port C
Port B
Port A
Bit 0
(LSB)
Low
Battery
Warning
The coding is as follows : 0 : not detected
1:
detected

RTM Elster AMCO encoder
Application Status (internal parameter ID = 0x01)
Bit Number
Bit 7
(MSB)
bit 6
bit 5
Bit Definition
Leak detection
(extreme or
residual)
Back flow
detection
on Port B
Back flow
detection
on Port A
encoder profile
bit 4
bit 3
bit 2
bit 1
Encoder
Encoder
Encoder
Encoder
misread
misread
communication communication
detection on detection on fault detection fault detection
Port B
Port A
on Port B
on Port A
Bit 0
(LSB)
Low
Battery
Warning
The coding is as follows : 0 : not detected
1:
detected
EVO RTM-UserMan
19
RTM Elster AMCO applicative PFS
Coronis Systems
4.3.5.Leakage Detection Status
This control byte is used to detect leakage in real time. Indeed, each bit is set to one when a leakage is
detected and reset to zero automatically when it ended. This information can be read by the standard read
parameter command. This parameter is in read access only.

RTM Elster AMCO pulse
Leakage Detection Status (internal parameter ID = 0x02)
Bit Number
Bit 7
(MSB)
bit 6
bit 5
bit 4
bit 3
bit 2
bit 1
Bit 0
(LSB)
Bit Definition
High
threshold
(extreme
leak)
Port D
Low
threshold
(residual
leak)
Port D
High
threshold
(extreme
leak)
Port C
Low
threshold
(residual
leak)
Port C
High
threshold
(extreme
leak)
Port B
Low
threshold
(residual
leak)
Port B
High
threshold
(extreme
leak)
Port A
Low
threshold
(residual
leak)
Port A
Pulse profile
The coding is as follows : 0 -> not detected
1 ->
detected

RTM Elster AMCO encoder
Leakage Detection Status (internal parameter ID = 0x02)
Bit Number
Bit 7
(MSB)
bit 6
bit 5
bit 4
bit 3
bit 2
bit 1
Bit 0
(LSB)
Low
threshold
(residual
leak)
Port B
High
threshold
(extreme
leak)
Port A
Low
threshold
(residual
leak)
Port A
Bit Definition
Not used
Not used
Not used
Not used
High
threshold
(extreme
leak)
Port B
encoder profile
The coding is as follows : 0 -> not detected
1 ->
detected
EVO RTM-UserMan
20
RTM Elster AMCO applicative PFS
Coronis Systems
4.4.Writing RTC parameter
RTM Elster AMCO RTC can be updated using “Write Parameter” command.
RTC Structure :
RTC (internal parameter ID = 0x04)
Day
Month
Year
(1)
Day of the
week
(2)
Hour
Minute
Seconds
1 byte
1 byte
1 byte
1 byte
1 byte
1 byte
1 byte
(1) Year = 0x00 means that the current year is 2000
(2) Day of the week : value from 0 to 6:
Day of Week
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Value
ATTENTION :
1) When configured in Fixed Network Mode, and when synchronized on the network, RTM
Elster AMCO RTC is updated automatically through Radio Synchronization mechanism.
In this case, it is not allowed to update RTC from the user software because it can
disturb the Pseudo Bubble Up emission sequence.
2) When configured in Fixed Network Mode, RTM Elster AMCO Clock Synchronization
accuracy is maintained below 2 seconds thanks to Coronis Synchronization scheme.
When configured in Drive By (or Walk By) Mode, Clock drift is defined by the 32kHz
used as a reference for RTM Elster AMCO. To reduce this clock drift, RTM Elster
AMCO 32kHz reference clock is calibrated in manufacturing stage and an embedded
feature will balance the clock temperature drift.
3) It is not advised to switch the network RTC from winter to summer time and conversely
since it could have a transient impact on Pseudo Bubble Up emission sequence,
Datalogging accuracy, TOU Buckets accuracy, and all applicative periodic events that
could happen on RTM Elster AMCO.
4) Writing RTC parameter on an unsynchronized RTM will automatically deactivate the
TOU Buckets functionnality
EVO RTM-UserMan
21
RTM Elster AMCO applicative PFS
Coronis Systems
4.5.Meter reading sampling period configuration
Several RTM Elster AMCO embedded features (datalogging in time steps, leakage detection, back flow
detection) are based on periodic reading management. So, in order to synchronize these features RTM
Elster AMCO offers the possibility to program a kind of “Meter Reading Sampling Period” principle that is
shared between the features listed above in parenthesis.
4.5.1.Reading sampling period parameter
 For both RTM Elster AMCO profile (pulse or encoder)
Reading sampling period (internal parameter ID = 0x07)
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
[b7:b2] : Sampling period expressed in time units
Bit 1
Bit 0
[b1:b0] : time unit
00 : 1 minute
01 : 5 minutes
10 : 15 minutes
11 : 30 minutes
minimum : once a minute
maximum : 63 times 30 minutes = 31 h 30 min
[B7..B2] cannot be set to zero !
ATTENTION :
1) Meter sampling reading management starts only on associated feature activation (datalogging in
time steps, back flow or leakage detection). This allows to avoid power consumption (especially
when encoder profile is selected) while no periodic sampling is necessary. Once one of this
associated feature is activated, the sampling will start on nex hour “on the dot”.
2) Each meter reading sampling period parameter modification must be followed by a user
initialization of all the associated features (datalogging in time steps, back flow or leakage
detection).
4.5.2.Sampling activation type parameter
 For both RTM Elster AMCO profile (pulse or encoder)
Sampling activation type (internal parameter ID = 0x08)
Bit Number
Bit 7
(MSB)
bit 6
bit 5
bit 4
bit 3
bit 2
bit 1
Bit 0
(LSB)
Bit Definition
Not
used
Not
used
Not
used
Not
used
Not
used
Not
used
00 : Immediate Start
01 : Start on next hour “on the dot”
10 : Not used
11 : Not used
This parameter allows to program the way the user wants the RTM Elster AMCO to start reading sampling
mechanism on associated feature activation.
➢
Immediate Start: using this activation type, user wants the RTM Elster AMCO to start the meter
reading sampling immediately after associated feature activation (datalogging in time steps, back
flow, or leakage detection).
➢
Start on next hour on the dot: using this activation type, user wants the RTM Elster AMCO to start
the meter reading sampling on next hour on the dot after associated feature activation (datalogging in
time steps, back flow, or leakage detection).
ELIMINATED
ATTENTION:
If the user wants the meter reading sampling to be synchronized on each RTM Elster AMCO which is
part of a Fixed Network System, it is advised to use “start on next hour on the dot” since RTC on each
RTM is updated automatically through radio synchronization mechanism.
EVO RTM-UserMan
22
RTM Elster AMCO applicative PFS
Coronis Systems
5.RTM Elster AMCO functionalities
5.1.Fixed Network/Walk By/ Drive By switching method
(Refers to DR[5] Section 1.0.1)
According to §4.3.2 (Operating mode parameter description), RTM Elster AMCO is able to operate in “Fixed”
network, “Walk By”, and “Drive By” installations. The operation in “Walk By” and “Drive By” is exactly the
same.
RTM Elster AMCO operating in “Fixed” network mode just needs a setting command coming from a handheld computer to switch in “Drive By” mode operation. Conversely, once operating in “Drive By” (or in “Walk
By”), only a new setting command is required to make it switching in “Fixed” Network mode operation.
5.2.Datalogging management
(Refers to DR[3] Section 1.0.16 and 1.0.21; DR[4,5] Section 1.0.15 and 1.0.18)
The datalogging mode enables periodic logging of meter readings for each Port. The frequency of these
readings can be set in three different ways :
 data logging in time steps (selectable from 1 minute to 31 ½ hours),
 data logging once a week (day and hour of the day selectable),
 data logging once a month(date* and hour of the day selectable).
*when datalogging once a month is selected, date can be selected from the 1st to the 28th of each month.
Datalogging feature allows to store up to :
➢ 2100 readings when one Port is connected,
➢ 1050 readings when two Ports are connected,
➢ 700 readings when three Ports are connected,
➢ 525 readings when four Ports are connected.
Each Port has its own datalogging table. When the storage table is full, most recent logs overwrite oldest
ones.
Each time the datalogging settings are modified, storage tables are reset.
Datalogging table structure for one Port (A) connected:
RTC value on
last logged
reading
Last logged
reading on Port A
Log 0
Last but one logged
reading on Port A
Log 1
Port A
Log 2
Port A
Log 3
7 bytes
4 bytes
4 bytes
4 bytes
4 bytes
...
Port A Log
n-1
First log
Port A Log
(n-1)
4 bytes
4 bytes
2100 logged readings maximum whatever the number of Ports connected
n= 2100 readings max.
EVO RTM-UserMan
23
RTM Elster AMCO applicative PFS
Coronis Systems
Datalogging table structure for two Ports (A & B) connected:
RTC value on
last logged
readings on
each Port
Last logged
reading on Port A
Log 0
7 bytes
4 bytes
...
Port A
Log (m-2)
Port A
Log (m-1)
Last logged
reading on Port B
Log 0
4 bytes
4 bytes
...
Port B
Log (m-2)
Port B
Log (m-1)
4 bytes
4 bytes
2100 logged readings maximum whatever the number of Ports connected
m= 1050 readings max.
Depending on the number of Ports configured, RTM Elster AMCO knows exactly where to store each Port
readings, and so, where to recover them. This is done thanks to a pointer on the table and dynamic offsets,
depending on the number of Ports configured in the RTM Elster AMCO.
ATTENTION :
Only the last logged reading is time stamped. It is necessary to know the datalogging configuration to
compute others logged reading time stamps. That's why RTM Elster AMCO sends back datalogging
configuration every time a request to return logged reading is addressed to it.
5.2.1.Datalogging parameters access
The table below gives the list of parameters used for datalogging initialization.
N°
Size
in
bytes
Description
Access
Right
(Pulse
Profile)
Access
Default value
Right
(Hexa)
(encoder
Profile)
Restriction on
parameters
Datalogging feature parameters
0x07
Reading Sampling Period
R/W
R/W
0x0B
0x08
Sampling activation type
R/W
R/W
0x01
0x01 only
0x10
Measurement Period (datalogging in time steps)
expressed in multiple of “Reading Sampling Period”
R/W
R/W
0x01
0x12
Day of the week, or of the month (datalogging)
R/W
R/W
0x01
Conform day needed
0x13
Hour of measurement
(datalogging once a week, or once a month)
R/W
R/W
0x08
Conform hour needed
0x14
number of records in the datalogging table
(all ports records cumulated)
0x0000
Read only
EVO RTM-UserMan
24
RTM Elster AMCO applicative PFS
Coronis Systems
5.2.2.Datalogging mode activation
Datalogging mode is activated (or deactivated) by setting bits 3 and 4 in “Operating Mode” parameter.
ATTENTION :
Stopping then restarting the datalogging mode implies the re-initialization of the storage table. In this case,
all the logged readings will be lost.
It is advised to configure and activate the datalogging at the same time (with a single radio frame).
How to manage datalogging feature in RTM Elster AMCO “Operating Mode” parameter ?
 Writing request data format with only operating mode
Applicative
command
1 byte
0x19
Operating Mode
2 bytes
'0000000000000000'
'0000000000000100'
'0000000000001000'
'0000000000001100'
deactivate
time steps
once a week
once a month
Mask on Operating Mode
(indicate the bits that must
be updated)
Number of
param to write
2 bytes
1 byte
'0000000000001100' (0x000C)
Mask value to write only the
Datalogging Field in Operating
Mode
0x00
5.2.3.Datalogging in time steps
This type of datalogging is used to log the readings for each port at periods ranging from one minute to over
thirty hours.
Parameter :
 measurement period of the datalogging in time steps : expressed as a multiple of the reading
sampling period (parameter 0x07). (from 1 minute to 31h30minutes)
5.2.4.Datalogging once a week
This type of datalogging is used to log the readings for each Port once a week. The time, and day
of the week, logging is carried out, may be set with a parameter.
Parameters :
 Time of measurement (datalogging once a week) : this parameter allows to synchronize the
periodic measurement on RTM Elster AMCO RTC. It is expressed in multiple of hour, and its
value must be set from 0 to 23.
 Day of the week (datalogging once a week) : this parameter allows to select the day of week
according to the table below.
EVO RTM-UserMan
Value
Day of the week
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
25
RTM Elster AMCO applicative PFS
Coronis Systems
5.2.5.Datalogging once a month
This type of datalogging is used to log the readings for each Port once a month. The time and day
(from 1 to 28) logging is carried out may be set with a parameter.
Parameters :
 Time of measurement (datalogging once a month) : this parameter allows to synchronize the
periodic measurement. It is expressed in multiple of hour, and its value must set from 0 to 23.
 Day of the month (datalogging once a month) : the format is different from the datalogging
once a week. Indeed, the day of measurement is set from 1 to 28. And, the system does not
manage changes in the number of days depending on the month (day of the month setting cannot
exceed the 28th).
EVO RTM-UserMan
26
RTM Elster AMCO applicative PFS
Coronis Systems
5.3.RTM-Register interface
(Refers to DR[3] Section 1.0.17 to 1.0.19; DR[4,5] Section 1.0.16 and 1.0.17)
RTM Elster AMCO radio module is able to manage up to four Ports connected to pulse registers or up to two
Ports connected to encoders.
Register interface selection (pulse or encoder) is made by parameter configuration. So, there is only one
embedded software reference to manage. Nevertheless, the wiring connections on the PCB are different
between pulse and encoder interface. So, this means that Elster AMCO will have to manage two hardware
references. One for pulse registers interface and the second for encoder interface.
5.3.1.Pulse register three wire interface
pulse
ground
Tamper
pulse
pulse
PORT A
ground
ground
Tamper
Tamper
PORT B
pulse
PORT C
ground
Tamper
PORT D
RTM Elster AMCO pulse Interface
RTM Elster AMCO pulse profile list :
 RTM – 1 to 4 ports
: Ports A to D are used for measurement of pulses coming from
pulse registers.
Note:
Since wiring connections on PCB are different between pulse and encoder RTM, the profile configuration has
to be made by Coronis during manufacturing stage. Depending on the product reference ordered by Elster
AMCO, Coronis needs to manage each specific wiring and profile configuration at the same time to avoid
problems in the field during installation. Two different product references will be managed depending on the
expected register to connect (Pulse register or Encoder).
EVO RTM-UserMan
27
RTM Elster AMCO applicative PFS
Coronis Systems
5.3.2.Encoder three wire interface
Data
+v
0v
+v
Data
0v
PORT B
PORT A
RTM Elster AMCO encoder Interface
Encoder compatibility list :
RTM Elster AMCO first release is compatible with the encoders below :
 Elster AMCO Scancoder
–
Specs : 6170 M 1009
 Elster AMCO Invision 11Class
–
Specs : 6170 m 1042
 Elster AMCO Invision 21Class
–
Specs : 6170 Q 0009
 SENSUS ECR II and III encoders:
–
Specs : ui1203r19.pdf
–
V frame R field supported only,
A future release of RTM Elster AMCO, with no additional development fee to pay on Elster AMCO side, will
have to manage additional encoders that are listed below :
 NEPTUNE Pro E49N, ARB V, eCoder,
 BADGER RTR, ADE,
 HERSEY Translator.
EVO RTM-UserMan
28
RTM Elster AMCO applicative PFS
Coronis Systems
RTM Elster AMCO encoder profile list :
 RTM – Single or Dual Port(s)
: Ports A & B are used for encoders reading.
Note:
Since wiring connections on PCB are different between pulse and encoder RTM, the profile configuration has
to be made by Coronis during manufacturing stage. Depending on the product reference ordered by Elster
AMCO, Coronis needs to manage each specific wiring and profile configuration at the same time to avoid
problems in the field during installation. Two different product references will be managed depending on the
expected register to connect (Pulse register or Encoder).
EVO RTM-UserMan
29
RTM Elster AMCO applicative PFS
Coronis Systems
5.4.RTM-register pairing
5.4.1.Programming current register reading (pulse register only)
This feature allows to initialize the current reading of each Port.
RTM Elster AMCO measures, and count pulses coming from the pulse register. It is thus necessary to
establish the link between the reading of the meter given in volume unit (gallon, for example), and RTM
Elster AMCO current reading accessible through radio link.
Example : if the water meter indicates 1000 gallons.
- if the pulse register is from type k = 1 (1 pulse per gallon)
1000 pulses represent 1000 gallons, so the value to be programmed into the RTM current
reading will be 1000.
- if the pulse register is from type k = 10 (1 pulse per 10 gallons)
100 pulses represent 1000 gallons, so the value to be programmed into the RTM current
reading will be 100.
- if the pulse register is from type k = 100 (1 pulse per 100 gallons)
10 pulses represent 1000 gallons, so the value to be programmed into the RTM current
reading will be 10.
 Request data format
Applicative
command
Writing type
Current
reading A
Current
reading B
Current
reading C
Current
reading D
1 byte
1 byte
4 bytes
(MSB first)
4 bytes
(MSB first)
4 bytes
(MSB first)
4 bytes
(MSB first)
0x02
(*)
(*)Writing type : indicates which current readings have to be written or not.
Writing type byte
b7
b6
b5
b4
Not used Not used Not used Not used
b3
b2
b1
b0
Port D
0: skip
1: write
Port C
0: skip
1: write
Port B
0: skip
1: write
Port A
0: skip
1: write
 Response data format
EVO RTM-UserMan
Applicative
acknowledgment
command
Writing status
1 byte
1 byte
0x82
0x00 : writing OK
0xFF : writing error
30
RTM Elster AMCO applicative PFS
Coronis Systems
5.4.2.Programming pulse value (pulse register only)
In order to know through a radio command the pulse value of the meter connected to the RTM Elster AMCO,
specific parameters for each Port allows to store the corresponding pulse value.
The pulse value is used to convert the water consumption read in number of pulses, in volume unit ( gallon
for example).
RTM Elster AMCO provides up to 4 parameters to store the pulse value of each wired water meter.
ATTENTION:
the pulse value will only be stored for informative purpose. RTM Elster AMCO does not use it to convert
automatically the readings. Because of the wide range of pulse value, all operations are processed in
number of pulses, it is up to the user software to convert the information in volume unit.
Applicative
command
Associated internal parameters
Description
0x18
0x19 ; 0x1A ; 0x1B ; 0x1C
Request to read the pulse value parameters
0x98
0x19 ; 0x1A ; 0x1B ; 0x1C
pulse value reading response
0x19
0x19 ; 0x1A ; 0x1B ; 0x1C
Request to set the pulse value
0x99
0x19 ; 0x1A ; 0x1B ; 0x1C
pulse value configuration acknowledgment
The pulse value parameters are reached by standard reading, and writing parameters commands (described
in §4.2.).

0x19
pulse value on Port A,

0x1A
pulse value on Port B,

0x1B
pulse value on Port C,

0x1C
pulse value on Port D.
5.4.3.Definition of the pulse value parameters
MSB
b7
LSB
b6
b5
Volume Unit
b4
b3
b2
b1
b0
pulse value

pulse value : The range is from 1 to 15. ZERO value will be rejected.

Volume Unit : this unit is U (where U is the value contained in bits [b7:b4].
In order to standardize the information, the minimum unit is the liter.
EVO RTM-UserMan
31
RTM Elster AMCO applicative PFS
Coronis Systems
The table below gives the different possible unit:
Unit used
(hexadecimal)
[b7:b4]
Unit
liters
kilo-liters
US gallons
US gallons x 1000
Imperial gallons
cubic feet x 100
cubic meters
cubic meters x10
cubic meters x 100
9 to F
Reserved for future use
5.4.4.Programming meter model (pulse register only)
“meter model” parameters gives an indication on the digital register type connected on each Port. It can be
initialized during “RTM-Register pairing” phase but it is not mandatory. Default value is 0 and corresponds to
unknown type. This field is just for informative purpose.
Applicative
command
Associated internal parameters
Description
0x18
0x15 ; 0x16 ; 0x17 ; 0x18
Request to read the meter model parameters
0x98
0x15 ; 0x16 ; 0x17 ; 0x18
Meter model reading response
0x19
0x15 ; 0x16 ; 0x17 ; 0x18
Request to program the meter model
0x99
0x15 ; 0x16 ; 0x17 ; 0x18
Meter model programming acknowledgment
“meter model” parameters are reached by standard reading, and writing parameters commands (described in
§4.2.).

0x15
meter model on Port A,

0x16
meter model on Port B,

0x17
meter model on Port C,

0x18
meter model on Port D.
EVO RTM-UserMan
32
RTM Elster AMCO applicative PFS
Coronis Systems
The table below gives the correspondence between the meter type parameter value and the physical digital
register connected:
Meter type value
Corresponding Meter model
0x00
Unknown (default)
0x01
TBD by Elster AMCO (ex : C700 5/8”)
0x02
TBD by Elster AMCO (ex : C700 1”)
0x03
TBD by Elster AMCO (ex : C700 1.5”)
0x04
TBD by Elster AMCO (ex : C700 2”)
0x05
TBD by Elster AMCO
0x06
TBD by Elster AMCO
0x07
TBD by Elster AMCO
0x08
TBD by Elster AMCO
...
TBD by Elster AMCO
ATTENTION:
the meter model will only be given for informative purpose. RTM Elster AMCO does not use it. This
parameter could be useful for user software to ensure proper register reading interpretation for billing
purposes for example. It's up to user software to define the correspondence between meter model
parameter value and digital register type connected.
EVO RTM-UserMan
33
RTM Elster AMCO applicative PFS
Coronis Systems
5.4.5.Encoder model detection
(Refers to DR[3] Section 1.0.17; DR[4,5] Section 1.0.16)
RTM Elster AMCO embeds a feature allowing to recognize the encoder model connected.
This feature is performed either when profile selection parameter is programmed with encoder profile value,
or using a dedicated radio command.
RTM Elster AMCO run all encoders drivers and recognizes the connected encoders models.
Once the initialization is completed, RTM Elster AMCO sends back to the command initiator the encoder
model.
Note :
This command has to be performed once the RTM is connected to the encoder, either in the field during
installation phase or during manufacturing phase of the RTM.
 Request data format
Applicative command
1 byte
0x0C
 Response data format
The total length is 7 Bytes
Applicative
acknowledgment
command
Status
Encoder A
Encoder A
model
Status
Encoder B
Encoder B
model
1 byte
1 byte
2 bytes
1 byte
2 byte
0x8C
0x00 = OK
0xFF = sensor error
(1)
0x00 = OK
0xFF = sensor error
(1) : Encoder model description:
Encoder model is 2 bytes long with the MSByte indicating the encoder manufacturer (ELSTER or SENSUS)
and the LSByte indicating the encoder model (example: Scancoder or Invision for Elster AMCO) and this
value takes different meaning depending on the brand.
The table below describes the different encoder models written in field “Encoder model”:
EVO RTM-UserMan
Manufacturer
Elster AMCO
SENSUS
Encoder
Manufacturer (MSB)
0x01
0x02
Adapter Code (LSB)
0x00 (Scan_Coder)
010 (Dual Scan)
0x2x (Multi Scan)
0x30 (Q100)
0x40 (Scan_Counter)
0x50 (Aqua Master)
0x60 (Invision 11C)
0x70.(Invision 21C)
MANUFACTURER_ID
(First byte of the serial code)
34
RTM Elster AMCO applicative PFS
Coronis Systems
Encoder model is then stored in an internal parameter which is in read access only.
Applicative
command
Associated internal
parameters
Description
0x18
0x1D ; 0x1E
Request to read the encoder model parameters
0x98
0x1D ; 0x1E
Encoder model reading response
“encoder model” parameters are accessible by standard reading parameters command (described in §4.2.).

0x1D
encoder model on Port A,

0x1E
encoder model on Port B,
5.4.6.Encoder Unit (Encoder register only)
Each encoder embeds its unit in an internal parameter and the RTM Elster AMCO reads out this information
after encoder model detection. It stores the unit inside a read only parameter.
The unit parameter contains two important information that are the position of the decimal point and the unit.
ATTENTION:
the unit value will only be given for informative purpose. RTM Elster AMCO does not convert the current
unit to a standard GALLON unit and all operations are processed without taking into account the unit and
the decimal point position, it is up to the user software to convert the information in desired unit.
Applicative
command
Associated internal
parameters
Description
0x18
0x1F ; 0x20
Request to read the unit parameters
0x98
0x1F ; 0x20
Encoder Unit reading response
The MSByte indicates the unit.
The LSByte indicates the number of digits before the decimal point.
Default value is assigned to 0xFFFF.
The table below gives the different possible unit (MSB byte) :
EVO RTM-UserMan
MSB unit value
(hexadecimal)
Unit definition
Elster AMCO
encoder
SENSUS
encoder
0x01
Cubic meters (m3)
0x11
Cubic meters * 10
0x21
Cubic meters * 100
0x02
US Gallons * 1000
0x03
Imperial gallons
0x04
liters
0x05
Cubic feet * 100
0x06
US gallons
0x07
-”K” Multiplier (*1000)
0x08
Kilo liters
0x30
Cubic feet
0x31
Cubic Inches
0x32
Cubic Yards
0x33
Acre feet
TBD
TBD
TBD
TBD
35
RTM Elster AMCO applicative PFS
Coronis Systems
5.4.7.Reading encoder internal data (Encoder only)
This feature allows to access directly to the information returned by the encoder(s) connected to RTM Elster
AMCO.
ATTENTION:
Data returned could be different according to the encoder model connected.
 Reading encoder internal data request data format
Applicative command
1 byte
0x0B
 Reading encoder internal data acknowledgment data format
The total length depends on encoder returned data length
Applicative
acknowledgment
command
Encoder
model on
Port A
Encoder
model on
Port B
Size of the
returned data
on Port A
Size of the
returned data
on Port B
Encoder data
different
according to
encoder
connected on
Port A
Encoder data
different
according to
encoder
connected on
Port B
1 byte
2 bytes
2 bytes
1 byte
1 byte
N bytes
N bytes
0x8B
0xFFFF
if no
encoder
connected
0xFFFF
if no
encoder
connected
0x00
if no encoder
connected
0x00
if no encoder
connected
(*)
(*)
(*) Information returned by encoders: if any problem occurred during the communication with the encoder,
then the information returned in the encoder data field is set to 0xFF (N= 1 byte).
“Encoder data” returned in case of Elster AMCO encoder connected (N = 29 bytes) :
Size
(in bytes)
Description
AMCO/ELSTER
company identifier
0x4B
Value of meter wheels
Provide the meter value in ASCII characters
User serial number
10
10 ASCII characters
Registration units code
registration units
Encoded wheel digits
4,5 or 6 active digits
Digits before decimal point
Counted from the first “V” digit ( most significant)
Example: if d=4 & VVVVVV = 654321 then the value = 6573.21
Option
Indicates major software version
Manufacture adapter code
Example : 0x3730 = “Invision 21C”
Error code
Checksum
Information
EVO RTM-UserMan
36
RTM Elster AMCO applicative PFS
Coronis Systems
5.5.RTM reading management
(Refers to DR[3] Section 1.0.22; DR[4,5] Section 1.0.19)
RTM Elster AMCO offers the possibility to recover different types of readings listed below:
➢
Current reading,
➢
Daily consumption profile readings,
➢
Datalogging table,
➢
TOU buckets.
These different way to recover reading from RTM Elster AMCO are described in details in this section.
Furthermore, RTM Elster AMCO sends back on each of these requests, control information formatted as a
generic header described below. This one is useful to manage network supervision.
5.5.1.Generic header structure
The total length of the generic header is 23 Bytes
Profile
Selection
(1)
Operating
mode
Application
Status
Leakage
Detection Status
current RTC
QoS
(2)
Life counter
(3)
Meters/Encoders
connected
information
(4)
1 byte
2 bytes
1 byte
1 byte
7 bytes
1 byte
2 bytes
8 bytes
(1) “Profile selection” parameter is useful to inform the user software on current profile selected on RTM
Elster AMCO. Indeed, user software needs to use this parameter to be able to handle correctly the data
received format.
(2) The QoS value gives an image of the previous radio reception signal strength.
(3) The “life counter” value gives an estimated quantity of energy that remains in RTM Elster AMCO battery.
User software has to take into account the default value of this counter to compute an estimated remaining
lifetime.
(4) This field has different meaning and format depending on RTM Elster AMCO profile selected:
pulse profile
Encoder
profile
Byte 1
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 8
pulse value
Port A
pulse value
Port B
pulse value
Port C
pulse value
Port D
Meter model
on Port A
Meter model
on Port B
Meter model
on Port C
Meter model
on Port D
Encoder unit on Port A
EVO RTM-UserMan
Encoder unit on Port B
Encoder model on Port A
Encoder model on Port B
37
RTM Elster AMCO applicative PFS
Coronis Systems
5.5.2.Current register reading
When current index reading is expected, RTM Elster AMCO sends back through a radio frame the current
readings on each Port connected. If a Port has no meter connected to it, then the corresponding current
reading is set to 0x7FFFFFFF.
 Request data format
Applicative command
1 byte
0x01
 Response data format (pulse registers connected)
The total length is 40 Bytes
Applicative
acknowledgment
command
Generic
Header
Current reading
Port A
Current reading
Port B
Current reading
Port C
Current reading
Port D
0x81
23 bytes
4 bytes
(MSB first)
4 bytes
(MSB first)
4 bytes
(MSB first) (1)
4 bytes
(MSB first) (1)
 Response data format (encoders connected)
The total length is 32 Bytes
Applicative
acknowledgment
command
Generic
Header
0x81
23 bytes
EVO RTM-UserMan
Current Reading Current Reading
on Port A
on Port B
4 bytes
(MSB first)
4 bytes
(MSB first)
38
RTM Elster AMCO applicative PFS
Coronis Systems
5.5.3.Daily consumption profile reading
Daily consumption profile reading request allows to recover:
➢
generic header,
➢
current readings,
➢
logged readings 4th, 8th, 12th, 16th, and 20th positions in the datalogging table (if
datalogging is set).
ATTENTION:
Daily consumption profile is accurate only when datalogging every hour is programmed.
All other datalogging configuration will not provide daily information using this particular
command.
 Request data format
Applicative command
1 byte
0x03
 Response data format
The total length for 1 Port managed is 62 Bytes
The total length for 2 Ports managed is 86 Bytes
The total length for 3 Ports managed is 110 Bytes
The total length for 4 Ports managed is 134 Bytes
Applicative
acknowledgment
command
0x83
Generic
Header
23 bytes
RTC on last
logged
reading
Datalogging
Parameters
Current readings area
4th, 8th, 12th, 16th, 20th,
position logged readings
area
7 bytes
7 bytes
(See section
§5.2.1 for field
description)
Variable (2)
Variable (2)
(1) Datalogging parameters field:
Parameter ID
Parameter
description
EVO RTM-UserMan
Byte 1
Byte 2
Byte 3
Byte 4
Byte 5
0x07
0x08
0x10
0x12
0x13
Reading
Sampling
Period
Sampling
activation type
Byte 6
Byte 7
0x14
Hour of
Measurement
Day of the
measurement
number of records in the
Period
week, or of the
datalogging table
(datalogging once
(datalogging in
month
time steps)
(datalogging) a week, or once a (all ports records cumulated)
month)
39
RTM Elster AMCO applicative PFS
Coronis Systems
(2) format and size of the fields “current readings area”, ”4th, 8th, 12th, 16th, 20th, position logged readings area”
depend on the number of ports managed. The tables below describes the format and the size of these fields.
➢
Pulse profile selected
Current readings area
( byte order : [Bxx..B0] )
Number of Ports
➢
4th, 8th, 12th, 16th, 20th,
position logged readings area
( byte order : [Bxx..B0] )
Size : 4 bytes
[B3:B0]
: current reading on Port A
Size : 20 bytes
[B19:B0] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port A
Size : 8 bytes
[B7:B4]
: current reading on Port A
[B3:B0]
: current reading on Port B
Size : 40 bytes
[B39:B20] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port A
[B19:B0] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port B
Size : 12 bytes
[B11:B8] : current reading on Port A
[B7:B4]
: current reading on Port B
[B3:B0]
: current reading on Port C
Size : 60 bytes
[B59:B40] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port A
[B39:B20] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port B
[B19:B0] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port C
Size : 16 bytes
[B15:B12] : current reading on Port A
[B11:B8] : current reading on Port B
[B7:B4]
: current reading on Port C
[B3:B0]
: current reading on Port D
Size : 80 bytes
[B79:B60] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port A
[B59:B40] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port B
[B39:B20] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port C
[B19:B0] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port D
Encoder profile selected
Number of Ports
Current readings area
( byte order : [Bxx..B0] )
Size : 4 bytes
[B3:B0] : Current reading on Port A
Size : 20 bytes
[B19:B0] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port A
Size : 8 bytes
[B7:B4] : Current reading on Port A
Size : 40 bytes
[B39:B20] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port A
[B3:B0] : Current reading on Port B
[B19:B0] : 4th, 8th, 12th, 16th, 20th,
logged readings on Port B
EVO RTM-UserMan
4th, 8th, 12th, 16th, 20th
position logged readings area
( byte order : [Bxx..B0] )
40
RTM Elster AMCO applicative PFS
Coronis Systems
5.5.4.Datalogging table reading
First of all, it is important to note that only the last logged reading is time stamped. So, CORONIS advises to
read datalogging table from the last logged reading in order to be able to compute the time stamp of each log.
 Request data format
Applicative
command
Requested ports
logged readings
Expected Logged
Readings by Port
Offset in records table
1 byte
1 byte
2 bytes (MSB first)
2 bytes
(*)
0x07
: request to read datalogging table
from the most recent logged reading
: request to read datalogging table from
the most recent logged reading + n.
(*)Requested index : indicates which logging table is expected,
Requested ports logged readings
b7
b6
b5
b4
Not used Not used Not used Not used
b3
b2
b1
b0
Port D
readings
Port C
readings
Port B
readings
Port A
readings
0: skip
1: requested
0: skip
1: requested
0: skip
1: requested
0: skip
1: requested
 Response data format
If the amount of logs requested is too large to be returned with a single radio frame, RTM Elster AMCO
automatically uses “CORONIS multiframe” process, which is useful to decrease consumption and response
time. This process successively transmits several frames containing the recordings from the most recent to
the oldest one.
➢ First frame applicative data format
Applicative
acknowledgment
command
Generic
header
Datalogging
Parameters
RTC on last
logged reading
Frame
counter
Data zone
1 byte
23 bytes
7 bytes
7 bytes
1 byte
Variable
(*)
0x87
(See section
§5.2.1 for field
description)
(1) Frame counter starts with the number of frame that will be transmitted : n
EVO RTM-UserMan
41
RTM Elster AMCO applicative PFS
Coronis Systems
➢ Next frame applicative data format
Acknowledgment
command
Frame counter
(decreased on each
frame)
Data zone
1 byte
1 byte
Variable
0x87
m(
Source Exif Data: 
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
Page Count                      : 71
Title                           : RTM Elster AMCO applicative PFS
Producer                        : StarOffice 7
Create Date                     : 2007:11:13 17:28:57+01:00


EXIF Metadata provided by EXIF.tools
FCC ID Filing: S28-EVO

Navigation menu