Modbus PX Io

s
Desigo™ PX Open
PX Open M-bus
Engineering guide
Version 4.1 / 5.0 / 5.1 / 6.0
CM2Y9774en_04
2016-07-31 Building Technologies
Contents
0 Before you start ....................................................................................... 4
0.1 Revision history ......................................................................................... 4
0.2 Trademarks ............................................................................................... 4
0.3 Related documents ................................................................................... 4
1 Introduction ............................................................................................. 5
1.1 Positioning of the PX Open M-bus solution .............................................. 5
1.2 Requirements and limitations in relation to the M-bus system ................. 5
2 Project engineering overview ................................................................ 6
2.1 The integration workflow ........................................................................... 6
2.1.1 Adding a system controller ........................................................................ 6
2.1.2 DP-Import in System Design ..................................................................... 6
2.1.3 Creating the technical hierarchy ............................................................... 6
2.1.4 Creating the M-bus subsystem structure .................................................. 7
2.1.5 Synchronizing the project to PX Design.................................................... 8
2.1.6 Navigating to the CFC project in PX Design ............................................. 9
2.1.7 Adding and setting the COMBLK and MSGBLK blocks to CFC. ............ 10
2.1.8 Adding the main pin (main value) ........................................................... 11
2.1.9 Adding text blocks ................................................................................... 11
2.1.10 Node Setup, compiling the CFC project and downloading the program . 11
3 Project engineering details .................................................................. 12
3.1 Desigo Xworks Plus ................................................................................ 12
3.2 CFC-Editor von PX Design ..................................................................... 13
3.2.1 M-bus data point mapping via meter tables ............................................ 13
3.2.2 M-bus data point mapping via instance table.......................................... 14
3.2.3 M-bus data point mapping via DP key words.......................................... 16
3.2.4 M-bus data point mapping via DIF, DIFE, VIF, VIFE for manufacturer-
specific M-bus data points....................................................................... 17
3.2.5 M-bus data point mapping via RAW for manufacturer-specific M-bus
data points ............................................................................................... 18
4 Functional scope of the application .................................................... 21
4.1 Overview ................................................................................................. 21
4.2 Communication ....................................................................................... 21
4.2.1 The M-bus protocol ................................................................................. 21
4.2.2 Polling response of the M-bus master .................................................... 23
4.2.3 BACnet Reliability [Rlb] ........................................................................... 23
4.3 Setting parameters .................................................................................. 26
4.3.1 Monitoring the communications .............................................................. 28
4.3.2 Scan priorities and waiting periods ......................................................... 29
4.3.3 Setting the baud rate using the user-defined meter table. ...................... 31
5 Details of M-bus data point mapping .................................................. 32
5.1 M-bus data point mapping, directly via the I/O address .......................... 32
5.1.1 Meter table .............................................................................................. 32
5.1.2 Instance table .......................................................................................... 40
5.1.3 Data point key words and units ............................................................... 42
6 Commissioning ..................................................................................... 45
7 Technical Data ....................................................................................... 45
2 / 47
Siemens Contents CM2Y9774en_04

Building Technologies 2016-07-31
8 Software and firmware versions.......................................................... 45
3 / 47
Siemens PX Open M-bus CM2Y9774en_04

Building Technologies Before you start 2016-07-31
0 Before you start
0.1 Revision history
Version Date Document No. Change Section Pages

V5.1/6.0 2016-07 CM2Y9774en_04 New hardware: System controller Whole document —
PXC001.. and PXA40-RS.. extension modules
V2.36 / 2013-08 CM2Y9774en_02 M-bus data point mapping via:
4.1 / 5.0 - Meter table 3.2.1/5.1.1 13 / 34
- Instance table 3.2.2/5.1.2 14 / 42
- DP key words 3.2.3/5.1.3 17 / 43
- DIF, DIFE, VIF, VIFE 3.2.4 18
- Manufacturer-specific M-bus data points 3.2.5 19
Function/R15
Scan priorities 4.2.3 24
PX M-bus changed to PX Open M-bus 4.3.2 30
PX OPEN Monitor changed to PX Open monitor Whole document —
0.2 Trademarks
The following trade names and product names are registered trademarks:
BACnet American National Standard (ANSI/ASHRAE 135-2012)
0.3 Related documents
Reference Title Document number
[1] The M-Bus: A Documentation M-Bus User group Version 4.8

http://www.m-bus.com/mbusdoc/default.php November 11, 1997
[2] PX Open M-bus data sheet CM2N9774

[3] PX Open Monitor, User Manual CA2Y9755
[4] System controller PXC001.. and Option module PXA40-RS.., data sheet CM1N9223
4 / 47
Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

1 Introduction
1.1 Positioning of the PX Open M-bus solution
Topologies
The Desigo building automation and control system supports the integration of
third-party devices and systems at all levels (see the topology diagram above).
M-bus meters to be integrated at the automation level are integrated with the PX
Open M-bus solution, which runs on the PXC001... system controller fitted with an
extension module PXA40-RS... .
PX Open M-Bus as The M-bus meters and M-bus systems are integrated into the Desigo system.
M-bus master The values of the M-bus data points and the status of the existing data connection
to the data points are mapped to BACnet objects by the PX Open M-bus solution.
In this way, these M-bus data points can be made available in all the devices in the
Desigo system.
PX Open Monitor The PX Open Monitor software, described in the User's Guide [3], is available for
the monitoring and analysis of data traffic on the M-bus.
1.2 Requirements and limitations in relation to

the M-bus system
Secondary addressing The PX Open M-bus solution does not support secondary addressing of the M-bus
meters.
Configuring the M-bus M-bus meters cannot be configured via the PX Open M-bus.
devices
Slave Search An automatic slave search feature is not supported on the M-bus.
5 / 47

Building Technologies Introduction 2016-07-31
2 Project engineering overview
2.1 The integration workflow
2.1.1 Adding a system controller
As a first step, add a PX Open controller in the "Network Configurator" in XWP.
2.1.2 DP-Import in System Design
The DP-Import tool feature in XWP is used to import the complete M-bus subsys-
tem structure.
If you are using DP-Import, you can go straight to section 2.1.5.
2.1.3 Creating the technical hierarchy
1. In Point Configurator, create the required plant/partial plant hierarchy.
2. In "Network Configurator create the required plant/partial plant hierarchy.
6 / 47

Building Technologies Project engineering overview 2016-07-31
2.1.4 Creating the M-bus subsystem structure
1. In the Technical hierarchy view in System Design, create the required M-bus
subsystem structure (e.g. with each meter corresponding to a "component").
2. Assign the required data points to the meters and complete the data point
fields (the "I/O Address" field must be completed in accordance with the map-
ping instructions).
3. Create the new component Mtr1 (Meter 1).
4. Create new data points to the component Mtr1.
5. Set the new Mtr1 data points.
7 / 47

2.1.5 Synchronizing the project to PX Design
1. Synchronize to CFC.
---> Clicking “Generate CFC data and exit” will guide you directly to CFC.
2. Navigate to CFC.
3. Reorganize the CI blocks.
8 / 47

2.1.6 Navigating to the CFC project in PX Design
Navigate XWP to the CFC project in PX Design. When you open the project, you
will see the meter components created in XWP.
1. Select "Edit I/O Addresses".
2. Set the I/O address to the data points.
3. Set I/O addresses in CFC.
9 / 47

