2 M-Bus water meter flowIQ® 2101/3100 ................................................................................................................ 4
5 Data communication ............................................................................................................................................. 6
6 Reading loggers from flowIQ® 2101/3100 wired M-Bus....................................................................................... 17
7 Configuration of meter via the M-Bus network .................................................................................................... 17
1.2 M-Bus communication .................................................................................................................................. 4
5.1 Bus communication ...................................................................................................................................... 6
3.1.4 Controlling and regulating ..................................................................................................................... 5
5.2 Communication interval ................................................................................................................................ 6
5.3 Addressing forms .......................................................................................................................................... 6
5.7 Information codes ....................................................................................................................................... 14
5.7.1 Status field .......................................................................................................................................... 15
7.2 Setting Date and time ................................................................................................................................. 19
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
8.1 RSP_UD data flowIQ® 2101/3100 data using Kamstrup specified VIFE....................................................... 20
8.2 RSP_SKE response from flowIQ® 2101/3100 .............................................................................................. 25
8.3 Data header in RSP_UD ............................................................................................................................... 26
8.4 DIF (Data Information Field) ........................................................................................................................ 27
8.5 Primary VIF (Value Information Field) ......................................................................................................... 28
8.6 Special purpose VIF ..................................................................................................................................... 29
8.7 Main VIFE-code extension ........................................................................................................................... 29
This technical description describes the wired M-Bus interface of water meters flowIQ 2101 and flowIQ 3100.
For further technical information about these water meters, please refer to their respective Technical Description.
•
M-Bus is a bus system especially suited for communication with consumption meters. The system consists of an
M-Bus Master and one or more meters with M-Bus interface.
M-Bus is standardized in the European standard EN 13757, as well as in the OMS TR02.
Communication on the M-Bus is an asynchronous serial bit transmission in half duplex mode, which means that it is
possible only to transmit one way at a time on the M-Bus.
The framing of the communication is 1 start bit, 8 data bits, 1 parity bit (even) and 1 stop bit.
The M-Bus is communicating via voltage modulation from the M-Bus Master to the M-Bus water meter and current
modulation from the M-Bus water meter to the M-Bus Master. Communication media is via an ordinary two-wire
cable. A twisted pair, non-shielded cable is recommended.
The M-Bus water meter supports primary, secondary and enhanced secondary addressing as well as 300, 2400 and
9600 baud communication speed.
The M-Bus water meter flowIQ® 2101/3100 are designed with manufacturer specified VIF extensions, so called
VIFE codes.
These VIFE codes are formatting the data, whereby decoding of the content is much easier, as when using
manufacturer specified data.
The connection of the M-Bus water meter and the M-Bus network is realized with a fixed two wire cable.
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
The M-Bus interface is integrated in the flowIQ® 2101/3100.
The bus is polarity independent.
The M-Bus water meter have a max power consumption of 1 unit load (1.5 mA) drawn from the M-Bus Master.
Rin: 440 Ohm
Cin: 0.5nF
Bus current and voltages according to EN 13757-2.
The M-Bus water meters fulfil the requirements in the M-Bus standard EN 13757:2013 as well as the
OMS TR02:2015 and can be used in a wide variety of applications using M-Bus protocol.
The M-Bus water meters are designed with focus on high flexibility to fulfill a wide pallet of existing and future
applications.
The flowIQ® 2101/3100 support high quantities of data and all relevant data for analysis can be read out.
This is valid for both actual meter data as well as for target data.
All relevant data for billing purposes can be read out from the flowIQ® 2101/3100.
The wired M-Bus datagram in flowIQ® 2101/3100 is fixed and cannot be altered
The water meter can deliver online data in intervals down to 15 seconds (however at reduced battery lifetime) for
controlling and regulating purposes with a high communication speed.
As M-Bus is polarity independent there is no + and ÷ to care about.
Configuring the primary address can be done with METERTOOL HCW using an optical readout head or via the
M-Bus network. It is recommended that the entire M-Bus system is not powered up during installation of new MBus water meters.
The M-Bus water meter design is based on the newest technology, offering high-speed communication as well as
very frequent reading interval.
The transmission speed is automatically detected by the M-Bus water meter. When the M-Bus water meter
receives a message from the M-Bus Master on a certain speed, it will reply with the same speed.
The M-Bus water meters flowIQ® 2101/3100 supports 300, 2400 and 9600 baud communication speed.
In order to maintain the full 16 years battery lifetime of the water meter, the read out interval shall be longer than
1 minute. Since the most frequent integration interval in the flowIQ® 2101/3100 is 32 seconds, a more frequent
reading is not recommended. A more frequent reading interval than 32 seconds will provide redundant
information.
To make the M-Bus system operate with more M-Bus water meters connected, it is necessary to distinguish
between the individual M-Bus water meter. This is done by means of following M-Bus ID numbers in each M-Bus
meter:
• Primary address: 001...250, and the special addresses 0, 253, 254 and 255
• M-Bus ID number: 8 digits 00000000… 99999999
• Manufacturer ID: Always 2D2Ch for ’KAM‘ for Kamstrup M-Bus water meter
When the M-Bus Master sends a message on the M-Bus, some or all of the above ID numbers on the M-Bus water
meters are encoded in the message. Thus, only the M-Bus water meter with the addressed ID numbers will reply.
Manufacturer ID, Version ID and Fabrication number are permanently encoded into the M-Bus water meter and
cannot be changed.
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
A valid primary M-Bus address has a value between 000 and 250.
The primary M-Bus address is either configured specific in the flowIQ® 2101/3100 or the last digits of the meter
number are used.
As factory default, the primary address in flowIQ® 2101/3100 equals to the last 3 digits of the meter number. If the
last 3 digits are larger than 250 (e.g. 345) the first digit is ignored and the M-Bus water meter address is only
determined by the last 2 digits (e.g. 45).
During the ordering process specific primary addresses can be specified.
Changing the primary address can be performed in following ways:
• Programming with METERTOOL HCW, via Optical Readout Head
• Remotely, via M-Bus master
In connection with primary addressing of the M-Bus, two or more M-Bus water meters on the same M-Bus system
cannot have the same primary address. However, in connection with secondary addressing or enhanced secondary
addressing it is possible to distinguish M-Bus water meters with the same primary address on the same M-Bus.
•
Standard address range for an M-Bus water meter is 001... 250.
In addition to this, there are 4 special addresses that work as follows:
Adr. 000: Ordinary primary address reserved for non-configured M-Bus water meter.
Adr. 253: Used for secondary addressing.
Only M-Bus water meters selected by (enhanced) secondary addressing will reply.
Adr. 254: All M-Bus meters will reply to this address. The address can only be used in systems where only 1 M-Bus
water meter is connected.
Adr. 255: No M-Bus meter will reply to this address, but all will receive the message. This address makes it
possible e.g. to change the baud rate, on an entire system at the same time, by sending only one
telegram.
04h, 07h, 0Ah, 0Bh, 0Ch, or 0Dh (see also ID numbers) or FFh
Checksum
Xxh Stop character
16h
A valid secondary M-Bus address has a value between 00000000 and 99999999 and is in the flowIQ® 2101/3100
identical to the unique serial number.
In connection with secondary addressing, the M-Bus water meters are selected via the primary address 253 with its
8 byte long complete M-Bus ID consisting of:
• M-Bus ID number. Default from Kamstrup: The last 8 digits in the meter number / customer number (4 bytes)
• Manufacturer ID = ASCII characters ‘KAM’ for Kamstrup encoded to the value 2D2Ch (2 bytes)
• Version/generation ID number for MULTICAL® 21 = 34h (1 byte)
• Device type ID (1 byte)
These 8 bytes make up the secondary address of the M-Bus water meter. It is possible to replace the individual
bytes with wildcard characters. See chapter 5.3.4 for further information.
Selection of M-Bus water meter via secondary address
(and deselecting other M-Bus water meter):
•
As long as the M-Bus water meter is selected, it will reply to primary address 253, which is dedicated to secondary
addressing. The M-Bus water meter is deselected either by
• sending a new selection via primary address 253 with a secondary address – different from the one of the
M-Bus water meter (by means of which another M-Bus meter may be selected, if necessary)
or
• sending normalization (SND_NKE) to primary address 253.
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
A valid secondary M-Bus address has a value between (M-Bus ID No. 00000000-99999999) / (M-Bus fabrication No.
00000000-99999999) and is, in the flowIQ® 2101/3100, identical to the unique serial number.
The M-Bus water meter secondary address can therefore be extended in order to comprise the 8 digit BCD
‘fabrication number’ (4 bytes) – identical with the serial number of the meter. This number is unique for each
flowIQ® 2101/3100 and cannot be changed after the meter has been produced.
In connection with enhanced secondary addressing, the M-Bus water meter is selected by adding ‘fabrication
number’ as an ordinary data record with DIF = 0Ch (for 4 bytes, 8 digit BCD) and VIF = 78h (for fabrication number)
in the selection telegram after the secondary address.
When a M-Bus water meter is selected via enhanced secondary address, it will reply to primary address 253, as it is
with the ordinary secondary addressing. The M-Bus water meter is deselected either by
• sending a new selection via primary address 253 with an enhanced or ordinary secondary address – different
from the one from the M-Bus water meter (by means of which another M-Bus meter may be selected, if
necessary)
or
• sending a normalization (SND_NKE) to primary address 253.
•
Selection of M-Bus water meter via enhanced secondary address (and deselecting other M-Bus water meter):
The M-Bus water meter supports wild card search for an easy search for connected meters. Some or all digits of
the meters secondary and/or enhanced secondary addresses can be replaced with wild cards when searching for
meters in an M-Bus network. The integrated break detection functionality eases the meter search on the M-Bus
network.
The M-Bus water meter will not compare the wildcard characters with the equivalent digits in “its own” secondary
and enhanced secondary address, and the M-Bus water meter will be selected if the other characters match.
The 8 digits in the M-Bus ID number and the 8 digits in the ‘fabrication number‘ (= serial number) can each be
replaced by the wildcard character Fh.
The binary values ‘Manufacturer ID’ (2 bytes), ‘Version / generation ID’ (1 byte), and ‘Device type ID’ (1 byte) in the
secondary address may be replaced by the wildcard byte value FFh.
The values for DIF = 0Ch (for 4 bytes, 8 digit BCD) and VIF = 78h (for fabrication number) in connection with
enhanced secondary addressing cannot be replaced by wildcard values.
By means of wildcard characters (BCD Fh) and values (binary FFh), an M-Bus Master can, relatively quickly, search
the M-Bus for connected M-Bus water meters, without knowing the M-Bus water meters primary, secondary or
enhanced secondary addresses in advance.
The M-Bus protocol comprises following telegram / message format types:
In the default application the FCB bit is not used and the M-Bus water meter accepts both FCB = 0 and FCB = 1.
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
Short frame. Request for time-critical data alarm.
Start character
10h C-field
5Ah or 7A
A-field
xxh or FDh
Checksum
Xxh Stop character
16h REQ_UD2:
Short frame. Request for data from the M-Bus interface.
Start character
10h
C-field
5Bh or 7B
A-field
xxh or FDh
Checksum
xxh Stop character
16h REQ_SKE:
Short frame. Status request.
Start character
10h C-field
49h A-field
xxh or FDh
Checksum
xxh Stop character
16h
•
Communication on the M-Bus is initiated by the M-Bus Master. After this the addressed M-Bus water meter
replies. Basically, there are 2 different communication sequences (from M-Bus Master to M-Bus water meter):
SEND -> CONFIRM
REQUEST -> RESPONSE
When using ‘SEND -> CONFIRM’ the M-Bus Master sends a command or data to the M-Bus water meter, that
replies with an acknowledgement (ACK). The acknowledgement (ACK) just means that the M-Bus water meter has
received the telegram successfully, but it has not necessarily accepted the contents.
When using ‘REQUEST -> RESPONSE’ the M-Bus Master sends a request to the M-Bus water meter, which in return
replies with a datagram according to the request.
The M-Bus water meter only supports ‘Mode 1’ data format where all multi-byte data values to and from the MBus water meter are transmitted with Least Significant Byte (LSB) first.
In the default application the FCB / FCV bit in the C-field is not used and the M-Bus water meter accepts both FCB =
0 and FCB = 1.
The M-Bus water meter does not use DFC (Data Flow Control) / ACD (Access Demand) bits, which means that both
bits will always have the value 0 in the C-Field from the M-Bus water meter.
The following describes the individual M-Bus telegrams, from M-Bus Master to M-Bus water meter and from M-Bus
water meter to M-Bus Master, that are supported.
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
51h = data send, 52h = secondary address
selection
Data byte 1
xx : : : :
Data byte 1
xx
Checksum
xxh
Stop character
16h
5.6 M-Bus slave to M-Bus master
RSP_UD:
RSP_SKE:
ACK:
5.6.1 REQ_UD2 -> RSP_UD
•
Data to M-Bus Master. See telegram later.
Data to M-Bus Master. See telegram later.
Data format from M-Bus Master received successfully.
Description of the codes of the individual formats can be viewed later in this document.
Communication takes place in following sequences:
To collect meter data, from the M-Bus water meter, an REQ_UD2 is transmitted from the M-Bus Master.
The M-Bus water meter checks the message, and if it is correct, the M-Bus water meter returns with an RSP_UD,
which is meter data packed according to the M-Bus format for RSP_UD.
Long frame.
Short frame.
Single control character.
An example of a RSP_UD datagram can be viewed later in the manual.
REQ_UD1 from the M-Bus Master is a request for time-critical (alarm) data from the M-Bus water meter.
The flowIQ® 2101/3100 M-Bus water meter does not support time-critical data (alarm protocol), but it replies with
an ACK (link layer receipt) when receiving REQ_UD1, which means that the M-Bus water meter does not have any
time-critical (alarm) data to transmit.
In this way, the M-Bus water meter will function in M-Bus systems with other M-Bus interface supporting timecritical data (alarm protocol).
REQ_SKE from the M-Bus Master is a request for communication status and for information on whether the M-Bus
water meter has any time-critical (alarm) data to send. When receiving an REQ_SKE the M-Bus water meter replies
with an RSP_SKE, but as the M-Bus water meter does not support time-critical data (alarm protocol), and cannot
have overflow in its input buffer, the status bits ACD (Access Demand) and DFC (Data Flow Control) will always be =
0 in the M-Bus water meter reply, which means that the M-Bus water meter does not have any time-critical (alarm)
data to send and has no buffer overflow.
•
Therefore, the M-Bus water meter will function in M-Bus systems with other M-Bus interface supporting timecritical data (alarm protocol) and using communication status bit.
The M-Bus Master normalizes the M-Bus water meter with an SND_NKE and the M-Bus water meter acknowledges
successful receipt of the message by means of an ACK. An SND_NKE to primary address 253 will deselect the M-Bus
water meter, if it was selected by means of secondary or enhanced secondary addressing.
The M-Bus Master wishes to send data to the M-Bus water meter, or to select/deselect the M-Bus water meter via
secondary or enhanced secondary addressing. The M-Bus water meter acknowledges successful receipt of the
SND_UD telegram by means of an ACK. The acknowledgement (ACK) just means that the M-Bus water meter has
received the telegram successfully in the Data Link Layer and is as such no guarantee that the M-Bus water meter
has accepted the contents of the Application Layer.
Therefore, when receiving an SND_UD command with a new baud rate, the M-Bus water meter will acknowledge
receipt by means of an ACK, even though it ignores the contents, as the M-Bus water meter automatically detects
the baud rate on receipt.
flowIQ® 2101/3100 indicates in the display, and in the wired M-Bus datagram, if a special state in the meter, called
info codes, are present:
DRY: Meaning that the meter is not water filled, in this case nothing is measured.
REVERSE: Meaning that the water is flowing in the wrong direction in the meter.
LEAK: Meaning that the water has been running for more than 24 hours.
BURST: Meaning that the water flow is constantly high for more than 30 minutes.
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
TAMPER: Meaning that the meter has been disassembled in an attempt of fraud.
The info code will disappear from the display and from the wired M-Bus datagram, when the condition that
initiated it disappears. Info codes initiate the Temporary error (bit 4) in the status field.
flowIQ® 2101/3100 info codes are mapped to the error bit ‘Temporary error’ (bit 4) when any info code is active.
Further, the ‘Power Low’ (bit 2) in the status field is set, when battery power is low.
The ‘Status field’ in the M-Bus data header can have one of the following values, or the sum of more values:
•
Temporary Error (Bit 4) is set when one of the info codes is active in flowIQ® 2101/3100.
The datagram in flowIQ® 2101/3100 M-Bus water meter has a fixed data content.
Previously, Kamstrup has placed a number of special registers like configuration values in the manufacturer
specified part of the telegram. This has required quite extensive knowledge of the meter in order to decode and
format these data correct.
In order to be able to decode special data registers in an easier way, Kamstrup has taken the approach to define a
number of manufacturer VIF extensions – so called VIFE. The outcome is that most reading systems can show the
special registers in clear reading.
Below an example showing manufacturer specified data vs. Manufacturer specified VIFE:
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
flowIQ® 2101 and flowIQ® 3100 1.6 and 2.5 and 4.0 m3/h
M-Bus data header
Actual data
Monthly data
Meter data
M-Bus ID
Water meter reading (volume)
Monthly target meter reading
Information codes
flowIQ® 3100 Q3 = 6.3 m3/h and higher.
M-Bus data header
Actual data
Monthly data
Meter data
M-Bus ID
Water meter reading (volume)
Date/Time
Monthly target meter reading
Info
6
Reading loggers from flowIQ® 2101/3100 wired M-Bus
7
Configuration of meter via the M-Bus network
•
The datagram is fixed and cannot be changed. The datagram from flowIQ® 3100 large meter versions differs slightly
from the one in flowIQ® 2101, because these large meters do not measure the water temperature.
Manufacturer ID
Version ID
Device type
Access counter
Status (set if any info codes is
active)
Configuration (not used)
Manufacturer ID
Version ID
Device type
Access counter
Status (info codes)
Configuration (not used)
Volume reverse
Hour counter
Actual flow
Actual water temperature
Actual ambient temperature
Min Flow Day
Max Flow Day1)
Min water temp Day
Avg. water temp Day
Min ambient temp Day
Max ambient temp Day
Avg. ambient temp Day
Date/Time
Volume reverse
Hour counter
Actual flow
Actual ambient temperature
Min Flow Day
Max Flow Day1)
Min ambient temp Day
Max ambient temp Day
Avg. ambient temp Day
1)
1)
1)
1)
1)
1)
1)
1)
1)
1)
Min Flow 1 Month
Max Flow 1 Month
Min water temp Month
Avg. water temp Month
Min Ambient temp Month
Max Ambient temp Month
Avg. Ambient temp Month
Target date
Min Flow 1 Month
Max Flow 1 Month
Min Ambient temp Month
Max Ambient temp Month
Avg. Ambient temp Month
Target date
Config number
Meter Type (main / sub type)
Meter SW Revision
Config number
Meter Type (main / sub
type)
Meter SW Revision
1)
The daily flow and temperatures are the actual daily minimum, average or maximum values logged from midnight
until the present reading time.
The loggers in the flowIQ® 2101/3100 can only be read with an optical reading head, the optical eye in the meter
and the program LogView.
Following parameters can be sent to the M-Bus water meter, in order to change the configuration of the
flowIQ® 2101/3100:
• Primary M-Bus address
• Date and time
Selection of the M-Bus water meter via secondary address or enhanced secondary address, and application
select/reset is obtained via SND_UD telegram from the M-Bus Master to the M-Bus water meter. Selection of
device for secondary addressing is made by CI-field = 52h, and application select/reset by CI-field = 50h.
The M-Bus water meter will also reply with an acknowledgement (ACK) when receiving a set of baud rate telegrams
(CI-field = B8h... BFh), but will ignore the contents, as the M-Bus interface is furnished with automatic baud rate
detection.
The individual datagram for writing data in the M-Bus water meter are shown subsequently.
•
A dedicated register in the flowIQ® 2101/3100 is used for storing the primary address. This register may be
overwritten with a new M-Bus primary address using the datagram format below.
During the ordering process the primary address for each meter can be specified. Normally it is the last 2-3
digits of the customer number.
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
VIF: Date and time, e.g. 02-09-04 13:10 standard time, valid
Date, time LSB
0Ah
IV, 0, MI5, MI4, MI3, MI2, MI1, MI0
Date, time
2Dh
SU, HY1, HY0, H4, H3, H2, H1, H0
Date, time
82h
Y2, Y1, Y0, D4, D3, D2, D1, D0
Date, time MSB
09h
Y6, Y5, Y4, Y3, M3, M2, M1, M0
Checksum
Xxh Stop character
16h
Note:
7.3 Application select/reset
•
To synchronize the time in the meter towards a main application real time clock, the time and date may be sent to
the flowIQ® 2101/3100 using the datagram format below.
To avoid disturbing the internal loggers, setting the time must be done in due time before or after an hour shift.
Typically the date/time is set once each 24 hour.
As flowIQ® 2101/3100 uses two digits to indicate year (00... 99), the flowIQ® 2101/3100 M-Bus always sends
information concerning year as 2000... 2099 (bit HY1:HY0 always = 01 in ‘Date and time record’, VIF = 6Dh and DIF
= 04h, compound data type F).
See EN13757-3 Annex A ‘Coding of data records’ for details on how to decode the Date/Time data type.
In connection with application reset the flowIQ® 2101/3100 M-Bus water meter returns an ‘ACK’. Nothing further
happens and nothing is reset.
8.1 RSP_UD data flowIQ® 2101/3100 data using Kamstrup specified VIFE
RSP_UD: Standard profile monthly target data, shown for a Version ID for flowIQ® 2101/3100 water meter.
flowIQ® 2101/flowIQ® 3100:
Byte
Field
Value
Description
1
Start character
68h 2
L-field
8Ah
Length 138 bytes
3
L-field
8Ah
Length 138 bytes
4
Start character
68h
5
C-field
08h
Code for RSP_UD
6
A-field
65h
Primary address (eg. 101)
7
CI-field
72h
8
ID Number
78 BCD
E.g.: ID = 12345678
9
56 BCD
10
34 BCD
11
12 BCD
12
Man. ID
2Dh
Manufacturer ID for Kamstrup A/S (KAM)
13
2Ch
14
Version ID
1Fh
Version ID for flowIQ2101 (or 1Dh for flowIQ3100)
15
Device ID
16h
E.g.: 16h = Cold Water
16
Access Number
xxh
Increments after each RSP_UD.
17
Status Field
00h
Error message. 00 = no error.
18
Config
00h
Not used
19
00h
20
DIF
04h
4 bytes binary
21
VIF
13h
Volume in m3 with 3 decimals
22
Volume
72h
69.490 m3
23
0Fh
24
01h
25
00h
26
DIF
04h
4 bytes binary
27
VIF
93h
Reverse volume in m3 with 3 decimals
28
3Ch
29
Volume Reverse
13h
0.019 m3
30
00h
31
00h
•
When using M-Bus Masters and/or reading software of another manufacturer, the same commands must be used.
The flowIQ® 2101/3100 M-Bus water meter only support commands stated in this description.
The datagram is fixed.
Complete description of reply with examples of readings from the M-Bus water meter (RSP_UD) on request from
M-Bus Master (REQ_UD2):
DIF = Data Information Field, DIFE = DIF Extension
VIF = Value Information Field, VIFE = VIF Extension
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
Code for RSP_SKE (ACD bit and DFC bit is always = 0)
A-field
6A h
Slave address (e.g. address = 106)
Checksum
xx h
Stop
16 h
•
A target value may read as zero, until passing the set target date.
Reply from the M-Bus water meter (RSP_SKE) on request for communication status from M-Bus Master (REQ_SKE):
The ACD (Access Demand) and DFC (Data Flow Control) status bits (bit 5 and bit 4 respectively) in the C-field will
always be = 0 in the reply, which means that the M-Bus water meter does not have any time-critical (alarm) data
to send and has no buffer overflow, as the M-Bus water meter does not support time-critical data (alarm protocol).
But the (empty) RSP_SKE reply to REQ_SKE request ensures, that the M-Bus water meter will function in M-Bus
systems with other M-Bus interfaces, supporting time-critical data (alarm protocol) and using communication
status bit.
The VIF codes contain both unit and scaling factor for the record value. The VIF codes for volume and flow will, as
far as possible, reflect the display reading in the water meter as regards unit, decimal point and number of
decimals.
Thus, the VIF codes for these data values will vary depending on the configuration of the flowIQ® 2101/3100.
The relevant VIF codes are listed in the table below.
temperature since midnight
actual month
m³∗100
Wired M-Bus
Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
VIFE’s and data following are manufacturer specific
Note:
8.7 Main VIFE-code extension
VIF (hex)
Coding
Description
Usage
0Eh
00001110
Metrology firmware version
Legal meter software revision
17h
00010111
Error flags (binary)
Meter Error (info) code (see section 5.7.2)
Note:
See EN13757-3 table 26 for a complete list of primary VIF’s and for the compound CP-16 format.
CODING: VIF-field coding in the data package
SUBJECT: Subject in the record
UNIT: Unit required
SIZE: Unit programmed in VIF
•
The M-Bus water meter uses information from the meter to place units, decimal points and number of decimals on
the values in the M-Bus telegram, ensuring that they correspond to the values read on the meter display, as far as
it is supported in the M-Bus protocol.
Special purpose VIF codes used.
See EN13757-3 table 27 for a complete list of special purpose VIF’s
If primary VIF is 0FDh, a VIFE will follow. The following VIFE codes are used.
See En13757-3 table 28, for a complete list of VIFE codes.