MultiCube 350/650/950

M-Bus Communications Guide

Revision 07
1 Safety
This document gives details of the communications option of the MultiCube electricity meter. Labels on each meter give
details of equipment ratings for safe operation. Take time to examine all labels before commencing installation. Safety
symbols on the meter have specific meanings as:

Caution Risk of Danger Danger

Refer to Instructions Risk of Electric Shock

Safety may be impaired if the instructions are not followed or the meter is used in a manner not
specified by the manufacturer.

Contains no user serviceable parts. Field wiring and commissioning should only be carried out
by qualified personnel, in compliance with applicable national regulations.
e.g. National Electrical Code (NEC) for US; Canadian Electrical Code for Canada

For further Information contact the manufacturer:

Address: Northern Design (Electronics) Ltd: 228 Bolton Road, Bradford, West Yorkshire, BD3 0QW.
(UK)
Web: http://www.ndmeter.co.uk
Note: This manual is intended to be used as a supplement to the MultiCube350/650/950 Installation Guide which
contains further safety information and safe installation instructions.

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 1

2 Connection
2.1 M-Bus Terminals
Voltage: 42Vdc
Cable: 30-14 AWG, Stripped 5.5 to 6.5mm (0.2” to 0.25”)
Torque: 0.5Nm (4.4in lb)

2.2 Schematic
The MultiCube meters are wired as follows into a standard M-Bus network.

Figure 2-1 Basic M-Bus Network

2.2.1 M-Bus Unit Loading

The MultiCube requires <4mA current consumption from the bus. This is equivalent to 3 standard loads.

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 2

3 Protocol
3.1 Data Transmission
• Baud Rate 1200, 2400, 4800 or 9600
• Character size: 11 Bits (1-Start, 8-Data, 1-Parity, 1-Stop)
• Bit sequence: LSB first
• Parity – Even

3.2 Addressing
A number of M-Bus IDs need to be reserved for each MultiCube, depending on how many meter points it can
measure as follows:

Meter Type M-Bus IDs Required

Meter Points Virtual Meter Main Unit Total IDs Required
MultiCube950 3 0 (1 optional) 1 4 (5)
MultiCube650 2 N/A 1 3
MultiCube350 1 N/A N/A 1
The user is required to set the master ID (M) and the meter automatically assigns the other IDs consecutively as
shown in the table below:

Meter Type Master ID Meter 1 ID Meter 2 ID Meter 3 ID Virtual Meter ID

MultiCube 950 M M+1 M+2 M+3 M+4
MultiCube 650 M M+1 M+2
MultiCube 350 N/A M

M can be set to any value within the following ranges.

Meter Type M minimum M maximum
MultiCube 950 0 247 (246*)
MultiCube 650 0 248
MultiCube 350 0 250
*virtual meter option

3.3 Master/Meter Names

The user may provide individual, 12 Character, ASCII Names, for the Master and each individual meter. These Allow
a remote host to identify the units by convenient load or system names (eg “Lighting DB1”).

3.4 Access Counter

Each M-Bus sub-unit in the MultiCube (Master, 3xMeters, Virtual Meter) maintains its own access counter which is
provided the reply header (RSP_UD). This counter is incremented each time the individual sub-unit is accessed
using a REQ_UD2 command irrespective of the data table accessed.
Individual access counters may be reset to zero by sending an SND_NKE command to the sub-unit.

3.5 Master Data Table (ID = M)

The Master unit provides the following parameterised data.

Parameter Format
Data Set 1 (Standard Table) 8 Bit Integer
Serial Number 8 Digit BCD
System Model Name “MultiCube950-MB”, “MultiCube650”, “MultiCube350” 12 Character Text String
System Name – User defined string EG “Warehouse D1” 12 Character Text String
Firmware Version 8 Character ASCII
Number of Meters Connected (Including Virtual) (=4 For MultiCube950V) 8 Bit Integer
Number of Power Cycles Long Integer
On Time Total (Seconds since new) Long Integer
On-Time (Seconds since last power fail) Long Integer
Demand Period - Power 8 Bit Integer
Demand Period - Volts 8 Bit Integer
Demand Period - Amps 8 Bit Integer
Master Data Table 1

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 3

3.6 Reading the Master Data Table (ID=M)

3.6.1 Reading the Master Data Table from the Master (ID = M)
The master data table can be read directly from the master using the REQ_UD2 command.

3.6.1.1 Master Table Request Format

Byte Use Value Notes
1 Start 0x10 Start byte
2 C Field 0x5B/0x7B REQ_UD2 – Request Class 2 Data
3 A Field 0-250 Address of MultiCube Master
4 Checksum 0-255 Arithmetic Sum of C Field and A Field (no carry)
5 Stop 0x16 Stop byte
REQ_UD2 – Read Master Table

3.6.1.2 Master Table Reply Format

Bytes Use Value Notes
1 Start 0x68
1 Length 0x67 C Field to End Of User Data
1 Length 0x67 Repeated L Field
1 Start 0x68
1 C Field 0x08 RSP_UD
1 A Field 0-250 Address of MultiCube Main Unit
1 CI Field 0x72 Variable Data Types - Sent LSB first
4 Serial Number XXXXXXXX Main unit Serial Number (8 Digit BCD)
2 Manufacturer 0x388D Northern Design Manufacturer Number – As registered with Flag
1 Version 0x01 ND Version of the M-Bus Interface
1 Medium 0x02 Electricity Type Meter
1 Access Count XXX Counter – Increase by 1 after each reply
1 Status 0x00 Status Byte – Not used by MultiCube
2 Signature 0x0000 Reserved for future use

Data Set = 1
Bytes Field Value Notes
1 DIF 0x01 8 Bit Integer Data
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x00 ND data Type = Data Set
1 Data 0x01 Data Set = 1

Serial Number
Bytes Field Value Notes
1 DIF 0x04 32 Bit Integer Data
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x01 VIFE = Serial Number
4 Data xxxxxxxx Serial Number value

System Model Name

Bytes Field Value Notes
1 DIF 0x0D ASCII Data String (Variable Length)
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x6E Meter Type Name (12 ASCII Characters)
1 Length 0x0C Length of String (12)
12 Data xxxxxxxxxxxx Model Name “MultiCube950”, “MultiCube650”, “MultiCube350”

System Name
Bytes Field Value Notes
1 DIF 0x0D ASCII Data String (Variable Length)
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x6F Main Unit Name (12 ASCII Characters)
1 Length 0x0C Length of String (12)
12 Data xxxxxxxxxxxx User Set Meter Name eg “Warehouse D1”

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 4

Firmware Version
Bytes Field Value Notes
1 DIF 0x02 16 bit integer
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x63 VIFE Firmware Version
2 Data Xxxx Firmware Version

Number of Meters Connected (4 for MultiCube950V with 1 virtual)

Bytes Field Value Notes
1 DIF 0x01 8 Bit Integer
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x79 VIFE Number of Meters
1 Data 0x04 Number of meters (4 Including Virtual)

Number of Power Cycles

Bytes Field Value Notes
1 DIF 0x04 32 Bit Integer
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x7D VIFE Number of Power Cycles
4 Data XXXXX Number of power cycles

