CA2 Y9772 en

Desigo™ PX Open
PX Modbus
Engineering guide
Versions 5.1 SP and higher
CA2Y9772en_05
2015-03-31 Building Technologies
2 / 34
Siemens Desigo PX Open Modbus CA2Y9772en_05

Building Technologies 2015-03-31
Table of Contents
1 Introduction ............................................................................................. 5
1.1 Positioning of the PX Open Modbus solution ........................................... 5
1.2 Requirements and limitations in relation to the Modbus system .............. 6
2 Project engineering overview ................................................................ 7
2.1 I/O address................................................................................................ 7
2.1.1 Universal example for Modbus master ..................................................... 9
2.2 Setting parameters and outputs .............................................................. 11
3 Functional scope of the application.................................................... 13
3.1 Overview ................................................................................................. 13
3.2 Communication ....................................................................................... 14
3.2.1 The Modbus protocol .............................................................................. 14
3.2.2 Polling by the Modbus master................................................................. 15
3.2.3 Updating the output values from the viewpoint of the Modbus master ... 16
3.2.4 Collating several data points in a single telegram .................................. 16
3.2.5 BACnet Reliability ................................................................................... 17
3.2.6 Monitoring the communications .............................................................. 18
4 Project engineering details .................................................................. 20
4.1 I/O address.............................................................................................. 20
4.1.1 Overview ................................................................................................. 20
4.1.2 Detailed description of the mapping information..................................... 21
4.2 Modbus settings ...................................................................................... 23
5 Details of the Modbus protocol ........................................................... 24
5.1 Extensions to the Modbus protocol ......................................................... 24
5.1.1 Suppressing the transmission of a variable number of data points ........ 24
5.1.2 BitPos function: Reading/Writing individual bits in the Modbus registers24
5.1.3 Feedback function: Transmission of pulses and value sequences......... 25
5.1.4 Transmission of 32-bit values ................................................................. 27
5.1.5 Periodic writing of outputs ....................................................................... 27
5.1.6 Format conversion .................................................................................. 27
5.2 Data conversion ...................................................................................... 28
6 Commissioning ..................................................................................... 32
7 Technical data ....................................................................................... 32
8 Software and firmware versions.......................................................... 32
Index ................................................................................................................ 33
3 / 34

Building Technologies Table of Contents 2015-03-31
0 Before you start
0.1 Revision history
Version Date Document No. Change Section Page(s)

V5.1 2014-06 CA1Y9772en_0 · Replacement of PXC00… with all all
5 PXC001…
4.0 2009-01 CA1Y9772en_04 · Universal example for Modbus master 2.2.1 9
· Time Gap for Modbus Slave only 4.2 22
V2.37 2007-03 CA1Y9772en_03 · Illustration 1.1 5
· Correction: Preset Single Register 2.1.1 9
· Correction: Baudrate Modbus 2.2 10
· I/O Address 4.1 19
· Data type 5.2 29
· Layout corrections Whole document
V2.36 2006-07 CA1Y9772en_01 PXC…-U automation station with PXA30-RS 1.2, 3 6, 13
extension module as an alternative hardware
option
Revision history added 4
New sections added: “Reference to 4
trademarks and product names” and
“Related documents”
Minor text corrections (nomenclature) with no Whole document
effect on content
Revised index Index
0.2 Reference to trade names and product

names
The following trade names and product names are registered trademarks:
BACnet American National Standard (ANSI/ASHRAE 135-1995)
Modbus® MODICON, Inc., Industrial Automation Systems, North
Andover, Massachusetts USA, and see modbus.org
0.3 Related documents
Ref. Title Document

[1] Modicon Modbus Protocol Reference Guide, June 1996 PI-MBUS-300
(MODICON,Inc., Industrial Automation Systems, North Rev. J
Andover, Massachusetts USA)
[2] PX Open Modbus, data sheet CA2N9772
[3] PX Open Monitor, user manual CA2Y9755
[4] PX Open -CRS system controller, data sheet CA2N9771
4 / 34

Building Technologies Before you start 2015-03-31
1 Introduction
1.1 Positioning of the PX Open Modbus solution
The Desigo building automation and control system supports the integration of
third-party devices and systems at all levels (see the topology diagram above).
Modbus devices and systems are integrated at the automation level using the PX
Open Modbus solution, which runs on the PXC001.D system controller.
Integration can be achieved in either direction:
· When Modbus devices or systems are integrated into a Desigo system
à the PXC001.D or PXC001-E.D with a PXA40-RS… extension module if
necessary) acts as the Modbus master.
The values of the Modbus data points and the state of the existing data
connection with the data point are mapped to BACnet objects by the PX Open
Modbus solution. In this way, the Modbus data points can be made available in
all the devices in the Desigo system.
· When a Desigo system or Desigo device is integrated into a Modbus system,
à the PXC001.D with or PXC001-E.D (with a PXA40-RS… extension module if
necessary) acts as a Modbus slave.
A third-party Modbus master can be used to integrate the data points from the
Desigo system via the PX Open Modbus slave.
Further, the data traffic on the Modbus can be monitored and analyzed by use of
the PX Open Monitor software, which is described in the User's Guide for the
Desigo PX Open Monitor [3].
5 / 34

Building Technologies Introduction 2015-03-31
1.2 Requirements and limitations in relation to
the Modbus system
Modbus function codes Function Code Description

supported 01 Read Coil Status
02 Read Input Status
03 Read Holding Registers
04 Read Input Registers
05 Force Single Coil
06 Preset Single Register
15 Force Multiple Coils
16 Preset Multiple Registers
Use as master PX Open Modbus master

and as slave
The PX Open Modbus master allows the integration of 1…247 Modbus slaves.
PX Open Modbus slave
The PX Open Modbus slave enables the Desigo system to be integrated by a
third-party Modbus master.
Limitations In RTU mode, the Modbus slaves can only be operated in a point-to-point
configuration. In a multi-drop configuration, it must either be possible to program
the Modbus master with appropriate time settings, or the network must be operated
in ASCII mode.
For details of the Modbus settings, refer to chapter 4.2.
6 / 34

Building Technologies Introduction 2015-03-31
2 Project engineering overview
2.1 I/O address
The parameter IOAddress contains information about how to address a data point
of an I/O block on the Modbus, which function code to use and which format
conversion procedures are required.
The structure of the parameter IOAddress is always as follows (see also Data
conversion, chapter 5.2):
M = MappingInfo1(MappingInfo2.MappingInfo3.MappingInfo4.MappingInfo5.MappingInfo6[DataType])/Free syntax
Element Meaning Range Description

