Bosch Buderus Logamatic 5000 Series Instruction Manual

User Documentation
1|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Guideline on controlling the Logamatic
5000/Control 8000 controller series via Mod-
bus TCP/IP
This document helps you to realize the connection and control of the Logamatic
5000/Control 8000 controller series via Modbus TCP/IP with your building control
system.

User Documentation
2|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Contents
1. General information about the control of the Logamatic 5000/Control 8000
controller series via Modbus TCP/IP........................................................... 4
2. Activating the controller via Modbus TCP/IP............................................... 5
2.1 Determining relevant Modbus TCP/IP data points.....................................6
2.2 Checking the current firmware of the controller .........................................6
2.3 Necessary settings on the controller..........................................................7
2.4 Network behavior and diagnostic options of the controller ......................10
2.5 Data types and Register Width ................................................................10
2.6 Control of the controller via Modbus TCP/IP from and including version
1.3.X .........................................................................................................11
2.6.1 Temperature-controlled heat request via Modbus TCP/IP from version
1.3.X..................................................................................................13
2.6.2 Power-controlled heat request via Modbus TCP/IP from and including
version 1.3.X......................................................................................14
2.6.3 Information on 'Heat request via Modbus' and 'Internal heat request'
parameters ........................................................................................14
2.7 Control via Modbus TCP/IP in the network ..............................................15
2.7.1 Control via Modbus TCP/IP in the controller network ..........................16
2.7.2 Control via Modbus TCP/IP in combination with Logaflow HSM plus ...17
3. General information on the message concept of the controller ................ 21
3.1 General information on HMI Status of the control device ........................22
3.2 General Information on Boiler Malfunctions.............................................22
3.3 General information on the evaluation of current messages on the
controller ..................................................................................................23
4. General information about Modbus TCP/IP Heart Beat............................ 24
5. General information about the conversion of the Modbus address
scheme ...................................................................................................... 25
6. Additional information for setting or reading single bits in a Modbus
Register ..................................................................................................... 26
6.1 Setting individual bits in the Modbus Register .........................................26
6.2 Reading single bits from Modbus registers..............................................27
7. Additional information about converting values to ASCII characters........ 29
8. Outdated software versions and their peculiarities ................................... 30
8.1 Control of the controller via Modbus TCP/IP up to and including version
1.2.7.X......................................................................................................30

User Documentation
3|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
8.1.1 Power controlled heat request via Modbus TCP/IP up to and including
version 1.2.7.X...................................................................................32
8.1.2 Information on parameter 'Heat request only via Modbus ....................32

