G350 M BusModuleDescription

Commercial in Confidence
LANDIS + GYR
Libra 4*5 Wired M-Bus Gas Module and

Libra 4*4 Wireless M-Bus Gas Module
Product Specification
File name:PS002F.doc
th
: Product Specification
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 1 of 66
1. PRELIMINARIES
1.1 Abstract
This specification describes the physical and functional requirements of two domestic M-Bus modules that shall
operate in conjunction with the L+G electronic Galvanic E6V gas meter to provide an AMR communicating system
in conjunction with a FLEX Electricity meter. Libra 4*4 is a wired M-Bus module and Libra 4*5 is a wireless M-Bus
module. The * is a digit which indicates the connection variant.
The types LIBRA 4*4 and LIBRA 4*5 modules shall incorporate functionality to provide valve control and automatic
meter readings. Hereafter, the term Libra Module shall refer to either module.
1.2 Conventions
Incomplete or questionable sections within this document are enclosed within angled brackets: <.>. The text
string TBD (To Be Defined) precedes the opening brackets. The questionable aspects or the degree of
incompleteness are specified within the brackets. The document state is incomplete as long as any TBD sections
remain.
1.3 Revision History

Doc. Ref.
Draft A
Draft B
Date
26/9/2007
6/12/2007
Author
P. Harrison
P. Harrison
Draft C
Draft D
Draft E
11/12/07
27/2/08
12/05/08
P. Harrison
P. Harrison
P. Harrison
Draft F
4/6/08
P. Harrison
Comment
First Draft text in yellow under debate
Updated with review changes and changed NTA requirements
(2.0)
Updated with review changes
Changes due to changed NTA requirements (2.1)
Changes due to changed NTA requirements (2.2)
Name change from Libra 324
Changes following review on 2/6/08.
Rolling registers have numbers removed.
High Flow Interlock parameter changes and failure display
defined.
Index display does not have valve state.
New valve state displays added.
Temperature compensated display added to service menu.
Engineering menu split into Service and Engineering menus to
keep marriage / divorce separate.
Re-open valve added to Service menu.
Corrected Link key record encoding.
Factory option to allow non-encrypted commands.
Removed excessive flow cannot be done by current base meter.
Added Wired M-Bus battery life calculation assumption and use of
address filter required if not so.
Repeated Communications tamper is now Security warning.
Added 10 day hourly profile registers and 31 daily profile registers.
Unused fault codes removed E02, E07
Clarified B and C flag handling (now temporary errors).
Requirement numbering format changed.
Added use of Storage bit in DIF for hourly values.
Added setting of Function and location information.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 2 of 66
1.4 Product Family

This document is part of a range of documents that define the Smart Gas metering range of products Libra210s
(Smart card prepayment meter), LIBRA 310 Smart credit meter with LPR interface, Libra 410 Smart credit meter
with GSM and LPR interface.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 3 of 66
TABLE OF CONTENTS
1.
PRELIMINARIES ...............................................................................................................................................2
1.1
1.2
1.3
1.4
2.
INTRODUCTION................................................................................................................................................7
2.1
2.2
2.3
2.4
2.5
3.
Abstract...........................................................................................................................................................2
Conventions....................................................................................................................................................2
Revision History..............................................................................................................................................2
Product Family................................................................................................................................................3
Purpose ..........................................................................................................................................................7
Scope..............................................................................................................................................................7
References .....................................................................................................................................................7
Definitions, Acronyms and Abbreviations.......................................................................................................8
Glossary of Terms ..........................................................................................................................................9
PHYSICAL REQUIREMENTS .........................................................................................................................10
3.1
Hardware configuration ................................................................................................................................10
3.2
Meter Parameters.........................................................................................................................................11
3.2.1
Meter Types ..........................................................................................................................................11
3.2.2
Meter Valves .........................................................................................................................................11
3.3
Case Construction ........................................................................................................................................11
3.3.1
General..................................................................................................................................................11
3.3.2
Case used with E6V ..............................................................................................................................12
3.3.3
Case Material ........................................................................................................................................12
3.3.4
Serial Numbers......................................................................................................................................12
3.3.5
Installation .............................................................................................................................................13
3.3.6
Temperature Range ..............................................................................................................................13
3.3.7
Environmental Withstand ......................................................................................................................13
3.4
EMC..............................................................................................................................................................14
3.4.1
Electrostatic Discharge Immunity..........................................................................................................14
3.4.2
Electromagnetic Susceptibility ..............................................................................................................14
3.4.3
RF Susceptibility....................................................................................................................................14
3.4.4
Emissions ..............................................................................................................................................15
3.4.5
Radio Equipment Additional EMC Requirements .................................................................................15
3.4.6
Radio Equipment Spectrum Usage.......................................................................................................15
3.5
Reliability ......................................................................................................................................................15
3.6
Safety............................................................................................................................................................15
3.6.1
Childproof ..............................................................................................................................................16
3.6.2
Users .....................................................................................................................................................16
3.6.3
Gas ........................................................................................................................................................16
3.6.4
Hardware Interlock ................................................................................................................................16
3.7
Customer Interface Requirements ...............................................................................................................17
3.7.1
Push Buttons .........................................................................................................................................17
3.7.2
Display...................................................................................................................................................17
3.7.3
Warning Buzzer.....................................................................................................................................17
3.8
Real Time Clock ...........................................................................................................................................18
3.9
Battery ..........................................................................................................................................................19
3.9.1
General..................................................................................................................................................19
3.9.2
E6V Application .....................................................................................................................................19
3.10
Copyright Infringement Detection .............................................................................................................19
3.11
Galvanic Communication Port ..................................................................................................................20
3.12
Watchdog ..................................................................................................................................................20
3.13
Recovery From reset ................................................................................................................................20
4.
MODULE FUNCTIONALITY............................................................................................................................21
4.1
Introduction ...................................................................................................................................................21
4.1.1
Physical Implementation .......................................................................................................................21
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 4 of 66
4.2
Interfaces ......................................................................................................................................................21
4.3
Modes of Operation ......................................................................................................................................21
4.4
Marriage and Divorce ...................................................................................................................................21
4.5
External Communications.............................................................................................................................21
4.6
Displays ........................................................................................................................................................22
4.7
Operating States...........................................................................................................................................23
4.7.1
Unpowered State...................................................................................................................................23
4.7.2
UnMarried State. ...................................................................................................................................24
4.7.3
Active State. ..........................................................................................................................................24
4.7.4
Meter Index Display...............................................................................................................................25
4.8
Rolling Registers ..........................................................................................................................................25
4.8.1
Rolling Register Displays ......................................................................................................................26
4.8.2
Rolling Register Access ........................................................................................................................27
4.9
Valve Control ................................................................................................................................................27
4.9.1
General..................................................................................................................................................27
4.9.2
Event Actions ........................................................................................................................................28
4.9.3
Operation with E6V Meters ...................................................................................................................28
4.9.3.1
Meter Index Limits transferred to E6V ...........................................................................................28
4.10
Valve Opening ..........................................................................................................................................29
4.10.1 High Flow Open interlock ......................................................................................................................30
4.11
Buzzer Operation ......................................................................................................................................30
4.11.1 Operational Status.................................................................................................................................30
4.12
Libra Module Reference Numbers............................................................................................................31
4.13
Software Version Number.........................................................................................................................31
5.
CONFIGURATION DATA................................................................................................................................32
5.1
Overview.......................................................................................................................................................32
5.2
Purge Volume ...............................................................................................................................................32
5.2.1
Volume Limit..........................................................................................................................................32
5.2.2
Time Limit ..............................................................................................................................................32
6.
ACCOUNTING .................................................................................................................................................33
6.1
General Functions ........................................................................................................................................33
6.2
Profile Registers ...........................................................................................................................................33
6.3
Cumulative Registers ...................................................................................................................................33
6.3.1
Volume Registers ..................................................................................................................................33
6.3.2
Total Volume today ...............................................................................................................................33
6.3.3
Total Volume Last 7 Days .....................................................................................................................34
6.3.4
Total Volume Last 28 Days ...................................................................................................................34
6.3.5
Total Volume Last 12 Months ...............................................................................................................34
6.3.6
End of Day Processing..........................................................................................................................34
7.
SERVICE OPERATION ...................................................................................................................................35

7.1
Engineering Menu ........................................................................................................................................35
7.1.1
Divorce ..................................................................................................................................................36
7.1.2
Marriage (to E6V) ..................................................................................................................................36
7.2
Service Menu................................................................................................................................................37
7.2.1
Purge .....................................................................................................................................................37
7.2.2
Event and Status Clearing ....................................................................................................................38
7.2.3
Unbind ...................................................................................................................................................39
7.2.4
Battery Change .....................................................................................................................................39
7.2.5
Open Valve Operation...........................................................................................................................40
7.2.6
Temperature Compensated Meter Reading .........................................................................................40
8.
OPERATIONAL ERRORS...............................................................................................................................41
8.1
Event Log......................................................................................................................................................41
8.2
Event Definitions...........................................................................................................................................42
8.2.1
Libra Module Event Definitions .............................................................................................................42
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 5 of 66
8.2.1.1
E 01 Leaky Valve ........................................................................................................................42
8.2.1.2
E11 Valve Open Operation Failure ................................................................................................42
8.2.1.3
E3 Security Warning ...................................................................................................................43
8.2.1.4
E6 Reverse volume.....................................................................................................................43
8.2.1.5
E26 Meter Failed to Action Command ........................................................................................43
8.2.1.6
E28 Libra Module Software Fault ...............................................................................................43
8.2.1.7
E29 Libra Module Hardware Fault ..............................................................................................43
8.2.1.8
E30- Libra Module EEPROM Fault ................................................................................................43
8.2.2
E6V Status ............................................................................................................................................43
8.2.2.1
FA Catastrophic Error .................................................................................................................44
8.2.2.2
FB Major Event ...........................................................................................................................44
8.2.2.3
FC Major Problem .......................................................................................................................44
8.2.2.4
FF Low Battery............................................................................................................................44
Event Actions...........................................................................................................................................................45
8.3
Event Displays ..............................................................................................................................................45
8.4
Mapping to M-Bus Error Status ....................................................................................................................46
8.4.1
Reset of M-Bus Error Status .................................................................................................................46
9.
BATTERY ........................................................................................................................................................47
9.1
10.
Battery Usage Timer.....................................................................................................................................47

COMMUNICATIONS LINK TO ELECTRICITY METER .................................................................................49
10.1
Wired M-Bus Link......................................................................................................................................49
10.1.1 Communications Parameters................................................................................................................49
10.1.2 Bus Addressing .....................................................................................................................................49
10.1.3 M-Bus Discovery Process .....................................................................................................................50
10.1.4 Wired Unbinding....................................................................................................................................51
10.2
Wireless M-Bus Link .................................................................................................................................51
10.2.1 General Operation.................................................................................................................................51
10.2.2 Link Layer Usage ..................................................................................................................................51
10.2.3 Wireless Binding....................................................................................................................................52
10.2.3.1 Binding (NTA).................................................................................................................................53
10.2.3.2 Binding (Dongle) ............................................................................................................................54
10.2.4 Wireless Unbinding ...............................................................................................................................55
10.2.5 Wireless Pre-binding .............................................................................................................................55
10.3
Security .....................................................................................................................................................55
10.3.1 Block size filling when encryption used..............................................................................................57
10.4
Application Messaging ..............................................................................................................................57
10.4.1 Readout List ..........................................................................................................................................57
10.4.2 Manufacturer ID.....................................................................................................................................57
10.4.3 Message Types .....................................................................................................................................57
10.4.3.1 Data Request .................................................................................................................................57
10.4.3.2 Fixed Data Header .........................................................................................................................59
10.4.3.3 Variable Data Blocks......................................................................................................................59
10.4.3.4 Encoding of Hourly Values.............................................................................................................60
10.4.3.5 Set Time and Date .........................................................................................................................61
10.4.3.6 Gas Disconnect Message ..............................................................................................................62
10.4.3.7 Gas Reconnect Message...............................................................................................................63
10.4.3.8 Set Location Information ................................................................................................................65
10.4.3.9 Set Function Location ....................................................................................................................65
11.
FACTORY CONFIGURATION ........................................................................................................................66
12.
INITIAL MODULE STATES.............................................................................................................................66
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 6 of 66
2. INTRODUCTION
2.1 Purpose
This document shall act as the definitive requirements of the physical and functional features of two Gas
Communicating Modules, Libra 4*4 and Libra 4*5. This meter is intended to satisfy the requirements of the Dutch
NTA (see reference[19]). For the Dutch market, these shall be Libra 424 and Libra 425. The meters only differ in
the communication interface.
2.2 Scope
The scope of this document is to define the requirements of the Libra Module in terms that shall permit its design,
manufacture and testing. It shall define the control interfaces to the meters.
This document shall define the operation of the module with existing site commissioning and servicing tools and the
data transfers to and from those tools.
This document shall define:
The electrical and physical requirements of the module;
Performance standards with which the module shall comply;
The operational features of the module to enable designers to create the product hardware and firmware;
Module functionality against which product testing shall be performed;
The communications interfaces for remote access applications;
Configuration features for module definition.
2.3 References
Document
Number
1
2
3
4
5
6
7
8
9
10
Description
Document Number/Location
Data exchange for meter reading, tariff and load control