On Time in Seconds – Total

Bytes Field Value Notes
1 DIF 0x04 32 Bit Integer
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x7E VIFE Total ON Time (in seconds)
4 Data XXXXX Total ON Time

On Time in Seconds – Since Last Power Cycle

Bytes Field Value Notes
1 DIF 0x04 32 Bit Integer
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x7F VIFE ON Time since last power cycle (in seconds)
4 Data XXXXX ON Time since last power cycle

Demand Period - Power

Bytes Field Value Notes
1 DIF 0x02 16 Bit Integer
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x7C VIFE Code for Demand period - Power
2 Data XXXXX Demand period - Power

Demand Period - Volts

Bytes Field Value Notes
1 DIF 0x02 16 Bit Integer
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x7B VIFE Code for Demand period - Volts
2 Data XXXXX Demand period - Volts

Demand Period - Amps

Bytes Field Value Notes
1 DIF 0x02 16 Bit Integer
1 VIF 0xFF Manufacturer Specific Data Type to follow
1 VIFE 0x7A VIFE Code for Demand period - Amps
2 Data XXXXX Demand period - Amps

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 5

3.6.2 Reading the Master Data Table from a Meter point (ID=M+1 to M+4, or ID = M if
no Master (MultiCube350) )
The master data table can be read from any individual meter point by first setting an alternate parameter table, then
using the REQ_UD2 command.

3.6.2.1 Setting meter point to alternative master data table request format
Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x05 Length Field
3 Length 0x05 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x53/0x73 SND_UD
6 A Field 0-250 Address of MultiCube Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x0F Special DIF
9 VIF 0x01 Alternate parameter table 1 = master data table
10 Checksum 0-255 Arithmetic Sum of C Field to Last Data Byte (no carry)
11 Stop 0x16 Stop byte
Set meter to alternative master data table

3.6.2.2 Meter point reply format

Bytes Use Value Notes
1 ACK 0xE5 Meter point will respond with master data table on next REQ_UD2

Following completion of this sequence, the instrument (master or meter point) will respond to the next REQ_UD2 with
the master data table.

Note that once the master table has been read, the REQ_UD2 command reverts to standard meter data tables, as
described in 3.7.

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 6

3.7 Meter Data Tables (ID = M+1 to M+4)
Each individual meter in the MultiCube (including the virtual meter) provides parameterised data in two consecutive
data tables as follows:

Parameter Format Parameter Format

Data Set = 1 8 Bit Integer Data Set = 2 8 Bit Integer
kWh Total Long Integer Meter Name 12 Character ASCII
kvarh Total Long Integer Meter Configuration 8 Bit Integer
kVAh Total Long Integer Amps 1 Peak hold 16 Bit Integer
kWh - Phase 1 Long Integer Amps 2 Peak hold 16 Bit Integer
kWh - Phase 2 Long Integer Amps 3 Peak hold 16 Bit Integer
kWh - Phase 3 Long Integer Amps 1 Demand (sliding window) 16 Bit Integer
kvarh - Phase 1 Long Integer Amps 2 Demand (sliding window) 16 Bit Integer
kvarh - Phase 2 Long Integer Amps 3 Demand (sliding window) 16 Bit Integer
kvarh - Phase 3 Long Integer Volts 1 Demand (sliding window) 16 Bit Integer
kWh Total Export Long Integer Volts 2 Demand (sliding window) 16 Bit Integer
kvarh Total Export Long Integer Volts 3 Demand (sliding window) 16 Bit Integer
Amps - Phase 1 Integer Amps 1 Maximum demand 16 Bit Integer
Amps - Phase 2 Integer Amps 2 Maximum demand 16 Bit Integer
Amps - Phase 3 Integer Amps 3 Maximum demand 16 Bit Integer
Volts - Phase1 - n Integer Volts 1 Maximum demand 16 Bit Integer
Volts - Phase2 - n Integer Volts 2 Maximum demand 16 Bit Integer
Volts - Phase3 - n Integer Volts 3 Maximum demand 16 Bit Integer
Frequency Integer Total kW Demand (sliding window) 16 Bit Integer
P F Total Integer Total KVA Demand (sliding window) 16 Bit Integer
PF - Phase 1 Integer Total kW Maximum demand 16 Bit Integer
PF - Phase 2 Integer Total KVA Maximum demand 16 Bit Integer
PF - Phase 3 Integer Amps 1 THD 16 Bit Integer
kW Total Integer Amps 2 THD 16 Bit Integer
kW - Phase 1 Integer Amps 3 THD 16 Bit Integer
kW - Phase 2 Integer Volts 1 THD 16 Bit Integer
kW - Phase 3 Integer Volts 2 THD 16 Bit Integer
kvar Total Integer Volts 3 THD 16 Bit Integer
CT Primary 16 Bit Integer
System Voltage 16 Bit Integer

Meter Table 1 Meter Table 2

3.7.1 Truncated Meter Data Tables

The MultiCube may be configured to send “Truncated” M-Bus parameterised data tables in order to minimise
transmission time. In Truncated mode Table 1 is limited up to and including kvarh total Export and Table 2 up to and
including Amps 3 peak.
To enable/disable truncate table mode refer to Section 3.27.

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 7

3.8 Reading the Meter Data Tables (ID=M+1 to M+4)

3.8.1 Meter Table Request Format – Table 1

Byte Use Value Notes
1 Start 0x10 Start byte
2 C Field 0x7B REQ_UD2 – Request Class 2 Data With FCB Set (Table 1)
3 A Field 0-250 Address of MultiCube Meter point
4 Checksum 0-255 Arithmetic Sum of C Field and A Field (no carry)
5 Stop 0x16 Stop byte
REQ_UD2 – Read Meter Table 1

3.8.2 Meter Reply Format (Table 1)

Byte Use Value Notes
0 Start 0x68 Start byte
1 Length 0xEC (0x6C) C Field to End Of User Data
2 Length 0xEC (0x6C) Repeated L Field
3 Start 0x68 Start byte
4 C Field 0x08 RSP_UD
5 A Field 0-250 Address of MultiCube meter point
6 CI Field 0x72 Variable Data Types - Sent LSB first
7-10 Serial Number xxxxxxxx MultiCube Main unit Serial Number (8 Digit BCD)
11-12 Manufacturer 0x388D Northern Design Manufacturer Number – As registered with Flag
13 Version 0x02 ND Version of the M-Bus Interface
14 Medium 0x02 Electricity Type Meter
15 Access Cnt 0-255 Counter – Increase by 1 after each reply
16 Status 00 Status Byte – Not used by MultiCube
17-18 Signature 0x0000 Reserved for future use

Data Set = 1
Bytes Field Value Notes
19 DIF 0x01 8 Bit Integer Data
20 VIF 0xFF Manufacturer Specific Data Type to follow
21 VIFE 0x00 ND data Type = Data Set
22 Data 0x01 Data Set = 1

Total Import kWh

Bytes Field Value Notes
23 DIF 0x04 Data Format = 32 Bit Integer
24 VIF Energy Scale See table 3.10.2
25-28 Data XXXXXXXX Total Import kWh Value