4. Navigate to the point configurator.
5. Navigate to the CFC to the M-bus subsystem.
2.1.7 Adding and setting the COMBLK and MSGBLK blocks to

CFC.
Block COMBLK (FB495) allows you to set up communication ports for third-party
devices, and license numbers. The block is used in conjunction with PX Open for
internal communication settings and license settings.
Block MSGBLK (FB496) handles error statistics associated with communications
with third-party devices and other internal information. This block is used in con-
junction with PX Open to display and configure error statistics.
Important! • It is essential that both blocks are added to the CFC project.
• Each one must be added once only for each PXC001... controller.
10 / 47

2.1.8 Adding the main pin (main value)
A "main pin" must be set for all elements mapped to BACnet (partial plant, aggre-
gates, components and rooms).
Important! In the case of solutions created in Point Configurator, the main pin is already set.
2.1.9 Adding text blocks
If text blocks are to be used for meter integration in the project, these must be add-
ed directly here, in the CFC project. Text blocks are not supported in Point Config-
urator.
2.1.10 Node Setup, compiling the CFC project and download-

ing the program
The remaining steps in the procedure, such as "Node Setup", "compiling the CFC
project" and "downloading the program" are the same as for a standard PX control-
ler.
In the case of the PX Open M-bus solution, the complete program should be down-
loaded.
11 / 47

3 Project engineering details
3.1 Desigo Works Plus
The information about how a data point from an M-bus meter is addressed (the
mapping information) is contained in the I/O address.
The mapping information can be
• entered directly in CFC in the I/O address field, or
• imported automatically from an external table using the DP Import function of
Point Configurator.
The meters can be mapped within the technical hierarchy, e.g. as components. The
individual values from the meters are mapped in CFC to the standard data point
types CI or AI.
When an M-bus data point is integrated via a CI data point type, the data type
UINT32 must be entered in the I/O address. The signal type is selected accordingly
with UINT32, but is not relevant for the application in CFC.
When an M-bus data point is integrated via data point type AI, the data type FLOAT
must be entered in the I/O address. The signal type is selected accordingly with
FLOAT, but is not relevant for the application in the CFC.
Note M-bus data points are mapped to the following ranges:
Data point type (DP) Value range

CI 0 to 4,294,967,295
AI -3.403E+38 bis 3.403E+38
CI 0, 1
12 / 47

Building Technologies Project engineering details 2016-07-31
3.2 CFC-Editor von PX Design
3.2.1 M-bus data point mapping via meter tables
mapping information) is contained in the I/O address of the D-MAP block.
Mapping information can be entered directly in the CFC Editor of XWP.
Mapping information is available as an index in table form, meter table 0, which
corresponds to the M-bus data point to be mapped to the D-MAP block. You will
find meter table 0 in section 5.1.1.
The syntax for the mapping information is as follows:
M=x(y.z[DATATYPE])
Element Definition Range Description
x M-bus 1 … 250 M-bus slave address

primary address
y M-bus 0 … 999 Table 0 is used as the default table and corresponds to the meter table.
"meter table" Tables 1 to 999 refer to the device-specific text blocks.
z Data point 0 … 65535 The index numbers for meter table 0 are predefined and cannot be
index number changed. Index numbers for data points from the device-specific text
blocks can be used freely.
DATATYPE Data type BOOL, UINT16, SINT16, Data formats mapped from the M-bus data points to the associated
UINT32, SINT32, FLOAT BACnet object.
Recommendation
• If an M-bus data point is integrated via an AI block, FLOAT should be selected as the data type.
• When an M-bus data point is integrated via a CI block, UINT32 should be selected as the data
type.
13 / 47

