6 Administration of the product
This chapter covers the wireless M-Bus implementation and wired M-Bus implementation of the product.
The M-Bus implementation is according to the new M-Bus standard EN13757-2, EN13757-3, EN13757-4
(2011) and the OMS specification.
The product itself operates as a normal M-Bus slave, which can be addressed using primary and
secondary addressing. The wired slave implementation is used to configure the product and read status
information about connected slaves.
6.1 Wireless M-Bus Receiver
The product handles all widely used wireless M-Bus slaves which conforms to the wireless M-Bus
standard and/or OMS specifications. Both wireless M-Bus slaves sending installation requests and slaves
only sending spontaneous data can be handled.
6.1.1 Installation mode
Installation mode can be started using the display or by issuing M-Bus command on the wired M-Bus
slave implementation on the product, see section 6.3.18.
When installation mode is activated, wireless M-Bus slaves sending SND_IR telegrams or SND_NR
telegrams are automatically added to the slave list. The product can also be configured to only handle
slaves which transmit SND_IR telegrams (installation requests), see section 5.5.5 and 6.3.19.
6.1.2 Normal operation
Installed wireless M-Bus slaves will be directly readable on the wired M-Bus slave port on the product.
Depending on key handling and telegram contents, the information will be available as standard M-Bus
data (decrypted and readable) or the data will be put in an M-Bus container, which contains the complete
wireless M-Bus telegram received from the meter.
Container settings can be changed in the display or by issuing M-Bus command on the wired M-Bus slave
interface, see section 5.6.4 and 6.3.21.
6.1.3 FAC mode
Currently the product cannot be used to open an FAC window for bidirectional communication. This is a
feature which will be implemented in future releases.
6.1.4 Telegram handling
All telegrams from wireless M-Bus slaves are handled, but are handled differently depending on contents.
If a telegram is encrypted or the C and CI-fields are unknown to the product, the telegram is always
stored and available as container telegrams on the wired M-Bus interface.
Telegram types listed in Table 7 and Table 8 Handled CI-fields for “extended link layer” received from
wireless M-Bus slaves are stored and can be read on the wired M-Bus slave interface with any standard
M-Bus software. Only the latest telegram received from a wireless M-Bus slave is stored.
The product also adds an optional information block on the wired M-Bus interface before the actual
wireless M-Bus telegram information. The information block added depends on the DIF/VIF mode set, see
5.6.5 and 6.3.22.
6.1.4.1 Handled C-fields
To Next Page
Loading...