Total Import kvarh (UNIT 2)

Bytes Field Value Notes
29 DIF 0x84 Data Format = 32 Bit Integer
30 DIFE 0x80 UNIT=2 Reactive Register (BIT0 = 0)
31 DIFE 0x40 UNIT=2 (BIT1 = 1)
32 VIF Energy Scale See table 3.10.2
33-36 Data XXXXXXXX Total Import kvarh Value

Total Import kVAh (UNIT 4)

Bytes Field Value Notes
37 DIF 0x84 Data Format = 32 Bit Integer
38 DIFE 0x80 UNIT=4 Apparent Register (BIT0 = 0)
39 DIFE 0x80 UNIT=4 (BIT1 = 0)
40 DIFE 0x40 UNIT=4 (BIT2 = 1)
41 VIF Energy Scale See table 3.10.2
42-45 Data XXXXXXXX Total Import kVAh Value

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 8

Phase 1 Import kWh
Bytes Field Value Notes
46 DIF 0x04 Data Format = 32 Bit Integer
47 VIF Energy Scale See table 3.10.2
48 VIFE 0xFF Manufacturer VIFE to follow
49 VIFE 0x68 0x68: Phase 1
50-53 Data XXXXXXXX Phase 1 Import kWh Value

Phase 2 Import kWh

Bytes Field Value Notes
54 DIF 0x04 Data Format = 32 Bit Integer
55 VIF Energy Scale See table 3.10.2
56 VIFE 0xFF Manufacturer VIFE to follow
57 VIFE 0x69 0x69: Phase 2
58-61 Data XXXXXXXX Phase 2 Import kWh Value

Phase 3 Import kWh

Bytes Field Value Notes
62 DIF 0x04 Data Format = 32 Bit Integer
63 VIF Energy Scale See table 3.10.2
64 VIFE 0xFF Manufacturer VIFE to follow
65 VIFE 0x6A 0x6A: Phase 3
66-69 Data XXXXXXXX Phase 3 Import kWh Value

Phase 1 Import kvarh (UNIT 2)

Bytes Field Value Notes
70 DIF 0x84 Data Format = 32 Bit Integer
71 DIFE 0x80 UNIT=2 Reactive Register (BIT0 = 0)
72 DIFE 0x40 UNIT=2 (BIT1 = 1)
73 VIF Energy Scale See table 3.10.2
74 VIFE 0xFF Manufacturer VIFE to follow
75 VIFE 0x68 0x68: Phase 1
76-79 Data XXXXXXXX Phase 1 Import kvarh Value

Phase 2 Import kvarh (UNIT 2)

Bytes Field Value Notes
80 DIF 0x84 Data Format = 32 Bit Integer
81 DIFE 0x80 UNIT=2 Reactive Register (BIT0 = 0)
82 DIFE 0x40 UNIT=2 (BIT1 = 1)
83 VIF Energy Scale See table 3.10.2
84 VIFE 0xFF Manufacturer VIFE to follow
85 VIFE 0x69 0x69: Phase 2
86-89 Data XXXXXXXX Phase 2 Import kvarh Value

Phase 3 Import kvarh (UNIT 2)

Bytes Field Value Notes
90 DIF 0x84 Data Format = 32 Bit Integer
91 DIFE 0x80 UNIT=2 Reactive Register (BIT0 = 0)
92 DIFE 0x40 UNIT=2 (BIT1 = 1)
93 VIF Energy Scale See table 3.10.2
94 VIFE 0xFF Manufacturer VIFE to follow
95 VIFE 0x6A 0x6A: Phase 3
96-99 Data XXXXXXXX Phase 3 Import kvarh Value

Total Export kWh

Bytes Field Value Notes
100 DIF 0x84 Data Format = 32 Bit Integer
101 DIFE 0x40 UNIT=1 (Export kWh)
102 VIF Energy Scale See table 3.10.2
103-106 Data XXXXXXXX Total Import kWh Value

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 9

Total Export kvarh (UNIT 3)
Bytes Field Value Notes
107 DIF 0x84 Data Format = 32 Bit Integer
108 DIFE 0xC0 UNIT=3 Reactive Register (BIT0 = 1)
109 DIFE 0x40 UNIT=3 (BIT1 = 1)
110 VIF Energy Scale See table 3.10.2
111-114 Data XXXXXXXX Total Import kvarh Value

Data Stops Here In Truncated Table Mode

Phase 1 Amps
Bytes Field Value Notes
115 DIF 0x02 Data Format = 16 Bit Integer
116 VIF 0xFD Use Extended VIF Code Table
117 VIFE 0xD9-0xDD Amps Resolution 0.001A to 0.01kA
118 VIFE 0xFF Manufacturer VIFE to follow
119 VIFE 0x68 0x68: Phase 1
120-121 Data XXXXX Phase 1 Amps Value

Phase 2 Amps
Bytes Field Value Notes
122 DIF 0x02 Data Format = 16 Bit Integer
123 VIF 0xFD Use Extended VIF Code Table
124 VIFE 0xD9-0xDD Amps Resolution 0.001A to 0.01kA
125 VIFE 0xFF Manufacturer VIFE to follow
126 VIFE 0x69 0x69: Phase 2
127-128 Data XXXXX Phase 2 Amps Value

Phase 3 Amps
Bytes Field Value Notes
129 DIF 0x02 Data Format = 16 Bit Integer
130 VIF 0xFD Use Extended VIF Code Table
131 VIFE 0xD9-0xDD Amps Resolution 0.001A to 0.01kA
132 VIFE 0xFF Manufacturer VIFE to follow
133 VIFE 0x6A 0x6A: Phase 3
134-135 Data XXXXX Phase 3 Amps Value

Phase 1 Volts
Bytes Field Value Notes
136 DIF 0x02 Data Format = 16 Bit Integer
137 VIF 0xFD Use Extended VIF Code Table
138 VIFE 0xC7-0xCB Volts Resolution 0.01V to 0.1kV
139 VIFE 0xFF Manufacturer VIFE to follow
140 VIFE 0x68 0x68: Phase 1
141-142 Data XXXXX Phase 1 Volts Value

Phase 2 Volts
Bytes Field Value Notes
143 DIF 0x02 Data Format = 16 Bit Integer
144 VIF 0xFD Use Extended VIF Code Table
145 VIFE 0xC7-0xCB Volts Resolution 0.01V to 0.1kV
146 VIFE 0xFF Manufacturer VIFE to follow
147 VIFE 0x69 0x69: Phase 2
148-149 Data XXXXX Phase 2 Volts Value

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 10

Phase 3 Volts
Bytes Field Value Notes
150 DIF 0x02 Data Format = 16 Bit Integer
151 VIF 0xFD Use Extended VIF Code Table
152 VIFE 0xC7-0xCB Volts Resolution 0.01V to 0.1kV
153 VIFE 0xFF Manufacturer VIFE to follow
154 VIFE 0x6A 0x6A: Phase 3
155-156 Data XXXXX Phase 3 Volts Value