3.2.2 M-bus data point mapping via instance table
If manufacturer documentation for the meter is not available, the desired data type
can be read from the meter with the help of the MBSheet tool from Relay (see:
http://www.relay.de/en/produkte/software/mbsheet.html).
Tariff number, Storage number and Module number are read directly – together
with the data type and unit. You can reference the index number from the instance
table in section 5.1.2 from data type and unit and use it together with Tariff number,
Storage number and Module number in the following mapping information.
The syntax for the mapping information is as follows:
M=x(0.b.c.d.e[DATATYPE])

x M-bus 1…250 M-bus slave address
primary address
0 M-bus 0 Table 0 is used as the default table and corresponds to the meter
"meter table" table.
b Module number 0…1023 Device internal module number, also referred to as device (Device unit
field in the DIFE portion of the telegram).
c Storage number 0...65535 Storage number ("Storage number" field in the DIF and DIFE portion
of the telegram).
d Tariff number 0…65535 Tariff number ("Tariff number" field in the DIFE portion of the tele-
gram).
e Data point 0 …65535 The index numbers from the instance table.
index number
DATATYPE Data type BOOL, UINT16, SINT16, Data formats mapped from the M-bus data points to the associated
UINT32, SINT32, FLOAT BACnet object.
Recommendation
• If an M-bus data point is integrated via an AI block, FLOAT should be selected as the data type.
• When an M-bus data point is integrated via a CI block, UINT32 should be selected as the data
type.
14 / 47

Example 1 The following example shows the addressing of the cooling energy for a Kamstrup
Multical 601 Heating/cooling meter.
With MBSheet, the following addressing elements can be identified:
M=90(0.3.0.0.1[UINT32])
M-Bus Slave Address 90
Meter Table 0
Module number 3
Storage number 0
Tariff number 0
DP Index Energy KWh 1
Type: instant. (1)
Access to the type with the addressing from the instance table:
(1 = Inst, 2 = Max, 3 = Min, 65535 = Err)
Example 2 The following example shows the addressing of the 15 monthly energy values for
an ULTRAHEAT XS 2WR6 energy meter.
With MBSheet, the following addressing elements can be identified (framed in red):
The addressing of the 15 previous month energy values can be done as follows:
First previous month energy values  M=6(0.0.2.0.1[UINT32])

Second previous month energy values  M=6(0.0.3.0.1[UINT32])
*
*
*
14th previous month energy values  M=6(0.0.15.0.1[UINT32])
15th previous month energy values  M=6(0.0.16.0.1[UINT32])
15 / 47

3.2.3 M-bus data point mapping via DP key words
Text blocks can be used to map M-bus data points via "keywords". The standard
blocks such as CI or AI always refer to the I/O addresses of these text blocks.
I/O address input in the text block: M=x.y(1)
x Meter table number 1 … 999 Table for a specific meter type
y Text block number 1…X Number of a text block within the meter table
(1) — — This value must always be (1)
The following is an example of a meter table No. 1, generated with two text blocks.
Input rules The following input rules apply to the individual text fields and the designation of
the "DP keywords":
Entries in the Value field of the text block:
"DP Index", "DP keyword" and "Unit".
Example in CFC "1" "Energy" "KWh"

For a table of data point key words see section 5.1.3 – Data point key words and
units.
The meter table (see illustration above) only needs to be created once for each
meter type. Several meters in the subsystem can point to the same text block.
16 / 47

3.2.4 M-bus data point mapping via DIF, DIFE, VIF, VIFE for
manufacturer-specific M-bus data points
You will need this solution for vendor-specific M-bus data points which cannot be
read from the meter by the generic M-bus User Group approach.
The TXTBLK block can be used to set up text strings corresponding to the vendor-
specific data points. The text block must adopt the information required for this
purpose, such as DIF, DIFE, VIF and VIFE from the manufacturer's tables.
The text block only needs to be created once for each meter type. Several meters
in the subsystem can point to the same text block.
Input rules The following input rules apply to the individual text fields.
"DP-Index" "Data point name" "Unit" "DIF:xx" "DIFE:xx" "VIF:xx" "VIFE:xx"
If you use several DIFEs and VIFEs, the values should be separated with commas:
"DIFE:80,40"
If there is no DIFE or VIFE, there will be an empty space between the inverted
commas (see example), i.e. "DIFE:" or "VIFE:" is not allowed in the meter table:
Example
Note: VIF/DIF coding must match the VIF/DIF coding of the M-bus device re-
sponse telegram.
17 / 47

3.2.5 M-bus data point mapping via RAW for
manufacturer-specific M-bus data points
This solution is required for manufacturer-specific M-bus data points that cannot be
read from the meter using a generic approach by the M-bus user group, and for
which the manufacturer does not describe using data identification per M-bus
standard.
Read data using:
– Byte data in the supplier specific part of the telegram.
– Data length.
– Data format with the M-bus data types.
Text blocks can be used to map M-bus data points via "manufacturer-specific M-
bus data points".
Input rules The following input rules apply to the individual text fields:
"DP-Index" "Data point name" "Unit" "RAW:t,b,a,f.y"
Text block Ranges Description

element RAW
t 1...256 Telegram number,
1 = first RSP-UD telegram,
2 = second RSP-UD telegram.
b 1…999 Byte position in the manufacturer specific part of the telegram, from
st
0x0F or 0x1F up to 1 Byte of the data to be mapped.
a 1...256 Number of bytes to be read.
f 0...14 Data format number (f stands for the encoding of the data field of the
M-bus).
. Separates the data format and the actual bit address of the byte (next
field, optional).
st
y 1...8 Bit address in the 1 Byte of a, whereat f=0 and a=1 in order to evalu-
ate the right Byte. Suitable for BI data points.
Data format Number Data format

0 1 Byte for Bit access
1 8 Bit Integer
2 16 Bit Integer
3 24 Bit Integer
4 32 Bit Integer
5 32 Bit Real (Float)
6 48 Bit Integer
7 64 Bit Integer
9 2 digit BCD
10 4 digit BCD
11 6 digit BCD
12 8 digit BCD
14 12 digit BCD
18 / 47

Example 1 RSP_UD2 telegram.
Meaning First RSP_UD2 telegram; from 0x0F or 0x1F up to the 1st Byte of the data to be
mapped are 11 Bytes, 4 Bytes to be mapped, coded as 8 digit BCD.
Coded in TXTBLK
Result in CFC
19 / 47

Example 2 RSP_UD2 telegram.
Meaning First RSP_UD2 telegram, from 0x0F or 0x1F up to the 1st Byte of the data to be
mapped there are 3 Bytes, 1 Byte to be mapped, coded as 1 Byte for Bit access,
map 1st Bit.
Encoded in TXTBLK
Result in CFC
20 / 47

4 Functional scope of the application
4.1 Overview
Function • The PX Open M-bus solution enables data points from M-bus devices to be in-
tegrated into the Desigo system.
• The values of the M-bus data points and the status of the existing data connec-
tion with the data point are mapped to BACnet objects by the PX Open M-bus
solution.
• The PX Open M-bus solution is implemented as an M-bus master.
Hardware platform The hardware platform is the system controller or the PXC001… with (optional)
extension modules PXA40-RS.. .
Technical information Maximum number of M-bus data points: Up to 2000

Number of M-bus slaves on the PX Open M-bus: 1 … 250
Electrical interface: RS 232 (peer-to-peer)
RS 232 (Peer-to-Peer): 300, 1200, 2400, 4800 or 9600 Baud
RS 485 (Multi-Drop): 300, 1200, 2400, 4800 or 9600 Baud
4.2 Communication
4.2.1 The M-bus protocol
The following section provides only a brief overview of the M-bus protocol.
For a detailed specification, refer to the document [1].
Master/slave protocol The M-bus protocol is a master/slave protocol. By definition, this means that an M-
bus network contains one master and at least one slave.
Transactions The M-bus master starts the transactions over the network with a slave query.
over the M-bus The slave concerned sends a response.
Supported M-bus Service Order Type of communication

communication ser- 0 REQ_UD2
vices 1 (Default) SND_NKE before every REQ_UD2
2 SND_UD "Check Frame" before every REQ_UD2
3 SND_UD "Data Frame" before every REQ_UD2
4 SND_UD "Data Frame" (on start-up only) before every REQ_UD2
5 REQ_UD1 before every REQ_UD2
Creating the SND_UD The SND_UD "Data Frame" is created in the associated text block. It is possible to
enter more than one SND_UD "Data Frame" entries in one text block.
21 / 47

Building Technologies Functional scope of the application 2016-07-31
"SND_UD" "Nr" "xxyyzz"
Example in CFC "SND_UD" "1" "8801FD50"

"SND_UD" "2" "8802FD50"
"SND_UD" "3" "8803FD50"
Telegram sequence on M-bus:
Important: The meter is only queried (see the yellow highlighted section above)
if referenced is made to this slave in CFC using an M-bus mapping variant.
22 / 47

4.2.2 Polling response of the M-bus master
At regular intervals, the M-bus master reads the data points and required commu-
nications service from the slaves. If a slave fails to respond, the master waits after
each query for the (relatively long) response-timeout time to elapse. This causes a
major delay in the exchange of data with those slaves that still have to respond.
To overcome this, the PX Open M-bus solution works in "master mode" as follows:
• Telegram is repeated
• If the slave still fails to respond, any pending queries for this slave are skipped
until all the pending queries for the other slaves have been processed once.
Note The state of the M-bus data points is mapped

to the "Reliability" parameter, Rlb (refer to
BACnet Reliability, next sub-section).
4.2.3 BACnet Reliability [Rlb]
The status of the M-bus data points is mapped to the [Rlb] (Reliability) parameter.
In the standard I/O blocks, one [Rlb] parameter is available for each M-bus data
point. By contrast, the Discipline I/O blocks COMBLK and MSGBLK have a single,
shared, [Rlb]. This applies jointly to all M-bus data points of the Discipline I/O.
Reliability value Meaning
0 / NO_FAULT_DETECTED The connection between data point and slave is OK.
2 / OVER_RANGE Value of the M-bus data point is higher than the defined value range.
3 / UNDER_RANGE Value of the M-bus data point is lower than the defined value range.
8 / PROCESS_ERROR Processing error of ComBlock, MessageBlock or TextBlock inputs.
10 / CONFIGURATION_ERROR Invalid data type configured for data point.
68 / INVALID_ADDR Error while programming the IO address or the meter table.
70 / INVALID_PARAM Internal error at the creation of a data point.
80 / UNRELIABLE_OBJECT Connection problem between M-bus slave and a data point.
84 / MEMORY_LIMIT_REACHED Number of licensed data points has been exceeded.
In the event of an error, more information can be obtained by use of the PX Open
Monitor (see also User's Guide, PX Open Monitor [3]).
Suppression of alarm If one or more slaves fail to respond, the M-bus master sets the Reliability parame-
messages in the event ter of all the affected I/O blocks to UNRELIABLE_OBJECT.
of a bus failure In the case of a common source, a very large number of alarms can be triggered (a
"burst"), which can overload the entire system.
To prevent this, in cases where there is "No response from slave", it is possible to
selectively suppress this change to the Reliability parameter. The "free syntax" in
the IO address string is used for this purpose:
M=X(Y.Y.Y.Y.Y[Z])/R15
Recommendation We recommend that at least one data point per slave should not be suppressed.
23 / 47

Delay of alarm mes- PX Open M-bus offers the function /R15 to suppress all alarms and device faults.
sages in the event of a In order to avoid short-term dysfunctions on the M-bus and to prevent the points
bus failure from going immediately to alarm, you can increase the number of repetitions (De-
fault=2) via the diagnostic point D=97 and/or increase the ScanCycles (Default=2)
via the diagnostic point D=99. Thus, the alarm message can be delayed.
Definition of the following diagnostic points:

1. The max. number of repetitions can be set via the diagnostic point D=97 as
follows:
– Settings in the analog out (AO) point have to be adjusted as follows:
o IOAddr: D=97
o EnPgm=Yes
o Slope=1
o Icpt=0
– The values for the pin ValPgm mean the following:
o ValPgm=0 ---> 2 repetitions (Default)
o ValPgm=1 ---> 1 repetition
o ValPgm=2 ---> 2 repetitions
o ValPgm=n ---> n repetitions (n < 1000)
2. The max. number of ScanCycles can be set via the diagnostic point D=99 as
follows:
– Settings in the analog out (AO) point have to be adjusted as follows:
o IOAddr: D=99
o EnPgm=Yes
o Slope=1
o Icpt=0
– The values for the pin ValPgm have the following meaning:
o ValPgm=0  2 ScanCycles (Default)
o ValPgm=1 1 ScanCycle
o ValPgm=n  n ScanCycles (n < 1000)
Time limitation between The time limit between two repeating SND_NKE- or REQ_UD2 telegrams must be
repeating SND_NKE or adjustable as certain meters (Sontex) have a sleep mode while operating on bat-
REQ_UD2 telegrams teries to save them and must be awaken with a slave query, i.e. that the first tele-
gram is not answered and a new query must occur within 2 seconds as the meter
otherwise returns to sleep mode.
Via the diagnostic point D=98 the time limitation between two telegram repetitions
(SND_NKE or REQ_UD2) can be set as follows:
– Set the analog out data point (AO) as follows:
o IOAddr: D=98
o EnPgm=Yes
o Slope=1
o Icpt=0
– The values for the pin ValPgm have the following meaning:
o ValPgm=0  2.5 FrmTio im COMBLK (Default)
o ValPgm=100  100ms
o ValPgm=1000  1 s
Limitation The M-bus master starts transactions on the network with a slave scan SND_NKE.
of REQ_UD2 The queried slave responds with 0xE5.
telegrams The master demands with REQ_UD2 meter data from the slave. It does not ask for
certain points in this scan, but rather scans data in general.
24 / 47

The slave responds with RES_UD2 with a number of data that are all described
with an identification code. The master selects data of interest to it.
The master demands with another REQ_UD2 the next data if in the received
RES_UD2, from the slave this is requested with 0x1F.
The limitation of REQ_UD2 telegrams that the master can send maximum to the
slave can be configured as follows.
"NUMBER REQ_UD2" "Maximum number of telegrams"
Example in CFC In the following example one single REQ_UD2 telegram is queried from the slave
with the address 43 (0x2B), though in the RES_UD2 telegram 0x1F is set and this
means that there would be more data available:
Telegram sequence on the M-bus:
25 / 47

4.3 Setting parameters
In the PX Open M-bus solution, the communications parameters and information

about the program status are contained in two "Discipline I/Os", the Communica-
tion Block COMBLK and the Message Block MSGBLK
These two Discipline I/Os must be present once only in every CFC program (ap-
plication) of a system controller.
Communication Block Variable Variable Data type Description Recommended

COMBLK name type settings
Baud VAR_INPUT UINT32 Baud rate on M-bus
300 / 2400 / 9600 2400
StpBit VAR_INPUT UINT16 Number of stop bits on the M-bus 1
Parity VAR_INPUT MULTI Parity on the M-bus Even
1: No parity / 2 : Even / 3 : Odd
CharLngth VAR_INPUT UINT16 Number of data bits per character on the 8
M-bus
7/8
RegNum VAR_INPUT UINT32 License number for the 0
a)
M-bus solution
CharTio VAR_INPUT FLOAT Character timeout [ms] 50
Maximum time between two characters on
the M-bus
FrmTio VAR_INPUT FLOAT Frame timeout [ms]
Maximum time for transmission of an M-
bus telegram
at 9600 Baud 400
at 2400 Baud 1300
at 300 Baud 10000
ScanDly VAR_INPUT FLOAT Polling time (M-bus master) [ms]
Interval time between tow queries
50 … 5000 1000
ComInfo1 VAR_INPUT FLOAT Delay [min] before the re-reading of all 0
slaves on the M-bus starts
Value 0 = Timer not activated:
the value under ScanDly will apply
slaves on the M-bus with "SCAN PRIO 2"
(SCAN PRIO selected in the associated
text block)
text block)
text block)
ComInfo5 VAR_INPUT FLOAT — —
IOAddr VAR_INPUT Refers here only to the COMBLK and is “M=1(1)“
used to define the internal mapping table.
[Rlb] etc. Alarm-Handling for the entire block —
– = Reserved for other third-party solutions
a)
Note! Licensing as per the Release notes.
26 / 47

