Kamstrup flowIQ 2101, Техническое описание, Страница: 25 / 30

Wired M-Bus • Water Meters flowIQ® 2101/3100 TECHNICAL DESCRIPTION
Kamstrup A/S · Technical Description · 55121944_A1_GB_08.2016
25
flowIQ® 3100:
Byte Field Value Description
96 DIF 42h 2 byte binary, monthly value
97 VIF 6Ch Type G (Compound CP16)
98 Target Date 21h CP16: 2321h = 2017-03-01
99 23h
100 DIF 02h 2 byte binary
101 VIF FFh Kamstrup specific vif: info code
102 20h
103 Info 00h 00 = no info codes
104 00h
105 DIF 06h 6 byte binary
106 VIF FFh Kamstrup specific vif: Config number
107 11h
108 Config Number DDh Config no: 175462DEDDh = 0100200013533
109 DEh
110 62h
111 54h
112 17h
113 00h
114 DIF 02h 2 byte binary
115 VIF FFh Kamstrup specific vif: Meter type
116 1Ah
117 Meter Type 03h Meter Type: flowIQ3100 Cold Water
118 22h
119 DIF 02h 2 byte binary
120 VIF FDh Kamstrup specific vif: Software revision
121 0Eh
122 SW Revision 01h Software revision: D1
123 04h
124 Checksum xxh
125 Stop Character 16h
Note:
A target value may read as zero, until passing the set target date.
8.2 RSP_SKE response from flowIQ® 2101/3100
Reply from the M-Bus water meter (RSP_SKE) on request for communication status from M-Bus Master (REQ_SKE):
RSP_SKE:
Start 10h
C-field 0B h 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
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.