Frequency
Bytes Field Value Notes
157 DIF 0x02 Data Format = 16 Bit Integer
158 VIF 0xFF Manufacturer VIF Code to Follow
159 VIFE 0x04 Frequency - Resolution = 0.01Hz
160-161 Data XXXXX Frequency 5000=50.00

System PF
Bytes Field Value Notes
162 DIF 0x02 Data Format = 16 Bit Integer
163 VIFE 0xFF Manufacturer VIFE to follow
164 VIFE 0x03 Power Factor – Resolution 1.000
165-166 Data XXXXX System Power Factor Value

Phase 1 PF
Bytes Field Value Notes
167 DIF 0x02 Data Format = 16 Bit Integer
168 VIF 0xFF Manufacturer VIFE to follow
169 VIFE 0x83 Power Factor – Resolution 1.000
170 VIFE 0xFF Manufacturer VIFE to follow
171 VIFE 0x68 0x68: Phase 1
172-173 Data XXXXX Phase 1 Power Factor Value

Phase 2 PF
Bytes Field Value Notes
174 DIF 0x02 Data Format = 16 Bit Integer
175 VIF 0xFF Manufacturer VIFE to follow
176 VIFE 0x83 Power Factor – Resolution 1.000
177 VIFE 0xFF Manufacturer VIFE to follow
178 VIFE 0x69 0x69: Phase 2
179-180 Data XXXXX Phase 2 Power Factor Value

Phase 3 PF
Bytes Field Value Notes
181 DIF 0x02 Data Format = 16 Bit Integer
182 VIF 0xFF Manufacturer VIFE to follow
183 VIFE 0x83 Power Factor – Resolution 1.000
184 VIFE 0xFF Manufacturer VIFE to follow
185 VIFE 0x6A 0x6A: Phase 3
186-187 Data XXXXX Phase 3 Power Factor Value

System kW
Bytes Field Value Notes
188 DIF 0x02 Data Format = 16 Bit Integer
189 VIF Power scale See table 3.10.3
190-191 Data XXXXX System Active Power Value

Phase 1 kW
Bytes Field Value Notes
192 DIF 0x02 Data Format = 16 Bit Integer
193 VIF Power scale See table 3.10.3
194 VIFE 0xFF Manufacturer VIFE to follow
195 VIFE 0x68 0x68: Phase 1
196-197 Data XXXXX Phase 1 Active Power Value

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 11

Phase 2 kW
Bytes Field Value Notes
198 DIF 0x02 Data Format = 16 Bit Integer
199 VIF Power scale See table 3.10.3
200 VIFE 0xFF Manufacturer VIFE to follow
201 VIFE 0x69 0x69: Phase 2
202-203 Data XXXXX Phase 2 Active Power Value

Phase 3 kW
Bytes Field Value Notes
204 DIF 0x02 Data Format = 16 Bit Integer
205 VIF Power scale See table 3.10.3
206 VIFE 0xFF Manufacturer VIFE to follow
207 VIFE 0x6A 0x6A: Phase 3
208-209 Data XXXXX Phase 3 Active Power Value

System kvar
Bytes Field Value Notes
210 DIF 0x82 Data Format = 16 Bit Integer
211 DIFE 0x80 UNIT=2 Reactive Register (BIT0 = 0)
212 DIFE 0x40 UNIT=2 (BIT1 = 1)
213 VIF Power scale See table 3.10.3
214-215 Data XXXXX System kvar Value

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 12

3.8.3 Meter Table Request Format – Table 2
Byte Use Value Notes
1 Start 0x10 Start byte
2 C Field 0x5B REQ_UD2 – Request Class 2 Data With FCB reset (Table 1)
3 A Field 0-250 Address of MultiCube meter point
4 Checksum 0-255 Arithmetic Sum of C Field and A Field (no carry)
5 Stop 0x16 Stop byte
REQ_UD2 – Read Meter Table 2

3.8.4 Meter Reply Format - Table 2

Byte Use Value Notes
0 Start 0x68 Start byte
1 Length 0xEE (0x42) C Field to End Of User Data
2 Length 0xEE (0x42) Repeated L Field
3 Start 0x68 Repeated start Byte
4 C Field 0x08 RSP_UD
5 A Field 0-250 Address of MultiCube meter point
6 CI Field 0x72 Variable Data Types - Sent LSB first
7-10 Serial Number Xxxxxxxx MultiCube Main unit Serial Number (8 Digit BCD)
11-12 Manufacturer 0x388D Northern Design Manufacturer Number – As registered with Flag
13 Version 0x02 ND Version of the M-Bus Interface
14 Medium 0x02 Electricity Type Meter
15 Access Count 0-255 Counter – Increase by 1 after each reply
16 Status 00 Status Byte – Not used by MultiCube
17-18 Signature 0x0000 Reserved for future use

Data Set = 2
Bytes Field Value Notes
19 DIF 0x01 8 Bit Integer Data
20 VIF 0xFF Manufacturer Specific Data Type to follow
21 VIFE 0x00 ND data Type = Data Set
22 Data 0x02 Data Set = 2

Meter Name (12 Character ASCII)

Bytes Field Value Notes
23 DIF 0x0D Variable Length Field Type
24 VIF 0xFF Manufacturer Specific Data Type to follow
25 VIFE 0x70 ND data Type = Meter Name ASCII Encoded
26 LVAR 0x0C Length = 12 Characters of ASCII data.
27-38 Data xxxxxxxxxxxx Meter Name - 12 Characters

Meter Configuration 0=3Ph, 1=3 x 1Ph, 2=Virtual

Bytes Field Value Notes
39 DIF 0x01 8 Bit Integer Data
40 VIF 0xFF Manufacturer Specific Data Type to follow
41 VIFE 0x72 ND data Type = Meter Type 0=3Ph, 1=3 x 1Ph, 2=Virtual
42 Data Xxx Meter Type Value

Phase 1 Peak Amps

Bytes Field Value Notes
43 DIF 0x02 Data Format = 16 Bit Integer
44 VIF 0xFD Use Extended VIF Code Table
45 VIFE 0xD9-0xDD Amps Resolution 0.001A to 0.01kA
46 VIFE 0xFF Manufacturer VIFE to follow
47 VIFE 0xE8 0xE8: Phase 1 (VIFE to follow)
48 VIFE 0xFF Manufacturer VIFE to follow
49 VIFE 0x66 VIFE=0x66 Value represents a peak hold
50-51 Data XXXXX Phase 1 Peak Amps Value

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 13

Phase 2 Peak Amps
Bytes Field Value Notes
52 DIF 0x02 Data Format = 16 Bit Integer
53 VIF 0xFD Use Extended VIF Code Table
54 VIFE 0xD9-0xDD Amps Resolution 0.001A to 0.01kA
55 VIFE 0xFF Manufacturer VIFE to follow
56 VIFE 0xE9 0xE9: Phase 2 (VIFE to follow)
57 VIFE 0xFF Manufacturer VIFE to follow
58 VIFE 0x66 VIFE=0x66 Value represents a peak hold
59-60 Data XXXXX Phase 2 Peak Amps Value

Phase 3 Peak Amps