Message Block MSGBLK Variable Variable type Data Description Recommended
name type (see also CFC description) settings
InsDate VAR_INPUT ASCII Entry of engineering date 0
RstSsys VAR_INPUT BOOL Reset PX Open 0
MsgStppr VAR_INPUT UINT16 Message Stepper 0
ResetMsg VAR_INPUT BOOL Reset Messages 0
ToolMod VAR_INPUT BOOL Tool Mode 0
MsgLv1 VAR_INPUT UINT16 Message Level 0
LogfLv1 VAR_INPUT UINT16 Logfile Level 0
MsgTrg VAR_INPUT UINT16 Trigger MesNr 0
PrvMsgNr VAR_INPUT UINT16 Before MesNr. 0
NxMsgNr VAR_INPUT UINT16 After MesNr. 0
SfWVn VAR_OUTPUT FLOAT SW Version 0
SfwSta VAR_OUTPUT UINT16 SW State 0
NumEr VAR_OUTPUT UINT16 Error Counter 0
ComEr VAR_OUTPUT UINT16 Comfail Counter 0
AddMsg2 VAR_OUTPUT FLOAT Additional message 2 0
AddMsg1 VAR_OUTPUT FLOAT Additional message 1 0
Licence VAR_OUTPUT BOOL b) FALSE
License Ok
TRUE = valid license present
IOAddr Refers here only to the MSGBLK “M=1(1)“
and is used to define the internal
mapping table
[Rlb] etc. Alarm handling for entire block —
— = Reserve for other third-party solutions
b)
Note! Licensing as per Release notes.
Encoding SwStatus The Pin SwStatus of the MSGBLK shows more detailed and more reliable infor-
mation about the subsystem status:
SwStatus Description
0 (EStartCreate) Getting MAC address or Neuron ID.
1 (EStartSuspend) DETDriver terminated, delayed start message will be sent (delay of 1000ms).
2 (EStartDET) Waiting for a valid ID
3 (EStartLicence) License check
4 (EStartRunApplication) New DBase sort
5 (EApliReset) Reset application
6 (EApliDBaseOK) DBase OK, start application init
7 (EApliDBaseContinue) The dbase sort is not finished,
8 (EApliInitOK) Application init OK, start the Driver3rd
9 (EApliInitContinue) The initialization for user data is not finished
10 (EApliDriverOK) Driver init OK
11 (EApliDriverContinue) Driver third init is in process
12 (EApliUserState) Start user application
13 (EApliActivePolling) Polling
14 (EApliActiveServer) Processing server services
The whole startup and initialization sequence can last up to 1 minute. Once the
startup has completed and during normal operation, the PX Open M-bus should be
in state 13. This indicates that the PX Open M-bus is polling the M-bus devices.
27 / 47