Classification of degrees of protection provided by
enclosures.
Specification for installation, exchange, relocation and
removal of gas meters with a maximum capacity not
exceeding 6 m3/h (2nd and 3rd family gases). Low
pressure (2nd family gases).
Ultrasonic domestic gas meters
Electrical apparatus for explosive gas atmospheres,
construction, testing and marking of type of protection
n apparatus.
Bar coding. Symbology specifications. 'PDF417'
Fire hazard testing, needle flame test method.
Apparatus , confirmatory test arrangement and guidance
flames
Environmental Testing, Tests. Test A. Cold.
Standards on Electromagnetic Compatibility
Information Technology Equipment: Radio disturbance
BSEN 62056-21:2002
BSEN 60529:1992
BS6400 1:2006
BSEN 14236: 2007

BS 60079-15:2005,
BS DD ENV 12925:1998
BS EN 60695-2-4/2:1996
IEC 60068-2-1
IEC 61000 Series
BS EN 55022:1998
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 7 of 66
Document
Number
11
12
13
14
15
16
17
18
19
20
21
Description
Document Number/Location
characteristics. Limits and methods of measurement.

Methods of testing plastics. Thermal properties.
Flammability of a small, inclined test piece exposed to
an alcohol flame (laboratory method).
Electromagnetic compatibility. Generic emission
standard. Residential, commercial and light industry
Safety of Toys
Communication systems for and remote reading of
meters Part 3: Dedicated application layer
Communication systems for meters and remote reading
of meters Part 4: Wireless meter readout (Radio
meter reading for operation in the 868 MHz to 870 MHz
SRD band)
Communication system for meters and remote reading
of meters Part 1: Data exchange
Communication systems for and remote reading of
meters Part 2: Physical and link layer
P2 companion standard version 2.1
Netherlands Technical Agreement 2.2

(NTA)
Telecontrol equipment and systems - part 5
Transmission protocols - Section 5.2 Link transmission
procedures
E6V (Adaptive+) Basic Communications Protocol
BS 2782-1:1982
BS EN 61000-6-3:2001
BS 5665: 1989
BS EN 13757-3
BS EN 13757-4
BS EN 13757-1
BS EN 13757-2
NUON
NEN
BS EN 60870-5-2
L+G
2.4 Definitions, Acronyms and Abbreviations

Item
Meaning
CB
Cold Boot
CRC
CRN
Cyclic Redundancy Check

Customer Reference Number
CV
DST
E6V
EMC
Calorific Value the energy content of gas expressed in MJ/m

Daylight saving time
Ultrasonic Gas Meter with integral valve
Electromagnetic compatibility
ESD
NV
Electrostatic Discharge
Non Volatile (memory) memory such as EEPROM which does not require power to
maintain its value
Universal Coordinated Time
UTC
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 8 of 66
2.5 Glossary of Terms
Binding
The process of associating two devices to enable successful communications
Cold boot
Cold boot is a module reset, normally applied at the factory. On Cold Boot all of the Modules registers are reset to
zero. The Libra Module shall initiate a Cold boot when there is no electronic signature in the non-volatile memory
at power up.
Commissioning
At binding the LPR communications commences.
Divorce
Divorce is the process by which an E6V meter is de-registered from the Libra Module.
E6V
An electronic gas meter manufactured by Landis + Gyr.
Effective Time
A time, set within the Module, that defines when new tariff data shall become active.
Marriage
Marriage is the registration of an E6V meter to a Libra Module such that the meter will communicate and receive
commands from the Libra Module.
Purge
A process in which gas is allowed to flow through the pipes in order to clear any trapped air. Charges are not
applied to Purged gas.
UnMarried Libra Module State

In an un married state the Libra Module is in standby state and does not communicate with the base meter or any
other LPR communications, but engineering mode is available to perform either a marriage or divorce (options of
valve open or closed are available).
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 9 of 66
3. PHYSICAL REQUIREMENTS
3.1 Hardware configuration

The Libra Module shall have the hardware configuration as shown in Figure 1 below:
Display
Low Power
Radio
E6V Galvanic Port
Microcontroller
M-Bus
Port
ASIC
Power up
Reset
Button A
Interrupt
controller
Buzzer
RTC
Button B
Battery
monitor
Watchdog
Figure 1 Hardware Configuration

Libra Modules hardware components are listed with their functions in Table 1 below.
Component
E6V Galvanic Port
Display
Button A
Button B
RTC
Low Power Radio *
Function
A communications port with the E6V meter, which transmits meter readings,
valve status and meter status data using the BSEN 601107 protocol.
Liquid crystal display for customer and operational information.
Advances the display sequences and initiates valve opening
Used to select functions when servicing the Libra Module and updating the
meter index display.
Real Time Clock.
Radio Communications link to Electricity Meter for AMR and Valve control
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 10 of 66
M-Bus Port *
Interrupt Controller
Battery Monitor
Watchdog
Power up reset
Buzzer
Wired link to Electricity Meter for AMR and Valve control

Reports events to microcontroller e.g. wake up at certain time
Monitors and reports battery state
Timer that triggers reset if microcontroller ceases to function properly
A pulse generated when the battery is applied to the de-energised electronics
Audible tone generator for user prompts
Table 1 Hardware Components
Note that either the Low Power Radio or M-Bus port will be fitted in production.
3.2 Meter Parameters

3.2.1 Meter Types
The module shall operate with domestic gas meters manufactured to
BS EN 14236: 2007.
See Section 2.3
3
The meter rating (Qmax) shall be 6m /h at a maximum operating pressure of 75mbar.

[REQ:METER-1]
3.2.2 Meter Valves

The meters used with the Libra Module shall have an integral electrically operated valve
3
With the valve open the total mean pressure absorption shall not exceed 2mbar at a flow rate of 6m /h of air.
With the valve closed by normal operation of the mechanism the rate of leakage through the valve shall not exceed
5 l/h with an inlet pressure of 100mbar.
The valve must function correctly before and after the full duration of a vapour test as defined in section 7.3.2.2 of
BS EN 1359, see Section 2.3 [015].
The module shall have the capacity to close and open the meter valve.
[REQ:METER-2]
The valve function for at least 10,000 operations.
[REQ:METER-3]
3.3 Case Construction

3.3.1 General
The case shall meet the requirements of BSEN 60079-02004 and BSEN 60079-15 to protection level N (zone 2).
The case shall be suitable for mounting within domestic premises and should be capable of being re-cycled at the
end of the Modules life.
The module shall be sealed in position when assembled onto the meter.
With the meter mounted in the normal service position all OFGEM approved meter seals or markings shall be
visible.
With the module mounted in its normal position the meter index shall be fully visible.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 11 of 66
The case shall carry a property label.

[REQ:METER-4]
3.3.2 Case used with E6V

The enclosure of the Libra Module shall be a 2-part plastic moulding. The front moulding shall be fitted with an
LCD window, 2 button caps.
The rear moulding shall use the galvanic connection methodology developed for the Galvanic version of the E6V.
The Libra Module shall be secured in place on the front of the meter by two screws. The screws shall permit the
fitting of a utility seal.
Suitable locations shall be included on the enclosure for labels required by the customer or metrology authority.
3.3.3 Case Material

The Libra Module shall be constructed of a self-extinguishing polycarbonate material with no internal circuitry
visible from the outside of the unit when mounted in its normal operating position.
The case material shall have a flammability rating of V0 to IEC 60707:1999.
The modules case shall meet the requirements of BS EN 60695-11-5:2005 (needle flame test), severity 30
seconds, see Section 2.3 [012].
[REQ:METER-5]
Physical Withstand
The case shall withstand impact, pressure and vibration without damage in accordance with:
BS 6941 New number! Appendix B for normal risk of mechanical damage from impact energy of 3.5J;
Appendix M of BS 4161 prEN14236: Part 3: 1989, withstand of vibration and transit shock;
The windows shall withstand an impact of 0.2J and in accordance with BS4161 Part 3: 1989: Section 4.5.4.
[REQ:METER-6]
3.3.4 Serial Numbers

The serial number of the integrated Gas meter and module is referred to as the Equipment Identifier by NTA.
The E6V base meter provides a serial number in the following format : Snnnnnnnn\YY\mm which is an S followed
by an 8 digit serial number, a 2 digit year of manufacture and a 2 digit model number e.g. "S00000123\08\54".
NTA require the following format for the equipment identifier : Meter code, 5 character code assigned by KIWA-Gastec = 28100
Serial number, 10 characters, assigned by the vendor, with leading zeroes if the number is shorter than 10
characters
Year of manufacturing, 2 characters, assigned by the vendor as year of century
The Equipment Identifier will be composed as follows :
5 character meter code written in NV memory at customisation (28100 for NTA)
2 digit model number from base meter
8 digit serial number from base meter
2 digit year from base meter
[REQ:METER-7]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 12 of 66
The module shall have a label fitted to the rear of the Libra Module with a unique module serial number, this will not
be entered in any memory.
[REQ:METER-8]
The module shall have its date of Manufacture stored on the manufacturing database linked to Jabil module serial
number; and have its date of Warranty expiry stored on the manufacturing database linked to the Jabil module
serial number.
[REQ:METER-9]
The bar code format shall be to BS DD ENV 12925:1998, code 128, see Section 2.3 [011].
[REQ:METER-10]
3.3.5 Installation
The combined meter and module shall be capable of being installed in accordance with BS 6400 -1, see Section
2.3 [007].
[REQ:METER-11]
The module when attached to the meter shall meet the requirement of operation within an explosive atmosphere,
zone 2, in accordance with BS 60079-15:2005, see Section 2.3 [010].
[REQ:METER-12]
3.3.6 Temperature Range

The module shall operate in the range -10C to +40C.
[REQ:METER-13]
The storage temperature shall be -20C to +60C.
[REQ:METER-14]
3.3.7 Environmental Withstand

The module case shall provide environmental protection to level IP55 against dust and water penetration, in
accordance with BSEN 60529, see Section 2.3 [005].
[REQ:METER-15]
It shall not be possible for water to collect in any part of the combined meter/module assembly when installed in
accordance with BS6400: part1.
[REQ:METER-16]
The module shall operate within a relative humidity range of 30 to 98% condensing.
[REQ:METER-17]
The module shall be demonstrated to operate correctly following the completion of damp heat cycling test defined
in BS60068_2_30 part 2 severity a in a powered operational state.
The Libra Module or any element designed for external installation, shall be demonstrated to operate correctly
following the completion of damp heat cycling test defined in BS60068_2_30 part 2 severity b in a powered
operational state. In addition the module shall remain reliable and usable at environmental temperatures between
-20oC and +60oC (assuming dry air).
[REQ:METER-18]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 13 of 66
3.4 EMC
The Libra Module shall not emit any electromagnetic energy likely to cause interference with proprietary radio or
television receiving equipment that complies to Radio Agency requirements.
The Libra Module shall not emit any electromagnetic energy likely to cause the malfunction of any other electronic
or electrical equipment that may be reasonably expected to be found in the home and which meets an appropriate
standard of immunity.
Any reasonable level of electromagnetic energy of either transient or continuous nature shall not affect the normal
operation of the module.
The Libra Module shall be CE marked.
[REQ:METER-19]
3.4.1 Electrostatic Discharge Immunity

The module shall meet the ESD immunity requirements in accordance with BS EN 601000-4-2 using 10 contact
discharges to each of:
a) The conductive Surfaces;
b) A horizontal coupling plane;
c) A vertical coupling plane;
at a discharge severity level 3 i.e. 6 kV at intervals of 10 seconds.
[REQ:METER-20]
The module shall meet the ESD immunity requirements in accordance with BS EN 601000-4-2 using 10 air
discharges to insulating surfaces at severity level 3 i.e. 8 kV, at intervals of 10 seconds.
[REQ:METER-21]
NOTE: During the tests the inlet boss of the meter shall be connected to the ground plane used for testing.
3.4.2 Electromagnetic Susceptibility

The module shall be immune to the effects of electromagnetic high frequency fields and meet the requirements of
BS EN 61000-4-3 to severity level 3, see Section 2.3 [014].
[REQ:METER-22]
The module shall be immune to the effects of electromagnetic induction at 50Hz and meet the requirements of BS
EN 61000-4-8 to severity level 3 for 15 minutes.
[REQ:METER-23]
The module shall be immune to the effects of electromagnetic induction from pulsed fields and meet the
requirements of BS EN 61000-4-9 to severity level 3 for 15 minutes.
[REQ:METER-24]
Module has to meet the requirements of ETSI EN 301 489-01V1.6.1 and ETSI EN 301 489-01V1.6.1
3.4.3 RF Susceptibility
The module shall be immune to radio frequency amplitude modulated fields and meet the requirements of BS EN
61000-4-3 at severity level 3, i.e. 10V/m.
[REQ:METER-25]
The module shall be immune to radio frequency pulse modulated fields and meet the requirements of BS EN
55022, see Section 2.3 [016].
[REQ:METER-26]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 14 of 66
3.4.4 Emissions
The module shall as a minimum meet the requirements for levels of emissions as defined in BS EN 61000-6-3, the
target level however shall be to meet the requirements specified in BS EN14236. see Section 2.3, [018].
[REQ:METER-27]
3.4.5 Radio Equipment Additional EMC Requirements