Bytes Field Value Notes
61 DIF 0x02 Data Format = 16 Bit Integer
62 VIF 0xFD Use Extended VIF Code Table
63 VIFE 0xD9-0xDD Amps Resolution 0.001A to 0.01kA
64 VIFE 0xFF Manufacturer VIFE to follow
65 VIFE 0xEA 0xEA: Phase 3 (VIFE to follow)
66 VIFE 0xFF Manufacturer VIFE to follow
67 VIFE 0x66 VIFE=0x66 Value represents a peak hold
68-69 Data XXXXX Phase 3 Peak Amps Value

Data Stops Here In Truncated Table Mode

Phase 1 Amps Demand

Bytes Field Value Notes
70 DIF 0x02 Data Format = 16 Bit Integer
71 VIF 0xFF Use Manufacturer Specific VIFE
72 VIFE 0xB8-0xBC Manufacturer Specific VIFE – Amps demand. See table 3.10.1
73 VIFE 0xFF Manufacturer VIFE to follow
74 VIFE 0x68 0x68: Phase 1
75-76 Data XXXXX Phase 1 Amps Demand Value

Phase 2 Amps Demand

Bytes Field Value Notes
77 DIF 0x02 Data Format = 16 Bit Integer
78 VIF 0xFF Use Manufacturer Specific VIFE
79 VIFE 0xB8-0xBC Manufacturer Specific VIFE – Amps demand. See table 3.10.1
80 VIFE 0xFF Manufacturer VIFE to follow
81 VIFE 0x69 0x69: Phase 2
82-83 Data XXXXX Phase 2 Amps Demand Value

Phase 3 Amps Demand

Bytes Field Value Notes
84 DIF 0x02 Data Format = 16 Bit Integer
85 VIF 0xFF Use Manufacturer Specific VIFE
86 VIFE 0xB8-0xBC Manufacturer Specific VIFE – Amps demand. See table 3.10.1
87 VIFE 0xFF Manufacturer VIFE to follow
88 VIFE 0x6A 0x6A: Phase 3
89-90 Data XXXXX Phase 3 Amps Demand Value

Phase 1 Volts Demand

Bytes Field Value Notes
91 DIF 0x02 Data Format = 16 Bit Integer
92 VIF 0xFF Use Manufacturer Specific VIFE
93 VIFE 0xB0-0xB5 Manufacturer Specific VIFE – Volts Demand. See table 3.10.1
94 VIFE 0xFF Manufacturer VIFE to follow
95 VIFE 0x68 0x68: Phase 1
96-97 Data XXXXX Phase 1 Volts Demand Value

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 14

Phase 2 Volts Demand
Bytes Field Value Notes
98 DIF 0x02 Data Format = 16 Bit Integer
99 VIF 0xFF Use Manufacturer Specific VIFE
100 VIFE 0xB0-0xB5 Manufacturer Specific VIFE – Volts Demand. See table 3.10.1
101 VIFE 0xFF Manufacturer VIFE to follow
102 VIFE 0x69 0x69: Phase 2
103-104 Data XXXXX Phase 2 Volts Demand Value

Phase 3 Volts Demand

Bytes Field Value Notes
105 DIF 0x02 Data Format = 16 Bit Integer
106 VIF 0xFF Use Manufacturer Specific VIFE
107 VIFE 0xB0-0xB5 Manufacturer Specific VIFE – Volts Demand. See table 3.10.1
108 VIFE 0xFF Manufacturer VIFE to follow
109 VIFE 0x6A 0x6A: Phase 3
110-111 Data XXXXX Phase 3 Volts Demand Value

Phase 1 Peak Amps Demand

Bytes Field Value Notes
112 DIF 0x02 Data Format = 16 Bit Integer
113 VIF 0xFF Use Manufacturer Specific VIFE
114 VIFE 0xB8-0xBC Manufacturer Specific VIFE – Amps demand. See table 3.10.1
115 VIFE 0xFF Manufacturer VIFE to follow
116 VIFE 0xE8 0xE8: Phase 1 (VIFE to follow)
117 VIFE 0xFF Manufacturer VIFE to follow
118 VIFE 0x66 VIFE=0x66 Value represents a peak hold
119-120 Data XXXXX Phase 1 Peak Amps Demand Value

Phase 2 Peak Amps Demand

Bytes Field Value Notes
121 DIF 0x02 Data Format = 16 Bit Integer
122 VIF 0xFF Use Manufacturer Specific VIFE
123 VIFE 0xB8-0xBC Manufacturer Specific VIFE – Amps demand. See table 3.10.1
124 VIFE 0xFF Manufacturer VIFE to follow
125 VIFE 0xE9 0xE9: Phase 2 (VIFE to follow)
126 VIFE 0xFF Manufacturer VIFE to follow
127 VIFE 0x66 VIFE=0x66 Value represents a peak hold
128-129 Data XXXXX Phase 2 Peak Amps Demand Value

Phase 3 Peak Amps Demand

Bytes Field Value Notes
130 DIF 0x02 Data Format = 16 Bit Integer
131 VIF 0xFF Use Manufacturer Specific VIFE
132 VIFE 0xB8-0xBC Manufacturer Specific VIFE – Amps demand. See table 3.10.1
133 VIFE 0xFF Manufacturer VIFE to follow
134 VIFE 0xEA 0xEA Phase 3(VIFE to follow)
135 VIFE 0xFF Manufacturer VIFE to follow
136 VIFE 0x66 VIFE=0x66 Value represents a peak hold
137-138 Data XXXXX Phase 3 Peak Amps Demand Value

Phase 1 Peak Volts Demand

Bytes Field Value Notes
139 DIF 0x02 Data Format = 16 Bit Integer
140 VIF 0xFF Use Manufacturer Specific VIFE
141 VIFE 0xB0-0xB5 Manufacturer Specific VIFE – Volts Demand. See table 3.10.1
142 VIFE 0xFF Manufacturer VIFE to follow
143 VIFE 0xE8 0xE8: Phase 1 (VIFE to follow)
144 VIFE 0xFF Manufacturer VIFE to follow
145 VIFE 0x66 VIFE=0x66 Value represents a peak hold
146-147 Data XXXXX Phase 1 Peak Volts Demand Value

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 15

Phase 2 Peak Volts Demand
Bytes Field Value Notes
148 DIF 0x02 Data Format = 16 Bit Integer
149 VIF 0xFF Use Manufacturer Specific VIFE
150 VIFE 0xB0-0xB5 Manufacturer Specific VIFE – Volts Demand. See table 3.10.1
151 VIFE 0xFF Manufacturer VIFE to follow
152 VIFE 0xE9 0xE9: Phase 2 (VIFE to follow)
153 VIFE 0xFF Manufacturer VIFE to follow
154 VIFE 0x66 VIFE=0x66 Value represents a peak hold
155-156 Data XXXXX Phase 2 Peak Volts Demand Value

Phase 3 Peak Volts Demand