4.3.1 Monitoring the communications
A convenient means of monitoring the communications is the PX Open Monitor (for

a detailed description refer to the User's Guide [3].
The main screen displays the following information:

1. FW version of the connected system controller.
2. Communication Block
3. Message Block
4. Log file  Log file information
5. Connected  Connection status
Note All the screenshots illustrated here contain simulated information.
In the Protocol Analyzer pane, the reader can see the raw data of the communi-
cation between PX Open M-bus and third-party automation system.
28 / 47

4.3.2 Scan priorities and waiting periods
M-bus devices may be setup to be scanned based on a priority. It is possible to

engineer a customized meter table in which a polling priority option can be set. This
will then bind M-bus devices using this meter table to a specific polling priority. The
syntax required for the meter table entry for the polling priority is as follows:
The following input rules apply to the individual text fields:

Input rules Entries in the Value field of the text block:
"SCAN PRIO" "Polling priority number"
Example "SCAN PRIO" "2"
Where "SCAN PRIO" is the syntax for the polling priority, and "2" is the polling pri-
ority number.
If no entry is made into the meter table, then no polling priority is assumed. This
means that the M-bus device will be polled on a continual basis based on the time
needed to complete the scan cycle (which depends on the number of M-bus devic-
es on the bus).
The timer settings for the polling priorities can be set via the COMBlk Block pins
ComInfo2 - ComInfo4. The values entered in these pins are in minutes.
The other important thing to note here is that the values entered here must be in a
priority. For example, Prio2 is higher than Prio3, which is in turn higher than Prio4.
This means that value for Prio2 must be less than that for Prio3, which in turn must
be less than that for Prio4.
Example Prio2=10mins, Prio3=30mins und Prio4=60mins
Prio1 is reserved for all M-bus devices integrated into the PX Open M-bus and
overrides all the other Prio settings (i.e.ComInfo 1 overrides all settings for
ComInfo2-4).
Scanning COMBLK Meter table entry syntax

priority block
No entry required, value has to be 0, global scan timer for all M-bus
1 ComInfo1 devices integrated into PX Open M-bus.
2 ComInfo2 "SCAN PRIO" "2"
29 / 47

Configuration of
COMBLK block
Configuration example
for the 1st TXTBLK
block with SCAN PRIO
2:
Configuration example
for the 2nd TXTBLK
block with SCAN PRIO
3:
30 / 47

4.3.3 Setting the baud rate using the user-defined meter table.
Whenever older M-bus devices that are only running with 300 baud have to be
integrated, then the baud rate can be set using the user-defined meter table.
The following input rules apply to the individual text fields:

Input rules Entries in the Value field of the text block:
"BAUD" "Baud rate"
Example in CFC "BAUD" "300"
Important
• With meters referencing the above mentioned user-defined meter table the
master communicates at a baud rate of 300 Bit/s.
• With the remaining meters the master communicates at the baud rate set in
the pin BAUD of the COMBLK block.
31 / 47

5 Details of M-bus data point mapping
5.1 M-bus data point mapping, directly via the
I/O address
mapping information) is contained in the I/O address of the D-MAP block.
Mapping information is available as an index in table form for meter table 0 which
corresponds to the M-bus data point to be mapped to the D-MAP block.
5.1.1 Meter table
Note • All data points from 0 to 386 can be used in AI or CI D-MAP blocks.
• Data point 254, Application Reset, must be used in a BO, AO or MO block (Write
Only).
• Data point 255, Device Status, can be used in an AI, CI, BI or MI block.
DP index no. DP name Units

0 Energy Milliwatt Hours mWh
1 Energy Milliwatt Hours * 10 mWh * 10
2 Energy Milliwatt Hours * 100 mWh * 100
3 Energy Watt Hours Wh
4 Energy Watt Hours * 10 Wh * 10
5 Energy Watt Hours * 100 Wh * 100
6 Energy Kilowatt Hours kWh
7 Energy Kilowatt Hours * 10 kWh * 10
8 Energy J J
9 Energy J * 10 J * 10
10 Energy J * 100 J * 100
11 Energy kJ kJ
12 Energy kJ * 10 kJ * 10
13 Energy kJ * 100 kJ * 100
14 Energy MJ MJ
15 Energy MJ * 10 MJ * 10
16 Volume Milliliters ml
17 Volume Milliliters * 10 ml * 10
18 Volume Milliliters * 100 ml * 100
19 Volume Liters l
20 Volume Liters * 10 l * 10
21 Volume Liters * 100 l * 100
22 Volume m3 m3
23 Volume m3 * 10 m3 * 10
24 Mass g g
25 Mass g * 10 g * 10
26 Mass g * 100 g * 100
27 Mass kg kg
28 Mass kg * 10 kg * 10
29 Mass kg * 100 kg * 100
30 Mass Tons t
31 Mass Tons * 10 t * 10
32 OnTime Seconds s
33 OnTime Minutes min
32 / 47

Building Technologies Details of M-bus data point mapping 2016-07-31
34 OnTime Hours h
35 OnTime Days d
36 Operation Time Seconds s
37 Operation Time Minutes min
38 Operation Time Hours h
39 Operation Time Days d
40 Power Milliwatts mW
41 Power Milliwatts * 10 mW * 10
42 Power Milliwatts * 100 mW * 100
43 Power Watts W
44 Power Watts * 10 W * 10
45 Power Watts * 100 W * 100
46 Power kW kW
47 Power kW * 10 kW * 10
48 Power J/h J/h
49 Power J/h * 10 J/h * 10
50 Power J/h * 100 J/h * 100
51 Power kJ/h kJ/h
52 Power kJ/h * 10 kJ/h * 10
53 Power kJ/h * 100 kJ/h * 100
54 Power MJ/h MJ/h
55 Power MJ/h * 10 MJ/h * 10
56 Volume Flow Milliliters/h ml/h
57 Volume Flow Milliliters/h * 10 ml/h * 10
58 Volume Flow Milliliters/h * 100 ml/h * 100
59 Volume Flow Liters/h l/h
60 Volume Flow Liters/h * 10 l/h * 10
61 Volume Flow Liters/h * 100 l/h * 100
62 Volume Flow m3/h m3/h
63 Volume Flow m3/h * 10 m3/h * 10
64 Volume Flow µl/min * 100 µl/min * 100
65 Volume Flow Milliliters/min ml/min
66 Volume Flow Milliliters/min * 10 ml/min * 10
67 Volume Flow Milliliters/min * 100 ml/min * 100
68 Volume Flow Liters/min l/min
69 Volume Flow Liters/min * 10 l/min * 10
70 Volume Flow Liters/min * 100 l/min * 100
71 Volume Flow m3/min m3/min
72 Volume Flow µl/s µl/s
73 Volume Flow µl/s * 10 µl/s * 10
74 Volume Flow µl/s * 100 µl/s * 100
75 Volume Flow Milliliters/s ml/s
76 Volume Flow Milliliters/s * 10 ml/s * 10
77 Volume Flow Milliliters/s * 100 ml/s * 100
78 Volume Flow Liters/s l/s
79 Volume Flow Liters/s * 10 l/s * 10
80 Mass Flow g/h g/h
81 Mass Flow g/h * 10 g/h * 10
82 Mass Flow g/h * 100 g/h * 100
83 Mass Flow kg/h kg/h
84 Mass Flow kg/h * 10 kg/h * 10
85 Mass Flow kg/h * 100 kg/h * 100
86 Mass Flow tons/h t/h
87 Mass Flow tons/h * 10 t/h * 10
33 / 47