MappingInfo1 Modbus address 1 .. 247 Modbus slave address
+1000 An offset of +1000 added to a slave
address indicates that the data point
is a feedback value.
MappingInfo2 Modbus service code 1,2,3,4,5,6, Service code with which the data point
15,16 is to be transmitted.
MappingInfo3 --- 0 ---
MappingInfo4 Modbus register 0 .. 65535 Modbus register address of the data
address point. For values transmitted in two
registers, the register with the lower
value should be entered here.
MappingInfo5 Additional functions 0 0 : BitPos Function disabled
1 .. 16 1 .. 16 : BitPos enabled. The value
indicates the position of the bit in the
Modbus register.
MappingInfo6 Format 0 .. 9 Indicates which function is to be used
for data conversion.
Data type Data type BOOL, UINT16,
SINT16, UINT32,
SINT32, FLOAT
Free syntax Control element 0…3 characters Free syntax is used as control
element for special functions.
For examples see 3.2.5 and 5.1.
Example of two function blocks with an associated "IOAddr" pin in CFC chart
7 / 34

Building Technologies Project engineering overview 2015-03-31
The task of the commissioning engineer is to find the relevant information in the
third-party documentation, and to carry out the addressing of each data point in the
CFC.
Practical example Mapping table for a Modbus energy meter
8 / 34

2.1.1 Universal example for Modbus master
Modbus view
Modbus register address
Modbus memory range

vs. CFC view
Modbus slave address
Modbus service code
Description of the
Modbus function
Function blocks in
(MappingInfo1)
(MappingInfo4)
(MappingInfo2)
Application
CFC Editor
XXX YYYY 1 0X Read Coil Status DI Read multiple DIs
XXX YYYY 2 1X Read Input Status DI Read multiple DIs
XXX YYYY 3 4X Read Holding Register AI Read multiple AIs
XXX YYYY 4 3X Read Input Register AI Read multiple AIs
XXX YYYY 5 0X Force Single Coil DO Write single DO
XXX YYYY 6 4X Preset Single Holding AO Write single AO
Register
XXX YYYY 15 0X Force Multiple Coils DO Write multiple DOs
XXX YYYY 16 4X Preset Multiple Holding AO Write multiple AOs
Registers
For the IOAddr of function blocks, the following "mapping strings" must be added:
Service Application "Mapping strings" for the IOAddr

code of the CFC function blocks
1 Read multiple DI’s M = ...