The module shall meet the requirements as detailed in:
ETSI EN 301 489-01 V1.6.1 "Electromagnetic compatibility and Radio spectrum Matters (ERM); Electromagnetic
Compatibility (EMC) standard for radio equipment and services - Part 1: Common technical requirements"
And
ETSI EN 301 489-03 V1.4.1 "Electromagnetic compatibility and Radio spectrum Matters (ERM); Electromagnetic
Compatibility (EMC) standard for radio equipment and services - Part 3: Specific conditions for Short-Range Devices
(SRD) operating on frequencies between 9 kHz and 40 GHz"
[REQ:METER-28]
3.4.6 Radio Equipment Spectrum Usage

The Libra Module shall meet the requirements detailed in:
ETSI EN 300 220-1 V2.1.1 (2006-04) "Electromagnetic compatibility and Radio spectrum Matters (ERM);
Electromagnetic Compatibility (EMC) standard for radio equipment and services - Part 3: Specific conditions for
Short-Range Devices (SRD) operating on frequencies between 9 kHz and 40 GHz"
ETSI EN 300 220-1 V2.1.1 (2006-04) "Electromagnetic compatibility and Radio spectrum Matters (ERM); Short
Range Devices (SRD); Radio equipment to be used in the 25 MHz to 1 000 MHz frequency range with power levels
ranging up to 500 mW - Part 1: Technical characteristics and test methods"
CEPT ERC/REC 70-03 (31 October 2006) "ERC Recommendation 70-03 Relating to the use of Short Range
Devices (SRD)"
[REQ:METER-29]
3.5 Reliability
The module shall have a minimum design life of 20 years.
[REQ:METER-30]
In normal use the module shall not require maintenance (including battery replacement) within a 10 year period.
[REQ:METER-31]
3.6 Safety
The Libra Module shall comply with EN71 Part 1: 1988, Part 2: 1994, Part 3: 1995.
[REQ:SAFE-1]
The Libra Module module shall meet the requirements BS EN 61010-1 Safety Requirements for electrical
equipment for measurement, control and laboratory use, General requirements.
[REQ:SAFE-2]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 15 of 66
3.6.1 Childproof
The module shall be designed so as not to present a safety hazard, especially to young children. In this respect it
shall be designed to be in accordance with BS 5665: Parts 1, 2 and 3: 1989 for children under 36 months, with the
exception of the clause in part 2 section 5.1 which states that toys shall not contain flammable gases, see Section
2.3 [019].
[REQ:SAFE-3]
The accessible edges of the Libra Module shall be not be sharp and shall be tested in accordance with Section
4.18 of BS 5665 : Part 1: 1989.
[REQ:SAFE-4]
3.6.2 Users
The external design of the module shall be such as to minimise the possibility of injury to any users.
No accessible part of the system shall present a toxic hazard and there shall be no emission of toxic material in
normal use.
[REQ:SAFE-5]
3.6.3 Gas
The module shall not be capable of opening the valve without physical intervention and an appropriate mechanism
to ensure that it is a deliberate and legal action.
[REQ:SAFE-6]
The failure of the module or any single part of the module and meter combination operating outside of specification
shall not cause the valve to open once it has closed unless this is caused by failure of the valve components
directly responsible for sealing the valve.
[REQ:SAFE-7]
3.6.4 Hardware Interlock

There shall be a hardware interlock for valve opening when the Libra Module operates with an E6V meter.
[REQ:SAFE-8]
When conditions at the module are satisfied for the valve to be opened, the module shall transmit a hardwaregenerated interlock signal to the meter.
[REQ:SAFE-9]
The hardware interlock signal shall depend upon the following conditions being met simultaneously:
Button A is pressed for more than 5 seconds and then released within 16 seconds.
As second interlock the safety ASIC must see a further signal prior to enabling the valve open signal. This must
deliver equivalent safety levels as per L210.
The valve open operation must occur within 2 minutes of commencing operation.
[REQ:SAFE-10]
It shall not be possible for the valve to be opened without the hardware interlock signal being present.
[REQ:SAFE-11]
Valve closures shall not depend upon the interlock signal.
[REQ:SAFE-12]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 16 of 66
3.7 Customer Interface Requirements

3.7.1 Push Buttons
The Libra Module shall have two pushbuttons:
One red and marked A;
The other black and marked B.
[REQ:BTN-1]
The buttons shall be easily distinguishable by a partially sighted person by an embossed feature on either the
buttons or the case adjacent to the buttons.
[REQ:BTN-2]
The buttons shall incorporate a travel limit in order to limit excessive pressure being applied to the button or its
mounting.
[REQ:BTN-3]
Operation of the buttons to wake up the Libra Module shall be limited to a maximum limit in any one day this limit
shall be configurable at the factory.
[REQ:BTN-4]
3.7.2 Display
The Module shall provide a 2-line, 16-character per line dot matrix, liquid crystal display.
[REQ:LCD-1]
The display shall support upper and lower case characters, and at least 8 user-defined characters.
[REQ:LCD-2]
The minimum height of the display characters shall be 4.85 mm.
[REQ:LCD-3]
The design lifetime of the LCD shall be a minimum of 20 years.
[REQ:LCD-4]
The contrast ratio of the LCD, when active, shall be such that the display shall be readable throughout the angular
range of +/- 45 degrees in both the horizontal and vertical planes, over the operating temperature range.
[REQ:LCD-5]
It shall be possible for the system microcontroller to turn the power supply to the LCD on and off, as required.
[REQ:LCD-6]
3.7.3 Warning Buzzer

The Libra Module shall be fitted with a buzzer with a frequency in the range 1500 to 3000Hz to provide audible
signals.
[REQ:BUZZ-1]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 17 of 66
The Libra Module shall be capable of producing a number of unique audible indication tones as defined in Table 2
below.
Output
Tone 1
Tone 2
Tone 3
Tone 4
Tone 5
Tone Pattern Produced by Buzzer

1 x 0.25 sec ON
2 x 0.25 sec ON separated by 0.25 sec OFF
3 x 0.25 sec ON separated by 0.25 sec OFF
2 sec ON
12 x 0.125 sec ON separated by 0.125 sec
OFF
Table 2 Tones Produced by Buzzer

[REQ:BUZZ-2]
3.8 Real Time Clock

The Libra Module shall maintain a crystal controlled Real Time Clock.
[REQ:RTC-1]
The RTC shall have calendar facility and correct leap year implementation.
[REQ:RTC-2]
The RTC shall operate using Standard Time.
[REQ:RTC-3]
The RTC shall maintain accuracy better than 30 minutes per year at a temperature of 20C.
[REQ:RTC-4]
The clock shall have a range from 01/01/1990 to 31/12/2089.
[REQ:RTC-5]
The RTC shall use a two-digit year counter, with a base year of 1990 (i.e. 1990 = 90).
[REQ:RTC-6]
When 2089 is reached the Libra Module date shall wrap around to 1990.
[REQ:RTC-7]
The real time clock in the module shall be set to the time in the electricity meter when bound.
[REQ:RTC-8]
The E6V shall synchronise its time with the Libra Module clock at least once per day.
[REQ:RTC-9]
NOTE: The E6 meters calendar runs pre 1990 to post 2089.
The Libra Module shall use the E6V meter calendar between 1990 and 2089 only.
[REQ:RTC-10]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 18 of 66
3.9 Battery
3.9.1 General
Battery life shall be a minimum of 10 years based on the average number of weekly events set out in Table 3
below.
Event
MBus Communications (wired only)
LPR Communications (wireless only)
Valve operation
Number / week
168 (=24x7)
168 (=24x7)
0.25
Table 3 Module Average Weekly Activity

[REQ:BATT-1]
NOTE : For the Wired M-Bus meter, an assumption is made here that there will be no more than an average of 4
communications transactions per hour e.g. a read of this meter and 3 others. If this assumption is not valid (e.g.
the use of Wireless Dongle on the wired M-Bus to communicate with an In Home Unit with communications every
15s), then a hardware architecture change of the Wired M-Bus meter will be required. The simplest change would
be the addition of a small address filtering processor (powered by M-Bus) to prevent the module being woken
frequently by other communications traffic.
It shall not be necessary to break any metrology authority seal in order to change the battery.
[REQ:BATT-2]
3.9.2 E6V Application

The battery for the module for use with an E6V meter shall operate from a single, Tadiran Lithium Thionyl Chloride
battery.
[REQ:BATT-3]
The battery shall be a D-cell and have a capacity of 19AH.
[REQ:BATT-4]
The battery shall have a nominal voltage of 3.6V.
[REQ:BATT-5]
The maximum open circuit voltage shall be 3.7V.
[REQ:BATT-6]
3.10 Copyright Infringement Detection

The Libra Module firmware shall include non-functional code at selected locations to act as Copyright breach
detectors.
[REQ:CODE-1]
The Copyright protection code shall have no effect on the operation of the Libra Module application.
[REQ:CODE-2]
The Copyright protection code shall be designed in such a manner that recreation of the application from the
product specification or software design specification would not include the copyright features.
[REQ:CODE-3]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 19 of 66
3.11 Galvanic Communication Port

The Libra Module for use in conjunction with an E6V meter shall be equipped with a Galvanic communications port
that shall support one or two protocols. These are the FLAG protocol or a custom gas meter protocol. All gas
meters support the former, while the latter is only supported by the latest meters. The custom protocol gives
significantly faster base meter access and consequent savings in battery consumption.
The FLAG protocol conforms to the requirements of BS EN 601107, see Section 2.3 [004].The port shall operate at
4800 baud after a sign on at 300 baud. The data format of the communications shall be 7 Data bits, 1 Stop bit and
even parity.
[REQ:COM-1]
The custom protocol E6V (Adaptive+) Basic Communications Protocol is documented in reference [21].
[REQ:COM-2]
The module shall determine at marriage if the base meter supports the custom protocol. If it does, this protocol will
be used instead of the FLAG protocol for all base communications.
[REQ:COM-3]
3.12 Watchdog
The Libra Module shall incorporate a hardware reset (watchdog) that shall enable recovery from fault conditions
without any apparent change to the Libra Modules operation.
[REQ:SAFE-13]
3.13 Recovery From reset

The meter shall function correctly after recovering from a reset condition. It will recover the time and date from the
base meter. It will operate using this time until the time is set again via the M-Bus interface.
[REQ:SAFE-14]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 20 of 66
4. MODULE FUNCTIONALITY
4.1 Introduction
4.1.1 Physical Implementation
The Libra Module shall be a hardware platform suitable for use with the Landis+Gyr E6V Galvanic Gas meters with
internal valve
[REQ:BASE-1]
4.2 Interfaces
The hardware interfaces are shown Figure 1.
The E6V meter there shall be a physical connection to the meter, with the meter providing connections to the
communications port and battery, all meter reading and valve control shall be performed by communications
between the two elements.
Communications between the Libra Module and the E6V meter shall be in accordance with the protocol described
in L+G E6 - Quantum Prepayment Interface.
[REQ:BASE-2]
The communication interface shall be set to normal security level type 04 module and the key index to 0xF.
[REQ:BASE-3]
4.3 Modes of Operation

The Libra Module shall operate in credit mode for this application.
[REQ:MODE-1]
In Credit mode the default position for the valve is open, messages received via the LPR can change the state of
the valve.
4.4 Marriage and Divorce

For a module to operate with an E6V meter it must be married to that meter. The marriage process registers the
meters particulars with the module and thereafter the module shall communicate with that meter only in order to
provide measurement and control functions.
[REQ:MODE-3]
The module and meter association generated by marriage shall be broken by a divorce procedure. Following
divorce both the meter and the module can be married to other elements.
[REQ:MODE-4]
4.5 External Communications

There are two mutually exclusive options for external communications, one of which always applies. These are :th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 21 of 66
Option 1 : The Libra Module shall be equipped with a Low Power Radio (LPR) device that enables instructions and
data transfers to take place between the Libra Module and the support system via an electricity meter.
[REQ:MODE-5]
Option 2 : The Libra Module shall have an M-Bus port that enables instructions and data transfers to take place
between the Libra Module and the support system via an electricity meter.
[REQ:MODE-6]
4.6 Displays
The dialogue map below shows the displays that the module has and the user navigation between them. The only
start points are Cold Boot or Wait. The effect of timeouts is not shown. The display goes off after a period of
inactivity.
Cold Boot
Unmarried
only to marriage
Pin Entry
A
PIN entry
Meter Index
Wait
PIN error
Valve State
C
Engineering
Service
Unbind
Time
Valve open
Marriage ?
Temp Comp
Reading
Volume today
hold
Marrying
Clear Events
Volume last 7
days
Release
Purge
Volume last 28
days
wait - opening
valve
Divorce
Re-open Valve
Volume last 12
months
Divorce - valve
operate ?
Battery change
Temperature
A
C
confirm
Software Version
change battery
now
A
A
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 22 of 66
The current status of the Libra Module shall be indicated on its display.
[REQ:DISP-1]
The user display shall be normally in an inactive state, i.e. it shall appear blank.
[REQ:DISP-2]
When a button is pressed the display shall be activated to show the current status.
[REQ:DISP-3]
When the Libra Module has an E6V base meter and a button is pressed the Libra Module shall interrogate the
meter for its current index and status and update the current status of the Libra Module.
[REQ:DISP-4]
The display shall remain active for 0.5 minute from the last button press.
[REQ:DISP-5]
The display shall provide the user interface to the Libra Module.
[REQ:DISP-6]
In circumstances where the data required for a requested display is not immediately available, for example it may
be necessary for the LIBRA Module to read the E6V meter or to perform a complex calculation, then the display
shall show the message Please Wait until the data is available.
[REQ:DISP-7]
The Libra Module shall minimise the time for which Please Wait shall be indicated.
[REQ:DISP-8]
The text on the display will have a production selectable language. The initial languages are English Dutch and
German, with English being the default.
[REQ:DISP-9]
4.7 Operating States