88 Flow Temperature millideg C m°C
89 Flow Temperature millideg C * 10 m°C * 10
90 Flow Temperature millideg C * 100 m°C * 100
91 Flow Temperature deg C °C
92 Return Temperature millideg C m°C
93 Return Temperature millideg C * 10 m°C * 10
94 Return Temperature millideg C * 100 m°C * 100
95 Return Temperature deg C °C
96 Temperature difference millideg K mK
97 Temperature difference millideg K * 10 mK * 10
98 Temperature difference millideg K * 100 mK * 100
99 Temperature difference deg K K
100 External temperature millideg C m°C
101 External temperature millideg C * 10 m°C * 10
102 External temperature millideg C * 100 m°C * 100
103 External temperature deg C °C
104 Pressure millibar mbar
105 Pressure millibar * 10 mbar * 10
106 Pressure millibar * 100 mbar * 100
107 Pressure bar bar
108 Time Point Date DD.MM.YY
109 Time Point Date-Time
3
110 Heat Cost Allocator m /h
111 Reserved -
112 Averaging Duration Seconds s
113 Averaging Duration Minutes min
114 Averaging Duration Hours h
115 Averaging Duration Days d
116 Actuality Duration Seconds s
117 Actuality Duration Minutes min
118 Actuality Duration Hours h
119 Actuality Duration Days d
120 Fabrication Number -
121 Enhanced Identification -
122 Bus Address -
124 Credit Currency Currency
125 Credit Currency*10 Currency*10
128 Debit Currency Currency
129 Debit Currency*10 Currency*10
132 Access Number
133 Medium
134 Manufacturer
135 Parameter set Identification
136 Model/Version
137 HW Version
138 FW Revision Number
139 SW Version
140 Customer Location
141 Customer number
142 Access code user
34 / 47

143 Access code operator
144 Access code SYSOP
145 Access code developer
146 Password
147 Error flags
148 Error mask
149 Reserved
150 Digital output
151 Digital input
152 Baudrate
153 Response delay time
154 Retry
155 Reserved
156 First storage
157 Last storage
158 Size of storage
159 Reserved
160 Storage interval Seconds secs
161 Storage interval Minutes mins
162 Storage interval Hours hrs
163 Storage interval Days days
164 Storage interval Months months
165 Storage interval Years years
166 Reserved
167 Reserved
168 Duration since last readout secs
169 Duration since last readout mins
170 Duration since last readout hrs
171 Duration since last readout days
172 Start of tariff
173 Duration of tariff mins
174 Duration of tariff hrs
175 Duration of tariff days
176 Period of tairff mins
177 Period of tariff hrs
178 Period of tariff days
179 Period of tariff months
180 Period of tariff years
181 No VIF
182 Reserved
183 Reserved
184 Reserved
185 Reserved
186 Reserved
187 Reserved
188 Voltage nanoVolts (10-9) nV
189 Voltage nanoVolts * 10 (10-8) nV*10
190 Voltage nanoVolts * 100 (10-7) nV*100
191 Voltage microVolts (10-6) µV
192 Voltage microVolts*10 (10-5) µV*10
193 Voltage microVolts*100 (10-4) µV*100
194 Voltage milliVolts (10-3) mV
195 Voltage milliVolts*10 (10-2) mV*10
196 Voltage milliVolts*100 (10-1) mV*100
35 / 47

197 Voltage Volts V
198 Voltage milliVolts*10 V*10
199 Voltage milliVolts *100 V*100
200 Voltage KiloVolts kV
201 Voltage KiloVolts *10 kV*10
202 Voltage KiloVolts *100 kV*100
203 Voltage MegaVolts MV
204 Current nanoAmps (10-9) nA
205 Current nanoAmps*10 (10-8) nA*10
206 Current nanoAmps*100 (10-7) nA*100
207 Current microAmps (10-6) µA
208 Current microAmps*10 (10-5) µA*10
209 Current microAmps*100 (10-4) µA*100
210 Current milliAmps (10-3) mA
211 Current milliAmps*10 (10-2) mA*10
212 Current milliAmps*100 (10-1) mA*100
213 Current Amps A
214 Current milliAmps*10 A*10
215 Current milliAmps *100 A*100
216 Current KiloAmps kA
217 Current KiloAmps *10 kA*10
218 Current KiloAmps *100 kA*100
219 Current MegaAmps MA
220 Reset Counter
221 Cumulation counter
222 Control signal
223 Day of week
224 Week number
225 Time point of day change
226 State of parameter activation
227 Special supplier info
228 Duration since last cumulation hrs
229 Duration since last cumulation days
230 Duration since last cumulation months
231 Duration since last cumulation years
232 Operating time battery hrs
233 Operating time battery days
234 Operating time battery months
235 Operating time battery years
236 Date and time of battery change
237 Reserved
238 Reserved
239 Reserved
240 Reserved
241 Reserved
242 Reserved
243 Reserved
244 Reserved
245 Reserved
246 Reserved
247 Reserved
248 Reserved
249 Reserved
250 Reserved
36 / 47

251 Reserved
252 Reserved
253 Bus Status from Variable Data Fixed Header
254 Application reset (SND_NKE) manuell -
255 Device Status: Error Report
(1 = OK; 2 = CFail; 3..255 general application errors from
CI code 0x70 offseted by 3)
256 Energy kWh*100 kWh*100
257 Energy MWh MWh
258 Reserved
259 Reserved
260 Reserved
261 Reserved
262 Reserved
263 Reserved
264 Energy MJ*100 MJ*100
265 Energy GJ GJ
266 Reserved
267 Reserved
268 Reserved
269 Reserved
270 Reserved
271 Reserved
272 Volume m3*100 m3*100
273 Volume m3*1000 m3*1000
274 Reserved
275 Reserved
276 Reserved
277 Reserved
278 Reserved
279 Reserved
280 Mass t*100 t*100
281 Mass kt kt
282 Reserved
283 Reserved
284 Reserved
285 Reserved
286 Reserved
287 Reserved
288 Reserved
289 Volume 0.1 Feet3 0.1 Feet3
290 Volume 0.1 American Gallons 0.1 Gallons
291 Volume American Gallons Gallons
292 Volume Flow 0.001 Gallons/min 0.001 Gallons/min
293 Volume Flow Gallons/min Gallons/min
294 Volume Flow Gallons/h Gallons/h
295 Reserved
296 Power kW*100 kW*100
297 Power MW MW
298 Reserved
299 Reserved
300 Reserved
301 Reserved
302 Reserved
37 / 47