User Documentation
4|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
1. General information about the control of the
Logamatic 5000/Control 8000 controller series
via Modbus TCP/IP
If you want to control the controller from a building management system (BMS) via
Modbus TCP/IP, connect the network interface 1 (LAN 1) of the controller (see Fig-
ure 1-1: Module BCT 531 - Representation of the available interfaces) to your ma-
chine network, in which the BMS is also located, using a network cable. You can
then start up the controller properly (see the documentation "Service manual for the
specialist - Logamatic 5311/Control 8311" or "Service manual for the specialist -
Logamatic 5313/Control 8313").
Figure 1-1: Modul BCT 531/BCT 831 –Representation of the available interfaces

User Documentation
5|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
2. Activating the controller via Modbus TCP/IP
In the following section you will find an excerpt of the cover sheet of the data point
list of the controller, which is relevant for the setup and use of the Modbus TCP/IP
communication. The complete data point list can be downloaded from the Buderus
website.
The data of the Modbus addresses are listed in decimal format. To convert the ad-
dresses to the Modicon scheme, please refer to the chapter "General information
about the conversion of the Modbus address scheme". When using the data points,
please make sure that you select the correct register types and carry out any neces-
sary conversions of the received values. The conversions are necessary to transfer
decimal places.
The Modbus TCP/IP server of the controller supports the following nine Modbus
function codes and data types:
Function Name
Function Code
Read Coils
01
Read Discrete Inputs
02
Read Multiple Holding Register
03
Read Input Registers
04
Write Single Coil
05
Write Single Holding Register
06
Write Multiple Coils
15
Write Multiple Holding Registers
16
Read/Write Multiple Registers
23
Data Type
Description
Coils
Read- and Writeable, 1 Bit
Discrete Inputs
Readable, 1 Bit
Input Registers
Readable, 16 Bit
Holding Registers
Read- and Writeable, 16 Bit
Note:
Currently the data types Coils and Discrete Inputs are not used by the con-
troller. Therefore the function codes 01, 02, 05 and 15 have no relevance for
the control of the controller.

User Documentation
6|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Starting with firmware version 1.3.X, the control, parameterization and some
Modbus addresses of the controller via Modbus TCP/IP have changed.
Therefore, check during commissioning which firmware your controller has
(see chapter "Checking the current firmware of the controller") and, if neces-
sary, perform a firmware update first. If you already control a controller with a
version below 1.3.X via Modbus TCP/IP, you can activate the use of old
Modbus addresses in your controller (see chapter "Necessary settings on
the controller"). If you have activated the Modbus compatibility mode, you do
not have to make any changes to your current solution for control via Mod-
bus TCP/IP (see chapter "Outdated software versions and their peculiari-
ties"). Updating the firmware to the latest version is recommended.
The decision whether to use the decimal or modicon scheme depends on the
software used and the configuration of the BMS. Please contact the manu-
facturer of your BMS for further information on the correct scheme.
2.1 Determining relevant Modbus TCP/IP data points
The data points provided by the controller or specified in the data point list vary de-
pending on the hardware modules installed and their configuration. Since the con-
troller provides all data points in the list, not all data points are relevant for you.
If, for example, you have not connected a boiler to the controller and want to read
out the corresponding data points of the boiler, you will only receive invalid values
(e.g. flow temperature of boiler = 0 °C). When writing data points that are not availa-
ble in the control system, you can set the values, but they have no influence on the
behavior of the controller.
The data point list is structured according to components. If, for example, you do not
use a boiler, you can ignore any data points that refer to the boiler component.
Therefore, before using the data point list, check which data points are suitable for
your application. Your Buderus representative can assist you in selecting the appro-
priate data points for your system.
If you use heating circuit modules, you must also pay attention to the slot. The slot
determines the number of the heating circuit. You should also make sure that you
have configured (e.g. activated) the components (heating circuits, boiler, etc.) in the
controller accordingly.
2.2 Checking the current firmware of the controller
You can check the firmware used in the controller as follows:
First switch to the information menu. Click on the "Version" menu item here. You will
find the current firmware in the "Operating system" parameter. If the displayed firm-
ware is smaller than 1.3.X or if you have activated the mode "Modbus compatibility

User Documentation
7|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
for firmware smaller than 1.3.6", you have to use the old Modbus data point list and
control (see chapter "Outdated software versions and their peculiarities").
Figure 2-1: Information Menu
If, on the other hand, a firmware greater than or equal to 1.3.X is displayed, please
use the Modbus data point list with the new control that matches the firmware cur-
rently in use (see chapter "Control of the controller via Modbus TCP/IP from and in-
cluding version 1.3.X").
2.3 Necessary settings on the controller
First switch on the control and wait until it is completely ready for operation. On the
user interface, you can then open the service menu with a long click on the "Fault
message overview" icon at the bottom left.

User Documentation
8|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Figure 2-2: Overview with button to settings menu
Here you switch to the menu “Connectivity”
Figure 2-3: Settings Menu
In the following you have to make some settings for the Modbus TCP/IP communi-
cation at the controller. In particular, you must pay attention to the settings shown in
bold, which may differ from the factory settings in your control device:

User Documentation
9|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Name
Parameters to
be selected
Importance
LAN1
Modbus TCP/IP
(Factory setting:
internet)
The controller activates the Modbus
TCP/IP functionality, which is necessary for
data transfer.
Modbus communication
With Heart
Beat / Without
Heart Beat
(Factory setting:
No)
The controller uses a Modbus TCP/IP con-
nection with/without heartbeat. For further
information, please refer to the chapter
General Information on Modbus TCP/IP
Heart Beat.
Time overrun
120 to 600 sec-
onds (Factory
setting: 180 sec-
onds)
Defines the timeout of the Modbus TCP/IP
heartbeat. If the time is exceeded until a
new counter value is received, an error
message is generated.
Write access
On (Factory set-
ting: On)
Enables write access via Modbus TCP/IP
and is therefore a prerequisite for external
setpoint setting via Modbus TCP/IP.
Providing data from substa-
tions
On (Factory set-
ting: Off)
Activates the provision of data from internal
control components as well as from substa-
tions connected via Modbus TCP/IP. This
parameter must always be activated for
communication via Modbus TCP/IP!
Heat request only via Modbus
(Only valid until Firmware
1.2.7.X)
On
(Factory setting:
Off)
If activated, a heat request can only be ac-
cepted via Modbus TCP/IP. Heat require-
ments that may be generated by built-in
function modules are not taken into ac-
count. For further information, please refer
to the chapter "Information about parame-
ter “Heat requirement only via Modbus”".
Note: This parameter is only valid until
Firmware 1.2.7.X.
Address assignment
Static / DHCP
If you do not have a DHCP server in the
machine-network, select static for the ad-
dress assignment and then set the IP ad-
dress, the network mask and the gateway -
otherwise you can select DHCP. Hint:
The limitation of the IP address is that you
are not allowed to use the IP address
range 172.31.42. X because it is used for
internal purposes of the regulation.
Activate Modbus compatibility
for Firmware lower 1.3.6
Off
(Factory setting:
Off)
Activates or deactivates the Modbus-com-
patibility mode. Please, use this mode only,
if you already a controller to version 1.2.7.
X head via Modbus TCP/IP by your GLT.
Provided that the Modbus-compatibility
mode was activated, you can Reuse the
old Modbus data points / activation without
any change in your existing solution.

User Documentation
10|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
If you have made all settings concerning the Modbus TCP/IP communication, you
can apply the settings via the "Save" button. The "Cancel" button is used to discard
any changes that have been made. As soon as you have saved the changed con-
nectivity settings, the controller is ready for communication via Modbus TCP/IP.
To define which components can generate a heat request at the controller, please
refer to the chapter "Information on 'Heat request via Modbus' and 'Internal heat re-
quest' parameters'" for the necessary configuration.
Note: Up to version 1.2.7.X, this setting was controlled via the "Heat request only via
Modbus" parameter (see chapter "Information on 'Heat request only via Modbus' pa-
rameter" and chapter "Outdated software versions and their peculiarities").
2.4 Network behavior and diagnostic options of the control-
ler
When using Modbus TCP/IP, the Modbus Device ID (Unit Identifier) of the controller
is set to 255 by default. This can be changed from version 1.5.13 (see chapter "Nec-
essary settings on the controller"). In addition, when using Modbus TCP/IP, any val-
ues are transmitted in the byte order Big-Endian (Most Significant Bit (MSB) First)
also known as "order3210" or "or-derDCBA" (see chapter "Data types and Register
Width").
Up to software version 1.5.X it was not possible to address the controller with the
network diagnostic tool "Ping". This has been changed as of software version 1.5.X:
Activate this function by setting the "Local Area Network" parameter to "Modbus
TCP/IP" (see chapter "Necessary settings on the controller"). This way the controller
responds to the ping request and you can see that the controller is reachable in the
network.
2.5 Data types and Register Width
The controller supports the following data types, which must be used via Modbus
TCP:
Data Type
Bits
Bytes
Value Range
Bit (bit)
1
0
From 0 to 1
Integer (int)
16
2
From 0 to 65535
Signed Integer
(signed int)
16
2
From -32768 to +32767
Long (long)
32
4
From -2147483648 to
[phone]
The Modbus registers have in each case a width of 16 bits. On this occasion, the
registers are built up as follows:

User Documentation
11|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Register
Valency
MSB
LSB
Bit number
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Byte number
2
1
Hint: If you read a register with the data type "Long", you must take into account
that the value is divided into two successive registers, since the memory of only one
register would not be sufficient to map such a large number. In this case the register
to be read looks as follows:
Register (High)
Register (Low)
Valency
M
S
B
L
S
B
M
S
B
L
S
B
Bitnum-
ber
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Byten-
umber
4
3
2
1
2.6 Control of the controller via Modbus TCP/IP from and in-
cluding version 1.3.X
Please use the following control of the controller from firmware "1.3.X".

User Documentation
12|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Register
type
Address
Bit
Data point
name
Data
type
Value
Range
Importance
Holding
Register
0
Heartbeat (in)
INT
If the connection is to be monitored for
timeout, the counter that is different from
the old value, which can be read via the
Heart Beat (out) register, must be written
on this register.
Holding
Register
1
Heartbeat (out)
INT
If the register is read, the current counter
value of the heart beat (in) can be called
up.
Holding
Register
400
Set-point
flow temp. in °C
INT
From 0 to
120
Set-point of the currently required boiler
flow temperature.
Hint: The maximum system temperature
depends on the installed boiler and there
power.
Holding
Register
401
Set-point
system power
in %
INT
From 0 to
100
Set-point of the topically demanded system
output.
Holding
Register
402
Mode of opera-
tion
INT
0 (Off)
or
1 (Opera-
tion)
Operating mode for boiler request. 0 = Off
= Boilers are off, consumers continue to be
controlled 1 = Operation = normal opera-
tion over boiler heat request
Holding
Register
405
Bit block for
Cascade control
BIT
See the following table entries
Holding
Register
405
0
Lead boiler
BIT
0 (inactive)
or
1 (active)
If you implement your own cascade control
system as BMS, you can sign the current
boiler as the guide boiler via this bit.
Through this, the follow-up times of the
boiler circuit pump will be adjusted.
Hint: The functionality is not implemented
yet and is made available at a later time
than software update.
Holding
Register
405
1
Prioritization
BIT
0 (inactive)
or
1 (active)
Allows the boilers to be prioritized. This is
used, for example, for a faster warm water
demand.
Hint: The functionality is not implemented
yet and is made available at a later soft-
ware update.
Holding
Register
405
2
Temperature-
controlled regu-
lation
BIT
0 (inactive)
or 1 (active)
Activates or deactivates the temperature
controlled operation of the boiler.

User Documentation
13|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Holding
Register
405
3
Power-control-
led regulation
BIT
0 (inactive)
or 1 (active)
Activates or deactivates the power con-
trolled operation of the boiler.
Notes:
Data type Integer (int) corresponds to 16 bits (Bit0 to Bit15), see chapter
"Data types and register width".
The addresses mentioned here refer to the fact that the controller is config-
ured as master. If you use the controller as slave, please refer to chapter
"Control via Modbus TCP/IP in the controller network".
To set individual bits in a Modbus register (as required for Holding Re-gister
405), please refer to chapter "Supplementary information on setting or read-
ing individual bits in a Modbus register".
The data point "Setpoint system supply temperature in °C" affects the stra-
tegy in the controller. Here, the specific structure of the system or module
configuration in the controller determines which heat generators are acti-
vated or deactivated by the controller.
A power-steered control can only be used if one or more boilers of the same
type are connected to the control device. This function is not possible with
several different heat generators.
2.6.1 Temperature-controlled heat request via Modbus TCP/IP from
version 1.3.X
To be able to send a temperature-controlled heat request via Modbus, you must first
configure the controller accordingly. Please note the information in chapter "Infor-
mation about parameters 'Heat request via Modbus' and 'Internal heat request'" if
you want to control the heat request exclusively via the BMS.
If you now want to generate a temperature-controlled heat request, you must de-
scribe the following registers:
Register
Value of Register
Operation Mode
(Holding Register 402)
1
Flow Temperature Set point
(Holding Register 400)
X in °C
Leading Boiler
(Holding Register 405; Bit0)
1
Temperature controlled operation
(Holding Register 405; Bit2)
1
Power controlled operation
(Holding Register 405; Bit3)
0

User Documentation
14|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Note:
With the values from the above example, a temperature-controlled heat re-
quest with X °C, which is to work as a lead boiler, is sent to a boiler. For a
system with FM-CM, the guide boiler function must be enabled.
X in °C corresponds to your desired flow temperature.
2.6.2 Power-controlled heat request via Modbus TCP/IP from and in-
cluding version 1.3.X
To be able to send a power request via Modbus, you must first configure the control-
ler accordingly (see chapter "Information on parameters 'Heat request via Modbus'
and 'Internal heat request'").
Then you can write to the following Modbus registers:
Register
Value of Register
Operation Mode
(Holding Register 402)
1
Flow Temperature Set point
(Holding Register 400)
X in %
Leading Boiler
(Holding Register 405; Bit0)
1
Temperature controlled operation
(Holding Register 405; Bit2)
0
Power controlled operation
(Holding Register 405; Bit3)
1
Note:
With the values from the above example, a power-controlled heat request
with X %, which is to work as a lead boiler, is sent to a boiler. In the case of a
system with FM-CM, it is mandatory to enable the guide boiler function.
You can only use the output-guided control if you have deactivated the inter-
nal heat request.
X in % corresponds to your desired output..
2.6.3 Information on 'Heat request via Modbus' and 'Internal heat re-
quest' parameters
You can use the following parameters of the controller to define how a heat or power
request can be generated at the controller. The parameters for configuring the be-
havior can be found in the Service menu > Heat generation > Strategy data > Basic
settings. Depending on the parameterization, this may have an effect on the control.

User Documentation
15|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
If you have connected additional function modules (e.g. for a heating circuit) or sub-
stations to the control, you can activate the heat request for these function modules
via the "Internal heat request" parameter.
If you want to generate a heat request via Modbus, you must activate the parameter
"Heat request via Modbus". Depending on which heat requests you have activated,
the behavior of the control is influenced as follows:
Parametres
„Internal heat re-
quest“
Parametres „Heat
request through
Modbus“
Impact
Off
Off
No heat requests from the control unit are
taken into account.
On
Off
Only heat requests of internal function mod-
ules are considered.
Off
On
Only heat requests via Modbus are consid-
ered (exclusive mode).
On
On
Internal and Modbus heat requests are
taken into account (parallel mode).
2.6.3.1 Exclusive mode of heat demand
In the exclusive mode of the heat request, any heat requests from internal function
modules are ignored. This gives you full control from the BMS of any heat demand
generated by the controller. In this mode you can use a heat request via a tempera-
ture controlled as well as a power controlled heat request.
2.6.3.2 Parallel mode of the heat request
In the parallel mode of the heat request, both heat requests from internal function
modules and heat requests via Modbus are taken into account. A heat request via
Modbus, which comes from the BMS, can only add a heat request. Existing heat re-
quests from other modules are not influenced by this. The setpoint is always the
highest heat demand. You cannot use a power-controlled heat request in this mode.
2.7 Control via Modbus TCP/IP in the network
With the controllers of the Logamatic 5000/Control 8000 controller series, it is possi-
ble to operate other controllers or components from the Buderus modular system
Logaflow HSM plus in a network. This creates a hierarchical structure in which there
can be one head station (master) and several substations (slaves). Additionally it is
possible with Logaflow HSM plus to create so called segment substations. A seg-
ment substation is a substation that can itself include further substations in the net-
work.

User Documentation
16|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Figure 2-4: Functional principle of Network
2.7.1 Control via Modbus TCP/IP in the controller network
If you operate the controller in a controller network, i.e. you have connected a mas-
ter controller and at least one slave controller, you can access the data points of the
slave controller via the master controller. The behavior of the controller, whether it is
to function as master or slave, is set via the rotary coding switch on the controller
(see documentation "Service manual for the specialist - Logamatic 5311" or "Service
manual for the specialist - Logamatic 5313").
Figure 2-5: Overview of control unit network with Logamatic 5000
The data points between a master and a slave controller differ only in their Modbus
address for addresses smaller than 8000. As soon as the controller acts as a slave,
you can access the data points via the master controller using the following formula:
    󰇛  󰇜
Note:
The already calculated addresses can be found in the data point list (sheets
Slave01 - Slave15).
The formula can only be used for data points with address less than 8000.
Data points from and including address 8000 are only available in the mas-
ter.

User Documentation
17|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Example:
Assuming you have two controllers (1x master and 1x slave) in use and have set up
a controller network. The rotary coding switch on the master controller is set to posi-
tion 0 (= master) and on the slave controller to position 1 (= slave 01). You have in-
stalled and configured a heating circuit module in slot 1 on the slave controller. If
you now want to access the current flow temperature of heating circuit 1 from the
slave controller, for example, you can calculate the address as follows:
   󰇛  󰇜
The Modbus address for the current flow temperature at heating circuit 1 is
at input register 102 at the master controller.
The position of the rotary coding switch on the slave controller is set to 1.
The position is multiplied by 500 and added to the master Modbus address
of the corresponding data point.
The calculated address for requesting the current flow temperature of heat-
ing circuit 1 from the slave controller via the master controller is located on
input register 602.
If you now request the calculated address (input register 602) at the master con-
troller, you will receive the current flow temperature of heating circuit 1 from the
slave controller.
Note:
You will find the already calculated addresses of all positions of the rotary
coding switch (slave 01-15 corresponds to the position of the rotary coding
switch 1-15) also in the Modbus TCP/IP data point list.
If you have connected one boiler each at the master and slave controller,
you need a cascade module at the master controller to control both boilers
via Modbus TCP/IP. If you have not installed a cascade module at the mas-
ter controller and have set up a controller network, the boiler at the slave
controller is blocked by the master controller. If you do not want to use the
cascade module, you must implement the cascade functionality in your build-
ing management system. In this case, you must use both control devices as
masters (no control device network may be created).
2.7.2 Control via Modbus TCP/IP in combination with Logaflow HSM
plus
You can operate the control unit in a network with the Buderus Logaflow HSM plus
modular system. For this, you need a connection between the master controller and
at least one HSM plus device. You can then access the data points of the HSM plus
via the master control device. The behavior of the controller, whether it is to function
as master or slave, is set via the rotary coding switch on the controller. Further infor-
mation can be found in the documentation "Service manual for the specialist -

User Documentation
18|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
Logamatic 5311/Control 8311" or "Service manual for the specialist - Logamatic
5313/Control 8313".
Figure 2-6: Overview network with Logamatic 5000 and Logaflow HSM plus
For the connection between Logamatic 5000 and Logaflow HSM plus the positions
Slave10 to Slave 15 are provided. Up to six HSM plus BSM can be connected to
one Logamatic 5000/Control 8000 (master). Each HSM plus BSM can be used as a
segment substation. Thus, up to eight additional HSM plus devices can be con-
nected to each HSM plus BSM.
Figure 2-7: Sample Installation of a Network
Note:
Another controller of the Logamatic 5000/Control 8000 controller series is always
integrated as a substation (slave). Use as a segment substation is not possible (see
Figure 2 7).
Example:

User Documentation
19|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
If you connect a HSM plus BSM to a Logamatic 5000, it is automatically integrated
as slave10 in the Logamatic 5000. A possible second, third, ... HSM plus BSM is in-
tegrated accordingly as slave11, slave12,… .
2.7.2.1 Access to Substation
All data points can be retrieved via the master using Modbus TCP. Since the ad-
dresses of the data points may differ depending on the system structure, you can
use the following formulas to calculate the corresponding addresses:
First you have to calculate the required offset for the respective slave (10 - 15):
    
You can now add this offset to the addresses of the HSM plus BSM. The result is
the address of the data point with which you can access the respective BSM via the
master.
    
Example:
You want to retrieve the address "Input Register 1 - Own Flow Temperature" from
slave11 via master.
     
      
2.7.2.2 Access to substation via segment substation
You can also access the substations of an HSM plus BSM (Slave10 - Slave15) via
the master. For this you must also first calculate the offset and then add this with the
address.
  󰇛  󰇜
  󰇛  󰇜
    
You can now also add this offset to the addresses of the respective HSM plus de-
vice. The result is the address of the data point with which you can access the re-
spective HSM plus device via the master.
   
Example:
You want to retrieve the address "Input Register 34 - HMI State" from slave 1 via
slave10 of the master:
 󰇛 󰇜  
  󰇛  󰇜  
      
    
You can access the HMI State of slave station 1 of segment slave station 10 via the
head-end station using the address "Input Register 10034".
Example:

User Documentation
20|33
© All rights with Robert Bosch GmbH, also for the case of protected rights applications
EN_User_documentation_Instructions_for_controlling_the_Logamatic_5000_controller_series_via_Modbus_TCP_I
P_20210203.docx | 10.02.2021
You want to retrieve the address "Input Register 34 - HMI State" from substation 8
via the master using Slave12:
 󰇛 󰇜 
  󰇛  󰇜  
     
      
You can access the HMI State of slave station 8 of segment slave station 12 via the
head-end station using the address "Input Register 21534".