The Libra Module shall have three operating states:
1. Unpowered;
2. Unmarried;
3. Active.
[REQ:MODE-7]
4.7.1 Unpowered State.

When the battery is disconnected from a Libra Module in any state, the Libra Module shall enter the Unpowered
State.
[REQ:MODE-8]
In the Unpowered state, the Libra Module shall be inactive and data shall be retained in non-volatile memory.
[REQ:MODE-9]
When the Libra Module changes from the Unpowered state it shall set a Power Recovery flag to on.
[REQ:MODE-10]
When the Libra Module Sets the Power Recovery Flag it shall set the time and date in the Battery Low time and
date fields.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 23 of 66
[REQ:MODE-11]
When the Libra Module is powered up from the unpowered state it shall check its application software by
calculating a checksum and comparing it with the checksum stored within the application data.
[REQ:MODE-12]
If the checksum comparison fails the Libra Module shall display Fail and an error code XX as the default display
as shown below.
F A I L
E X X
Figure 2 Failed on Power up

[REQ:MODE-13]
If the Libra Module is powered up for the first time and undergoes a cold Boot the display shall be as shown below.
CO LD
B O OT
P LE A S E WA I T
Figure 3 Standby Display after Cold Boot
[REQ:MODE-14]
A Libra Module in an Unpowered state may or may not be married to an E6V meter.
4.7.2 UnMarried State.

A Libra Module shall enter the unmarried state when a divorce is performed via the engineering mode.
The following display will be shown
U * * * * *
Figure 4 Unmarried Display

A Libra Module shall display the E6V status flags with no delay whilst in this mode.
[REQ:MODE-15]
4.7.3 Active State.

The Libra Module shall display the metrology index and valve status whilst in this mode when button A is pressed.
3
The meter index is displayed as 8 digits with 3 decimal points in units of m .
[REQ:MODE-16]
Register : Meter Index
M
x
3
Any meter error flag (B) is shown on bottom right of display.

[REQ:DISP-10]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 24 of 66
Pressing button A momentarily will show the valve state display. This has three different forms for Valve open,
closed and enabled.
[REQ:DISP-11]
The Valve Open display is
G
[REQ:DISP-12]
The Valve closed display is
G
[REQ:DISP-13]
The Valve enabled display is
G
P r
[REQ:DISP-14]
4.7.4 Meter Index Display

The Libra Module shall display the meter volume register in the meter index screen, this screen shall be displayed
when 2 presses of Button A are made from the LCD powered down state.
The module shall initiate a read from the meter and displays the information as soon as it is available.
[REQ:DISP-15]
To minimise the delay in waiting for the information to be available, a meter read from the module shall be initiated
on the first button press.
[REQ:DISP-16]
Once displayed the Meter Index shall be updated by pressing Button B.
[REQ:DISP-17]
4.8 Rolling Registers

The Libra Module shall be capable of displaying the values of a set of customer display registers referred to as
Rolling Registers.
[REQ:ROLL-1]
A short text description shall identify each Rolling Register.
[REQ:ROLL-2]
The Registers to be included and their order of display in Rolling Registers shall be configurable at the time of
manufacture or by CS message.
[REQ:ROLL-3]
The first Rolling Register shall always be set by the register order as detailed in Table 4 Rolling Registers and
register order
[REQ:ROLL-4]
Once Rolling Registers have been selected they shall be viewed by pressing button A to select each display in turn.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 25 of 66
[REQ:ROLL-5]
At the end of the sequence of Rolling Registers the display shall return to the default display.
[REQ:ROLL-6]
When Rolling Registers have been selected if there is no button press for 30 seconds the display shall return to the
default display.
[REQ:ROLL-7]
Standard Rolling Registers shall be accessed by pressing and holding down button A for 3 seconds.
[REQ:ROLL-8]
The table below defines those Rolling Registers available.
Description
Register
Order
Software Version
Time of day and date (Standard time)
Total volume today (total since day
commencing)
Total volume last 7 days
Total volume last 12 months
Meter Temperature
Table 4 Rolling Registers and register order
[REQ:ROLL-9]
4.8.1 Rolling Register Displays