Bytes Field Value Notes
157 DIF 0x02 Data Format = 16 Bit Integer
158 VIF 0xFF Use Manufacturer Specific VIFE
159 VIFE 0xB0-0xB5 Manufacturer Specific VIFE – Volts Demand. See table 3.10.1
160 VIFE 0xFF Manufacturer VIFE to follow
161 VIFE 0xEA 0xEA: Phase 3 (VIFE to follow)
162 VIFE 0xFF Manufacturer VIFE to follow
163 VIFE 0x66 VIFE=0x66 Value represents a peak hold
164-165 Data XXXXX Phase 3 Peak Volts Demand Value

System kW Demand
Bytes Field Value Notes
166 DIF 0x02 Data Format = 16 Bit Integer
167 VIF 0xFF Use Manufacturer Specific VIFE
168 VIFE 0x40-0x49 Manufacturer Specific VIFE – kW demand. See table 3.10.1
169-170 Data XXXXX System kW Demand Value

System kVA Demand

Bytes Field Value Notes
171 DIF 0x02 Data Format = 16 Bit Integer
172 VIF 0xFF Use Manufacturer Specific VIFE
173 VIFE 0x54-0x5D Manufacturer Specific VIFE - kVA demand. See table 3.10.1
174-175 Data XXXXX System kVA Demand Value

System kW Peak Demand

Bytes Field Value Notes
176 DIF 0x02 Data Format = 16 Bit Integer
177 VIF 0xFF Use Manufacturer Specific VIFE
178 VIFE 0x40-0x49 Manufacturer Specific VIFE – kW demand. See table 3.10.1
179 VIFE 0xFF Manufacturer VIFE to follow
180 VIFE 0x66 VIFE=0x66 Value represents a peak hold
181-182 Data XXXXX System kW Peak Demand Value

System kVA Peak Demand

Bytes Field Value Notes
183 DIF 0x02 Data Format = 16 Bit Integer
184 VIF 0xFF Use Extended VIF Code Table
185 VIFE 0xD4-0xDD Manufacturer Specific VIFE - kVA demand. See table 3.10.1
186 VIFE 0xFF Manufacturer VIFE to follow
187 VIFE 0x66 VIFE=0x66 Value represents a peak hold
188-189 Data XXXXX System kVA Peak Demand Value

Phase 1 Amps THD

Bytes Field Value Notes
190 DIF 0x02 Data Format = 16 Bit Integer
191 VIF 0xFF Use Manufacturer Specific VIFE
192 VIFE 0x06 Manufacturer Specific VIFE – Amps THD (0.1% Resolution)
193 VIFE 0xFF Manufacturer VIFE to follow
194 VIFE 0x68 0x68: Phase 1
195-196 Data XXXXX Phase 1 Amps THD Value

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 16

Phase 2 Amps THD
Bytes Field Value Notes
197 DIF 0x02 Data Format = 16 Bit Integer
198 VIF 0xFF Use Manufacturer Specific VIFE
199 VIFE 0x06 Manufacturer Specific VIFE – Amps THD (0.1% Resolution)
200 VIFE 0xFF Manufacturer VIFE to follow
201 VIFE 0x69 0x69: Phase 2
202-203 Data XXXXX Phase 2 Amps THD Value

Phase 3 Amps THD

Bytes Field Value Notes
204 DIF 0x02 Data Format = 16 Bit Integer
205 VIF 0xFF Use Manufacturer Specific VIFE
206 VIFE 0x06 Manufacturer Specific VIFE – Amps THD (0.1% Resolution)
207 VIFE 0xFF Manufacturer VIFE to follow
208 VIFE 0x6A 0x6A: Phase 3
209-210 Data XXXXX Phase 3 Amps THD Value

Phase 1 Volts THD

Bytes Field Value Notes
211 DIF 0x02 Data Format = 16 Bit Integer
212 VIF 0xFF Use Manufacturer Specific VIFE
213 VIFE 0x05 Manufacturer Specific VIFE – Volts THD (0.1% Resolution)
214 VIFE 0xFF Manufacturer VIFE to follow
215 VIFE 0x68 0x68: Phase 1
216-217 Data XXXXX Phase 1 Volts THD Value

Phase 2 Volts THD

Bytes Field Value Notes
218 DIF 0x02 Data Format = 16 Bit Integer
219 VIF 0xFF Use Manufacturer Specific VIFE
220 VIFE 0x05 Manufacturer Specific VIFE – Volts THD (0.1% Resolution)
221 VIFE 0xFF Manufacturer VIFE to follow
222 VIFE 0x69 0x69: Phase 2
223-224 Data XXXXX Phase 2 Volts THD Value

Phase 3 Volts THD

Bytes Field Value Notes
225 DIF 0x02 Data Format = 16 Bit Integer
226 VIF 0xFF Use Manufacturer Specific VIFE
227 VIFE 0x05 Manufacturer Specific VIFE – Volts THD (0.1% Resolution)
228 VIFE 0xFF Manufacturer VIFE to follow
229 VIFE 0x6A 0x6A: Phase 3
230-231 Data XXXXX Phase 3 Volts THD Value

CT Primary Rating
Bytes Field Value Notes
232 DIF 0x02 Data Format = 16 Bit Integer
233 VIF 0xFF Use Manufacturer Specific VIFE
234 VIFE 0x73 Manufacturer Specific VIFE – CT primary Rating
235-236 Data XXXXX CT primary Rating Value

System Voltage
Bytes Field Value Notes
237 DIF 0x02 Data Format = 16 Bit Integer
238 VIF 0xFF Use Manufacturer Specific VIFE
239 VIFE 0x78 Manufacturer Specific VIFE – System Voltage
240-241 Data XXXXX System Voltage Value

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 17

3.9 Use of M-Bus Sub-Units
3.9.1 Coding of Energy Parameters as Sub-Units of kWh
Extended DIFs are used to define a “sub-unit number”, in combination with a standard M-Bus Value Information Field
(VIF) to define energy parameters such as kvarh, kVAh, Export etc as follows:

Energy Registers
Sub – Unit Parameter
VIF (kWh)
Number
0 Import kWh
1 0x03-0x07 Export kWh
2 or Import kvarh
3 0x83-0x87 Export kvarh
4 kVAh
Coding of Energy Using Sub-Unit Numbers

3.9.2 Coding of Power Parameters as Sub-Units of kW

Extended DIFs are used to define a “sub-unit number”, in combination with a standard M-Bus Value Information Field
(VIF) to define power parameters such as kvar, kVA, kvar, etc as follows:

Instantaneous Values
Sub – Unit Parameter
VIF
Number
0 kW
1 0x2A-0x2F Not used
2 or kvar
3 0xAA-0xAF Not Used
4 kVA

3.10 Extended Value Information Fields (VIFEs)

Extended VIFs are used by the MultiCube as follows:

VIF/VIFE Usage
0xFF Manufacturer VIF Code to Follow
0xFD M-Bus Extended Code to Follow
0xFB M-Bus Extended Code to Follow

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 18

3.10.1 Manufacturer Specific VIFEs
The MultiCube uses manufacturer specific VIFE codes for:
• Parameter types not specified as M-Bus standard types
• Single Phase channel number