303 Reserved
304 Power MJ*100/h MJ*100/h
305 Power GJ/h GJ/h
306 Reserved
307 Reserved
308 Reserved
309 Reserved
310 Reserved
311 Reserved
312 Reserved
313 Reserved
314 Reserved
315 Reserved
316 Reserved
317 Reserved
318 Reserved
319 Reserved
320 Reserved
321 Reserved
322 Reserved
323 Reserved
324 Reserved
325 Reserved
326 Reserved
327 Reserved
328 Reserved
329 Reserved
330 Reserved
331 Reserved
332 Reserved
333 Reserved
334 Reserved
335 Reserved
336 Reserved
337 Reserved
338 Reserved
339 Reserved
340 Reserved
341 Reserved
342 Reserved
343 Reserved
344 Flow Temp mºF mºF
345 Flow Temp mºF*10 mºF*10
346 Flow Temp mºF*100 mºF*100
347 Flow Temp ºF ºF
348 Return Temp mºF mºF
349 Return Temp mºF*10 mºF*10
350 Return Temp mºF*100 mºF*100
351 Return Temp ºF ºF
352 Temp difference mºF mºF
353 Temp difference mºF*10 mºF*10
354 Temp difference mºF*100 mºF*100
355 Temp difference ºF ºF
356 External Temp mºF mºF
38 / 47

357 External Temp mºF*10 mºF*10
358 External Temp mºF*100 mºF*100
359 External Temp ºF ºF
360 Reserved
361 Reserved
362 Reserved
363 Reserved
364 Reserved
365 Reserved
366 Reserved
367 Reserved
368 Cold/warm Temp Limit mºF mºF
369 Cold/warm Temp Limit mºF*10 mºF*10
370 Cold/warm Temp Limit mºF*100 mºF*100
371 Cold/warm Temp Limit ºF ºF
372 Cold/warm Temp Limit mºC mºC
373 Cold/warm Temp Limit mºC*10 mºC*10
374 Cold/warm Temp Limit mºC*100 mºC*100
375 Cold/warm Temp Limit ºC ºC
376 Cumulation Count Max Power mW mW
377 Cumulation Count Max Power mW*10 mW*10
378 Cumulation Count Max Power mW*100 mW*100
379 Cumulation Count Max Power W W
380 Cumulation Count Max Power W*10 W*10
381 Cumulation Count Max Power W*100 W*100
382 Cumulation Count Max Power kW kW
383 Cumulation Count Max Power kW*10 kW*10
384 Reserved
385 Status in fixed data structure
386 Medium in fixed data structure
387 Counter 1 (Fixed data structure)
388 Counter 2 (Fixed data structure)
39 / 47

5.1.2 Instance table
The parameter Tariff, Storage Number and Unit can only be mapped with the meter
table 0.
DP index number DP index no. DP name Units

(see table) 1 Energy Instantaneous (Inst) (kWh) kWh
2 Energy Maximum (Max) (kWh) kWh
3 Energy Minimum (Min) (kWh) kWh
65535 Energy Error (Err) (kWh) kWh
4 Energy Instantaneous (Inst) (kJ) kJ
5 Energy Maximum (Max) (kJ) kJ
6 Energy Minimum (Min) (kJ) kJ
7 Energy Error (Err) (kJ) kJ
8 Volume Instantaneous (Inst) Liters l
9 Volume Maximum (Max) Liters l
10 Volume Minimum (Min) Liters l
11 Volume Error (Err) Liters l
12 Mass Instantaneous (Inst) kg kg
13 Mass Maximum (Max) kg kg
14 Mass Minimum (Min) kg kg
15 Mass Error (Err) kg kg
16 Power Instantaneous (Inst) W W
17 Power Maximum (Max) W W
18 Power Minimum (Min) W W
19 Power Error (Err) W W
20 Power Instantaneous (Inst) kJ/h kJ/h
21 Power Maximum (Max) kJ/h kJ/h
22 Power Minimum (Min) kJ/h kJ/h
23 Power Error (Err) kJ/h kJ/h
24 Volume Flow Instantaneous (Inst) Liters l/h
25 Volume Flow Maximum (Max) Liters l/h
26 Volume Flow Minimum (Min) Liters l/h
27 Volume Flow Error (Err) Liters l/h
28 Volume Flow Instantaneous (Inst) Liters l/min
29 Volume Flow Maximum (Max) Liters l/min
30 Volume Flow Minimum (Min) Liters l/min
31 Volume Flow Error (Err) Liters l/min
32 Volume Flow Instantaneous (Inst) Liters l/s
33 Volume Flow Maximum (Max) Liters l/s
34 Volume Flow Minimum (Min) Liters l/s
35 Volume Flow Error (Err) Liters l/s
36 Mass Flow Instantaneous (Inst) kg kg /h
37 Mass Flow Maximum (Max) kg kg /h
38 Mass Flow Minimum (Min) kg kg /h
39 Mass Flow Error (Err) kg kg /h
40 Flow Temp Instantaneous (Inst) ºC ºC
41 Flow Temp Maximum (Max) ºC ºC
42 Flow Temp Minimum (Min) ºC ºC
43 Flow Temp Error (Err) kg ºC ºC
44 Return Temp Instantaneous (Inst) ºC ºC
45 Return Temp Maximum (Max) ºC ºC
46 Return Temp Minimum (Min) ºC ºC
47 Return Temp Error (Err) ºC ºC
40 / 47

48 Temp difference Instantaneous (Inst) ºC ºC
49 Temp difference Maximum (Max) ºC ºC
50 Temp difference Minimum (Min) ºC ºC
51 Temp difference Error (Err) ºC ºC
52 External Temp Instantaneous (Inst) ºC ºC
53 External Temp Maximum (Max) ºC ºC
54 External Temp Minimum (Min) ºC ºC
55 External Temp Error (Err) ºC ºC
56 Pressure bar Instantaneous (Inst) bar
57 Pressure bar Maximum (Max) bar
58 Pressure bar Minimum (Min) bar
59 Pressure bar Error (Err) bar
60 Storage Interval hours (Inst) hrs
61 Storage Interval hours (Max) hrs
62 Storage Interval hours (Min) hrs
63 Storage Interval hours (Err) hrs
64 Start of Tariff hours (Inst) date
65 Start of Tariff hours (Max) date
66 Start of Tariff hours (Min) date
67 Start of Tariff hours (Err) date
68 Duration of Tariff hours (Inst) hrs
69 Duration of Tariff hours (Max) hrs
70 Duration of Tariff hours (Min) hrs
71 Duration of Tariff hours (Err) hrs
72 Period of Tariff hours (Inst) hrs
73 Period of Tariff hours (Max) hrs
74 Period of Tariff hours (Min) hrs
75 Period of Tariff hours (Err) hrs
76 Voltage Volts (Inst) V
77 Voltage Volts (Max) V
78 Voltage Volts (Min) V
79 Voltage Volts (Err) V
80 Current Amps (Inst) A
81 Current Amps (Max) A
82 Current Amps (Min) A
83 Current Amps (Err) A
41 / 47

5.1.3 Data point key words and units
M-bus data point map- Text blocks can be used to map M-bus data points via "keywords".
ping via TXTBLK The standard blocks such as CI or AI always refer to the I/O addresses of these
blocks and DP key- text blocks.
words
The text block only needs to be created once for each meter type.
Several meters in the subsystem can point to the same text block.
M-bus parameter keyword syntax Permitted syntax for units