The Rolling Registers are shown in the figure below.
Register : Software Version, it is highly recommended that this be used
S
[REQ:ROLL-10]
Register : Time and Date in standard time, not recommended for consumer viewing.
T
(
M
[REQ:ROLL-11]
Register : Volume since midnight
V
[REQ:ROLL-12]
Register : Volume last 7 whole days
V
7
n
D
m
[REQ:ROLL-13]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 26 of 66
Register : Volume last 28 whole days

V
[REQ:ROLL-14]
Register : Volume last 12 whole months
V
[REQ:ROLL-15]
Register : Temperature in meter
T
[REQ:ROLL-16]
Figure 5 Rolling Registers
The time display with standard time is not an option for the Dutch market.
4.8.2 Rolling Register Access

The Rolling Registers as shown above are accessed by pressing and holding button A from the default active
screen. The screens are incremented in the order shown in the Rolling register order table by pressing and
releasing button A.
[REQ:ROLL-17]
4.9 Valve Control

4.9.1 General
The Libra Module shall enable the flow of gas by opening the meter valve, provided that:
No uninhibited Events are present that require the valve to remain closed
Or
The module is in the service menu, relevant pass code is entered and purge is selected.
[REQ:VALVE-1]
Whilst button A is being held down Hold for Gas shall appear on the display.
[REQ:VALVE-2]
Open sequence as defined in 0
[REQ:VALVE-3]
The Libra Module shall attempt to open the valve, even if the meter indicates that the valve is already open (i.e. in
service mode from purge function).
[REQ:VALVE-4]
When the valve is opened for purging purposes it shall close when the purge volume limit or purge time limit are
exceeded.
[REQ:VALVE-5]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 27 of 66
The Libra Module shall display a warning message to turn off all appliances prior to allowing the valve to be
opened, Appliances Off?.
[REQ:VALVE-6]
If the Libra Module detects that the meter valve fails to open when required, a 'Valve open' Event shall be
registered. The module shall attempt a number of retries of this function, to be set at 3.
[REQ:VALVE-7]
The Libra Module shall have a facility for closing the valve at a particular date and time that is programmable via
the LPR interface.
[REQ:VALVE-8]
The Libra Module shall have a facility for enabling the valve at a particular date and time that is programmable via
the LPR interface.
[REQ:VALVE-9]
The Libra Module shall close the meter valve if instructed by the system.
[REQ:VALVE-10]
The Libra Module shall display whether the meter valve is open or closed.
[REQ:VALVE-11]
4.9.2 Event Actions

The Libra Module shall close the meter valve where required by a particular fault or operational condition.
[REQ:VALVE-12]
An indication that the meter valve has closed because of such an Event shall be recorded and be available as part
of the module status.
[REQ:VALVE-13]
The Events that cause the module to close a valve shall enabled or disabled by configuration at the factory.
[REQ:VALVE-14]
4.9.3 Operation with E6V Meters

Control of the E6V meter shall be implemented by control data sent from the Libra Module to the meter through the
E6-Galvanic interface.
[REQ:BASE-4]
All valve open commands sent to the E6V during normal operation shall be preceded by a Volume Index Threshold
Cut-off value. The Libra Module shall not issue valve open commands without index limits at any time other than
during an authenticated divorce procedure.
Module is a type 04 and will enable a valve open if vcut < vol index.
The maximum cut off value possible shall be set
[REQ:BASE-5]
4.9.3.1 Meter Index Limits transferred to E6V
After sending a new index limit to the E6V, the Libra Module shall read the pre-payment data back from the E6 to
check that the Volume Cut-off Enabled flag is set.
[REQ:BASE-6]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 28 of 66
4.10 Valve Opening

When the Libra Module is in Active State, valve opening shall be enabled when the meter has been commanded to
open its valve.
[REQ:VALVE-15]
The E6V valve control includes interlock and timing control procedures that are executed by the ASIC, see Section
2.3 [025].
[REQ:VALVE-16]
The valve opening process for the E6V meter is shown in the Figure 6 E6V Valve Opening Process, after the
Release A for gas screen the module shall display opening valve.
[REQ:VALVE-17]
Press and hold button A
Valve Open Screen
A p p l i a n c e s
H o l d
A
f o r
Hold A until release screen
Valve Open Screen 1.
H o l
Release button A when

instructed
Valve open screen 2.
R e l e a s e
f o r
g a s
Meter is opening the

valve
Valve Open Screen 3.
P l e a s e
Wa i t . .
O p e n i n g
V a l v e
f o r
O f f ?
g a s
g a s
Figure 6 E6V Valve Opening Process

[REQ:VALVE-18]
The valve opening command shall not be sent to the E6V meter until the consumer, responding to the offer of valve
opening, has held button A in the depressed position for 5 seconds.
[REQ:VALVE-19]
During the 5 second period the Libra Module shall display Hold A for gas.
[REQ:VALVE-20]
Once the command has been sent to the E6, the Libra Module software shall start a valve open interlock procedure
using the ASIC hardware.
[REQ:VALVE-21]
The ASIC shall check for the presence of a button A press sequence and for the software driving the card interface
port to the appropriate state.
[REQ:VALVE-22]
When these conditions are satisfied the ASIC shall commence the timing procedures required to control the
galvanic port that allows the E6 meter to open the valve.
[REQ:VALVE-23]
The software request shall be a continuous activation of the transmitter into the galvanic Port during the timed
interval that is initiated by the ASIC.
[REQ:VALVE-24]
The system shall achieve equivalent safety levels achieved with the L210 prepayment meter and module.
[REQ:VALVE-25]
th
Date of Issue: 5 June 2008
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F

Page 29 of 66
Once the valve open sequence has been completed the Libra Module shall return to its default display.
[REQ:VALVE-26]
4.10.1 High Flow Open interlock

This feature is only activated for a period of time after the valve is opened. Its purpose is quickly disconnect the
supply if a heavy load is detected (indicating that an appliance was left switched on). It has three parameters which
are set in production :
X flow limit : 1..255 litres
Y interlock time : 1..180 seconds
An enable flag for this feature
When the high flow open interlock is enabled and the valve is closed , the module shall set the cutoff volume in the
meter to X litres above the current index prior to initiating the valve open sequence. The module shall then
ascertain the status of the valve after Y Seconds, if the valve has not closed the module shall then set the cutoff
value to the desired level to maintain supply relevant to the module mode.
[REQ:VALVE-26]
During the High Flow Interlock operating period, the module display shall remain on the opening valve display.
[REQ:VALVE-27]
If the valve has closed during the interlock period, the buzzer beeps and the following display is shown for 4
seconds.
A
O
&
N
R
[REQ:VALVE-28]
4.11 Buzzer Operation

4.11.1 Operational Status
The Libra Module shall use a range of audible signals to indicate the state of execution of Libra Module functions.
[REQ:BUZZ-3]
Each signal in conjunction with the Libra Modules display shall give a unique audiovisual indication of the Libra
Module and Base Meter state.
[REQ:BUZZ-4]
The table below lists the tone that shall be emitted when a particular event occurs.
Tone
1
1
1
1
1
1
3
4
4
Event
Libra Module offers to open the valve
Marriage successful
Divorce successful
Libra Module power up diagnostics complete
Press button A to open the valve
Release button A to open the valve
Valve opened successfully
Valve open interlock timer expired
Failed to clear Event
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 30 of 66
Tone
4
5
Event
General process failure occurred
Fatal error
Table 5 Audio Signals Status
[REQ:BUZZ-5]
4.12 Libra Module Reference Numbers

The Libra Module serial number is defined in section 3.3.4.
The Libra Module shall have a unique PCB serial embedded at the time of manufacture,
[REQ:NUM-1]
The Libra Module shall have a module serial number label attached to the back of module to enable traceability of
the module if it returned to L+G.
[REQ:NUM-2]
4.13 Software Version Number

The Software version number has four separate elements as detailed below.
X1X2.X3X4.X5X6.X7X8
X1X2 is Communications type, 01 for wired M-Bus, 02 for Wireless M-Bus
X3X4 is spare (default to 00, spare for other use!)
X5X6 is the major software version, used to indicate major changes / upgrades in functionality
X7X8 is the minor software version, used to indicate minor changes or changes internal to the manufacturing
processes.
[REQ:VER-1]
The software version can be displayed in the rolling registers.
[REQ:VER-2]
The software version will be displayed for 2 seconds after power up.
[REQ:VER-3]
The M-Bus protocol requires that the software version be reported to the system. However it only allows a single
byte for encoding this number. This means that a M-Bus specific version number must be used. This has a range
of 0..255 and is incremented on each new release.
[REQ:VER-4]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 31 of 66
5. CONFIGURATION DATA
5.1 Overview
This data can be used to influence the operation of the meter. It is set at manufacture.
5.2 Purge Volume

The meter shall have the facility for an engineer to open the valve whilst the default state is valve closed to enable
a meter to be installed / commissioned.
This functionality shall be accessed from the engineering display when the correct pin code is entered.
[REQ:CFG-1]
5.2.1 Volume Limit

The maximum volume of gas (in litres) that the Libra Module shall allow to pass when in purge mode before closing
the valve. The Libra Module shall allow the purge volume limit (2 litre) to pass before commencing the valve
closing procedure unless the purge time limit, see Section 0 below, is reached.
[REQ:CFG-2]
5.2.2 Time Limit

The maximum period of time for which the Libra Module shall allow the valve to remain open in purge mode.
[REQ:CFG-3]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 32 of 66
6. ACCOUNTING
6.1 General Functions

The Libra Module shall maintain a record of its account status by reference to following gas usage registers:
The value of all gas flow through the associated meter.
[REQ:ACC-1]
6.2 Profile Registers

The Libra Module shall maintain hourly Profile registers for the previous 10 days of operation. These readings are
taken as close to the hour boundary as possible.
[REQ:ACC-2]
The Libra Module shall maintain daily Profile registers for the previous 31 days of operation. These readings are
taken as close to the hour boundary at the end of the day as possible.
[REQ:ACC-3]
Each register consists of :
an absolute meter index reading with a range of 0 to 99999.999 m3 and a resolution of 0.001 m3.
a timestamp with a resolution of minutes.

[REQ:ACC-4]
These shall be reset at manufacture or at marriage.
[REQ:ACC-5]
These registers can be read via the appropriate M-Bus link.
[REQ:ACC-6]
6.3 Cumulative Registers

The Libra Module shall maintain Cumulative registers that shall be reset at marriage.
[REQ:ACC-7]
3
Cumulative Volume Register shall have a range the range 0 to 99999m with no decimal points.
[REQ:ACC-8]
The cumulative registers shall be:
6.3.1 Volume Registers

The volume registers shall be available in the rolling register displays, see [REQ:ROLL-16]
Figure 5 Rolling Registers.
[REQ:ACC-9]
6.3.2 Total Volume today

The total volume of gas used since the start of the accounting day.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 33 of 66
[REQ:ACC-10]
6.3.3 Total Volume Last 7 Days

The total volume shall be logged for a 7 day rolling period.
3
7 day rolling Volume Register shall have a range the range 0 to 99999m .
[REQ:ACC-11]
6.3.4 Total Volume Last 28 Days

The total volume shall be logged for a 28 day rolling period.
3
28 day rolling Volume Register shall have a range the range 0 to 99999m .
[REQ:ACC-12]
6.3.5 Total Volume Last 12 Months

The total volume shall be logged for a 11 month rolling period plus the part element of the calendar month,
th
therefore the register is 11 months + number of days volume through calendar month i.e. for the 13 of December
the 12 month volume shown will equate to the total volume of gas consumed for the months January to November
st
th
(inclusive) plus the total daily consumption for the 1 to the 12 of December (inclusive).
3
12 month rolling Volume Register shall have a range the range 0 to 99999m .
[REQ:ACC-13]
6.3.6 End of Day Processing

At 1.45am each day the Libra Module shall:
Set the E6V meter clock to its clock value.
Evaluate and log its current status
Increment the battery life timer by 1 day.
[REQ:ACC-14]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 34 of 66
7. SERVICE OPERATION
The Libra Module will support service operations without the use of a field service tool. The service operations are
divided into two separate menus, a Service menu and an Engineering menu. These are selected by entering the
relevant PIN code.
Pressing button B for 5 seconds will bring up the Engineer Access screen (Figure 7), and then pressing button A to
enter the Pin code Access Screen (Figure 8).
E
Figure 7 Engineering Access Screen
e
B
P
<
>
>
Figure 8 Pin Code Access Screen

[REQ:SV-1]
The PIN code is 6 digits.
[REQ:SV-2]
When the Pin code Access screen is shown, as seen in Figure 8, the pin code is entered by pressing button A, at
the first press of button A the most significant digit of the pin code shall show 0 this can then be incremented by
pressing button A repeatedly. When the correct number is shown button B shall be pressed to move to the next
digit.
[REQ:SV-3]
This process is repeated until all 6 digits are correct, and button B is then pressed for greater than 3 seconds to
confirm the pass code.
[REQ:SV-4]
If the incorrect pin code is entered the Libra Module shall show for a short time.
P
Figure 9 Pin Code Error Screen

[REQ:SV-5]
7.1 Engineering Menu

The Libra Module shall display the Engineering menu of Libra Module functions that shall include:
Marriage (meter to module); (available when unmarried)
Divorce (meter from module); (available in all modes)
[REQ:SV-6]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 35 of 66
7.1.1 Divorce
Divorce shall de-register the E6V within the Libra Module. Divorce with valve open will only be offered if an
enabling system command has been received in the current day.
[REQ:SV-7]
On completion of the divorce process the E6V meter shall operate as a standard credit meter and the module shall
only display the volume index, by pressing button A. In this state the volume index shall be updated by pressing
button B.
[REQ:SV-8]
On completion of divorce the current key index and future key index shall be set to 0xF.
[REQ:SV-9]
Divorce shall be offered on a Libra Module in all states.
[REQ:SV-10]
The Divorce menu is available by entering the Engineering Screen and entering the 6 digit pin code as shown in
Figure 8, and pressing button B to move to next screen until the Divorce screen is shown
Divorce Service Screen 1
D I v o r c e ?
A = A c c e p t , B = N e x t
Figure 10 Divorce Screen 1

[REQ:SV-11]
Divorce Service Screen 2
V a l v e
V a l v e
O p e n ?
C l o s e d ?
A
B
Figure 11 Divorce Screen 2

[REQ:SV-12]
If A is selected the meter shall go through the valve open sequence, Figure 6.
[REQ:SV-13]
If B is selected the Libra Module shall instruct the meter to close the valve and display please wait until the
operation is complete.
[REQ:SV-14]
7.1.2 Marriage (to E6V)

During the marriage procedure the Libra Module shall be registered with the E6V meter as a Type 04 module with a
key index value of 0xF.
[REQ:SV-15]
When the Key Index is set to 0xF the module is designated as normal security type and CRC and P0 / P2 security
methods are employed for marriage and divorce.
[REQ:SV-16]
When the Marriage option is selected the Libra Module shall marry the E6V meter and remain in Active State.
[REQ:SV-17]
The Marriage Procedure is as follows:
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 36 of 66
Press and Hold Button B for greater than 5 seconds

The Engineering Screen is then shown:
Engineering Access Screen
E n g i n e e r i n g
Pin Code Access Screen
T y p e
P i n :
X X X X X X
A ^
B < >
B > 5 s :
E n t
Marriage Screen
M a r r y ?
A = A c c e p t
Button A is pressed and the

Pin code access screen is shown:
The correct pin code is entered and the
first service screen is shown, button B is
pressed until the marriage screen is shown:
, B = N e x t
Press Button A to Marry:
Marrying Screen
M a r r y i n g
The Libra Module shall then offer to open the

valve
Valve Open Screen
A p p l i a n c e s
O f f ?
H o l d A
f o r
g a s
Valve open Screen 1
H o l d
Valve open Screen 2
R e l e
f o r
Valve open Screen 3
P l e a s e
W a i t . .
Op e n i n g
V a l v e
m e t e r .
And the button A shall be pressed as instructed.

A
a s e
g a s
f o r
g a s
Figure 12 Marriage Process Screens

[REQ:SV-18]
7.2 Service Menu

The Libra Module shall display the service menu of Libra Module functions that shall include:
Clear module Events (available when married)
Clear meter diagnostics. (available when married)
Battery change (available in all modes)
Purging
Unbinding (gas meter to electricity meter)
Temperature compensated reading
Open valve operation (if state is open)
7.2.1 Purge
The Libra Module shall offer to open the meter valve for purging.
[REQ:SV-19]
If the offer to open the valve for purging is accepted, the meter valve shall open and the Libra Module shall display
that purging is active as shown in Figure 13 below.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 37 of 66
P u r g i n g
A - Q u i t ,
O N
X X X L
B - U p d a t e
Figure 13 Purging Display

[REQ:SV-20]
The amount of gas dispensed for purging shall be determined by the value set by configuration Data.
[REQ:SV-21]
As an alternative to purging a quantity of gas it shall be possible to set a time for purging.
[REQ:SV-22]
The purge time shall be defined in Configuration Data.
[REQ:SV-23]
When the purge limit or time limit is reached the valve shall be closed.
[REQ:SV-24]
Purge gas shall not incur any charges.
[REQ:SV-25]
Following the completion of the installation and commissioning operation the Libra Module shall move to the Active
state.
[REQ:SV-26]
The offer to purge gas shall be made even if the valve is already open.
[REQ:SV-27]
If the offer to open the valve for purge gas is accepted, the Libra Module shall open the valve.
[REQ:SV-28]
Provided no faults occur the valve shall remain open, until gas is passed to the volume or time limit set in
Configuration Data is reached, or until the Service operation is cancelled (This is achieved by pressing button A
from Figure 13 Purging Display). After the valve has closed during this operation if it was open prior to the service
operation the meter should default to the Credit enabled mode.
[REQ:SV-29]
When the limit is reached the valve shall be closed.
[REQ:SV-30]
If the offer to open the valve for purging is not accepted, then the valve shall remain in the state it was in prior to the
service operation.
[REQ:SV-31]
7.2.2 Event and Status Clearing

It shall be possible to reset Libra Module Events and E6V status reports through the service display.
[REQ:SV-32]
The Event and Status service screen shall be available by entering the Engineering Access Screen,
During service operations the Libra Module shall show each detected Event or Status, if any, as defined in 0.
[REQ:SV-33]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 38 of 66
Events shall be displayed, in turn with the most recent first.

[REQ:SV-34]
For each Event displayed, when button A is pressed the Libra Module shall clear the Event record.
[REQ:SV-35]
When no Events remain, the Libra Module shall display No Events Found.
[REQ:SV-36]
All Events shall show the date of the first instance of the Event.
[REQ:SV-37]
When no Events remain and button A is pressed the Libra Module shall display the detected E6V status flags.
[REQ:SV-38]
The Libra Module shall show each detected status flag in turn with most recent first.
[REQ:SV-39]
For each flag displayed, when button A is pressed the Libra Module shall attempt to clear the flag.
[REQ:SV-40]
When an E6V event is not present in the E6V message the E6V status flag shall be flag cleared.
[REQ:SV-41]
7.2.3 Unbind
It shall be possible to install the Libra Module in a number of system configurations.
A Libra Module shall be capable of being commissioned in a number of different use cases, namely:
It may be used on a wired M-Bus link from an Electricity Meter
It may be used on a LPR link from an Electricity Meter or a M-Bus wireless dongle
or
In either case it is bound to the master device in normal use. It is necessary to break this binding if an incorrect
binding was made during installation or the master device has failed and needs to be replaced.
Selecting for a Wired Module, causes its M-Bus address to be reset to 0.
[REQ:SV-42]
Selecting for a Wireless Module, causes it enter binding mode.
[REQ:SV-43]
Selecting for either Module, causes its Link encryption key to be removed.
[REQ:SV-44]
7.2.4 Battery Change

The battery change option shall be offered as one of the service menus accessed by entering the Engineering
Access Screen and entering the 6 digit access code at the pin Access code screen and pressing button B until the
Battery change screen is shown.
[REQ:SV-45]
Battery Change Screen
B a t t e r y
C h a n g e ?
A = A c c e p t , B = N e x t
Figure 14 Battery Change Screen

th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 39 of 66
[REQ:SV-46]
The Libra Module shall offer a battery change confirmation screen, as the impact of accidentally accepting a battery
change option will be warnings / incorrect status flags.
[REQ:SV-47]
Battery Confirmation Screen
C o n f i r m
C h a n g e ?
A = Y e s , B = N o
Battery Change Instruction
C h a n g e
N o w !
b a t t e r y
Figure 15 Battery Change Confirmation & Instruction Screen

[REQ:SV-48]
Following confirmation of the battery change the Libra Module shall send a battery change command to the base
E6V meter and shall reset all battery use counters.
[REQ:SV-49]
7.2.5 Open Valve Operation

It is possible for a meter to have an incorrect state for the valve. This could happen due to a knock during transport
changing an open valve (which is the shipping state) to be closed. An installer needs to be able to correct this. If
the valve is open, a menu option will allow the valve open sequence to be started.
[REQ:SV-50]
7.2.6 Temperature Compensated Meter Reading

The meter is currently certified as a non temperature compensated one. It also maintains a temperature
compensated register which some customers wish to access. As this is not certified, it cannot be viewed on
normally accessible displays. It can be viewed as the last item on the Service Menu.
Register : Temperature compensated meter reading
T
[REQ:SV-51]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 40 of 66
8. OPERATIONAL ERRORS
The Libra Module shall be capable of detecting and reporting a number of erroneous operational conditions,
referred to as Events that shall include hardware, software failures and tamper conditions. It is not always possible
to distinguish between the three different types of conditions.
The Libra Module shall record two event types; E6V status events (that the E6V events that logged within base
meter and are reported to the Libra Module as a status flag ) and Libra Module events (events that the Libra
Module detects either independently or by interrogation of the E6V).
When an Event occurs the Libra Module log the event and undertake the action detailed in Table 7 Event Table.
[REQ:EV-1]
Events may be inhibited, in which case the event shall not close the valve, cause an alert or produce a log entry.
[REQ:EV-2]
When an uninhibited Event occurs which causes the Libra Module to log an Event log then the presence of the
message shall not inhibit access to the Libra Modules Rolling Registers.
[REQ:EV-3]
8.1 Event Log

The Libra Module shall maintain an Event Log.
[REQ:EV-4]
Each entry in the Event Log shall include:
Event Type;
Time and Date of occurrence;
Flag to indicate whether the Event has been reset.
[REQ:EV-5]
Each time an Event is registered the next available log entry shall be filled.
[REQ:EV-6]
Once the Event log is full any additional faults and tampers shall not be logged.
[REQ:EV-7]
The Event Log shall be cleared on Cold Boot and on binding.
[REQ:EV-8]
The Event Log may be cleared during a servicing operation.
[REQ:EV-9]
The Event log shall have space for sixteen entries.
[REQ:EV-10]
Each Event shall have an associated flag that shall be set.
[REQ:EV-11]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 41 of 66
8.2 Event Definitions

The Libra Module shall detect and report fault conditions when in the Standby,or Active states.
[REQ:EV-12]
When the Libra Module detects a fault condition it may attempt to:
Close the meter valve, if set as an option
Log the type of fault condition detected.
Set a status flag that is sent to the Electricity meter via the Low Power radio communications, further details in the
Smart Meter LPR communications specification, and may cause an alert to be issued via the Electricity.
[REQ:EV-13]
Inhibited Events shall not close the valve, cause an alert or produce a log entry.
[REQ:EV-14]
If the particular Event detected does not require valve closure, only the log entry shall be carried out.
[REQ:EV-15]
Each fault when displayed during servicing, shall be identified by a unique alphanumeric character.
[REQ:EV-16]
A list of the unique numbers is given in Table 7.
[REQ:EV-17]
Each fault code shall be accompanied by a 16-character text description of the fault that has occurred. A listing of
the text messages is given in Figure 16.
[REQ:EV-18]
8.2.1 Libra Module Event Definitions

8.2.1.1 E 01 Leaky Valve
A Leaky Valve Event shall be generated when the Libra Module detects that the base meter is recording a flow of
gas when the valve is reported as closed.
[REQ:EV-19]
The threshold for leaky valve tamper shall be:
The meter index must have increased by a volume greater than or equal to 200 litres Updated to the latest meter
index every 1.45am event.
[REQ:EV-20]
8.2.1.2 E11 Valve Open Operation Failure
A Valve Open Fault shall be generated if the valve fails to open for 3 consecutive attempts when an open valve
request has been issued. This is a failure of the meter to open the valve, the meter shall report that the valve is
closed.
Note: this could happen if the timings of the safe to open are not adhered to, either a fault or the meter is being
operated outside its rated temperature.
[REQ:EV-21]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 42 of 66
8.2.1.3 E3 Security Warning

A decrypted command from the Electricity meter could not be decoded properly. This is probably due to an
incorrect Link key being used. It could be caused either by the Electricity meter having the wrong key or a fraud
attempt.
[REQ:EV-22]
8.2.1.4 E6 Reverse volume
A reverse volume event shall be generated when a Libra Module detects more than Y litres of reverse volume is
detected within a day.
Y shall default to 2000 litres, but should have a maximum of 10000 (99999 is acceptable) litres. Y shall be
programmable within the factory.
[REQ:EV-23]
8.2.1.5 E26 Meter Failed to Action Command
A Failed to Action Command fault shall be generated when a command issued by the Libra Module to the E6V
meter is not implemented within the time allowed for that command.
Operation
Action
Marriage
Marriage failed displayed
Divorce
Divorce failed displayed
Valve Open failure
Meter fails due to communications

problem
Battery change
Fails due to communications error.
Table 6 F26 Table

[REQ:EV-24]
8.2.1.6 E28 Libra Module Software Fault
This fault is generated when corruption is detected in the EEPROM contents.
[REQ:EV-25]
8.2.1.7 E29 Libra Module Hardware Fault
A fault has been detected in the module hardware.
[REQ:EV-26]
8.2.1.8 E30- Libra Module EEPROM Fault
An EEPROM fault has been detected. Note that a catastrophic EEPROM failure will cripple the module and hence
cannot be logged or reported.
[REQ:EV-27]
8.2.2 E6V Status

The E6V meter shall report E6V events that it detects. Events reported by the E6V meter shall be logged with the
following definitions.
[REQ:EV-28]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 43 of 66
8.2.2.1 FA Catastrophic Error

A Catastrophic Error shall be generated when the E6V meter reports a catastrophic error event (A flag) to the Libra
Module.
The module will display the Error flag on the Meter Index screen and report a permanent error to the electricity
meter when the status is next read. Pressing button A shall still show the Meter Index screen.
This event cannot be cleared other than by re-marrying the module.
All normal screens shall be accessible.
[REQ:EV-29]
8.2.2.2 FB Major Event
A Major Event fault shall be generated when the E6V meter reports that a major event (B flag) has been detected
and this condition is reported for four consecutive days.
This event shall be cleared if the E6V no longer reports it, but the log entry shall remain. It can also be cleared by
re-marrying the module.
The following events can trigger an FB status flag:
communications lockout of the meter communications.
Reverse flow detected.
Valve re-closures detected.
Test mode entered.
All normal screens shall be accessible.
[REQ:EV-30]
8.2.2.3 FC Major Problem
A Major Problem fault shall be generated when the E6V meter reports that a major problem (C flag) has been
detected and the condition is reported for four consecutive days.
This event shall be cleared if the E6V no longer reports it, but the log entry shall remain. It can also be cleared by
re-marrying the module.
[REQ:EV-31]
The following Events can trigger an FC flag
A recoverable memory error (non critical).
Missed measurements occur
Measurement errors occur.
8.2.2.4 FF Low Battery
Battery usage is monitored as a days counter in NV memory. The warning limit count for battery life is stored in NV
memory during production.
A Low Battery fault (F flag) shall be generated when the meter has detected that the battery will expire during the
next 6 months.
[REQ:EV-32]
The module will display the Error flag on the Meter Index screen and report a low battery to the electricity meter
when the status is next read. Pressing button A shall still show the Meter Index screen.
This event shall be cleared by a battery change procedure. It can also be cleared by re-marrying the module.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 44 of 66
Event Actions
A flag in fault data shall identify each Libra Module fault or tamper.
[REQ:EV-33]
The E6V meter shall report faults to the Libra Module using ASCII characters.
[REQ:EV-34]
All tampers and some faults shall be reset using the service operation and via messages received from the system.
[REQ:EV-35]
Table 7 below defines the actions taken on detection of each type of Event and whether the Event is re-settable
using a Service Operation.
Event
Code
Event type
Action taken
(When no inhibits)
E01
Leaky Valve
E11
Valve Open Operation failure
E3
Security warning
E6
Reverse flow greater than 200

litres per day is seen
E26
E6V Failed to Action

Command
E6V status report
Catastrophic meter failure,
meter may not be working
correctly.
E6V Event flag
Unexpected meter events,
communications, reverse flow.
Log and send on next

system message
system message.
FC
E6V Operational problem

Recoverable memory error or
measurement errors.

system message.
FF
Low Battery
E08
Software fault
E09
Hardware fault
E10
Eeprom fault

system message.
system message.
system message.
system message.
FA
FB
Attempt valve close,

log
Log & issue system
report
Log and send system
report
Log and send system
report
Recommended Field
Action
How Reset
At next
midnight
Yes
Remotely monitor product,

(close valve option to
generate call) Check
orientation of meter if a field
visit.

system message.
Plan visit to replace meter.
Monitor status over short

period ( 2 weeks), plan visit
to investigate / replace
meter if persists.
Monitor status over short
period ( 2 weeks), plan visit
to investigate / replace
meter if persists.
Plan visit within next few
months to change battery
Libra Module faulty replace
At next
midnight
At next
midnight
At next
midnight
No
Yes
Yes
Yes
N
Table 7 Event Table

[REQ:EV-36]
8.3 Event Displays

Figure 16 below shows a typical format for displays of faults and tampers that appear when the Servicing
Procedure is performed. The example shows a reverse flow event at a particular time.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 45 of 66
Figure 16 Event Displays

[REQ:EV-37]
There is a whole series of these. The top line indicates the type of event and the bottom line shows the time it
occurred on. They are only shown when present and through the engineering display.
8.4 Mapping to M-Bus Error Status

The M-Bus header sent to the Electricity Meter has a byte for status reporting. This is generated as follows :Bit
01
01
01
01
2
3
4
5
6
7
Name
Application error 00
Battery low
Permanent error
Temporary error
Clock
synchronisation
Fraud attempt
Valve alarm
Generation of
No error
Busy NOT used
Any application error TBA
Reserved
Event code FF or module reports battery life exceeded
Event code E08 or E09 or E10 or FA
E01 or E3 or E26 or (FB > 4 days) or (FC > 4 days)
New time more than 30s different from existing module time
Event code E6
Latest valve state not same as last commanded
[REQ:EV-38]
8.4.1 Reset of M-Bus Error Status

The M-Bus header status flags will be reset as follows :Bit
Name
01
01
01
01
2
3
4
Battery low
Permanent error
Temporary error
Clock
synchronisation
Fraud attempt
Valve alarm
6
7
Reset When
N/A
N/A
At next midnight.
N/A
When battery changed
None.
At next midnight. Note that if reason persists it will be set
again.
At next midnight.
At next midnight.
When valve state becomes the same as last commanded
[REQ:EV-39]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 46 of 66
9. BATTERY
The Libra Module shall have the facility to report the status of the Libra Module battery and the E6V meters battery,
where the E6V is the base meter.
[REQ:BATT-7]
Battery health shall be monitored by maintaining a battery usage timer.
[REQ:BATT-8]
9.1 Battery Usage Timer

The Libra Module shall have a means of assessing remaining battery life and shall indicate end of battery life at
least four weeks in advance of its exhaustion, assuming normal use.
[REQ:BATT-9]
The Libra Module shall maintain a battery life timer that shall be initialised during manufacture.
[REQ:BATT-10]
The battery life timer shall be recorded in days.
[REQ:BATT-11]
It shall be possible to reset the battery life timer during battery replacement.
[REQ:BATT-12]
The threshold at which end of battery life is indicated shall be configured during manufacture.
[REQ:BATT-13]
The threshold shall be specified in days and shall be in the range 180 to 9000 days.
[REQ:BATT-14]
When the battery lifetime threshold is passed, the Libra Module shall show a low battery icon on the default screen
that identifies the source of the battery alarm.
[REQ:BATT-15]
The display shall remain until the battery life timer is reset.
[REQ:BATT-16]
The Libra Module shall detect a low battery in the associated E6 meter using the data flags transmitted from the
meter.
[REQ:BATT-17]
The Libra Module shall report a low battery condition of the E6V meter.
[REQ:BATT-18]
The battery indication shall appear in default displays in the Standby and Active states.
[REQ:BATT-19]
The battery indicator shall be the last two digits on the bottom row of the default display, where there is insufficient
space the only the B section shall be displayed. i,e. in Credit Enabled mode.
[REQ:BATT-20]
The Libra Module shall clear the low battery indication only when a Service operation rests the battery timer.
[REQ:BATT-21]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 47 of 66
The Libra Module shall clear its E6 low battery indicator and the associated flag when it receives either a lower
order fault flag, or no longer receives any fault flag from the E6V.
[REQ:BATT-22]
The E6 battery low flag shall be written into the fault log such that it shall be possible to differentiate between a low
Libra Module battery and a low E6 battery, if two batteries are utilised.
[REQ:BATT-23]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 48 of 66
10. COMMUNICATIONS LINK TO ELECTRICITY METER

The module shall have either a wired M-Bus communications port or a wireless M-Bus port that complies with the
M-Bus protocol stack. These links will also comply with the P2 Companion standard [18], which defines how these
protocols are used. The link is to an Electricity Meter, which provides the link to the rest of the system. The
application functionality is the same regardless of the link type used.
There is some functionality which is specific to the type of link used, notably the establishment of the addressing
between electricity meter and the associated Gas meter.
10.1 Wired M-Bus Link

The module shall have a wired M-Bus communications port that complies with references [14,16,17,18]. This is a
wired link to an M-Bus master device, normally an Electricity Meter. The module is always the slave on this link.
[REQ:WIRED-1]
The application messages which are common to the wireless link are defined in section 10.
10.1.1 Communications Parameters

The link is half duplex. It uses a fixed baud rate of 2400 baud with 1 start bit, 8 data bits, even parity and 1 stop bit.
[REQ:WIRED-2]
The module is a slave on the link, it will only respond to requests from the Electricity meter.
[REQ:WIRED-3]
10.1.2 Bus Addressing

Only M-Bus primary addressing is used. The module has a bus address, which the master uses to address it. This
address is set to 0 at manufacture and at marriage. This address is reserved for un-configured slaves. The
module shall accept and answer all communication to this address, while its address is to 0.
[REQ:WIRED-3]
The module address can be set to a value in the range 1 to 250 by the bus master, during the discovery process
(see 0). The module shall accept and answer all communication to this address, when it is set.
[REQ:WIRED-4]
Addresses 251, 252 and 253 are reserved and not used.
Address 254 is the address for test and diagnosis. The module shall accept and answer all communication to
this address.
[REQ:WIRED-5]
Address 255 is the broadcast address. The module shall accept and execute all communication to this address but
will not reply to the bus master.
[REQ:WIRED-6]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 49 of 66
10.1.3 M-Bus Discovery Process

This process is described in reference [14] and in reference [18]
The M-Bus master periodically checks for new devices on address zero. It initiates communication by sending a
short frame: SND_NKE. If the module has its address set to 0, it replies to it. This is shown in the example below.
Field
Value
Description
Start Character
10H
Short format
C-Field
40H
SND_NKE
A-Field
00H
Primary Address of M-Bus slave
Checksum
xxH
Sum of A and C fields, two least

significant Hex digits
Stop Character
16H
Always 16H
The module responds with an acknowledgement that the message has been received.
Field
Single character
Value
E5H
Description
The slave returns SCC (single

control character )
[REQ:WIRED-7]
To change the primary address from zero to an open address the M-Bus master writes a new address to the M-Bus
slave using SND_UD with a DIF identifier of 1.
Field
Value
Description
Start Character
68H
Start byte long telegram
06H
Length
06H
Length (repeated)
Start Character
68H
53H
Control Field
00H
Address base address (00)
CI
51H
Data send (master to slave)
DIF
01H
Data identifier
VIF
7AH
Address data
xxH
New address
CS
25H
Checksum
Stop Character
16H
Always 16H
Field
Single character
Value
E5H
Description

control character )
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 50 of 66
[REQ:WIRED-8]
10.1.4 Wired Unbinding