The following table describes the Manufacturer Specific VIFE codes used in the MultiCube.
MultiCube Manufacturer VIFE Codes
VIFE Code Value Meaning Scaling
0x00 Data Set (Data Table Number) Unit
0x01 Serial Number 32 Bit Integer
0x02 Meter Type (Bit fields) Bit Fields
0x03 or 0x83 Power Factor 0.01
0x04 Frequency 0.01Hz
0x05 or 0x85 Volts % THD 0.1%
0x06 or 0x86 Amps % THD 0.1%
0x30-0x35 Volts Demand 0.001V to 100V
0xB0-0xB5 Volts Demand + extension (0x80)
0x38-0x3C Amps Demand 0.001A to 10A
0xB8-0xBC Amps Demand + extension (0x80)
0x40-0x49 kW Demand 0.001W to 1MW
0xC0-0xC9 kW Demand + extension (0x80)
0x4A-0x53 kvar Demand 0.001var to 1Mvar
0xCA-0xD3 kvar Demand + extension (0x80)
0x54-0x5D kVA Demand 0.001VA to 1MVA
0xD4-0xDD kVA Demand + extension (0x80)
0x60 Reset All Energies Reset All Energy values
0x61 Reset All Peaks Reset all peak holds
0x62 Reset all peak, min, sliding window demands -
0x63 Firmware Version 16 Bit Integer V1.01 = 101
0x64 Write Enable Unlock Key 32 Bit Integer
0x65 Set M-Bus Table Length (0=Short, 1=Long) Unit
0x66 Value is Peak Hold -
0x67 Value is Minimum Hold -
0x68 or 0xE8 Value is single phase - Phase 1 Unit
0x69 or 0xE9 Value is single phase – Phase2 unit
0x6A or 0xEA Value is single phase - Phase 3 unit
0x6B Value is Line-Line – Phase 1-Phase 2 unit
0x6C Value is Line-Line – Phase 2-Phase 3 unit
0x6D Value is Line-Line – Phase 3-Phase 1 unit
0x6E System Model Name (“Cube 950V-MB”) ASCII Coded Text
0x6F 12 Character Master Name ASCII Coded Text
0x70 12 Character Meter Name ASCII Coded Text
0x71 12 Character Virtual Meter Name ASCII Coded Text
0x72 Meter Type 0=3Ph, 1=3 x 1Ph, 2=Virtual 8 Bit Integer
0x73 CT primary 0.01A to 0.01KA
0x78 System Voltage 1V
0x79 Number of Meters Connected Unit
0x7A Demand Period – Amps 16 Bit Integer
0x7B Demand Period – Voltage 16 Bit Integer
0x7C Demand Period – Power 16 Bit Integer
0x7D Number of power Cycles 16 Bit Integer
0x7E Total ON Time – Seconds 32 Bit Integer
0x7F ON Time since Last Power Cycle 32 Bit Integer

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 19

3.10.2 Energy scaling VIF

Energy Scaling VIF

VIF VIF + Extension Scale Example Notes
-3
0x00 0x80 10 1 x mWh
-2
0x01 0x81 10 10 x mWh
-1
0x02 0x82 10 100 x mWh
-0
0x03 0x83 10 1 x Wh
1
0x04 0x84 10 10 x Wh
2
0x05 0x85 10 100 x Wh
3
0x06 0x86 10 1 x kWh
4
0x07 0x87 10 10 x kWh
5
0xFB 0x00 0xFB 0x80 10 100 x kWh
6
0xFB 0x01 0xFB 0x81 10 1 x MWh
Energy scaling VIF codes

3.10.3 Power scaling VIF

Power Scaling VIF

VIF VIF + Extension Scale Example Notes
-3
0x28 0xA8 10 1 x mW
-2
0x29 0xA9 10 10 x mW
-1
0x2A 0xAA 10 100 x mW
-0
0x2B 0xAB 10 1xW
1
0x2C 0xAC 10 10 x W
2
0x2D 0xAD 10 100 x W
3
0x2E 0xAE 10 1 x kW
4
0x2F 0xAF 10 10 x kW
5
0xFB 0x28 0xFB 0xA8 10 100 x kW
6
0xFB 0x29 0xFB 0xA9 10 1 x MW
Power scaling VIF codes

3.11 Error Reporting

M-Bus error reporting is not supported in the MultiCube meter.

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 20

3.12 Changing Settings in a MultiCube Using M-Bus
3.13 SND_UD
The send user data command is used to set parameters in the MultiCube units.
An acknowledge character 0xE5 (Single character) is always sent, to acknowledge the receipt of a valid SND_UD
command, if the Address and Checksum are correct. There is no exception system in M-Bus.

3.14 Password Protection

In order to write values to the MultiCube, an unlock key must first be sent over M-Bus to the Master or any of the
meters. This unlock key must match the user password before further M-Bus writes are accepted by the instrument.
The key will remain active until a SND_NKE command is received, addressed to the Master unit, any of the meters or
the meter loses mains supply.
Once the unlock key is active the user may change the user password to prevent unauthorised access to M-Bus
meter settings.
New meters are shipped with a default password of 9999. To change this password:
• Write 9999 to the unlock key
o This enables M-Bus write commands
• Write the new password using the Set New Password Command (below)
• At this point a SND_NKE is advised (but not essential)
• To enable further M-Bus write commands, set the unlock code to match the new user password.

3.15 Write the Unlock Code

Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x0A Length Field
3 Length 0x0A Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x04 Data format = 32 Bit Integer
9 VIF 0xFF Manufacturer Specific Data Being Sent
10 VIFE 0x64 ND VIFE Code for Unlock Key
11 Data Value 0 0x0F
12 Data Value 1 0x27
Example Unlock Key = 9999 (0x0000270F)
13 Data Value 2 0x00
14 Data Value 3 0x00
15 Checksum 0-255 Arithmetic Sum of C Field to Last Data Byte (no carry)
16 Stop 0x16 Stop byte
Write Enable Unlock Code

3.16 Set New User Password

Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x0A Length Field
3 Length 0x0A Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x04 Data format = 32 Bit Integer
9 VIF 0xFD Extended M-Bus VIFE Table used
10 VIFE 0x16 Extended VIFE for User Password
11 Data Value 0 0x57
12 Data Value 1 0x04
Example User Password = 1111
13 Data Value 2 0x00
14 Data Value 3 0x00
15 Checksum 0-255 Arithmetic Sum of C Field to Last Data Byte (no carry)
16 Stop 0x16 Stop byte
Set New User Password

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 21

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 22
3.17 Set Master Name
Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x13 Length Field
3 Length 0x13 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master
7 CI Field 0x51 Data sent LSB first
8 DIF 0x0D Data format = Variable Length
9 VIF 0xFF Manufacturer Specific Data Being Sent
10 VIFE 0x6F ND VIFE Code for 12 Character Master Name
11 Data Value 0 0x0C LVAR Length of variable ASCII String = 12 Example “Abcdefghijk”
12 Data Value 1 0x30 ‘0’
13 Data Value 2 0x35 ‘5’
14 Data Value 3 0x39 ‘9’
15 Data Value 4 0x43 ‘C’
16 Data Value 5 0x4D ‘M’
17 Data Value 6 0x20 ‘‘
18 Data Value 7 0x72 ‘r’
19 Data Value 8 0x65 ‘e’
20 Data Value 9 0x74 ‘t’
21 Data Value 10 0x73 ‘s’
22 Data Value 11 0x61 ‘a’
23 Data Value 12 0x4D ‘M’
24 Checksum 0-255 Arithmetic Sum of C Field to Last Data Byte (no carry)
25 Stop 0x16 Stop byte
Set Master 12 Character ASCII Name

