STMicroelectronics Wireless M-Bus User manual
Wireless M-Bus is a common standard used for AMR implementation in remote energy meter readers based on European standards. It's designed for communication over twisted pair cables and supports all network configurations except for ring networks. The Wireless M-Bus firmware stack is based on European Standard EN 13757-4:2011, which specifies the required physical and link layer parameters for systems using radio to read remote meters, especially for short range device SRD unlicensed telemetry bands. This European Standard encompasses systems for walk-by, drive-by and fixed installations.
Advertisement
Advertisement
UM1759
User manual
Wireless M-Bus firmware and application
Introduction
The M-Bus (meter bus) is a common standard used for AMR implementation in remote energy meter readers based on European standards (physical and link layer: EN 13757-2; application layer: EN 13757-3). The M-Bus is also compliant with European Standard
EN 1434 on heat meters.
The M-Bus interface is very cost effective, because it is designed for communication over twisted pair cables. For long distance communication, it supports all network configurations
(linear, star, etc.), except for ring networks. When queried, the meters send data to a concentrator which can be accessed either locally or remotely.
A radio variant of M-Bus, Wireless M-Bus, is also specified in EN 13757-4.
The Wireless Meter Bus is an open standard for Automatic Meter Reading at sub-1 GHz RF.
The relevant standards are:
•
European standard prEN 13757-4:2011 Wireless meter readout
•
European standard EN 13757-3:2004 Dedicated application layer (in common with M-
Bus)
•
ETSI EN 300 220 v2.3.1
The Wireless M-Bus firmware stack is based on EN 13757-4:2011.10 (Communication systems for meters and remote reading of meters - Part 4: Wireless meter readout (Radio meter reading for operation in SRD bands)). This European Standard specifies the required physical and link layer parameters for systems using radio to read remote meters, especially for short range device (SRD) unlicensed telemetry bands. The standard encompasses systems for walk-by, drive-by and fixed installations.
Figure 1. Basic Wireless M-Bus architecture
June 2014 DocID026279 Rev 1 1/50
www.st.com
Contents
Contents
2/50
UM1759
STEVAL-IKR002Vx (RF motherboard) . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Microcontroller and connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Extension connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Daughter board test point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Push buttons and joystick . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
STEVAL-IKR002Vx (RF module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
STEVAL-IDS001Vx (SPIRIT1 USB dongle) . . . . . . . . . . . . . . . . . . . . . . . 14
Microcontroller and connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Extension connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
STEVAL-IKR001Vx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
STEVAL-IKR001Vx (RF motherboard) . . . . . . . . . . . . . . . . . . . . . . . . . 18
STEVAL-IKR001Vx (RF module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Hardware connection between MCU and SPIRIT1 module . . . . . . . . . . . 20
Wireless M-Bus firmware APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
DocID026279 Rev 1
UM1759
Contents
WMBus_Appli.c: functions description . . . . . . . . . . . . . . . . . . . . . . . . . . 24
AES128.c: functions description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
AES128_ctr.c: functions description . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
WMBus_PhyDataMem.c: functions description . . . . . . . . . . . . . . . . . . . 34
Running the Wireless M-Bus application . . . . . . . . . . . . . . . . . . . . . . . 36
WMBUS application workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Running evaluation board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Programming the evaluation board with firmware . . . . . . . . . . . . . . . . . 38
Data communication sequence: (meter must be installed to the concentrator prior to this step) 41
Using evaluation board with GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Board configuration with PC-GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
DocID026279 Rev 1 3/50
50
Description
1 Description
UM1759
The Wireless M-Bus standard is defined by European Standard EN 13757-4 for physical and data link layers, while the application layer is defined by EN 13757-3.
The different types of devices are:
1.
Meters
3. Routers
The standard defines the communication between remote meters and mobile readout devices, stationary receivers, data collectors, etc. A typical application scenario is shown below:
Figure 2. Final application scenario
4/50
STMicroelectronics has developed a Wireless M-Bus firmware stack implementation based on its proprietary dual chip platform: the new SPIRIT1 RF Sub-1 GHz transceiver and the
STM32L15 ultra-low-power ARM Cortex-M3 microcontroller.
SPIRIT1:
The SPIRIT1 device is a very low-power, high performance RF transceiver intended for RF wireless applications in the sub-1 GHz band. It is designed to operate at 169, 315, 433, 868, and 915 MHz frequencies, and supports the following modulations: 2-FSK, GFSK, MSK,
OOK, and ASK. The air data rate is programmable from 1 to 500 kbps, depending on the selected modulation.
It has an integrated SMPS for very low power consumption: 9 mA in Rx and 21 mA in Tx mode at +11 dBm.
It uses a very small number of discrete external components and integrates a configurable baseband modem which supports data management, modulation and demodulation. Data management supports our proprietary, fully-programmable packet format, as well as the M-
Bus standard compliance format (all performance classes).
The SPIRIT1 is the native HW supporting the low level of the WM-Bus PHY protocol.
DocID026279 Rev 1
UM1759 Description
ST Ultra Low Power MCU: EnergyLite™ Family
The EnergyLite™ family of 8-bit (STM8L) and 32-bit (STM32L) MCUs are designed to meet the high-performance and energy-efficiency requirements of typically battery-powered gas, water, and heat meters in the WM-Bus scenario.
The STM8L and STM32L devices offer specific features for ultra-low power applications, including advanced ultra-low power modes, optimized dynamic run consumption and special safety features.
The ultra-low-power EnergyLite™ platform is based on the STMicroelectronics 130 nm ultra-low-leakage process technology, sharing common technology, architecture and peripherals.
The STM32 L1 series, based on ARM
®
Cortex™-M3, extends the ultra-low power concept without compromising performance. More than just ultra-low-power MCUs, the STM32 L1 series offers a wide portfolio of features, memory sizes and package pin counts: from 32 to
384 Kbytes of Flash memory (with up to 48 Kbytes of RAM and 12 Kbytes of true embedded
EEPROM), and from 48 to 144 pins.
The innovative architecture (with voltage scaling and ultra-low-power MSI oscillator) adds performance to design solutions requiring a very low power budget. The large number of embedded peripherals (USB, LCD interface, op amp, comparator, ADC with fast on/off mode, DAC, capacitive touch and AES), means that the STM32 L1 series is an expandable platform able to satisfy all application requirements.
The STMicroelectronics WM-Bus application layer is explained in this user manual.
DocID026279 Rev 1 5/50
50
Getting started UM1759
2.1 Package
The Wireless M-Bus package Includes the following:
1.
Documentation:
– Wireless M-Bus firmware and application user manual (this document)
– Wireless M-Bus stack application note
– The GUI help file
2. Firmware:
– Wireless M-Bus firmware
– SPIRIT1_Libraries
– STM32L1xx_StdPeriph_Lib
– STM32_USB-FS-Device_Driver
– WMBUS application and library files
3. PC-GUI:
– The PC-GUI setup
Download the set-up file for latest version of the GUI from the following link: http://ims.st.com/systemslab/download/setups/read_only.php?group_projects=0&pow_cod e=SW.APP0123.13
.
To install the GUI, the user should log on as administrator. SQL server compact is required by the GUI and is included in the installation program; if it is not already installed, the user is prompted to install it during the GUI installation routine.
Figure 3. Snapshot of GUI installation
6/50
The user then proceeds to accept the license agreement and complete the installation.
DocID026279 Rev 1
UM1759
The default firmware runs on the demo boards shown below.
Figure 4. STEVAL- IKR002Vx board
Getting started
•
A: mini USB connector CN1
•
B: jumper JP1 (position 1-2 = USB power source, position 2-3 = battery power source)
•
C: green LED DL6 (board is powered ON)
•
D: LIS3DH, an ultra-low power high performance three axes linear accelerometer
•
E: STLM75, a high precision digital CMOS temperature sensor, with I2C interface
•
F: extension connector
•
G: user interaction buttons (RESET, PUSH_BUTTON and JOYSTICK)
•
H: JTAG connector
•
I: five LEDs (DL1: green, DL2: orange, DL3: red, DL4: blue, DL5: yellow)
•
M: daughter board test points
•
L: RF module interface connector
DocID026279 Rev 1 7/50
50
Getting started
STEVAL-IDS001Vx board:
Figure 5. STEVAL-IDS001Vx board top
UM1759
Figure 6. STEVAL-IDS001Vx board bottom
8/50 DocID026279 Rev 1
UM1759 Getting started
STEVAL- IKR001Vx board:
Figure 7. STEVAL- IKR001Vx motherboard and RF module
DocID026279 Rev 1 9/50
50
Hardware description UM1759
The hardware supported includes:
•
STEVAL-IKR002Vx
•
STEVAL-IKR001Vx
•
STEVAL-IDS001Vx where x = 2, 3, 4, and 5.
The STM32L microcontroller on the RF motherboard drives the SPIRIT1 transceiver and communicates with PCs via USB.
A connector on the motherboard (
) allows JTAG interface access for programming
and debugging. The board can be powered through a mini-USB connector that may also be used for I/O interaction with a USB Host. The board also has a user button, a joystick and
RESET button for user interaction. A temperature sensor and accelerometer are included on the board. The RF module can be connected easily via a dedicated interface.
The features available on the boards include:
•
STM32L151RBT6 64-pin microcontroller
•
Mini USB connector for power supply and I/O
•
JTAG connector
•
RF daughterboard interface
•
One RESET button and one USER button
•
One LIS3DH accelerometer
•
One STLM75 temperature sensor
•
One joystick
•
5 LEDs
•
One PWR LED
•
One battery holder for 2 AAA batteries
•
One row of test points on the interface with the RF daughterboard
10/50 DocID026279 Rev 1
UM1759 Hardware description
Figure 8. STEVAL-IKR002Vx (RF motherboard)
3.1.1 Microcontroller and connections
The board has an STM32L151RB microcontroller. It’s an ultra-low-power microcontroller with 128 KB of flash memory, 16 KB of RAM, 32-bit core ARM cortex-M3, 4 KB of data
EEPROM, RTC, LCD, timers, USART, I2C, SPI, ADC, DAC and comparators.
The microcontroller is connected to different components including buttons, LEDs and connectors for external circuitry.
3.1.2 Power
The board can be powered either by the mini USB connector CN1 (area A in
two AAA batteries. To power the board via the USB bus, place jumper JP1 in position 1-2
(area B in
). To power the board with batteries, place two AAA batteries in the
battery holder at the rear of the board and set jumper JP1 to position 2-3.
When the board is powered, the green LED DL6 is ON (area C in
The board can also be powered by an external DC power supply. Connect the positive output of the power supply to the central pin of JP1 (pin 2) and the ground to one of the four test point connectors on the motherboard.
3.1.3 Sensors
Two sensors are available on the motherboard:
•
LIS3DH; an ultra-low power, high performance three-axes linear accelerometer (area D
). The sensor is connected to the STM32L through the SPI interface. Two
lines for interrupts are also connected.
•
STLM75; a high-precision digital CMOS temperature sensor, with I2C interface (area E
). The pin for the alarm function is connected to one of the STM32L GPIOs.
You can solder a connector on the motherboard to extend its functionality (area F in
). 16 pins of the microcontroller are connected to this expansion slot.
DocID026279 Rev 1 11/50
50
Hardware description
3.1.5
UM1759
Daughter board test point
A row of test points (area M in
) is available for debugging and testing. The available
signals are:
1.
GND
2. VDD
3. GPIO SDN (the pin to drive the SHUTDOWN for SPIRIT1)
3.1.6
10. SPIRIT1 GPIO1
12. GND
Push buttons and joystick
The board has two buttons, one to reset the microcontroller and the other is available to the application, and a digital joystick with 4 possible positions (left, right, up, down) (area G in
A JTAG connector (area H in
) allows on-board programming and debugging of the
STM32L microcontroller using an in-circuit debugger and programmer like the ST-LINK/V2.
3.1.8 LEDs
Five LEDs are available (area I in
•
DL1: green
•
DL2: orange
•
DL3: red
•
DL4: blue
•
DL5: yellow
12/50
The RF module includes 5 different possible BOM lists on the same PCB layout. Each one is optimized for the following different RF bands:
•
169 MHz
•
315 MHz
•
433 MHz
•
868 MHz
•
915 MHz
DocID026279 Rev 1
UM1759 Hardware description
The band is indicated by a dummy resistor on the board (area A in
). An SMA connector on the RF module (area B in
) allows connection with RF instruments like
spectrum analyzers and signal generators to the SPIRIT1 by RF cable, or connection with an antenna like the one included in the demo kit. The board is powered by the RF motherboard through the RF daughterboard connector (area D in
communicates with the microcontroller through this connector via SPI and some GPIOs.
The Vcc_RF pin of the RF daughterboard connector is linked to the Vbat of the SPIRIT1 through a jumper that can also be removed to measure current consumption (area C in
The RF module includes a memory EEPROM with RF module data stored at the time of manufacture. The information is stored in the first pages of the EEPROM and the memory may not be changed by user.
Figure 9. STEVAL-IKR002Vx (RF module)
The SPIRIT1 can be configured to increase the output power in transmission mode.
In the default configuration, the transmitter power amplifier (PA) output is biased by the
1.4 V SMPS voltage output through the L0 external inductor (position D0 in the schematic,
). This limits the maximum output power to about +11 dBm, measured at the
50 Ohm connector via the reference design.
Biasing the PA output through the inductor L0 directly connected to the battery instead of the SMPS output increases the maximum output power delivered at the 50 Ohm connector
(or at the antenna). The maximum output power changes with the voltage level applied at the PA output.
To switch to boost mode, the inductor L0 must be removed from position 1-2 D0 in the schematic and soldered at position 1-3 D0, then the voltage supply Vcc_RF must be provided.
DocID026279 Rev 1 13/50
50
Hardware description
Figure 10. STEVAL-IKR002Vx (RF module) boost mode configuration
UM1759
3.3
For more information see the application note AN4198 - SPIRIT1: increasing the output power, available on the SPIRIT1 web site or in the document folder of this release.
STEVAL-IDS001Vx (SPIRIT1 USB dongle)
The STEVAL-IDS001Vx is a single board that includes the SPIRIT1 radio transceiver and
STM32L microcontroller.
A strip line can be soldered, in B
, allowing the access to the SWD interface for programming and debugging and to the 4 GPIOs of the SPIRIT1. The board can be powered through the USB connector, in A
, that can also be used for I/O
interaction with a USB Host. The board has also two user buttons for user interaction, in G
.
This is the list of some of the features that are available on the module:
•
SPIRIT1 radio transceiver, in D
•
STM32L151CBU6 48-pin microcontroller, in C
.
•
USB connector for power supply and I/O, in A
•
One row of pins with SWD interface and SPIRIT1's GPIOs, in B
.
•
Chip antenna tuned for the entire bands supported (315 MHz, 433 MHz, 868 MHz and
.
•
Two user buttons, in G
•
14/50 DocID026279 Rev 1
UM1759
Figure 11. STEVAL-IDS001Vx
Hardware description
3.3.1 Microcontroller and connections
The board has an STM32L151CBU6 microcontroller. It's an ultralow power microcontroller with 128 KB of flash memory, 16 KB of RAM, 32-bit core ARM cortex-M3, 4 KB of data
EEPROM, RTC, timers, USART, I2C, SPI, ADC, DAC and comparators.
The microcontroller is connected to different components like buttons, LEDs and connectors for external circuitry.
There is the possibility to solder a strip line connector on the motherboard to access to the
SWD interface for programming and debugging, and to access to the 4 GPIOs of the
SPIRIT1, in B
The SWD interface is available through the pins in B in
. The SWD interface allows programming and de-bugging of the STM32L microcontroller on board, using an in-circuit debugger and programmer like the ST-LINK/V2. In
connect the ST-LINK/V2 with the board pins is showed.
DocID026279 Rev 1 15/50
50
Hardware description
Figure 12. SWD connection scheme with ST-LINK/V2
UM1759
16/50
The signals available on the STEVAL-IDS001Vx are:
1.
GND
2. VDD
3. nRESET
4. SWDIO
5. SWO/TRACE
6. SWCLK
10. SPIRIT1 GPIO3
The connection with the ST-LINK/V2 interface is the following, as showed in
Signal name
GND
VDD nRESET
SWDIO
SWO/TRACE
SWCLK
Table 1. SWD connection
STEVAL-IDS001Vx pin number
3
4
1
2
5
6
ST-LINK/V2 pin number
14
2
15
7
13
9
DocID026279 Rev 1
UM1759 Hardware description
3.3.4 Band
The STEVAL-IDS001Vx has 4 different possible BOM lists, each one optimized for different
RF band as follow:
•
315 MHz
•
433 MHz
•
868 MHz
•
915 MHz
The chip antenna used supports all these four bands of frequency.
The STEVAL-IDS001Vx provides two different RF connections: antenna (chip antenna tuned for all the supported bands, default configuration) and UFL connector. Although the default configuration allows communication on air, can be useful switch to the UFL connector to connect the STEVAL-IDS001Vx to RF equipment as spectrum analyzer or RF signal generator. To switch from antenna to UFL connector the C9 capacitor must be removed and the C36 capacitor must be soldered. To restore the default configuration and use the antenna the C36 capacitor must be removed and the C9 capacitor must be soldered. In Figure 13, the two pads for C9 and C36 are showed together with the chip antenna and UFL connector. According to the particular BOM, for each band, the value of
C36 is equals to C9.
Figure 13. RF connector scheme
For user interaction the board has two buttons both available to the application, G in F
.
3.3.7 LEDs
•
D1: yellow.
•
D2: green.
DocID026279 Rev 1 17/50
50
Hardware description UM1759
3.4 STEVAL-IKR001Vx
The SPIRIT1 DK is made up of two units connected to one PC or two PCs with USB cables.
Each unit is composed of an antenna for the selected band and two PCBs:
•
RF motherboard
•
RF module
3.4.1 STEVAL-IKR001Vx motherboard)
The previous version of the motherboard is supported. The supply voltage is provided or by
USB cable or by external power supply. The switch S1 turns on or off the SPIRIT1 DK - MB.
highlights some features of the board as follow:
1.
The power supply sources: USB connector and jack connector for external power supply. USB connector is used also for I/O with the microcontroller with a virtual COM port exposed to the PC.
2. Switch to turn ON or OFF the board.
4. Three button and a joystick: a) SCM_PS, not used b) RESET, for resetting the MB board c) Push_Button, used to enter in DFU mode d) Joystick, not used
5. Test point (TP), to probe the SPI signals, the 4 GPIOs of the SPIRIT1, the shutdown of the SPIRIT1 (SDN), the supply voltage of the SPIRIT1 (VCCRF). The list of signals available is: a) GND b) VCC_RF c) GPIO SDN (the pin to drive in SHUTDOWN the SPIRIT1) l) GND
18/50 DocID026279 Rev 1
UM1759 Hardware description
Figure 14. STEVAL-IKR001Vx (RF motherboard)
3.4.2 STEVAL-IKR001Vx module)
The RF module includes 5 different possible BOM lists, on the same layout PCB. Each one optimized for different RF band as follow:
•
169 MHz
•
315 MHz
•
433 MHz
•
868 MHz
•
915 MHz
The band indication is reported with a dummy resistor on the board, in A
. A SMA connector on the RF module, in B
, allows connection with RF instruments as
spectrum analyzer and signal generator to the SPIRIT1 by RF cable or also connect an antenna as the one included in the demo kit. The board is powered through the RF daughterboard connector, in D
, by the RF motherboard and communicates
through this connector by SPI and some GPIOs with the microcontroller.
The Vcc_RF pin of the RF daughterboard connector is linked to the Vbat of the SPIRIT1 through a jumper that can be also removed to measure the current consumption, in C
.
DocID026279 Rev 1 19/50
50
Hardware description
Figure 15. STEVAL-IKR001Vx (RF module)
UM1759
3.5 Hardware connection between MCU and SPIRIT1 module
The hardware connection between MCU (STM32L) and SPIRIT1 is using the following pins.
This is the minimum connection needed for communication between STM32L and SPIRIT1 device.
Figure 16. Connection diagram
20/50
The evaluation board is connected with SPIRIT1 module as per the table given below. The connections are shown for both connectors J6 and J7 in the STEVAL-IKR001Vx board.
Table 2. Evaluation board connection with connector J6
Evaluation board SPIRIT1 module (J6)
NC
3V3
NC
NC
GND
NC
GND
Pin#1 (NC)
Pin#2 (3V3)
Pin#3 (NC)
Pin#4 (NC)
Pin#5 (GND)
Pin#6 (NC)
Pin#7 (GND)
DocID026279 Rev 1
UM1759 Hardware description
Table 2. Evaluation board connection with connector J6
Evaluation board SPIRIT1 module (J6)
3V3
PC.2
3V3
Pin#8 (VccRF)
Pin#9 (SDN)
Pin#10 (VccRF)
Table 3. Evaluation board connection with connector J7
Evaluation board SPIRIT1 module (J7)
GND
GND
Px.x (SPI_CS)
Px.x
Px.x (SPI_SCK)
Px.x
Px.x (SPI_MOSI)
Px.x
Px.x (SPI_MISO)
Px.x
Pin#1 (GND)
Pin#2 (GND)
Pin#3(CS/NSS)
Pin#4 (GPIO_3)
Pin#5 (CLK)
Pin#6 (GPIO_2)
Pin#7 (SDI)
Pin#8 (GPIO_1)
Pin#9 (SDO)
Pin#10 (GPIO_0)
The WM-Bus protocol stack is developed on ST’s dual chip platform The SPIRIT1 is just implementing part of the WM-Bus physical layer, the PHY and LINK firmware stack layers are implemented STM32L15x, Ultra low power ARM Cortex-M3.
STM32L role
•
WM-Bus Application Layer
– Wireless M-Bus application layer partially implements the EN13757-3.
•
WM-Bus Link Layer
– MAC packet and CRC handling
– Encryption/ Decryption initiate/read.
•
WM-Bus PHY
– Init PHY for WM-Bus
– Interrupt Services
SPIRIT1 role
•
WM-Bus Modes
•
Header, Sync and trailer fields
•
Manchester/3-out-of-6-encoding
•
Sync detection
•
Tx and RX FIFO
DocID026279 Rev 1 21/50
50
Hardware description
Figure 17. Software architecture
UM1759
22/50 DocID026279 Rev 1
UM1759
4 Wireless M-Bus firmware APIs
Wireless M-Bus firmware APIs
The following are the files used for WM-Bus application layer implementation.
Figure 18. Structure of WMBUS application header file
Figure 19. Structure of WMBUS application source file
DocID026279 Rev 1 23/50
50
Wireless M-Bus firmware APIs UM1759
4.1.2
Filename
Table 4. WM-Bus Application layer files
Description
wmbus_appli.c
wmbus_appli.h
This file includes routines for WMBus application Layer
This file contains header for wmbus_appli.c
aes128.h
aes128.c
This file includes header for aes128
This file contains AES 128-bit key main program body aes128_ctr.c
This file contains the aes-ctr and aes-cbc program body
Wmbus_phydatamem.c This function contains routine for DATA EEPROM read and write of MCU
Wmbus_phydatamem.h This function contains the header for Wmbus_phydatamem.c
WMBus_Appli.c: functions description
The list of application layer routines is given below as described in wmbus_appli.c.
Name
Parameters
Description
Return type
Table 5. WM-Bus application add meter routine
WMBus_AppliAddMeter
WMBusDatabaseFrame_t databaseFrame:The meter parameters
This function will add meter to the database
SpiritBool: (S_TRUE or S_FALSE)
Name
Parameters
Description
Return type
Table 6. WM-Bus application delete meter routine
WMBus_AppliDeleteMeter uint64_t meterid: The meter ID
This function will delete the meter from the database
SpiritBool: (S_TRUE or S_FALSE)
Name
Parameters
Description
Return type
Table 7. WM-Bus application get encryption key routine
WMBus_AppliGetEncryptKey
EncryptionKey_t *keydata: The pointer to Encryption key string
This function will return the encryption key
None
24/50
Name
Parameters
Table 8. WM-Bus application get frame format routine
WMBus_AppliGetFrameFormat
None
DocID026279 Rev 1
UM1759
Description
Return type
Wireless M-Bus firmware APIs
Table 8. WM-Bus application get frame format routine
This function will return the WMBus frame format
FrameFormatType_t
Name
Parameters
Description
Return type
Table 9. WM-Bus application get group attribute routine
WMBus_AppliGetGroupAttr uint8_t groupid: The group ID
This function will return the number of meters in the group uint16_t: The number of meters in the group
Name
Parameters
Description
Return type
Table 10. WM-Bus application get group members routine
WMBus_AppliGetGroupMembers
MeterDatabase_t *pdatabase:The pointer to the array of MeterDatabase_t type uint8_t groupid:group ID
This function will fill update the meter ID and Group ID in the parameter passed and also return the number of meters in the database uint16_t: The number of the meters in the database
Name
Parameters
Description
Return type
Table 11. WM-Bus application get meter list routine
WMBus_AppliGetMeterList
MeterDatabase_t *pdatabase:The pointer to the array of MeterDatabase_t type
This function will fill update the meter ID and Group ID in the parameter passed and also return the number of meters in the database uint16_t: The number of the meters in the database.
Name
Parameters
Description
Return type
Table 12. WM-Bus application get operation mode routine
WMBus_AppliGetOperationMode
None
This function will RETURN the current operation mode
WMBusOperationMode_t
DocID026279 Rev 1 25/50
50
Wireless M-Bus firmware APIs UM1759
Name
Parameters
Description
Return type
Table 13. WM-Bus application indication call back routine
WMBus_AppliIndicaCallback
Indication *indic: This indicates type of request and associated data
LastEventLog_t LastEvent: log of last event
This function is called after invoking the indication service
None
Name
Parameters
Description
Return type
Table 14. WM-Bus application initialization routine
WMBus_AppliInit
None
This function will init the WMBUS application
None
Name
Parameters
Description
Return type
Table 15. WM-Bus application poll requests routine
WMBus_AppliPollRequests
None
This function will poll for the requests coming from the meters
LINK_STATUS
Name
Parameters
Description
Return type
Name
Parameters
Description
Return type
Table 16. WM-Bus application power on routine
WMBus_AppliPowerOn
None
This function will init the link layer after power on
LINK_STATUS
Table 17. WM-Bus application read meter routine
WMBus_AppliReadMeter uint64_t meterID uint8_t *buff :pointer to buffer
This function will handle meter read request from the PC-GUI length of the payload
26/50 DocID026279 Rev 1
UM1759 Wireless M-Bus firmware APIs
Name
Parameters
Description
Return type
Table 18. WM-Bus application read meter attribute routine
WMBus_AppliReadMeterAttr uint64_t MeterIDTemp The meter ID database uint8_t *tempBuff: The uint8_t array that contains the Board MFR ID
This function will return the board Manufacturer
ID(MFR+IDENTIFICATION) and encryption key
LINK_STATUS
Name
Parameters
Description
Return type
Table 19. WM-Bus application received data handler routine
WMBus_AppliRxDataHandler
Frame frame: The pointer to the link frame.
This function will handle the received data from the link layer.
None
Name
Parameters
Description
Return type
Table 20. WM-Bus application send meter data routine
WMBus_AppliSendMeterData uint8_t *buff, uint8_t length
This function will send Meter Data to concentrator.
LINK_STATUS
Table 21. WM-Bus application send meter installation request routine
Name
Parameters
WMBus_appliSendMeterInstallationRequest
None
Description
Return type
This function will handle the install meter request
LINK_STATUS
Name
Parameters
Description
Return type
Table 22. WM-Bus application set encryption key routine
WMBus_AppliSetEncryptKey
EncryptionKey_t keydata: The Encryption key. void *mfrID: The pointer to MFR IF+A-Field String.
This function will set the Encryption key.
None
DocID026279 Rev 1 27/50
50
Wireless M-Bus firmware APIs
Name
Parameters
Description
Return type
Table 23. WM-Bus application set frame format routine
WMBus_AppliSetFrameFormat
FrameFormatType_t frameFormat
This function will set the frame format
LINK_STATUS
UM1759
Name
Parameters
Description
Return type
Table 24. WM-Bus application set operation mode routine
WMBus_AppliSetOperationMode
WMBusOperationMode_t currmode: The current operation mode.
This function will set the current operation mode.
None
Name
Parameters
Description
Return type
Table 25. WM-Bus application data transmission sent routine
WMBus_AppliTxDataSentHandler
LINK_STATUS status
LastEventLog_t LastEvent
This function handles the data transmission and returns the link status and last event occurred
None
Name
Parameters
Description
Return type
Table 26. WM-Bus application update meter attribute routine
WMBus_AppliUpdateMeterAttr
WMBusDatabaseFrame_t databaseFrame: The database frame contains meter attribute.
This function will update the meter attributes (This will not add meter).
SpiritBool
Name
Parameters
Table 27. WM-Bus application update meter database routine
WMBus_AppliUpdateMeterDatabase
Frame *frame: The database frame contains meter data.
28/50 DocID026279 Rev 1
UM1759 Wireless M-Bus firmware APIs
Description
Return type
Table 27. WM-Bus application update meter database routine
This function will update the data received from the meters over WMBus interface.This will ignore if the meter is not registered.
SpiritBool
Name
Parameters
Description
Return type
Table 28. WM-Bus application write meter database routine
WMBUS_AppliWriteMeterDatabase
None
This function writes Meter database to internal EEPROM.
None
Name
Parameters
Table 29. WM-Bus application get board manufacturing ID routine
WMBus_GetBoardMnfID uint8_t *buff: The uint8_t array that contains the Board MFR ID.
Description
Return type
This function will return the board Manufacturer
ID(MFR+IDENTIFICATION).
None
Name
Parameters
Description
Return type
Table 30. WM-Bus application get time routine
WMBus_GetTime uint32_t *date, uint32_t *time
This function will the return Date and time
SpiritBool
Name
Parameters
Description
Return type
Table 31. WM-Bus application get device type routine
WMBus_GetWMBusDeviceType
None
This function will return the WMBus device type.
WMBusDeviceType_T:
0x01 -> METER
0x02 -> OTHER
0x03 -> ROUTER
0x04 -> SNIFFER
0xFF -> NOT_CONFIGURED
DocID026279 Rev 1 29/50
50
Wireless M-Bus firmware APIs
Name
Parameters
Table 32. WM-Bus application set board manufacturing ID routine
WMBus_SetBoardMnfID uint8_t *buff: The MFR ID in array format.
Description
Return type
This function will set the MFR ID(MFR+Identification field).
SpiritBool
UM1759
Name
Parameters
Description
Return type
Table 33. WM-Bus application set time routine
WMBus_SetTime uint32_t date, uint32_t time
This function will the set time and date of the board
SpiritBool
Name
Parameters
Description
Return type
Table 34. WM-Bus application RTC configuration routine
RTC_Config
None
This function will Configure the RTC clock source
None
Name
Parameters
Description
Return type
Table 35. WM-Bus application radio power on routine
Appli_RadioPowerON
None
This function will turn on the radio and waits till it enters the ready state
None
Name
Parameters
Description
Return type
Table 36. WM-Bus application radio power off routine
Appli_RadioPowerOFF
None
This function will shut down the radio
None
Name
Parameters
Table 37. WM-Bus application radio stand-by routine
Appli_RadioStandBy
None
30/50 DocID026279 Rev 1
UM1759
Description
Return type
Wireless M-Bus firmware APIs
Table 37. WM-Bus application radio stand-by routine
This function will put the radio in standby state
None
Name
Parameters
Description
Return type
Table 38. WM-Bus application get EEPROM entries routine
WMBus_AppliGetEEpromEntries
None
This function will read and send all meter entry in EEPROM of concentrator database to GUI uint8_t*: ptr to the buffer returned
Name
Table 39. WM-Bus application write meter database in EEPROM routine
Write_Meter_DB_EEPROM
Parameters
Description
Return type
None
This function will write meter database to EEPROM uint8_t*: ptr to the buffer returned
The list of encryption layer (which is also part of application layer) routines is given below as described in aes128_ctr.c.
Name
Parameters
Description
Return type
Table 40. WM-Bus AES decryption routine
AES_decrypt u32* input_pointer, u32* output_pointer u32* expkey: decryption key
This routine Decrypts one block of 16 bytes
None
Name
Parameters
Description
Return type
Table 41. WM-Bus AES encryption routine
AES_encrypt u32* input_pointer, u32* output_pointer u32* expkey: encryption key
This routine Encrypts one block of 16 bytes
None
DocID026279 Rev 1 31/50
50
Wireless M-Bus firmware APIs UM1759
Name
Parameters
Description
Return type
Table 42. WM-Bus AES key schedule for decryption routine
AES_keyschedule_dec u32* key: user key u32* exp: expanded key
This routine computes the expanded key (expkey) according to key for
AES128 decryption
None
The list of encryption layer (which is also part of application layer) routines is given below as described in aes128_ctr.c.
Name
Parameters
Description
Return type
Table 43. WM-Bus add counter routine
add_counter u32 *ctr : counter address
This routine increment counter by one upon encryption of each block
None
Name
Parameters
Description
Return type
Name
Parameters
Description
Return type
Table 44. WM-Bus bit-wise XOR routine
bitwise_xor unsigned char *ina: input block a address unsigned char *inb: input block b address unsigned char *out : output block address
This routine is for implementing XOR operation of blocks
None
Table 45. WM-Bus decrypts PDU routine
decrypt_pdu u32 *exp_key : expended key address unsigned char *cipher: input cipher data address int len: length unsigned char *plain: output plain data address
This routine decrypts the incoming stream
None
32/50 DocID026279 Rev 1
UM1759
Name
Parameters
Description
Return type
Name
Parameters
Description
Return type
Wireless M-Bus firmware APIs
Table 46. WM-Bus encrypts PDU routine
encrypt_pdu u32 *exp_key : expended key address unsigned char * plain: input plain data address int len: length unsigned char * cipher: output cipher data address
This routine Encrypts the incoming stream
None
Table 47. WM-Bus encrypts PDU CBC routine
encrypt_pdu_cbc u32 *exp_key : expended key address unsigned char * plain: input plain data address int len: length unsigned char * cipher: output cipher data address
Encrypts the incoming stream using AES-CBC algorithm
None
Name
Parameters
Description
Return type
Table 48. WM-Bus decrypts PDU CBC routine
decrypt_pdu_cbc u32 *exp_key : expended key address unsigned char * cipher: output cipher data address int len: length unsigned char * plain: input plain data address
Decrypts the incoming stream
None
Name
Parameters
Description
Return type
Table 49. WM-Bus application encryption routine
WMBus_AppliEncrypt u32 *exp_key : expended key address unsigned char * plain: input plain data address int len: length unsigned char * cipher: output cipher data address
This routine does key expansion before encryption starts
None
DocID026279 Rev 1 33/50
50
Wireless M-Bus firmware APIs
Name
Parameters
Description
Return type
Table 50. WM-Bus application decryption routine
WMBus_AppliDecrypt u32 *key: encryption key unsigned char *payload: input payload address int length: length
This routine provides key expansion before decryption starts
None
UM1759
The list of EEPROM function (which is also part of application layer) routines is given below as described in wmbus_phydatamem.c.
Name
Table 51. WM-Bus read encryption key in EEPROM meter database routine
Read_EEPROM_Mtr_DataBase
Parameters
Description
Return type uint64_t* buff: ptr to the receive meter id i.e. Rev_METER_ID
This function will read the memory region to obtain correct encryption key corresponding to the meter id received
None
Name
Parameters
Description
Return type
Table 52. WM-Bus erase EEPROM meter database routine
WMBus_EraseMeterDatabaseFromEEPROM uint8_t *buff: pointer to the buffer that contains entry no. and meter id uint32_t Saddress: starting address of loction in EEPROM uint8_t Wordlength: The data length to be deleted.
This function will erase the memory region
None
Name
Parameters
Description
Return type
Table 53. WM-Bus read meter database routine
WMBus_PhyReadMeterDatabase uint32_t Saddress: Starting address in EEPROM.
uint16_t length: The length of the data to be read.
uint32_t Eaddress: end address in EEPROM
This function will read the data from the EEPROM uint8_t*: pointer to EEpromMtrData
34/50 DocID026279 Rev 1
UM1759 Wireless M-Bus firmware APIs
Name
Parameters
Description
Return type
Table 54. WM-Bus write EEPROM meter database routine
WMBus_PhyWriteMeterDatabase uint8_t *buff: The pointer to the data to be written.
uint16_t length: The length of the data to be written.
uint32_t Saddress: Starting address in EEPROM
This function writes data to internal EEPROM
None
Name
Parameters
Description
Return type
Table 55. WM-Bus read EEPROM database routine
WMBus_ReadMeterEnkeyFromEEPROM uint32_t Saddress: Starting address in EEPROM.
uint16_t length: The length of the data to be read.
uint32_t Eaddress: end address in EEPROM
This function will read the data from the EEPROM uint8_t*: pointer to EEpromMtrData
Name
Parameters
Description
Return type
Table 56. WM-Bus write EEPROM database routine
WMBus_WriteMeterDatabaseToEEPROM uint8_t *buff: The pointer to the data to be written.
uint16_t length: The length of the data to be written.
uint32_t Saddress: Starting address in EEPROM
This function writes data to internal EEPROM
None
DocID026279 Rev 1 35/50
50
Running the Wireless M-Bus application
5 Running the Wireless M-Bus application
5.1
UM1759
WMBUS application workspace
The FW release package contains two workspaces:
1.
WMBUS_Example_STM32L: This firmware contains WM-Bus application example for meter and concentrator without GUI support
2. WMBUS_SDK: This firmware contains WMBus application example for concentrator with GUI support
The default configurations are:
1.
WMBUS_Example_STM32L workspace has support for four configurations: a) wmbus_vcom-concentrator-169: Concentrator FW for 169 MHz frequency band b) wmbus_vcom-concentrator-868: Concentrator FW for 868 MHz frequency band c) wmbus_vcom-meter-169: Meter FW for 169 MHz frequency band d) wmbus_vcom-meter-868: Meter FW for 868 MHz frequency band
36/50 DocID026279 Rev 1
UM1759 Running the Wireless M-Bus application
Figure 20. WMBUS_Example_STM32L: configurations
2. WMBUS_SDK workspace has support for two configurations: a) SPIRIT1_wmbus-gui-169: Concentrator FW for 169 MHz frequency band b) SPIRIT1_wmbus-gui-868: Concentrator FW for 868 MHz frequency band
DocID026279 Rev 1 37/50
50
Running the Wireless M-Bus application
Figure 21. WMBUS_SDK: configurations
UM1759
5.3
5.3.1
Running evaluation board
Follow the steps as mentioned to run the basic demo of WMBus application.
Programming the evaluation board with firmware
Following are the steps to program the meter and concentrator device with WM-Bus firmware:
1.
IAR version 6.5 or higher version must be used.
2. The workspaces are provided with configurations for 868 MHz and 169 MHz frequency bands for meter and concentrator
3. Flash the meter board using WMBUS_Example_STM32L workspace. The two configurations available for meter are: a) wmbus_vcom-meter-169: Meter FW for 169 MHz frequency band b) wmbus_vcom-meter-868: Meter FW for 868 MHz frequency band
4. You can select the desired configuration from drop down menu:
38/50 DocID026279 Rev 1
UM1759 Running the Wireless M-Bus application
Figure 22. Selecting configuration
T2
R2
N1
N2
S1
S1-m
S2
T1
5. Flash the concentrator board using WMBUS_SDK workspace. The two configuration available for concentrator are: a) SPIRIT1_wmbus-gui-169: Concentrator FW for 169 MHz frequency band b) SPIRIT1_wmbus-gui-868: Concentrator FW for 868 MHz frequency band
6. Make sure that meter and concentrator devices are programmed with same configuration i.e. if meter is programmed with 169 MHz configuration then same configuration should be used at concentrator side also.
Mode
Table 57. Wireless M-Bus frequency band vs. modes
Communication Frequency band to choose
Unidirectional
Unidirectional
Bidirectional
Unidirectional
Bidirectional
Bidirectional
Unidirectional
Bidirectional
868 MHz
868 MHz
868 MHz
868 MHz
868 MHz
868 MHz
169 MHz
169 MHz
7. Connect the concentrator to WMBus PC GUI: WMBus & Sniffer for SPIRIT1. Follow steps described in section 4.4 to use GUI.
8. Different meter types are supported in WMBus. For example: c) Heat meter=0x04 and so on.
User can set meter type using following: “Project tab -> Options -> C/C++ Compiler ->
Preprocessor” option.
DocID026279 Rev 1 39/50
50
Running the Wireless M-Bus application
Figure 23. Setting meter type
UM1759
Change DEVICE_METER_TYPE symbol in preprocessor setting for desired meter.
9. By default Encryption is disabled for all configurations. The Encryption can be enabled using following: “Project tab -> Options -> C/C++ Compiler -> Preprocessor” option.
Figure 24. WM-Bus firmware - encryption setting
40/50 DocID026279 Rev 1
UM1759 Running the Wireless M-Bus application
Define AES_CBC_ENABLE symbol in preprocessor setting.
10. Encryption key for three types of meter is preset in firmware which are:
As the first step it is required to install meter to concentrator.
Figure 25. WM-Bus installation request
5.3.3 Data communication sequence: (meter must be installed to the concentrator prior to this step)
Figure 26. WM-Bus data communication
5.4 Using evaluation board with GUI
The evaluation board programmed with concentrator FW must be connected to PC-GUI through USB port.
DocID026279 Rev 1 41/50
50
Running the Wireless M-Bus application
The Wireless M-Bus Application GUI has following windows:
1.
Monitoring Window
UM1759
The Wireless M-Bus devices can be configured using this window. The configurable parameters are the device type, header length, wireless M-bus mode, Manufacturer ID, RF power, time, typical response time etc. In this, the current configuration can also be retrieved. On pressing the connection button, the board type and WM-Bus mode parameters retrieved.
Figure 27. WMBUS configuration window
The meter window can be used to add meters, update meter attributes and delete meters from the database. This window is available only in case of concentrator.
42/50 DocID026279 Rev 1
UM1759 Running the Wireless M-Bus application
Figure 28. Meter window
The monitoring window offers view of meter reading and also the history of the meters.
There is a provision for exporting the meter reading database to *.csv format.
DocID026279 Rev 1 43/50
50
Running the Wireless M-Bus application
Figure 29. Monitoring window
UM1759
5.5 Board configuration with PC-GUI
In order to support the GUI, the board must be programmed with the WMBUS_SDK firmware as explained in
.
1.
After launching the GUI, connect using the top left icon. GUI will ask you to select the
Com port for the device. On successful connection the “connection successful” window will pop-up.
Figure 30. Select COM port for device
44/50 DocID026279 Rev 1
UM1759 Running the Wireless M-Bus application
Figure 31. Connection successful
2. The concentrator configuration can be retrieved using the “Receive All” icon. Go to configuration window which shows the current configuration of the concentrator board.
Also the entire configuration can be send to the board with the “Send All” icon. Refer
Figure 27: WMBUS configuration window
Figure 32. Configuration window
3. User can monitor the meter data received on concentrator side using monitoring window by clicking on “Auto Refresh” button.
DocID026279 Rev 1 45/50
50
Running the Wireless M-Bus application
Figure 33. GUI monitoring window
UM1759
Meter reading can be sent to concentrator device by pressing the right button of joystick on evaluation board (programmed as meter). Similarly Up key is used to increment the meter data by one unit.
LED indications on concentrator board:-
DL1:- Power LED
DL2:- The Data Rx ongoing
DL3:- ON-Data Communication Mode, OFF- Install Mode
DL5:- Meter is installed to concentrator
The meter data is displayed in the GUI as shown below:
Figure 34. GUI monitoring window with meter data
46/50
4. A new meter can be added to or deleted from Concentrator database using “Meter
Window”. This window is useful in a case when encryption is enabled. The window
DocID026279 Rev 1
UM1759 Running the Wireless M-Bus application
displays the concentrator database in “Edit Meter” section. The concentrator database contains Meter IDs and corresponding encryption keys.
By default values (Meter ID and Encryption Key) for three meters are stored in concentrator database. If encryption is enabled and any of these three meters comes online the concentrator will talk to them using encryption key allotted to them. Same encryption keys are also preset in meter firmware for: a) DEVICE_METER_TYPE = 0x02 (Electricity meter) b) DEVICE_METER_TYPE = 0x03 (Gas meter) c) DEVICE_METER_TYPE = 0x04 (Heat meter)
Concentrator database can contain values (Meter ID and Encryption Key) for ten meters at most.
User can add a new meter to concentrator database by using “Add Meter” section. User must enter meter ID, device type, encryption key, entry no. (entry no. corresponds to sequential EEPROM addresses of concentrator data base). After entering all details for meter, “Add” button should be pressed.
Figure 35. A view of concentrator database
DocID026279 Rev 1 47/50
50
Running the Wireless M-Bus application
Figure 36. Adding a new meter to concentrator database
UM1759
Figure 37. The new meter added to database
48/50
5. Delete a meter entry by selecting the row corresponding to that meter in “Edit Meter” section and click on “Delete” button.
File
wmbus_appli.c
aes128.c
aes128_ctr.c
Wmbus_phydatamem.
Table 58. Memory foot print for WM-Bus stack
Code memory- flash
(Bytes)
Data memory - RAM
(Bytes)
CONST Memory
(Bytes)
7 124
3 364
1 372
3 398
725
2 600
529
64
8
-
-
-
DocID026279 Rev 1
UM1759
Date
17-Jun-2014
Table 59. Document revision history
Revision Changes
1 Initial release.
Revision history
DocID026279 Rev 1 49/50
50
UM1759
Please Read Carefully:
Information in this document is provided solely in connection with ST products. STMicroelectronics NV and its subsidiaries (“ST”) reserve the right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any time, without notice.
All ST products are sold pursuant to ST’s terms and conditions of sale.
Purchasers are solely responsible for the choice, selection and use of the ST products and services described herein, and ST assumes no liability whatsoever relating to the choice, selection or use of the ST products and services described herein.
No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this document refers to any third party products or services it shall not be deemed a license grant by ST for the use of such third party products or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such third party products or services or any intellectual property contained therein.
UNLESS OTHERWISE SET FORTH IN ST’S TERMS AND CONDITIONS OF SALE ST DISCLAIMS ANY EXPRESS OR IMPLIED
WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF ST PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS
OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
ST PRODUCTS ARE NOT DESIGNED OR AUTHORIZED FOR USE IN: (A) SAFETY CRITICAL APPLICATIONS SUCH AS LIFE
SUPPORTING, ACTIVE IMPLANTED DEVICES OR SYSTEMS WITH PRODUCT FUNCTIONAL SAFETY REQUIREMENTS; (B)
AERONAUTIC APPLICATIONS; (C) AUTOMOTIVE APPLICATIONS OR ENVIRONMENTS, AND/OR (D) AEROSPACE APPLICATIONS
OR ENVIRONMENTS. WHERE ST PRODUCTS ARE NOT DESIGNED FOR SUCH USE, THE PURCHASER SHALL USE PRODUCTS AT
PURCHASER’S SOLE RISK, EVEN IF ST HAS BEEN INFORMED IN WRITING OF SUCH USAGE, UNLESS A PRODUCT IS
EXPRESSLY DESIGNATED BY ST AS BEING INTENDED FOR “AUTOMOTIVE, AUTOMOTIVE SAFETY OR MEDICAL” INDUSTRY
DOMAINS ACCORDING TO ST PRODUCT DESIGN SPECIFICATIONS. PRODUCTS FORMALLY ESCC, QML OR JAN QUALIFIED ARE
DEEMED SUITABLE FOR USE IN AEROSPACE BY THE CORRESPONDING GOVERNMENTAL AGENCY.
Resale of ST products with provisions different from the statements and/or technical features set forth in this document shall immediately void any warranty granted by ST for the ST product or service described herein and shall not create or extend in any manner whatsoever, any liability of ST.
ST and the ST logo are trademarks or registered trademarks of ST in various countries.
Information in this document supersedes and replaces all information previously supplied.
The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners.
© 2014 STMicroelectronics - All rights reserved
STMicroelectronics group of companies
Australia - Belgium - Brazil - Canada - China - Czech Republic - Finland - France - Germany - Hong Kong - India - Israel - Italy - Japan -
Malaysia - Malta - Morocco - Philippines - Singapore - Spain - Sweden - Switzerland - United Kingdom - United States of America
www.st.com
50/50 DocID026279 Rev 1
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
Key features
Automatic Meter Reading (AMR)
European standards compliant
Communication over twisted pair cables
Supports all network configurations except for ring networks
Radio variant for long distance communication
Sub-1 GHz RF
Short range device (SRD) unlicensed telemetry bands
Walk-by, drive-by and fixed installations
Frequently asked questions
The M-Bus (meter bus) is a common standard used for AMR implementation in remote energy meter readers based on European standards (physical and link layer: EN 13757-2; application layer: EN 13757-3). The M-Bus is also compliant with European Standard EN 1434 on heat meters.
The Wireless M-Bus standard is defined by European Standard EN 13757-4 for physical and data link layers, while the application layer is defined by EN 13757-3. The standard defines the communication between remote meters and mobile readout devices, stationary receivers, data collectors, etc. A typical application scenario is shown below: [Image].
The Wireless M-Bus firmware stack is based on EN 13757-4:2011.10 (Communication systems for meters and remote reading of meters - Part 4: Wireless meter readout (Radio meter reading for operation in SRD bands)). This European Standard specifies the required physical and link layer parameters for systems using radio to read remote meters, especially for short range device (SRD) unlicensed telemetry bands. The standard encompasses systems for walk-by, drive-by and fixed installations.