The meter shall support a method of breaking the binding between it and the Electricity meter. This shall be done
by an option on the engineering menu. Once selected, the meter M-Bus address is reset back to 0 and the link key
is removed.
[REQ:WIRED-9]
10.2 Wireless M-Bus Link

The module shall have a wireless 868MHz M-Bus communications port that complies with references [14,15,17,18].
This is a two-way radio link to an M-Bus master device, normally an Electricity Meter. Wireless meter data will be
exchanged according to reference [14] using T2 mode.
[REQ:LPR-1]
The application messages which are common to the wired link are defined in section 0.
10.2.1 General Operation

T2 mode actually consists of 2 modes
1. Reception mode (T2) : 100k baud
2. Transmission mode (T1) : 32.768k baud
[REQ:LPR-2]
The link layer of reference [20] with the format class FT3, variable length frames shall be used.
[REQ:LPR-3]
Transmitter duty cycle: module to master : 0.1 %
[REQ:LPR-4]
The module only powers up its LPR link when it needs to use it. The master normally has its LPR link in receive
mode.
[REQ:LPR-5]
The module communicates with the electricity meter a number of times per day. This number is programmable in
the range 1 .. 48, with a default of 24. The first period starts just after 12PM.
[REQ:LPR-6]
Every communications period, at a random time in the period start, the module device will send an access
demand message (which includes application data e.g. meter index), C=48H and wait for an acknowledge (C=00H
) of this request. If an acknowledge is received, then a link is established and the Electricity Meter master may now
send M-Bus messages to the slave. The module will power down its LPR link after a 100 millisecond period of no
received data.
[REQ:LPR-7]
10.2.2 Link Layer Usage