3.18 Set Meter Name

Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x13 Length Field
3 Length 0x13 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x0D Data format = Variable Length
9 VIF 0xFF Manufacturer Specific Data Being Sent
10 VIFE 0x70 ND VIFE Code for 11 Character Meter Name
11 Data Value 0 0x0C LVAR Length of variable ASCII String = 12 Example “Abcdefghijk”
12 Data Value 1 0x31 ‘1’
13 Data Value 2 0x6D ‘m’
14 Data Value 3 0x75 ‘u’
15 Data Value 4 0x4E ‘N’
16 Data Value 5 0x20 ‘‘
17 Data Value 6 0x20 ‘’
18 Data Value 7 0x20 ‘’
19 Data Value 8 0x72 ‘r’
20 Data Value 9 0x65 ‘e’
21 Data Value 10 0x74 ‘t’
22 Data Value 11 0x65 ‘e
23 Data Value 12 0x4D ‘M’
24 Checksum 0-255 Arithmetic Sum of C Field to Last Data Byte (no carry)
26 Stop 0x16 Stop byte
Set Meter 12 Character ASCII Name

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 23

3.19 Set Current Demand Period
Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x08 Length Field
3 Length 0x08 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x02 Data format = 16 Bit Integer
9 VIF 0xFF Manufacturer Specific Data Being Sent
10 VIFE 0x7A ND VIFE Code for Current MD period
11 Data Value 0 0x08
Example MD Period = 1800 Seconds
12 Data Value 1 0x07
13 Checksum 0-255 Arithmetic Sum of C Field to Last Data Byte (no carry)
14 Stop 0x16 Stop byte
Set Current Demand Period

3.20 Set Voltage Demand Period

Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x08 Length Field
3 Length 0x08 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x02 Data format = 16 Bit Integer
9 VIF 0xFF Manufacturer Specific Data Being Sent
10 VIFE 0x7B ND VIFE Code for Voltage MD period
11 Data Value 0 0x08
Example MD Period = 1800 Seconds
12 Data Value 1 0x07
13 Checksum 0-255 Arithmetic Sum of C Field to Last Data Byte (no carry)
14 Stop 0x16 Stop byte
Set Voltage Demand Period

3.21 Set Power Demand Period

Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x08 Length Field
3 Length 0x08 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x02 Data format = 16 Bit Integer
9 VIF 0xFF Manufacturer Specific Data Being Sent
10 VIFE 0x7C ND VIFE Code for Power MD period
11 Data Value 0 0x08
Example MD Period = 1800 Seconds
12 Data Value 1 0x07
13 Checksum 0-255 Arithmetic Sum of C Field to Last Data Byte (no carry)
14 Stop 0x16 Stop byte
Set Power Demand Period

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 24

3.22 Reset Energy Values
Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x06 Length Field
3 Length 0x06 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x00 Data format = No Data
9 VIF 0xFF Manufacturer Specific Data Being Sent
10 VIFE 0x60 ND VIFE Code for RESET ENERGIES
11 Checksum 0-255 Arithmetic Sum of C Field to Last VIFE (no carry)
12 Stop 0x16 Stop byte
Reset All Energy Values

3.23 Reset Peak Values

Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x06 Length Field
3 Length 0x06 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x00 Data format = No Data
9 VIF 0xFF Manufacturer Specific Data Being Sent
10 VIFE 0x61 ND VIFE Code for RESET PEAKS
11 Checksum 0-255 Arithmetic Sum of C Field to Last VIFE (no carry)
12 Stop 0x16 Stop byte
Reset All Peak Values

3.24 Reset Peak MD Values

Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x06 Length Field
3 Length 0x06 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x00 Data format = No Data
9 VIF 0xFF Manufacturer Specific Data Being Sent
10 VIFE 0x62 ND VIFE Code for RESET PEAK MD Values
11 Checksum 0-255 Arithmetic Sum of C Field to Last VIFE (no carry)
12 Stop 0x16 Stop byte
Reset All Peak MD Values

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 25

3.25 Set New Baud Rate
Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x03 Length Field
3 Length 0x03 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field XX CI Field = Set New Baud Rate
BA = 1200 Baud
BB = 2400 Baud
BC = 4800 Baud
BD = 9600 Baud
8 Checksum 0-255 Arithmetic Sum of C Field to CI Field (no carry)
9 Stop 0x16 Stop byte
Set New Baud Rate

3.26 Set Main Unit Address (M-Bus – ID)

Note: When setting the primary ID for the Master, the MultiCube automatically allocates the next 4 addresses,
consecutively to the 3-Meters and the Virtual meter.
Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x06 Length Field
3 Length 0x06 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x01 Data format = 1 Byte
9 VIF 0x7A M-Bus standard VIF – Set Primary Address
10 Data 1 – 245 New primary Address (M-Bus ID)
11 Checksum 0-255 Arithmetic Sum of C Field to CI Field (no carry)
12 Stop 0x16 Stop byte
Set New Master ID

3.27 Set Table Length (Truncated/Long)

Byte Use Value Notes
1 Start 0x68 Start byte
2 Length 0x07 Length Field
3 Length 0x07 Repeated L Field
4 Start 0x68 Start byte
5 C Field 0x73 SND_UD
6 A Field 1-245 Address of MultiCube Master or Meter point
7 CI Field 0x51 Data sent LSB first
8 DIF 0x01 Data format = 1 Byte
9 VIF 0xFF Manufacturer Specific Data Being Sent
10 VIFE 0x65 ND VIFE Code for Set Table Length
11 Data 0-1 0 = Truncated Tables Sent, 1=Long Tables Sent
12 Checksum 0-255 Arithmetic Sum of C Field to CI Field (no carry)
13 Stop 0x16 Stop byte
Set Table Length (Truncated / Long)

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 26

4 Specification
Internally supplied from MultiCube Auxiliary
Aux Mains Requires additional 0.5W max
Connection: Half duplex, 2 Wires + optional 0V
M-Bus Cable length: < 250m (refer to M-Bus specification)
Load: ¼ Unit load per meter (max 128 per bus)
Protocol: M-Bus
Baud: 1200 2400, 4800, 9600 user programmable
Address: 1-250 user programmable
Addresses required for each MultiCube
3.5kV (1 minute) M-Bus Port from all other circuit
Isolation
Reply: Maximum 250ms
Performance Rate: Min 10ms from reply to next request
Data: See data tables. Truncated and Long tables available
Environmental: Refer to MultiCube specification
General Dimensions: Add 10mm to depth of Cube400

DOC-MC950-MB-0001-07 MultiCube 350/650/950 M-Bus Communication Guide Page 27