(Modbus Coil Status) M = ....
M = XXX(1.0.YYYY.0.0...
2 Read multiple DI’s M = ...

(Modbus Input Status) M = ....
M = XXX(2.0.YYYY.0.0...
3 Read multiple AI’s M = ...
(Modbus Holding Registers) M = ....
M = XXX(3.0.YYYY. 0.0...
3 (cont'd) Read multiple DI’s M = XXX(3.0.YYYY. BitPos.0...
from one (or several successive) M = XXX(3.0.YYYY. BitPos.0...
Holding Registers M = XXX(3.0.YYYY. BitPos.0...
4 Read multiple AI’s M = ...
(Modbus Input Register) M = ....
M = XXX(4.0.YYYY. 0.0...
4 (cont'd) Read multiple DI’s M = XXX(4.0.YYYY. BitPos.0...
from one (or several successive) M = XXX(4.0.YYYY. BitPos.0...
Input Registers M = XXX(4.0.YYYY. BitPos.0...
5 Write single DO M = XXX(5.0.YYYY.0.0...
(ForceCoil
Coil)
6 Write single AO M = XXX(6.0.YYYY. 0.0...

(Modbus Holding Register)
6 (cont'd) Write multiple DO's M = XXX(6.0.YYYY. BitPos.0...

to a Modbus Holding Register M = XXX(6.0.YYYY. BitPos.0...
M = XXX(6.0.YYYY. BitPos.0...
9 / 34
Building Technologies Project engineering overview 2015-03
03-31
15 Write multiple DO's M = ...
to successive Coils M = ....
M = XXX(15.0.YYYY.0.0...
16 Write multiple AO's M = ...
to successive Holding Registers M = ....
M = XXX(16.0.YYYY. 0.0...
16 (cont'd) Write multiple DO's M = ...
to one (or multiple successive) M = ....
Modbus Holding Registers M = XXX(16.0.YYYY. BitPos.0...
Note BitPos values 1..16 designate the Bit that is to be handled.

BitPos = 0 means the BitPos function is disabled. However, disabled does not
mean the Bool type is forbidden (see section 5.2 "Data conversion"). Using the
Boolean type with BitPos = 0 means the entire Modbus 16 Bit register is used to
store the Boolean value.
10 / 34

2.2 Setting parameters and outputs
In the PX Open Modbus solution, the communications parameters and information

about the program status are contained in two "Discipline I/O" blocks, the
Communication Block (COMBLK) and in the Message Block (MSGBLK).
Important! These two Discipline I/Os must be present in every CFC program (application) of a
system controller.
Default
Communication Block Variabl Variable Data Description
Master
Slave
(COMBLK) e Name Type Type
01589 Baud VAR_INPUT UINT32 Baud rate on the Modbus
3 600 / 1200 / 2400 /4800 / 9600 9600 X X
COMBLK OB1
(38400 with PXC001.D)
Communic 7/- StopBit VAR_INPUT UINT16 Number of stop bits on the Modbus
0 OoServ Rlb 1 X X
1/2
600 Baud AlmSta
Parity VAR_INPUT MULTI Parity on the Modbus
1 StopBit Dstb None X X
No Parity / 2: Even / 3: Odd
1 Parity LstMsg
6 Length Length VAR_INPUT UINT16 Number of data bits per character on the
0 RegNum Modbus 8 X X
0.0 ChTmo 8 (fix)
0.0 FrTmo RegNum VAR_INPUT UINT32 License number for the
0.0 ScanDly 0 X X
Modbus solution 1)
0.0 Info1
0.0 Info2 ChTmo VAR_INPUT FLOAT Character timeout [mS]
0.0 Info3 Maximum time between two characters 100 X X
0.0 Info4 on the Modbus
0.0 Info5 FrTmo VAR_INPUT FLOAT Frame timeout [mS]
IOAddr 500 X X
Maximum time for the transmission of a
1 Reset
Modbus telegram
ScanDly VAR_INPUT FLOAT Polling time (Modbus Master) [mS]
Interval between two queries 500 X O
50…5000
Info1 VAR_INPUT FLOAT --- – – –
Info3 VAR_INPUT FLOAT Device Address (Modbus slave)
Modbus slave address – O X
1...247
IOAddr VAR_INPUT Refers here only to the COMBLK and is
– 2) X X
used to define the internal mapping table
Rlb usw. Alarm handling for the entire block – X X
– = Reserved for other third-party solutions
1. Licensing mechanism:
Refer to the data sheet for the PX Open Modbus solution [2]
Important! 2. No default value. HOWEVER, the following value must be entered to ensure
that the correct internal mapping table is selected:
"M=1(1)"
Mapping table
Device (Pseudo-address)
11 / 34

Message Block (MSGBLK) Variable Variable Data Description
Default
Name type type (see also DTS description)
01590 InsDate VAR_INPUT ASCII Entry of engineering date 0
4 ResetSub VAR_INPUT BOOL Reset PX Open 0
MSGBLK OB1
Message /- MeStep VAR_INPUT UINT16 Message Stepper 0
»
0 OoServ OpVers MeRes VAR_INPUT BOOL Reset Messages 0
16#FFFFFFFF InsDate State
Mode VAR_INPUT BOOL Tool Mode 0
0 ResetSub CntEr
1 MsgStep CntFail MeLev VAR_INPUT UINT16 Message Level 0
0 ResetMsg AddMsg2 LogLev VAR_INPUT UINT16 Logfile Level 0
0 ToolMod AddMsg1
0 MsgLvl License LogTrig VAR_INPUT UINT16 Trigger Mesnr 0
0 LogLvl ResetSta AmBefor VAR_INPUT UINT16 Before MesNr. 0
0 MsgTrig ToolCnct
AmAfter VAR_INPUT UINT16 After MesNr. 0
0 MsgBefor Res1
0 MsgAfter Res2 OpVers VAR_OUTPUT FLOAT SW Version 0
IOAddr Res3 State VAR_OUTPUT UINT16 SW State 0
1 Reset Res4
Res5 Couerr VAR_OUTPUT UINT16 Error Counter 0
Res6 Counter for program errors
Res7 CouCfai VAR_OUTPUT UINT16 Cfail Counter 0
Res8
Res9
Counter for communication errors
Res10 MeAdd1 VAR_OUTPUT FLOAT Mes. Additional 1 0
Rlb MeAdd2 VAR_OUTPUT FLOAT Mes. Additional 2 0
AlmSta
Dstb License VAR_OUTPUT BOOL License Ok 3) FALSE:
LstMsg TRUE = Identifies licensing as OK.
Res1 VAR_OUTPUT UINT16 Licence level
Res2 VAR_OUTPUT UINT16 Number of active data points
Res3 VAR_OUTPUT SINT16 Version 2.20.014 and higher:
Number of data points still available
in the licence range
(negative if higher than licence)
IOAddr Refers here only to the MSGBLK – 4)
and is used to define the internal
mapping table
Rlb usw. Alarm handling for the entire block – 5)
– = Reserved for other third-party solutions
1. Licensing mechanism:
Refer to the data sheet for the PX Open Modbus solution [2]
Important! 2. No default value. However, the following value must be entered to ensure
that the correct internal mapping table is selected:
"M=1(1)"
Mapping table
Device (pseudo address)
3. Version 2.20.014 and higher

If after a timeout period of 10 minutes the application is still not running (the
Modbus system may be unable to start for different reasons), the reliability of
the COMBLK will be set to APPLICATION_ALARM.
12 / 34

3 Functional scope of the application
3.1 Overview
· The PX Open Modbus solution enables data points from Modbus devices to be
integrated into the Desigo system.
· The values of the Modbus data points and the status of the existing data
connection with the data point are mapped to BACnet objects by the PX Open
Modbus solution.
· The PX Open Modbus solution can be used either as a Modbus master or as a
Modbus slave.
Hardware platform The hardware platform is the system controller, type PXE-CRS, or a modular
PXC…-U automation station fitted with a PXA30-RS extension module.
Technical information Maximum number of Modbus Up to 2000, depending on license

data points:
Number of Modbus slaves 1 … 247
connected to PX Open Modbus
master:
Electrical interface: RS232 (peer-to-peer) / RS 485 (multi-drop)
Baud rate: 600, 1200, 2400, 4800, 9600 and 19200 baud
Serial transmission RTU mode or ASCII mode

modes
Function codes Function Modbus function Application

supported code
01 Read Coil Status Read multiple DOs
02 Read Input Status Read multiple DIs
03 Read Holding Registers Read multiple AOs
04 Read Input Registers Read multiple AIs
05 Force Single Coil Write single DO
06 Preset Single Register Write single AO
15 Force Multiple Coils Write multiple DOs
16 Preset Multiple Registers Write multiple AOs
13 / 34

Building Technologies Functional scope of the application 2015-03-31
3.2 Communication
3.2.1 The Modbus protocol
The following section provides only a brief overview of the Modbus protocol.
For the full specification, refer to Modicon Modbus Protocol Reference Guide [1].
Master/slave protocol The Modbus is a master/slave protocol. By definition, this means that a Modbus
network contains one, and only one, master and at least one slave.
Transactions on the The Modbus master starts the transactions on the network with a slave query. The
Modbus slave either responds positively with the requested service (response) or transmits
an "exception message". In the remainder of this document, these query/response
sequences are also referred to as "Modbus telegrams".
Function codes The type of transaction is defined by the function code transmitted in the Modbus
telegrams. A function code defines the following:
· Structure of the telegram, query and response
· Direction of data transmission (master à slave or slaveàmaster)
· Data format of data point (bit or 16-bit register)
Transmission modes The Modbus protocol defines two alternative serial transmission modes:
These modes have the following characteristics:
RTU (Remote Terminal Unit) mode
· Binary-coded data
· Start and end of telegrams marked by timed pauses (a "silent interval") between
the characters transmitted.
· Check sum algorithm: CRC (Cyclic Redundancy Check)
ASCII mode
· Data in hexadecimal notation
· Beginning and end of telegrams marked by start and end characters.
· Check sum algorithm: LRC (Longitudinal Redundancy Check)
Telegrams with Certain types of Modbus transactions permit the transmission of a variable number
multiple data points of Modbus data points (bit or 16-bit register) in a single telegram.
14 / 34

3.2.2 Polling by the Modbus master
The Modbus master reads the data points from the slaves at regular intervals,
using the relevant function code (01, 02, 03 or 04). 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 Modbus solution works in "master mode" as
follows:
A) Slave fails to · Telegram is repeated

respond to query from · If the slave still fails to respond, any pending queries (read or write) for this slave
master are skipped until all the pending queries for the other slaves have been
processed once.
B) Slave responds to a · Telegram is repeated

query by sending an
exception message
· If the slave continues to respond with an exception message, the next pending
query is transmitted.
Note The state of the Modbus data points is mapped to the "Reliability" parameter, Rlb
(refer to BACnet Reliability, chapter 3.2.5).
15 / 34

3.2.3 Updating the output values from the viewpoint of the
Modbus master
Function Codes 05, 06, 15 and 16 serve to write data point values to the Modbus
slave. These values are written once when the master is started (with a positive
acknowledgement) and are subsequently rewritten only in the event of a change in
the data point value.
Since the value update is initiated only in the master in the event of a change of
value, there is a risk of data inconsistency after a reset or after a replacement of
the Modbus slave device.
To overcome this, the PX Open Modbus solution uses the following mechanism
when operating as master:
If a slave takes longer than a predefinable period of time to respond to queries
from the master ("Disconnected"), communication is re-established ("Connected")
and all values are written to the slave again.
3.2.4 Collating several data points in a single telegram
Modbus Function Codes 02 (Read Input Status), 03 (Read Holding Register), 04

(Read Input Register), 15 (Force Multiple Coils) and 16 (Preset Multiple Register)
can be used for the combined transmission of a variable number of Modbus data
points in a single Modbus telegram.
The PX Open Modbus solution makes automatic use of this option.
Modbus master Function Codes 02, 03 and 04 are used to read multiple data point values from the
Modbus slaves. In other words, these values are polled at regular intervals in the
slaves.
When operating as a master device, the PX Open Modbus solution automatically
constructs these polling telegrams so that within the predefined limits (max. length
of a telegram and max. number of registers) each telegram holds as many data
points as possible.
Function Codes 15 and 16 serve to write multiple data point values to the Modbus
slave. These values are written once when the program starts, and subsequently
whenever the data point value changes.
In master mode, the PX Open Modbus solution automatically constructs these
Write telegrams so that within the predefined limits (max. length of a telegram and
max. number of registers) each telegram holds as many modified (COV) data
points as possible.
Note As only the address of the first data point and the total number of data points can
be inserted in the Modbus telegram, it is only possible to combine data points with
addresses in continuous ascending order.
Response in the event If the Modbus master asks a slave for a data point which does not exist in that
of engineering errors slave, the master stops collating data points in combined telegrams, and reads or
writes the data points for each individual D-MAP parameter from the slave (this
may also be two Modbus data points). Periodically, the master repeats its attempt
to use combined telegrams for the exchange of data.
This approach ensures that the correct data point parameter settings are
transmitted despite the error.
Modbus slave
16 / 34

In the Modbus slave mode, the number of data points in a telegram is defined by
the master.
In slave mode, the PX Open Modbus solution returns an exception message if it
cannot resolve all the data points of a Write or Read query.
3.2.5 BACnet Reliability
The status of the Modbus data points is mapped to the Rlb (Reliability) parameter.
In the standard I/O blocks, one Rlb parameter is available for each Modbus data
point. By contrast, the Discipline I/O blocks COMBLK and MSGBLK have only one
shared Rlb parameter for all the Modbus data points of the Discipline I/O together.
Reliability value Meaning in Master Meaning in Slave

0 / NO_FAULT_DETECTED The connection between data point No error has been found in the
and slave is OK connection to the master. (It is
possible, however, that the master
has never polled this data point)
8 / PROCESS_ERROR The slave is responding with an Not applicable in slave mode.
exception code
68 / INVALID_ADDR An error occurred while Not applicable in slave mode.
programming the feedback value.
70 / INVALID_PARAM Error in parameter IOAddress Only occurs with certain errors when
(syntax) the master polls the data point.
71 FEEDBACK
80 / UNRELIABLE_OBJECT Connection between Modbus slave Not applicable in slave mode.
and this data point dropped.
84 / Number of licensed data points Number of licensed data points
MEMORY_LIMIT_REACHED reached reached
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 Modbus master sets the Reliability
messages in the event parameter of all the affected I/O blocks to UNRELIABLE_OBJECT. In the case of a
of a bus failure 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 I/OAdress string is used for this purpose:
M=X(Y.Y.Y.Y.Y[Z])/R15
We recommend that at least one DP per slave should NOT be suppressed.
17 / 34

3.2.6 Monitoring the communications
A convenient means of monitoring the communications is the PX Open Monitor [3].

The main screen displays the following information:
1. Currently connected PX Open application
2. Communication block
3. Message block
4. Log File
5. Connected à Connection status
Note All the screenshots illustrated here contain simulated information.
18 / 34

The Protocol Analyzer window provides the user with the following data:
1. Raw data from the communication between PX Open and the third-party
automation and control system
2. Data formatted on the basis of the description file.
19 / 34

4 Project engineering details
4.1 I/O address
The IOAddress pin of the I/O block contains information which defines
· how to address a data point of an I/O block on the Modbus,
· which function code to use and
· which format conversion procedures are required.
The structure of the parameter IOAddress is always as follows (see also chapter
5.2):
M = MappingInfo1(MappingInfo2.MappingInfo3.MappingInfo4.MappingInfo5.MappingInfo6[DataType]Free syntax
MappingInfo1 is different depending on whether the interface is operated as a

Modbus master or a Modbus slave.
4.1.1 Overview
Element Meaning Range Description

MappingInfo1 Modbus address 1 .. 247 Modbus slave address
for MASTER
mode +1000 An offset of +1000 added to a slave
address indicates that the data point is a
feedback value.
Important! MappingInfo1 --- 0 Code only, NO slave address!
for SLAVE The slave address for all data points of a
mode device is set in COMBLK/Info3.
MappingInfo2 Modbus service code 1,2,3,4,5,6, Service code with which the data point is
15,16 to be transmitted.
MappingInfo3 --- 0
MappingInfo4 Modbus Data Address 0 .. 65535 Modbus register address of the data
point. For values transmitted in two
registers, the register with the lower value
should be entered here.
MappingInfo5 Additional functions 0 0 : BitPos Function disabled
1 .. 16 1 .. 16 : BitPos enabled. The value
indicates the position of the bit in the
Modbus register.
MappingInfo6 Format 0 .. 9 Indicates which function is to be used for
data conversion.
Data type Data type BOOL,
UINT16,
SINT16,
UINT32,
SINT32,
FLOAT
Free syntax Control element 0…3 Free syntax used as control element for
characters special functions.
For examples see 3.2.5 and 5.1.
20 / 34

Building Technologies Project engineering details 2015-03-31
4.1.2 Detailed description of the mapping information
MappingInfo1 Operation as Modbus master:

In "Master" mode, MappingInfo1 contains the Modbus slave address.
The Modbus slave address indicates the Modbus device to which the data point is
to be transmitted, or from which the data point is to be read.
Operation as Modbus slave:
In Modbus slave mode, MappingInfo1 must always be set to 0.
Important! In Modbus slave mode, the slave address for all data points of a device is set in the
COMBLK/Info3 (see chapter 2.1).
MappingInfo2 In Modbus "Master" and "Slave" modes, MappingInfo2 contains the function code
to be transmitted with the data point on the Modbus. Since the function code also
defines the direction of the data traffic on the Modbus, this means that the I/O block
types with which the various function codes can be linked will differ, depending on
whether the Modbus solution is operated in master or slave mode.
Function Code Operation as Master Operation as slave

Input type Output type Input type Output type
01 Read Single Coil Admissible Illegal Illegal Admissible
02 Read Input Register Admissible Illegal Illegal Admissible
03 Read Holding Register Admissible Illegal Illegal Admissible
04 Read Input Register Admissible Illegal Illegal Admissible
05 Force Single Coil Illegal Admissible Admissible Illegal
06 Preset Single Register Illegal Admissible Admissible Illegal
15 Force Multiple Coil Illegal Admissible Admissible Illegal
16 Preset Multiple Register Illegal Admissible Admissible Illegal
MappingInfo3 MappingInfo3 must always be set to 0.
MappingInfo4 In Modbus "Master" and "Slave" modes, MappingInfo4 contains the register or bit
address to be transmitted with the data point on the Modbus.
For data types with a length of 32 bits, the PX Open Modbus solution automatically
uses two Modbus registers. After a data point with a length of 32 bits, therefore, the
next-but-one Modbus address must be allocated to the next data point.
MappingInfo5 The BitPos function can be enabled with values 1 … 16. Activation is only
permissible with the appropriate combination of data type and function code (see
the summary further below).
A value of 0 disables the BitPos function.
MappingInfo6 Values 1 … 9 enable the data conversion functions. Activation is only permissible
with the appropriate combination of data type and function code (see the summary
further below).
If a value of 0 is defined, no data conversion will take place.
21 / 34

The following conversion functions are available:
Format Name Function Possible with
Parameter these data types
0 No conversion All
1 SwapRegisters The two 16 bit registers are swapped before transmission to the Modbus and UINT32 / SINT32
after receipt from the Modbus
2 BCD16A The received data from the Modbus will be interpreted as a 16 Bit BCD Code UINT16
and transformed to a binary value.
A (binary) value to be sent on the Modbus will be converted into 16 Bit BCD
code
A : The first byte in the telegram is the most significant.
Example: Modbus Byte1 Modbus Byte2
Hex: 0x47 Hex: 0x19
BCD: 4 7 BCD: 1 9
Value = 4719
3 BCD16B The data received from the Modbus will be interpreted as a 16 Bit BCD Code UINT16
and converted into a binary value.
code
B : The first byte in the telegram is the least significant.
Example: Modbus Byte1 Modbus Byte2
Hex: 0x19 Hex: 0x47
BCD: 1 9 BCD 4 7
Value = 4719
4 BCD32A The data received from the Modbus will be interpreted as a 32 Bit BCD code and UINT32
converted into a binary value.
code
A: The first byte in the telegram is the most significant
Example: MB Byte1 MB Byte2 MB Byte3 MB Byte4
Hex: 0x53 Hex: 0x34 Hex: 0x47 Hex: 0x19
BCD:5 3 BCD: 3 4 BCD: 4 7 BCD: 1 9
Value = 53344719
5 BCD32B The data received from the Modbus will be interpreted as a 32 Bit BCD code and UINT32
converted into a binary value.
code
B: The first byte in the telegram is the least significant.
Hex: 0x19 Hex: 0x47 Hex: 0x34 Hex: 0x53
BCD: 1 9 BCD: 4 7 BCD: 3 4 BCD: 5 3
Value = 53344719
6 ACM16 The data received from the Modbus will be interpreted as follows. The value to UINT32
be sent on the Modbus will be converted as follows.
Value =Low Register + (High Register * 1000)
The first register transmitted in the telegram is the Low Register
Example: Byte 1 Byte 2 Byte 3 Byte 4
Hex: 0x02 Hex: 0xD6 Hex: 0x02 Hex: 0x83
726 643
Value = 726 = 643726 + (643 * 1000)
7 U32BITMOD100 The data received from the Modbus will be interpreted as follows. The value to UINT32
00 be sent on the Modbus will be converted as follows.
Value = (High Register * 10000) + Low Register
The first register transmitted in the telegram is the High Register
Example: Byte 1 Byte 2 Byte 3 Byte 4
Hex: 0x04 Hex: 0xD2 Hex: 0x16 Hex: 0x2E
1234 5678
Value = (1234 * 10000) + 5678 = 12345678
22 / 34

Format Name Function Possible with
Parameter these data types
8 S32BITMOD100 The data received from the Modbus will be interpreted as follows. The value to SINT32
00 be sent on the Modbus will be converted as follows.
Value = (High Register * 10000) + Low Register
The first register transmitted in the telegram is the High Register
Hex: 0xFB Hex: 0x2E Hex: 0xE9 Hex: 0xD2
-1234 -5678
Value = (-1234 * 10000) + -5678 = -12345678
9 SwapFloat The 4 Byte of the two 16 bit registers are swapped before transmission to the FLOAT
Modbus and after receipt from the Modbus
Hex: 0x7D Hex: 0x14 Hex: 0x48 Hex: 0x42
Value = 50.02
4.2 Modbus settings
In most cases, the information provided by the COMBLK and MSGBLK is sufficient.
For special functions or modifications, the PX Open Modbus solution includes a
group of output blocks which can be used to set special parameters.
It is not compulsory for these blocks to be present in the CFC program.
If they are not present, the default values will be used as listed.
Important! These parameters are read once only after power-up. Changes at runtime will
therefore only take effect after a system controller restart.
Name TimeGap (Modbus Slave only) Name AscMode

I/O Block Type AO I/O Block Type BO
Mapping Info D=52 Mapping Info D=53
Meaning Length of time between two characters Meaning TRUE: ASCII transmission mode
recognized as the beginning / end of the FALSE: RTU transmission mode
telegram
Eng. unit ms Eng. unit ---
Default 50 (*) Default FALSE:
Range 25 .. 1000 (*) Range 0 .. 1 (FALSE / TRUE)
(*) The values defined in the Modbus specification will not be achieved in Version 2.1. For this reason, operation as a Modbus slave in
RTU mode is possible only in a point-to-point configuration but not in a multi-drop arrangement.
Otherwise the third-party Modbus master must be capable of the appropriate time settings, or the network must be operated in ASCII
transmission mode.
Name Slave Name RegAmt
I/O Block Type BO I/O Block Type AO
Meaning TRUE: Modbus solution in slave mode Meaning Max. number of Modbus registers in one
FALSE: Modbus solution in master mode telegram
Eng. unit --- Eng. unit ---
Default FALSE: Default 64
Range 0 .. 1 (FALSE / TRUE) Range 2 .. 256
Name BitAmt Name DiscTim
I/O Block Type AO I/O Block Type AO
Meaning Maximum number of Modbus Single Bits Meaning If a slave remains disconnected for longer
(Coils or Input) in one telegram than the time specified here, then the
connection will be re-established and all
the output values will be rewritten.
Eng. unit --- Eng. unit sec
Default 64 Default 20
Range 1 .. 256 Range 5 .. 120
23 / 34

5 Details of the Modbus protocol
5.1 Extensions to the Modbus protocol
In may devices equipped with Modbus, the Modbus protocol is not fully
implemented. Not all the service codes can be used, and the data points are not
addressed strictly in accordance with the Modbus protocol.
In order to ensure the efficient integration of these devices, the PX Open Modbus
solution provides the add-ons described below.
5.1.1 Suppressing the transmission of a variable number of

data points
Some simple devices may not support the transmission of several data points in a
combined Modbus telegram.
In such cases the process of combining data points can be suppressed for specific
individual data points. The "free syntax" in the IOAdress string is used for this
purpose:
M=X(Y.Y.Y.Y.Y[Z])/R0
A data point defined in this way is always transmitted in a separate telegram.
5.1.2 BitPos function: Reading/Writing individual bits in the

Modbus registers
The Modbus protocol only allows single bits to be read with Function Codes 01
(Read Coil Status), 05 (Force Single Coil) and 15 (Force Multiple Coils).
However, many Modbus devices do not support all these function codes. The
BitPos function makes it possible to handle single bits despite this fact, and without
additional work in the CFC program.
BitPos can be used to link the I/O block types "Binary Input" and "Binary Output"
with single bits of a 16-bit Modbus register.
Example of a Modbus register linked with Function Code 04 (Read Input Register)
Note If different bit positions in the same register number are accessed (for example
100.1, 100.2, 100.3), the same Modbus function must be used for the writing of
all Bits from this register.
24 / 34

Building Technologies Details of the Modbus protocol 2015-03-31
Correct definition for the example above:
M=1(6,0,100,1,0[BOOL])
M=1(6,0,100,2,0[BOOL])
M=1(6,0,100,3,0[BOOL])
Incorrect use of bit positions:

M=1(6,0,100,1,0[BOOL])
M=1(16,0,100,2,0[BOOL])
M=1(6,0,100,3,0[BOOL])
5.1.3 Feedback function: Transmission of pulses and value

sequences
For the transmission of pulses or specific sequences of values of a Modbus data

point, it is important to ensure that a given state or value has been transmitted
before writing the next state or value to the data point. In order to be able to
program mechanisms of this kind in the CFC program of a Modbus master as
simply as possible, the PX Open Modbus solution uses the approach described
below.
The appropriate address can be entered as the feedback address in the output
modules. The last value acknowledged as having been received by the Modbus
slave then appears as the Feedback Value. In the CFC program, this value can be
used to determine when the next value or state may be written to the output.
Example Modbus master with a data point which contains a value.

This value is to be written to the slave.
1. A new value of 200 is to be written to the analog output
01583de
Analog Output
Neuer Wert: 200

PgmVal: 200 PrVal: 100
Analog Intput (Feedback)
PrVal: 100
2. The new value is transmitted to the slave via the Modbus.

01584en
Analog Output Value of 200 is

transmitted to
MODBUS
PrVal: 100
3. C) The receipt of the value is acknowledged by the slave as "Received".

PresentValue is then updated in FeedbackValue.
25 / 34

01585
Analog Output
Response: Ok
PrVal: 200
Feedback-addressing The Feedback address FbAddr has an offset of 1000 relative to IOAddr:
for the above example 01587 A
Io12
AO OB1
Analog o 5/-
0 OoServ PrVal
0.0 DefVal FbVal
1 Reset StaFlg
0 OpEn Rlb
0.0 OpVal AlmSta
1 PgmEn Dstb
0.0 PgmVal
M=1(16.0.0.0.0[UINT16]) IOAddr
M=1001(16.0.0.0.0[UINT16]) FbAddr
Fehler! Exception! In the block "Binary Output" the Feedback address has the data type UINT16
Es ist instead of BOOL:
nicht 01587 B
möglich, 3
durch BO OB1
Binary o 5/-
die 0 OoServ PrVal
Bearbeit 0.0 DefVal FbVal
ung von 1 Reset StaFlg
0 OpEn Rlb
Feldfunk 0.0 OpVal AlmSta
tionen 1 PgmEn Dstb
0.0 PgmVal
Objekte M=1(5.0.0.0.0[BOOL]) IOAddr
zu M=1001(5.0.0.0.0[UINT16]) FbAddr
erstellen
.
Direct feedback New for version 2.20.014 and higher:
from a BO
The R1 flag in the free syntax indicates a direct feedback from a BO.
This is required to convert the UINT16 to a BOOL in conformance with BACnet
Example of a direct feedback address:
M=1(1.0.0.0.0[UINT16])/R1
26 / 34

5.1.4 Transmission of 32-bit values
The Modbus protocol defines the 16-bit register as the largest data unit. 32 bit
values must therefore be transmitted in two registers.
The PX Open Modbus solution automatically occupies two 16-bit registers for the
data types concerned (FLOAT, UINT32 and SINT32), and also ensures that they
are always combined for transmission in a shared telegram (note that this requires
a function code capable of transmitting several registers in a single telegram.
5.1.5 Periodic writing of outputs
In versions 2.20.202 and higher the following mechanism is implemented:

There are three levels which determine the period of the writing.
To activate the periodic writing of outputs, the following R functions must be added
to the free syntax of the address string.
R function Level Writing interval

R2 1 every hour
R3 2 every 10 hours
R3 3 every 24 hours
· The writing actions of different levels are not necessarily synchronous

· A data point may be assigned to more than one level.
Mapping string Write Analog Output every hour:

examples: M=1(6.0.1.0.0[UINT16])/R2
Write Analog Output every 10 and every 24 hours:

M=1(6.0.1.0.0[UINT16])/R3/R4
5.1.6 Format conversion
In many devices incorporating the Modbus, special data formats (e.g. BCD, ACM
etc.) are used. There is a further problem, in that values which occupy two
registers, the sequence of the actual values can be defined in different ways.
The PX Open Modbus solution provides a whole range of conversion functions for
this application.
27 / 34

5.2 Data conversion
The specified data type defines the data type to which the Modbus data point is
mapped. The following data types are implemented:
· BOOL
· UINT16
· SINT16
· UINT32
· SINT32
· FLOAT
The selected data type is given in brackets at the end of the "MappingInfo" string.
Combination of The format of a Modbus data point can be influenced at various points on its
DataType, Format, journey through the PX Open system. The data format can be converted at the
BitPos and Function transition points A, B and C.
Code
Transition A is determined by the block type selected in CFC and the data type
selected in the IOAddress.
Transition B is determined by the data type selected in the IOAddress, the
conversion type in MappingInfo6 and the value for the BitPos function in
MappingInfo6.
Transition C is determined by the conversion type in MappingInfo6, the value for
the BitPos function in MappingInfo6 and the selected function code.
Checking There is no check of the selected combination in Transition A, but the combinations
used in Transition B and C are checked. The system will reject any conversion
processes which result in a loss of data (e.g. conversion from FLOAT to BIT).
Permitted data-type The direction of data flow determines which combinations are possible. This
combinations explains why there are only four different overview tables below.
Loss of accuracy with The conversion of 32-bit data types into FLOAT values is associated with a loss of
conversions into accuracy. The loss is 8 or 9 bits (for a signed and unsigned 32-bit value
FLOAT values respectively). This type of conversion arises with the combination of standard input
blocks with data types SINT32 and UINT32.
Important! If these combinations also include data conversion codes 1 (Swap Register) or 5
(BCD32B) the loss of accuracy moves to the most significant bits! These
combinations should therefore not be used.
28 / 34

Permissible combinations for input block types with Modbus operating as master:
Mapping Info BOOL SINT16 UINT16 SINT32 UINT32 FLOAT

DataType (2 Registers) (2 Registers) (2 Registers)
Mapping
Info6
Format
Parameter
0 No Conv. 01 Read Coil 01 Read Coil 01 Read Coil 01 Read Coil 01 Read Coil
02 Read Input 02 Read Input 02 Read Input 02 Read Input 02 Read Input
03 Read Holding 03 Read Holding 03 Read Holding 03 Read Holding 03 Read Holding
04 Read Input 04 Read Input 04 Read Input 04 Read Input 04 Read Input
1 Swap Register 01 Read Coil 01 Read Coil
02 Read Input 02 Read Input
03 Read Holding 03 Read Holding 03 Read Holding
04 Read Input 04 Read Input 04 Read Input
Do not use with Do not use with
Float Float
(default I/O) (standard I/O)
2 BCD16A 01 Read Coil
02 Read Input
03 Read Holding
04 Read Input
3 BCD 16B 01 Read Coil
02 Read Input
03 Read Holding
04 Read Input
4 BCD32A 01 Read Coil
02 Read Input
03 Read Holding
04 Read Input
5 BCD32B 01 Read Coil
Do not use 02 Read Input
with Float 03 Read Holding
(standard I/O) 04 Read Input
6 ACM16 01 Read Coil
02 Read Input
03 Read Holding
04 Read Input
7 01 Read Coil
U32BITMOD1000 02 Read Input
0 03 Read Holding
04 Read Input
8 01 Read Coil
S32BITMOD1000 02 Read Input
0 03 Read Holding
04 Read Input
BitPos 03 Read Holding
04 Read Input
MappingInfo5
29 / 34

Permissible combinations for output block types with Modbus operating as
master:
Mapping Info6
Format Parameter
0 No Conv. 05 Force S. Coil
06 Preset S.Reg 06 Preset S.Reg 06 Preset S.Reg
15 Force M.Coil
16 Preset M.Reg 16 Preset M.Reg 16 Preset M.Reg 16 Preset M.Reg 16 Preset M.Reg 16 Preset M.Reg
1 Swap Register 16 Preset M.Reg 16 Preset M.Reg 16 Preset M.Reg
2 BCD16A 06 Preset S.Reg
16 Preset M.Reg
3 BCD 16B 06 Preset S.Reg
16 Preset M.Reg
4 BCD32A 16 Preset M.Reg
5 BCD32B 16 Preset M.Reg
6 ACM16 16 Preset M.Reg
7 U32BITMOD10000 16 Preset M.Reg
8 S32BITMOD10000 16 Preset M.Reg
BitPos 06 Preset S.Reg
16 Preset M.Reg
MappingInfo5
Permissible combinations for input block types with Modbus operating as slave:
Mapping Info6
Format Parameter
0 No Conv. 05 Force S. Coil

06 Preset S.Reg 06 Preset S.Reg
15 Force M.Coil
16 Preset M.Reg 16 Preset M.Reg 16 Preset M.Reg 16 Preset M.Reg 16 Preset M.Reg
1 Swap Register 16 Preset M.Reg 16 Preset M.Reg 16 Preset M.Reg
Do not use with Do not use with
Float Float
(standard I/O) (standard I/O)
2 BCD16A 06 Preset S.Reg
16 Preset M.Reg
3 BCD 16B 06 Preset S.Reg
16 Preset M.Reg
4 BCD32A 16 Preset M.Reg
5 BCD32B 16 Preset M.Reg
Nicht verwenden
mit Float (Standard
I/O)
6 ACM16 16 Preset M.Reg
7 U32BITMOD10000 16 Preset M.Reg
8 S32BITMOD10000 16 Preset M.Reg
BitPos 06 Preset
S.Reg
16 Preset
M.Reg
MappingInfo5
30 / 34

Permissible combinations for output block types with Modbus operating as slave

DataType (2 (2 (2
Mapping Info6 Registers) Registers) Registers)
Format
Parameter
0 No Conv. 01 Read Coil
02 Read Input
03 Read 03 Read 03 Read 03 Read 03 Read 03 Read
Holding Holding Holding Holding Holding Holding
04 Read Input 04 Read Input 04 Read Input 04 Read Input 04 Read Input 04 Read Input
1 Swap Register 03 Read 03 Read 03 Read
Holding Holding Holding
04 Read Input 04 Read Input 04 Read Input
2 BCD16A 03 Read
Holding
04 Read Input
3 BCD 16B 03 Read
Holding
04 Read Input
4 BCD32A 03 Read
Holding
04 Read Input
5 BCD32B 03 Read
Holding
04 Read Input
6 ACM16 03 Read
Holding
04 Read Input
7 03 Read
U32BITMOD10000 Holding
04 Read Input
8 03 Read
S32BITMOD10000 Holding
04 Read Input
BitPos
MappingInfo5
31 / 34

6 Commissioning
The commissioning procedure involves simply downloading the firmware.
See also Data sheet PX Open System controller PXE-CRS [4]
7 Technical data
For technical data, refer to the following documents:
· PX Open System controller PXE-CRS, data sheet [4]
· PX Modbus solution, data sheet [2]
8 Software and firmware versions

Refer to the Release Notes
32 / 34

Building Technologies Commissioning 2015-03-31
Index
A M
Alarm Mapping information ..............................................21
suppression ....................................................... 17 Mapping strings .......................................................9
Applications .......................................................... 13 Message Block MSGBLK ...................................... 11
ASCII mode .................................................... 13, 14 Modbus
functions.............................................................13
B master ..............................................................5, 6
BitPos function ................................................ 21, 24 protocol ........................................................14, 24
Bus failure ............................................................. 17 settings...............................................................23
slave .................................................................5, 6
C telegram .............................................................16
CFC view ................................................................ 9 view ......................................................................9
Checking ......................................................... 14, 28 Modbus master polling ..........................................15
Communication
monitoring.......................................................... 18 O
Communication Block COMBLK........................... 11 Output
Cyclic Redundancy Check CRC ........................... 14 writing.................................................................27
D P
Data conversion .................................................... 28 Polling ....................................................................15
Desigo PX Open MONITOR ................................... 5 Project engineering .................................................7
Discipline I/Os ....................................................... 11 PXE-CRS ..............................................................13
PXE-CRS system controller ....................................5
E
Engineering errors ................................................ 16 R
Errors .................................................................... 16 Redundancy Check ...............................................14
Reliability Rlb ...................................................15, 17
F Requirements ..........................................................6
Feedback address FbAddr ................................... 26 RTU (Remote Terminal Unit) mode ............ 6, 13, 14
Feedback function ................................................ 25
FLOAT values ....................................................... 28 S
Format conversion ................................................ 27 Serial transmission modes ....................................14
Function codes ............................................... 13, 14
T
H Telegrams ..............................................................16
Hardware platform ................................................ 13 Third-party Modbus master .....................................5
Topology ..................................................................5
I Transmission
I/O address ........................................................... 20 32-bit values.......................................................27
I/OAddress .............................................................. 7 data ....................................................................24
Integration ............................................................... 5
U
L Updating output values..........................................16
limitations ................................................................ 6
Longitudinal Redundancy Check .......................... 14 W
Writing
intervals..............................................................27
33/34

Building Technologies Index 2015-03-31
Siemens Switzerland Ltd
Building Technologies Division
International Headquarters
Gubelstrasse 22
6301 Zug
Switzerland
Tel. +41 41-724 24 24 © Siemens Switzerland Ltd, 2002
www.buildingtechnologies.siemens.com Subject to change
34 / 34

Building Technologies 2015-03-31

CA2 Y9772 en

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CA2 Y9772 en

Hochgeladen von

Copyright:

Verfügbare Formate

Desigo™ PX Open

Siemens Desigo PX Open Modbus CA2Y9772en_05

Siemens Desigo PX Open Modbus CA2Y9772en_05

Version Date Document No. Change Section Page(s)

0.2 Reference to trade names and product

0.3 Related documents

Ref. Title Document

Siemens Desigo PX Open Modbus CA2Y9772en_05

Siemens Desigo PX Open Modbus CA2Y9772en_05

Modbus function codes Function Code Description

Use as master PX Open Modbus master

Siemens Desigo PX Open Modbus CA2Y9772en_05

Element Meaning Range Description

Siemens Desigo PX Open Modbus CA2Y9772en_05

Practical example Mapping table for a Modbus energy meter

Siemens Desigo PX Open Modbus CA2Y9772en_05

Modbus register address

Modbus memory range

Modbus slave address

Modbus service code

Service Application "Mapping strings" for the IOAddr

1 Read multiple DI’s M = ...

2 Read multiple DI’s M = ...

6 Write single AO M = XXX(6.0.YYYY. 0.0...

6 (cont'd) Write multiple DO's M = XXX(6.0.YYYY. BitPos.0...

Note BitPos values 1..16 designate the Bit that is to be handled.

Siemens Desigo PX Open Modbus CA2Y9772en_05

In the PX Open Modbus solution, the communications parameters and information

Siemens Desigo PX Open Modbus CA2Y9772en_05

Device (pseudo address)

3. Version 2.20.014 and higher

Siemens Desigo PX Open Modbus CA2Y9772en_05

Technical information Maximum number of Modbus Up to 2000, depending on license

Serial transmission RTU mode or ASCII mode

Function codes Function Modbus function Application

Siemens Desigo PX Open Modbus CA2Y9772en_05

Siemens Desigo PX Open Modbus CA2Y9772en_05

A) Slave fails to · Telegram is repeated

B) Slave responds to a · Telegram is repeated

Siemens Desigo PX Open Modbus CA2Y9772en_05

3.2.4 Collating several data points in a single telegram

Modbus Function Codes 02 (Read Input Status), 03 (Read Holding Register), 04

Siemens Desigo PX Open Modbus CA2Y9772en_05

3.2.5 BACnet Reliability

Reliability value Meaning in Master Meaning in Slave

We recommend that at least one DP per slave should NOT be suppressed.

Siemens Desigo PX Open Modbus CA2Y9772en_05

A convenient means of monitoring the communications is the PX Open Monitor [3].

Note All the screenshots illustrated here contain simulated information.

Siemens Desigo PX Open Modbus CA2Y9772en_05

Siemens Desigo PX Open Modbus CA2Y9772en_05

MappingInfo1 is different depending on whether the interface is operated as a

Element Meaning Range Description

Siemens Desigo PX Open Modbus CA2Y9772en_05

MappingInfo1 Operation as Modbus master:

Function Code Operation as Master Operation as slave

MappingInfo3 MappingInfo3 must always be set to 0.

Siemens Desigo PX Open Modbus CA2Y9772en_05

Siemens Desigo PX Open Modbus CA2Y9772en_05

4.2 Modbus settings

Name TimeGap (Modbus Slave only) Name AscMode

Siemens Desigo PX Open Modbus CA2Y9772en_05

5.1.1 Suppressing the transmission of a variable number of