An application message is transmitted using 2 or more blocks. The first block specifies the link layer service
required and the meter address. The link layer service is normally one of :
Send / no reply : daily send of readings by module
Send / confirm : command to module
Request / respond : request for status of module

th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 51 of 66
The second contains the M-Bus Control Information field and any required data. More blocks may need for longer
application data. The total maximum application data size is 245 bytes, carried in 17 blocks. The blocks are
transmitted one after the other from the sender with no gaps in transmission.
[REQ:LPR-8]
First block
Field
Size - bytes
Description
Length - the number of subsequent user

data bytes including the control and
address bytes and excluding the CRC
bytes
Control field see below
Manufacturer ID
Address unique to manufacturer
CRC
Second block (only exists if application data transmitted) possibly last block
Field
CI
Size - bytes
Description
M-Bus Control Information field
Data
15 or less
CRC
Data with M-Bus message
Optional blocks
Field
Size - bytes
Data
16 or less
CRC
Description
Data with M-Bus message
[REQ:LPR-9]
The control field has a different meaning depending on the direction, which it indicates. An outgoing field can
select between a SEND/CONFIRM, a SEND/NO REPLY or a REQUEST. A return field can select between
CONFIRM and RESPOND.
Note that the outgoing direction is defined by who initiated the message, which can be either the Electricity meter or
the module.
10.2.3 Wireless Binding

There are two wireless binding methods, one for binding with an electricity meter, the other for binding with an MBus wireless dongle. The former is specified by the NTA while the latter is necessary for use with the L+G Dongle.
In both cases the initial communication is the same. It is the Dongle reply which invokes its specific binding
method. The Dongle is connected on wired M-Bus to the relevant Electricity Meter.
Initially the meter is in storage mode and unbound. There are no wireless transmissions in this mode. Pressing
any button will cause the meter to send the initial binding message once per minute for a maximum period of one
hour. This may stop sooner if a reply is received to its message. This is referred to as installation mode.
[REQ:BIND-1]
Once a meter is bound, it performs it regular data transmissions. This is referred to as installed mode.
[REQ:BIND-2]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 52 of 66
If the meter enters installation mode and the hour period expires without binding, it will continue to send the initial
binding message once every hour. Pressing a button will cause it to start the 1 minute binding messages for
another hour.
[REQ:BIND-3]
The Gas meter sends the following access demand message to initiate the binding process (link layer fields
marked WL) :Field
L WL
C WL
M WL
A WL
CRC WL
CI
DIF
VIF
Production number
CRC WL
Value
Description
29
06H
CA 19
00 00 00
00 23 45
Xx xx
78H
0DH
78H
17 ASCII
characters
XX XX
Length = 29
Access demand install mode
Manufacturer ID = 19 CA
Module unique radio address

Variable length
Equipment Identifier
Also referred to as serial number
Checksum
[REQ:BIND-4]
10.2.3.1 Binding (NTA)

In this case, the operator uses the electricity meter to complete the binding. The Electricity meter displays all the
production numbers of access demand messages it receives from different meters. The operator selects the
relevant number and the Electricity meter sends a confirm to that meter. The meter is bound when that message is
received. There is only 3ms after the access demand to send the confirm.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 53 of 66
The confirm message is a link layer one.

Field
L WL
C WL
M WL
A WL
Value
Description
9
00H
CA 19
00 00 00
00 23 45
Xx xx
CRC WL
Length = 9
Confirm
[REQ:BIND-5]
10.2.3.2 Binding (Dongle)
In this case the operator uses the Gas Meter to select the Dongle to bind to. The Dongle has an 8 digit number
printed on it which uniquely identifies it, which is referred to as the binding number. First the operator puts both the
Gas Meter and the Dongle into install mode (in any order). The Gas Meter transmits its access demand message
once a minute. Any unbound Dongle should reply with a Dongle Confirm message at a random time up to 2
seconds afterwards. The randomisation is necessary as several Dongles may reply. This message contains the
Dongles unique binding number.
The Gas Meter displays the binding numbers received in sequence until the installer presses a button to accept
one. It then transmits an access demand message with the binding number of the selected Dongle. The Dongle
needs to send a Confirm message.
[REQ:BIND-6]
The Dongle Confirm message has the following fields process (link layer fields marked WL) :Field
L WL
C WL
M WL
A WL
Value
Description
17
07H
CA 19
00 00 00
00 23 45
Xx xx
51H
0DH
CRC WL
CI
DIF
Length = 17
Dongle confirm

Variable length
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 54 of 66
Field
VIF
Command
Binding number
CRC WL
Value
Description
7fH
00h
XX XX XX
XX
XX XX
Manufacturer specific
Binding number
Dongles binding number in packed
BCD
Checksum
[REQ:BIND-7]
The access demand message with the selected binding number has the following fields process (link layer fields
marked WL) :Field
L WL
C WL
M WL
A WL
CRC WL
CI
DIF
VIF
Command
Binding number
CRC WL
Value
Description
29
06H
CA 19
00 00 00
00 23 45
Xx xx
78H
0DH
7fH
00h
XX XX XX
XX
XX XX
Length = 29
Access demand install mode

Variable length
Binding number
Dongles binding number in packed
BCD
Checksum
[REQ:BIND-8]
10.2.4 Wireless Unbinding

The meter shall support a method of breaking the binding between it and the Electricity meter or Dongle. This shall
be done by an option on the engineering menu. Once selected, the meter is back in binding mode again and the
link key is removed.
[REQ:BIND-9]
10.2.5 Wireless Pre-binding

There is a factory option to supply the meter already bound to a wireless Dongle (which is shipped in the same
box). In this state, the meter shall not commence the normal hourly transmission until both buttons have been
pressed simultaneously.
[REQ:BIND-10]
10.3 Security
Each Electricity / Gas Meter pair will use a unique link key to encrypt application data records transferred between
them. Data sent from the Gas Meter will be encrypted if the link key exists, otherwise it will be transmitted unencrypted. The Gas Meter will not accept commands unless they are encrypted (and a link key exists).
[REQ:SEC-1]
There is considerable risk that the Link key distribution part of the system will not be operational before the first
units are installed. To overcome this, a flag (set in the factory) will allow unencrypted commands to be accepted
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 55 of 66
until a link key is supplied. Once a Link key has been supplied, this flag is reset. If the link key were removed, unencrypted commands would not be accepted.
[REQ:SEC-2]
The application telegram data section after the fixed header must be encrypted using the AES 128bit encryption
algorithm in CBC mode with a 128 bit key and an Initialisation Vector set to all 0s. The signature field in the
header (short or long) indicate encryption usage as follows :Status
algorithm
Status # bytes
Description
No Encryption
00
00
Used before link key available
AES Encryption
04h
XX
XX is number of encrypted bytes, must be

multiple of 16
The first data record sent in any direction will be the time and date. This ensures that the first block in CBC mode
has changing data.
[REQ:SEC-3]
The Electricity Meter sends the link key to the Gas Meter after binding. This key is encrypted using the meters
unique master key, but the message that sends it is not. Once the link key is delivered, all data transferred
thereafter is encrypted, except for a new link key.
The Gas meters unique master key is installed at manufacture. It is also securely transferred to the central
system, which uses it to send new link keys.
The Link key transfer message uses two 64 bit integer records to encode the key. It has the following fields (link
layer fields marked WL) :Field
L WL
C WL
M WL
A WL
CRC WL
CI
DIF
VIF
VIFE
Link key part 1
DIF
VIF
VIFE
Link key part 2
CRC WL
Value
Description
17
53H
CA 19
00 00 00
00 23 45
Xx xx
51H
07H
fdH
19h
8 x byte
07H
fdH
19h
8 x byte
XX XX
Length = 17

64 bit integer
Encryption key
Encrypted using meter master key
64 bit integer
Encryption key
Encrypted using meter master key
Checksum
[REQ:SEC-4]
The messages sent from the Electricity Meter to the Gas Meter have a short header added to specify the use of
Encryption.
Name
Value
Description
CI
5Ah
Access #
0..255
See fixed header
Status
1 byte
See fixed header
Short header used
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 56 of 66
Signature -
# bytes
Signature - algorithm
04h = AES
# encrypted bytes
[REQ:SEC-5]
10.3.1 Block size filling when encryption used

Due to the block mode that the encryption algorithm is used in, the data to be encrypted must be an integer multiple
of the block length which is 16 bytes. This will be achieved by appending M-Bus filler records to obtain the desired
data length. An M-Bus filler record simply consists of a single byte DIF with the value 2fh.
[REQ:SEC-6]
If the number of encrypted bytes is less than the remaining data of the telegram, unencrypted data may
follow after the encrypted data. They shall start at a record boundary, i.e. the first byte after the encrypted
data will be interpreted as a DIF.
[REQ:SEC-7]
10.4 Application Messaging

Customer Specific Messages provide a means of remote communication from Supply Company through the
support system to specific customers. These can come either via M-Bus or the radio link. It is not envisaged that
both links will be used on a single installation.
10.4.1 Readout List

The master requests data from the module using the REQ_UD2 message. The module sends the data defined by
the readout list. This is a fixed list, which defines the items to be read, and the order they are transmitted in. The
contents of this list are also sent once per day on the radio link (see section 10.2.1). The contents of the list are :1. Time and date
2. Equipment ID
3. Valve status
4. meter configuration (capability)
5. meter index recorded on last hour boundary
6. Temperature compensated meter reading on last hour boundary
[REQ:MSG-1]
10.4.2 Manufacturer ID
The Manufacturer ID field used in the fixed header is coded unsigned binary with 2 bytes. This manufacturer ID is
calculated from the ASCII code of EN 62056-21 manufacturer ID (three uppercase letters) with the following
formula :Man. ID = [ASCII(1st letter) 64] * 32 * 32 + [ASCII(2nd letter) 64] * 32 + [ASCII(3rd letter) 64]
The ID used by L&G is FML. This gives an ID of 19 AC.
[REQ:MSG-2]
10.4.3 Message Types