Energy MiliWh
MiliWh*10
MiliWh*100
Wh
Wh*10
Wh*100
KWh
KWh*10
Energy J J
J*10
J*100
KJ
KJ*10
KJ*100
MJ
MJ*10
Volume MiliL
MiliL*10
MiliL*100
L
L*10
L*100
m3
m3*10
Mass G
G*10
G*100
Kg
Mass (continued)
Kg*10
Kg*100
T
T*10
On Time Bitte Tabelle 0 benutzen.
Operating Time Bitte Tabelle 0 benutzen.
Power MiliW
MiliW*10
MiliW*100
W
W*10
W*100
KW
KW*10
Power J JHr
JHr*10
42 / 47

Power J (continued) JHr*100
KJHr
KJHr*10
KJHr*100
MJHr
MJHr*10
Volume Flow MiliLHr
MiliLHr*10
MiliLHr*100
LHr
LHr*10
LHr*100
m3Hr
m3Hr*10
Vol Flow Ext1 MicroL/Min
MiliL/Min
MiliL/Min*10
MiliL/Min*100
L/Min
L/Min*10
L/Min*100
m3/Min
Vol Flow Ext2 MicroL/Sec
MicroL/Sec*10
MicroL/Sec*100
MiliL/Sec
MiliL/Sec*10
MiliL/Sec*100
L/Sec
L/Sec*10
Mass Flow G/Hr
G/Hr*10
G/Hr*100
Kg/Hr
Kg/Hr*10
Kg/Hr*100
T/Hr
T/Hr*10
Flow Temp MiliDegC
MiliDegC*10
MiliDegC*100
DegC
Return Temp Return/MiliDegC
Return/MiliDegC*10
Return/MiliDegC*100
Return/DegC
Temp Difference MiliDegK
MiliDegK*10
MiliDegK*100
DegK
External Temp Ext/MiliDegC
Ext/MiliDegC*10
Ext/MiliDegC*100
Ext/DegC
43 / 47

Pressure MiliBar
MiliBar*10
MiliBar*100
Bar
Average Duration Bitte Table 0 benutzen
Actuality Duration Bitte Table 0 benutzen
Voltage NV
NV*10
NV*100
MicroV
MicroV*10
MicroV*100
MiliV
MiliV*10
MiliV*100
V
V*10
V*100
KV
KV*10
KV*100
MegaV
Current NA
NA*10
NA*100
MicroA
MicroA*10
MicroA*100
MiliA
MiliA*10
MiliA*100
A
A*10
A*100
KA
KA*10
KA*100
MegaA
44 / 47

6 Commissioning
See data sheet «System controller PXC001..D and option module PXA40-RS..» [4]
7 Technical Data
For technical data refer to:
• Data sheet PX Open PXC001… System controller and option modules [4]
• Data sheet PX Open M-bus [2]
8 Software and firmware versions

Refer to the corresponding Release Notes.
45 / 47

Building Technologies Commissioning 2016-07-31
Index
A L
Alarm suppression ......................... 23 Lizenzierungs-Mechanismus ......... 26
B M
BACnet Reliability [lRlb] ................. 23 Main pin .......................................... 11
Blocks Mapping information ...................... 13
COMBLK .............................. 10, 26 Master/slave protocol .................... 21
MSGBLK .............................. 10, 26 M-Bus data point mapping ............ 13
TXTBLK .......................... 16, 17, 42 M-bus master .................................. 5
M-bus master polling response ..... 23
C M-bus protocol............................... 21
CFC editor ..................................... 13 M-bus subsystem structure ............. 7
CFC project Meter table 0 ........................... 13, 32
Add blocks .................................. 10
Add text blocks ........................... 11 N
Communication monitoring ............ 28 Node setup ..................................... 11
Communication services ............... 21
Compile CFC project ..................... 11 P
Polling response ............................ 23
D Protocol analyzer........................... 28
Data point keywords ...................... 42 PX Design ..................................... 13
Data point mapping ........... 16, 32, 42 PX M-bus ......................................... 5
Desigo Xworks Plus ....................... 12 PX Open monitor ........................... 28
D-MAP block .................................. 13 PXA40-RS.. ..................................... 5
Download program ........................ 11 PXC001.. ......................................... 5
DP import ....................................... 12
DP import tool .................................. 6 R
DP keywords.................................. 16 Reliability Rlb ................................. 23
DP keywords.................................. 16 Requirements .................................. 5
E S
Engineering details ........................ 12 Setting parameters ........................ 26
Error statistics ................................ 10 Slave response.............................. 21
Extension modules PXA40-RS.. .... 21 SND_UD ........................................ 21
System controller PXC001.. ...... 6, 21
F System limits ................................... 5
Functions ....................................... 21
T
H Technical hierarchy.......................... 6
Hardware platform ......................... 21 Text blocks ..................................... 16
Text strings .................................... 17
I
Input rules .............. 16, 17, 18, 22, 25 X
Integrations workflow ....................... 6 XWP
Technical hierarchy ...................... 6
K
Keywords ....................................... 16
46/47

Building Technologies Index 2016-07-31
Siemens Switzerland Ltd
Building Technologies Division
International Headquarters
Gubelstrasse 22
6301 Zug
Schweiz
Tel. +41 41-724 24 24 © Siemens Switzerland Ltd, 2013
www.buildingtechnologies.siemens.com Subject to change.
47 / 47


Modbus PX Io

Uploaded by

Copyright:

Available Formats

Modbus PX Io

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Modbus PX Io

Uploaded by

Copyright:

Available Formats

s

Siemens Contents CM2Y9774en_04

Siemens PX Open M-bus CM2Y9774en_04

Version Date Document No. Change Section Pages

0.3 Related documents

Reference Title Document number

[1] The M-Bus: A Documentation M-Bus User group Version 4.8

[2] PX Open M-bus data sheet CM2N9774

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

1.2 Requirements and limitations in relation to

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

As a first step, add a PX Open controller in the "Network Configurator" in XWP.

2.1.2 DP-Import in System Design

2.1.3 Creating the technical hierarchy

1. In Point Configurator, create the required plant/partial plant hierarchy.

2. In "Network Configurator create the required plant/partial plant hierarchy.

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

4. Create new data points to the component Mtr1.

5. Set the new Mtr1 data points.

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

3. Reorganize the CI blocks.

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

1. Select "Edit I/O Addresses".

2. Set the I/O address to the data points.

3. Set I/O addresses in CFC.

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

5. Navigate to the CFC to the M-bus subsystem.

2.1.7 Adding and setting the COMBLK and MSGBLK blocks to

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

2.1.9 Adding text blocks

2.1.10 Node Setup, compiling the CFC project and download-

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

Note M-bus data points are mapped to the following ranges:

Data point type (DP) Value range

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

The syntax for the mapping information is as follows:

Element Definition Range Description

x M-bus 1 … 250 M-bus slave address

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

The syntax for the mapping information is as follows:

Element Definition Range Description

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

First previous month energy values  M=6(0.0.2.0.1[UINT32])

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

Element Definition Range Description

x Meter table number 1 … 999 Table for a specific meter type

(1) — — This value must always be (1)

Example in CFC "1" "Energy" "KWh"

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

Text block Ranges Description

Data format Number Data format

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

Technical information Maximum number of M-bus data points: Up to 2000

Supported M-bus Service Order Type of communication

Siemens Desigo™ PX Open – PX M-Bus CM2Y9774en_04

Example in CFC "SND_UD" "1" "8801FD50"