The are two main types of messages employed within the Libra Module, data request messages which are
primarily requests for information and Operation messages, which are primarily instructions for the Libra Module.
10.4.3.1
Data Request
This message requests that the module send the contents of the readout list to the master. This is sent using a
REQ_UD2 message. This is an NTA requirement.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 57 of 66
[REQ:MSG-3]
The example below is shown using the Wired M-Bus link layer (fields marked -WM). There are no M-Bus
application layer fields in this message.
Field
Value
Description
Start Character WM
10H
Short format
C-Field WM
5BH
REQ_UD2
A-Field WM
01H
Address of module = 1
Checksum WM
XxH
Sum of A and C fields, two least

significant Hex digits
Stop Character WM
16H
Always 16H
The meter response is
Fixed Data Header 12 Byte
Value
Description
Start WM
68H
Start byte Long Telegram
L WM
65H
Length 101 Bytes
L WM
65H
Length 101 Bytes
Start WM
68H
Start byte
C WM
08H
Sending of the required data
A WM
XxH
Primary address or 253 for secondary address
CI
72H
Answer of variable length
78H
Ident Number, e.g. 12345678 in BCD
Ident. Nr. 4
Byte
RSP-UD2 Data Record (with Production number and reading)
Field
56H
Manf. ID
CAH
34H
12H
19H
Version
33H
SW-Version, e.g. 51
Medium
03H
Device type : Gas
Access Nr
01H
Access Counter
Status
00H
No Error (Any Application Error = 02)
Signature
00H
Default 0 (no encryption on M-Bus here)
00H
Default 0 (no encryption on M-Bus)
Variable Data Blocks (Records)

CS WM
XxH
Checksum
Stop WM
16H
Stop
[REQ:MSG-4]
There is no equivalent operation on wireless M-Bus. Instead, the meter sends the data with the access demand
startup message for the radio link.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 58 of 66
[REQ:MSG-5]
Field
Value
Description
L WL
??H
Length = ?
C WL
48H
ACCESS DEMAND
M WL
CA 19
A WL
00 00 00
00 23 45
CRC WL
Meter unique radio address
Xx xx
CI
72H
Slave to master with 12 byte header
Fixed header
12 bytes
Variable data blocks (part 1)
3 bytes
CRC WL
See response for wired unit above
Xx xx
Up to 16
bytes
CRC WL
Xx xx
If required
Up to 16
bytes
If required
10.4.3.2 Fixed Data Header

This 12 byte structure is sent to the master with any data. It is defined section 10.3.3. The status field byte is
encoded as follows :Bit
0
1
2
Description
\-application errors 00 : none, 01 : busy, 10 : application error

/
Battery low
3
Permanent error
4
Temporary error
5
Clock synchronisation error
6
Fraud attempt registered
7
Valve operation failure
[REQ:MSG-6]
10.4.3.3 Variable Data Blocks
The variable data blocks data is specified by the readout list. It will at least consist of the Meter index and the valve
status.
The Meter reading (which is not temperature compensated) is encoded as follows :Field
Value
Description
DIF
VIF
VIFE
0CH
93H
3AH
8 digit BCD
Multiplier 0.001, units m3
Value is uncorrected
Data
43H
27H
41H
e.g. Value = 31412.734 m3
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 59 of 66
Field
Value
Description
31H
[REQ:MSG-7]
The temperature compensated meter reading is encoded as follows :Field
Value
DIF
VIF
Data
Description
0CH
13H
43H
27H
41H
31H
8 digit BCD
Multiplier 0.001, units m3
e.g. Value = 31412.734 m3
[REQ:MSG-8]
The Valve status is encoded as follows :Field
Value
Description
DIF
DIFE
VIF
89H
40H
FDH
2 digit BCD
Valve status
Valve
VIFE
Data
1AH
01H
31H
Digital status
0:closed, 1:open, 2:released
[REQ:MSG-9]
The Equipment Identifier is encoded as follows :Field
DIF
VIF
LVAR
Data
Value
Description
0DH
78H
Variable length string

Equipment Identifier
11H
32H,
..30H
Length 17
17 ASCII characters
[REQ:MSG-10]
The Meter Configuration is encoded as follows :Field
Value
Description
DIF
VIF
01H
FDH
1 byte binary
Extension
VIFE
Data
67H
03H
Special supplier information

Meter has clock and valve, it is not
temperature compensated.
[REQ:MSG-11]
The Meter Time and Date is encoded as in the Set Time and Date message.
[REQ:MSG-12]
10.4.3.4 Encoding of Hourly Values
The standard encoding of real time values is shown in the previous section. The reading will normally be an hourly
one. In this case the time will be the time of the reading. The Storage bit (= bit 6) in the DIF for both the register
and the time must be set for both the time record and the meter reading record.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 60 of 66
[REQ:MSG-13]
10.4.3.5 Set Time and Date
This sets the time and date in the RTC. This is done regardless of whether it crosses a 1.45 am boundary. The
message is sent with a SND_UD message. This is an NTA requirement.
The example below is shown using the Wired M-Bus link layer (fields marked -WM)
Field
Value
Description
Start Character -WM
68H
L WM
0BH
Length
L WM
0BH
Length (repeated)
Start Character WM
68H
C WM
53H
(FCB=0)
A -WM
01H
Module address = 1
CI
51H
DIF
06H
6 Bytes integer
VIF
6DH
Date and time compound data-type I
00H
e.g. 02-09-2004 13:10:00
0AH
0DH
2DH
82H
09H
CS WM
xxH
Checksum
Stop Character -WM
16H
Always 16H
Field
Single character -WM
Value
Description
E5H

control character )
[REQ:MSG-14]
The example below is shown using the Wireless M-Bus link layer (fields marked -WL)
Field
Value
Description
L WL
12H
Length = 18
C WL
43H
SEND/CONFIRM
M WL
CA 19
A WL
00 00 00
00 23 45
CRC WL
Xx xx
CI
51H
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 61 of 66
Field
Value
Description
DIF
06H
6 Bytes integer
VIF
6DH
Date and time compound data-type I
00H
e.g. 02-09-2004 13:10:00
0AH
0DH
2DH
82H
09H
CRC WL
XX XX
Checksum
Field
Value
Description
L WL
0FH
Length = 15
C WL
00H
CONFIRM - ACK
M WL
Xx xx
Manufacturer ID
A WL
00 03 00
00 23 45
CRC WL
E-Meter unique radio address
Xx xx
[REQ:MSG-15]
If the new time is more that 60 seconds different from the old time, a time sync error flag is set. This is reported in
the status field of the fixed header.
[REQ:MSG-16]
10.4.3.6 Gas Disconnect Message
This instructs the module to close the meter valve immediately.
Field
Value
Description
Start Character WM
68H
L WM
09H
Length
L WM
09H
Length (repeated)
Start Character WM
68H
C WM
53H
(FCB=0)
A WM
01H
Module address = 1
CI
51H
DIF
89H
2 digit BCD
DIFE
40H
Valve
VIF
FDH
Valve
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 62 of 66
Field
Value
Description
VIFE
1AH
Digital status
Data
00H
Close valve
CS WM
XxH
Checksum
Stop Character WM
16H
Always 16H
Field
Value
Description
E5H

control character )
[REQ:MSG-17]
Field
Value
Description
L WL
0FH
Length = 15
C WL
43H
SEND/CONFIRM
M WL
CA 19
A WL
00 00 00
00 23 45
CRC WL
Xx xx
CI
51H
DIF
89H
2 digit BCD
DIFE
40H
Valve
VIF
FDH
Valve
VIFE
1AH
Digital status
Data
00H
Close valve
XX XX
Checksum
CRC WL
Field
Value
Description
L WL
0FH
Length = 15
C WL
00H
CONFIRM - ACK
M WL
Xx xx
Manufacturer ID
A WL
00 03 00
00 23 45
CRC WL
Xx xx
[REQ:MSG-18]
10.4.3.7 Gas Reconnect Message
This instructs the module to shall enable the meter valve to be opened by the customer.
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 63 of 66
Field
Value
Description
Start Character WM
68H
L WM
09H
Length
L WM
09H
Length (repeated)
Start Character WM
68H
C WM
53H
(FCB=0)
A WM
01H
Module address = 1
CI
51H
DIF
89H
2 digit BCD
DIFE
40H
Valve
VIF
FDH
Valve
VIFE
1AH
Digital status
Data
02H
Release valve
CS WM
XxH
Checksum
Stop Character WM
16H
Always 16H
Field
Value
Description
E5H

control character )
[REQ:MSG-19]
Field
Value
Description
L WL
0FH
Length = 15
C WL
43H
SEND/CONFIRM
M WL
CA 19
A WL
00 00 00
00 23 45
CRC WL
Xx xx
CI
51H
DIF
89H
2 digit BCD
DIFE
40H
Valve
VIF
FDH
Valve
VIFE
1AH
Digital status
Data
02H
Release valve
CRC WL
XX XX
Checksum
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 64 of 66
Field
Value
Description
L WL
0FH
Length = 15
C WL
00H
CONFIRM - ACK
M WL
Xx xx
Manufacturer ID
A WL
00 03 00
00 23 45
CRC WL
Xx xx
[REQ:MSG-20]
10.4.3.8 Set Location Information
This instructs the module to store a string, which gives the connection location.
The data record encoding on either link is :Field
Value
Description
DIF
0DH
VIF
FDH
Extension
VIFE
10H
Customer Location
LVAR
0AH
Length = 10
Data
31H34H ASCII string with 10 characters
[REQ:MSG-21]
10.4.3.9 Set Function Location
This instructs the module to store a string, which is the EAN code for the connection.
The data record encoding on either link is :Field
Value
Description
DIF
0DH
VIF
FDH
Extension
VIFE
11H
Customer Location
LVAR
12H
Length = 18
Data
31H34H ASCII string with 18 characters
[REQ:MSG-22]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 65 of 66
11. FACTORY CONFIGURATION

The shall be two stages of factory configuration:
a) The module application firmware shall be programmed into the hardware platform;
b) Adding operational data to configure the module.
[REQ:FT-1]
#
Item
Format
Min
Max
Default
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Configuration ID
Pin number
Purge volume (litres)
Purge time limit (minutes)
High flow interlock enabled
High flow interlock volume limit (litres)
High flow interlock time (seconds)
Event flags enabled
Reverse volume flag trigger
Repeated communications trigger level
Allowed button wake-ups per day
Wireless Communications wake-ups per day
Battery life counter limit (days)
Allow un-encrypted commands
User language (0:English, 1:Dutch,
2:German)
Numeric
Numeric
Numeric
Numeric
Boolean
Numeric
Numeric
Boolean
Numeric
Numeric
Numeric
Numeric
Numeric
Boolean
Numeric
0
0
0
0
1
1
200
3
3
1
1860
0
65,535
999999
1000
60
255
180
5000
255
255
48
10,000
2
0
000000
300
30
No
20
20
Yes
2000
250
200
24
3,720
No
0
The rolling registers also need to be configured :#
Item
Required
1
2
3
4
5
6
7
8
Time and Date (standard time)

Software version
Total volume today
Total volume last 12 months
Functional location
EAN Code
Order
Recommended
NO
Yes
??
??
Additionally the following operational parameters need to be loaded :
reset battery life timer

security keys for M-Bus communications;
time and date.
wired M-Bus address to 0
unique wireless M-Bus address
12. INITIAL MODULE STATES

At initial manufacture all defaults shall be set to zero, elsewhere in this document or the Libra Module
parameterisation sheet indicates otherwise.
[REQ:FT-2]
th
Landis + Gyr Ltd
S8 567 0270 0 - PS002 Issue:F
Date of Issue:
5 June 2008
Page 66 of 66

G350 M BusModuleDescription

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

G350 M BusModuleDescription

Uploaded by

Copyright:

Available Formats

Commercial in Confidence

Libra 4*5 Wired M-Bus Gas Module and

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

1.3 Revision History

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

1.4 Product Family

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

SERVICE OPERATION ...................................................................................................................................35

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

Battery Usage Timer.....................................................................................................................................47

FACTORY CONFIGURATION ........................................................................................................................66

INITIAL MODULE STATES.............................................................................................................................66

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

The electrical and physical requirements of the module;

Performance standards with which the module shall comply;

Module functionality against which product testing shall be performed;

The communications interfaces for remote access applications;

Configuration features for module definition.

Data exchange for meter reading, tariff and load control

BSEN 14236: 2007

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

characteristics. Limits and methods of measurement.

Netherlands Technical Agreement 2.2

2.4 Definitions, Acronyms and Abbreviations

Cyclic Redundancy Check

Calorific Value the energy content of gas expressed in MJ/m

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

2.5 Glossary of Terms

UnMarried Libra Module State

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

3.1 Hardware configuration

Figure 1 Hardware Configuration

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

Wired link to Electricity Meter for AMR and Valve control

3.2 Meter Parameters

The meter rating (Qmax) shall be 6m /h at a maximum operating pressure of 75mbar.

3.2.2 Meter Valves

3.3 Case Construction

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

The case shall carry a property label.

3.3.2 Case used with E6V

3.3.3 Case Material

3.3.4 Serial Numbers

5 character meter code written in NV memory at customisation (28100 for NTA)

2 digit model number from base meter

8 digit serial number from base meter

2 digit year from base meter

Landis + Gyr Ltd

S8 567 0270 0 - PS002 Issue:F

3.3.6 Temperature Range

3.3.7 Environmental Withstand

Landis + Gyr Ltd