0% found this document useful (0 votes)
1K views38 pages

Desigo PX Open PX Modbus: Engineering Guide

Uploaded by

elhbabacar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
1K views38 pages

Desigo PX Open PX Modbus: Engineering Guide

Uploaded by

elhbabacar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 38

Desigo™ PX Open

PX Modbus
Engineering guide
Versions 5.1 SP and higher

CA2Y9772en_06
2017-04-24 Building Technologies
Table of Contents
0 Before you start ................................................................................... 3
0.1 Revision history ..................................................................................... 3
0.2 Reference to trade names and product names ....................................... 3
0.3 Related documents ................................................................................ 3
1 Introduction ......................................................................................... 4
1.1 Positioning ............................................................................................. 4
1.2 Requirements and limitations ................................................................. 5
2 Project engineering overview ............................................................. 6
2.1 I/O address ............................................................................................ 6
2.2 Setting parameters .............................................................................. 10
3 Application functionality ................................................................... 13
3.1 Overview ............................................................................................. 13
3.2 Communication.................................................................................... 14
3.2.1 Protocol definition ................................................................................ 14
3.2.2 Polling mechanism............................................................................... 15
3.2.3 Updating mechanism ........................................................................... 16
3.2.4 Multiple data points in a telegram ......................................................... 16
3.2.5 BACnet Reliability ................................................................................ 17
3.2.6 Communications monitoring................................................................. 18
4 Project engineering ........................................................................... 20
4.1 I/O address .......................................................................................... 20
4.1.1 Overview ............................................................................................. 20
4.1.2 Mapping information ............................................................................ 21
4.2 Special settings ................................................................................... 23
5 Protocol details.................................................................................. 25
5.1 Protocol Extension ............................................................................... 25
5.1.1 Force single telegram .......................................................................... 25
5.1.2 BitPos function..................................................................................... 25
5.1.3 Feedback function ............................................................................... 26
5.1.4 Adjustable Offset for MI/MO ................................................................. 28
5.1.5 Multi Register Values (>=32Bit) ............................................................ 29
5.1.6 Periodic writing .................................................................................... 31
5.1.7 Format conversion ............................................................................... 31
5.2 Data conversion................................................................................... 32
6 Commissioning .................................................................................. 36
7 Technical data .................................................................................... 36
8 Software and firmware versions ....................................................... 36

2 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies Table of Contents 2017-04-24
0 Before you start
0.1 Revision history

Version Date Document No. Change Chapter Page(s)


V6.1 2017-04 CA2Y9772en_06 · Corrections and general rework of the all all
document
V5.10 2014-06 CA2Y9772en_05 · Replacement of PXC00… with PXC001… all all
4.0 2009-01 CA2Y9772en_04 · Universal example for Modbus master 2.2.1 9
· Time Gap for Modbus Slave only 4.2 22
V2.37 2007-03 CA2Y9772en_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

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] PXC001 system controller, data sheet CM1N9223
[5] Modbus Application Protocol Specification V1.1b3
[6] Modbus Application Protocol Specification V1.1b

3 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies Table of Contents 2017-04-24
1 Introduction
1.1 Positioning

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 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].

4 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
1.2 Requirements and limitations

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.

5 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
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 Chapter
5.2 "Data conversion"):

M = MappingInfo1(MappingInfo2.MappingInfo3.MappingInfo4.MappingInfo5.MappingInfo6[DataType])/Free syntax

Element Meaning Range Description


MappingInfo1 Slave address 1 .. 247 Modbus slave address

+1000 An offset of +1000 added to a slave


address indicates that the data point
Broadcast is a feedback value.
0 Important: Broadcast is applicable
only for write commands.
MappingInfo2 Function code (FC) 1,2,3,4,5,6, Function code with which the data
15,16 point has to be transmitted.
MappingInfo3 --- 0 ---
MappingInfo4 Register address 0 .. 65535 Register address = Register number -
1. For values transmitted in two or
four registers (32 or 64 bit), the lowest
register address must be entered
here.
MappingInfo5 BitPos 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…40 characters Free syntax is used as control
element for special functions.

Example of two I/O-blocks with an associated "IOAddr" pin in CFC chart

6 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
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:

7 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
Universal example for Modbus master

Modbus view

I/O-blocks in CFC Editor


Modbus memory range
vs. CFC view

Description of the
Register address
(MappingInfo1)

(MappingInfo4)

(MappingInfo2)

function code
Slave address

Function code

Application
XXX YYYY 1 0X Read Coil Status BI Read multiple BI
XXX YYYY 2 1X Read Input Status BI Read multiple BI
XXX YYYY 3 4X Read Holding Register AI Read multiple AI
XXX YYYY 4 3X Read Input Register AI Read multiple AI
XXX YYYY 5 0X Force Single Coil BO Write single BO
XXX YYYY 6 4X Preset Single Register AO Write single AO
XXX YYYY 15 0X Force Multiple Coils BO Write multiple BO
XXX YYYY 16 4X Preset Multiple Registers AO Write multiple AO

For the IOAddr of function blocks, the following "mapping strings" must be added:

Function Application "Mapping strings" for the IOAddr


code of the CFC function blocks

1 Read multiple BI M = ...


(Modbus Coil Status) M = ....
M = XXX(1.0.YYYY.0.0...

2 Read multiple BI M = ...


(Modbus Input Status) M = ....
M = XXX(2.0.YYYY.0.0...
3 Read multiple AI M = ...
(Modbus Holding Registers) M = ....
M = XXX(3.0.YYYY. 0.0...
Read multiple BI from a Holding M = ...
Register M = ...
M = XXX(3.0.YYYY. BitPos.0...
4 Read multiple AI M = ...
(Modbus Input Register) M = ....
M = XXX(4.0.YYYY. 0.0...
Read multiple BI from Input M = ...
Registers M = ...
M = XXX(4.0.YYYY. BitPos.0...
5 Write single BO M = XXX(5.0.YYYY.0.0...
(Force Single Coil)

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


(Preset Single Register)

Write multiple BO to a Register M = ...


M = ...
M = XXX(6.0.YYYY. BitPos.0...

8 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
15 Write multiple BO M = ...
(Force Multiple Coils) M = ....
M = XXX(15.0.YYYY.0.0...

16 Write multiple AO M = ...


(Preset Multiple Registers) M = ....
M = XXX(16.0.YYYY. 0.0...

Write multiple BO M = ...


to a Register M = ....
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 Chapter 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.

9 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
2.2 Setting parameters

In the PX Open Modbus solution, the communication 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 only once in every CFC program
(application) of a system controller.
Communication

Recommended
Variable Name

Variable Type

Description

Master
Slave
(COMBLK)

Data Type
Block

Baud VAR_INPUT UINT32 Baud rate on Modbus


300 / 600 / 1200 / 2400 / 4800 / 9600 / 9600 X X
19200 / 38400 / 57600 / 115200
StpBit VAR_INPUT UINT16 Number of stop bits on the Modbus
1 X X
1/2
Parity VAR_INPUT MULTI Parity on the Modbus
None X X
None / Even / Odd
CharLngt VAR_INPUT UINT16 Number of data bits per character on
Modbus 8 X X
7/ 8
RegNr VAR_INPUT UINT32 License number for the
1) 0 X X
Modbus solution
CharTio VAR_INPUT FLOAT Character timeout [ms]
Maximum time between two characters 50 X X
on the Modbus
FrmTio VAR_INPUT FLOAT Frame timeout [ms]
Maximum time for the transmission of a 500 X X
Modbus telegram
ScanDly VAR_INPUT FLOAT Polling time (Modbus Master) [ms]
Interval between two queries 100 X O
50…5000
ComInfo1 VAR_INPUT FLOAT --- – – –
ComInfo2 VAR_INPUT FLOAT --- – – –
ComInfo3 VAR_INPUT FLOAT Device Address (Modbus slave)
Modbus slave address – O X
1...247
ComInfo4 VAR_INPUT FLOAT --- – – –
ComInfo5 VAR_INPUT FLOAT --- – – –
IOAddr VAR_INPUT STRING Refers here only to the COMBLK and is
M=1(1) X X
used to define the internal mapping table
Rlb etc. VAR_OUTPUT Alarm handling for the entire block – X X
– = Reserved for other third-party solutions

10 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
Note!
Message Block 1) Licensing as per defined in the Release Notes.

Recommended
(see also DTS
Variable type

description)
Description
(MSGBLK)

Variable
Name

Data
type
InsDate VAR_INPUT ASCII Entry of engineering date 0
RstSsys VAR_INPUT BOOL Reset PX Open subsystem 0
MsgStppr VAR_INPUT UINT16 Message Stepper 0
ResetMsg VAR_INPUT BOOL Reset Messages 0
ToolMod VAR_INPUT BOOL Tool Mode 0
MsgLvl VAR_INPUT UINT16 Message Level 0
LogfLvl 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 –
SfwSta VAR_OUTPUT UINT16 SW State –
NumEr VAR_OUTPUT UINT16 Error Counter –
Counter for program errors
ComEr VAR_OUTPUT UINT16 Cfail Counter –
Counter for communication errors
AddMsg2 VAR_OUTPUT FLOAT Mes. Additional 2 –
AddMsg1 VAR_OUTPUT FLOAT Mes. Additional 1 –
License VAR_OUTPUT BOOL License Ok 1) –
TRUE = Identifies licensing as OK.
Res1 VAR_OUTPUT UINT16 License level –
Res2 VAR_OUTPUT UINT16 Number of active data points –
Res3 VAR_OUTPUT SINT16 Number of data points still available –
in the license range
(negative if higher than license)
ErCksum VAR_OUTPUT UINT16 Checksum Error Counter –
IOAddr VAR_INPUT STRING Refers here only to the MSGBLK M=1(1)
and is used to define the internal
mapping table
Rlb usw. Alarm handling for the entire block –
– = Reserved for other third-party solutions

Encoding SwStatus The Pin SwStatus of the MSGBLK shows more detailed and more reliable
information 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

11 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
The whole startup and initialization sequence can last up to 1 minute. Once the
startup has completed and during normal operation, the PX Open Modbus should
be in state 13. This indicates that the PX Open Modbus is polling the Modbus
devices.

12 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
3 Application functionality
3.1 Overview

· The PX Open Modbus solution integrates data points from Modbus devices to
the Desigo system.
· The values of the Modbus data points and the status of the existing data
connection 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 PXC001.

Technical information Maximum number of Modbus Up to 3000 à depending on license


data points:
Address range Modbus slaves: 1 … 247
Electrical interface: RS232 (peer-to-peer) /
RS 485 (multi-drop) à electrically isolated
No Bus Termination equipped.
Baud rate: 300, 600, 1200, 2400, 4800, 9600, 19200,
38400, 57600, 115200 baud

Serial transmission RTU mode or ASCII mode


modes

Supported Function Function Modbus function Application


codes code
01 Read Coil Status Read multiple BOs
02 Read Input Status Read multiple BIs
03 Read Holding Registers Read multiple AOs
04 Read Input Registers Read multiple AIs
05 Force Single Coil Write single BO
06 Preset Single Register Write single AO
15 Force Multiple Coils Write multiple BOs
16 Preset Multiple Registers Write multiple AOs

13 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
3.2 Communication
3.2.1 Protocol definition

The following section provides only a brief overview of the Modbus protocol.
For the full specification, refer to Modicon Modbus Protocol Reference Guide [1],
[5], [6].

Master/slave protocol The Modbus is a master/slave protocol. By definition, this means that a Modbus
network contains 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 (read / write)
· 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 mode (Remote Terminal Unit)
· 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
· Start 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 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
3.2.2 Polling mechanism

The Modbus master reads the data points from the slaves at regular intervals.
Read function codes are 01, 02, 03 or 04.
The Modbus master writes the data points at startup, change of value (COV) and
periodically repeated (R-Functions à see Chapter 5.1.6). Write function codes are
05, 06, 15 or 16.
If a slave fails to respond, the master waits after each query for the parameterized
response timeout time to elapse. This causes a delay in the data exchange.
The following two failure cases are described:

A) Slave fails to · Telegram is repeated 3x or configurable via Diagnostics Point 97 à see Chapter
respond to query from 4.2.
master · If the slave still fails to respond, any pending queries (read or write) for this slave
are skipped until all the pending queries for the other slaves have been
processed once.

B) Slave responds to a · Telegram is repeated 3x or configurable via Diagnostics Point 97 à see Chapter
query by sending an 4.2.
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 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
3.2.3 Updating mechanism

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.
If a Modbus slave remains disconnected for 20 seconds (default), when the
connection will be reestablished, all the output values will be rewritten.
This disconnection timeout can be set with the Diagnostics Point D=59 (see
Chapter 4.2)

3.2.4 Multiple data points in a telegram

Modbus master Function Code 01, 02, 03 and 04 are used to read multiple data points from the
Modbus slaves. Function Code 15 and 16 are used to write multiple data points to
the Modbus slave. This collection of multiple data points will be done automatically
in a telegram.
Important! Only the data points with addresses in continuous ascending order are collected
automatically in a telegram.

Modbus slave The number of data points in a telegram is defined by the master request.
The PX Open Modbus slave returns an exception message if it cannot resolve all
the data points of a query.

Error behavior If the Modbus master asks a slave for a data point which does not exist, the master
stops sending collected data points in a telegram, which means the Modbus
master changes to one data point per telegram. Be aware that one data point may
consist of multiple registers, according to the chosen data type (e.g. UINT32 à 2
register). Periodically, the master retries to send collected data points in a
telegram.
The maximum number of register in one telegram can be set with the Diagnostics
Point D=56 and the maximum number of bits (Coils or Inputs) can be set with the
Diagnostics Point D=57 à see Chapter 4.2.

Modbus slave 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.

16 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
3.2.5 BACnet Reliability

The status of the Modbus data points is mapped to the Rlb (Reliability) pin.
Reliability value Meaning in Modbus Master Meaning in Modbus Slave
0 / NO_FAULT_DETECTED No error has been found in the No error has been found in the connection to
connection to the slave. the master à It is possible, that the master
has never polled this data point.
2 / OVER_RANGE Value of the Modbus data point is Value of the Modbus data point is higher
higher than the defined value than the defined value range.
range.
3 / UNDER_RANGE Value of the Modbus data point is Value of the Modbus data point is lower than
lower than the defined value the defined value range.
range.
8 / PROCESS_ERROR The slave is responding with an Not applicable in slave mode.
exception code.
10 / Invalid data type configured for Invalid data type configured for data point.
CONFIGURATION_ERROR data point.
68 / INVALID_ADDR Syntax error in address string. Syntax error in address string.
70 / INVALID_PARAM Syntax error in address string Syntax error in address string parameter à
parameter. Only occurs with certain errors when the
master polls the data point.
80 / UNRELIABLE_OBJECT No connection possible. Not applicable in slave mode.
84 / Number of licensed data points Number of licensed data points has been
MEMORY_LIMIT_REACHE has been exceeded. exceeded.
D

In the event of an error, more information can be obtained by use of the PX Open
Monitor Tool (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 avoid this behavior, the Reliability can be suppressed. The "free syntax" in the
I/O Address 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, that the
slave failure can be seen.

17 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
3.2.6 Communications monitoring

For the communications monitoring and status information, there is the PX Open
Monitor [3].
The main screen displays the following information:
1. Version information of the PX Open application
2. Communication block information
3. Message block information
4. Log File information
5. Connection status

Note All the screenshots illustrated here contain simulated information.

18 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
The Protocol Analyzer window provides the following information:
1. Raw data from the communication between PX Open and the third-party
automation and control system.
2. The formatted data according to the Description File.

19 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
4 Project engineering
4.1 I/O address

The I/O Address pin of the I/O block contains information which defines
· how to address a data point
· which function code to use
· which format conversion is required

The structure of the parameter I/O Address is defined as follows:

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 Slave address 1 .. 247 Modbus slave address
MASTER
mode +1000 An offset of +1000 added to a slave
address indicates that the data point is a
feedback value.

Broadcast 0 Important: Broadcast is applicable only


for write commands.
Important! MappingInfo1 --- 0 NO slave address!
SLAVE mode Slave address is set in COMBLK/Info3.
MappingInfo2 Function code (FC) 1,2,3,4,5,6, Function code with which the data point
15,16 has to be transmitted.
MappingInfo3 --- 0 ---
MappingInfo4 Register address 0 .. 65535 Register address = Register number - 1.
For values transmitted in two or four
registers (32 or 64 bit), the lowest register
address must be entered here.
MappingInfo5 BitPos 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…40 Free syntax used as control element for
characters special functions.

20 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
4.1.2 Mapping information

MappingInfo1 Operation as Modbus master:


In "Master" mode, MappingInfo1 contains the Modbus slave address.

Operation as Modbus slave:


Important! In Modbus slave mode, MappingInfo1 must always be set to 0.
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.
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 MappingInfo4 contains the Register address (= Register number – 1) à The same
is valid for Bit Registers.
For values transmitted in two or four registers (32 or 64 bit), the lowest register
address must be entered here.

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
Chapter 5.1.2).
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.
If a value of 0 is defined, no data conversion will take place.

21 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
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 FLOAT
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.
A (binary) value to be sent on the Modbus will be converted into 16 Bit BCD
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.
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: 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.
A (binary) value to be sent on the Modbus will be converted into 16 Bit BCD
code
B: The first byte in the telegram is the least significant.
Example: MB Byte1 MB Byte2 MB Byte3 MB Byte4
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 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
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
Example: MB Byte1 MB Byte2 MB Byte3 MB Byte4
Hex: 0xFB Hex: 0x2E Hex: 0xE9 Hex: 0xD2
-1234 -5678
Value = (-1234 * 10000) + -5678 = -12345678
9 SwapBytes The 4 Byte of the two 16 bit registers are swapped (Swap Register and Swap UINT16, SINT16,
bytes in Register) before transmission to the Modbus and after receipt from the UINT32, SINT32,
Modbus FLOAT
Example: MB Byte1 MB Byte2 MB Byte3 MB Byte4
Hex: 0x7D Hex: 0x14 Hex: 0x48 Hex: 0x42
Value = 50.02

4.2 Special 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 settings.
It is not compulsory for the following I/O 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 only
take effect after a 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 CharTio + 5ms (*) Default FALSE
1)
Range 15..65535 (*) Range FALSE / TRUE
(*) The values defined in the Modbus specification will not be achieved. 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.

1) TimeGap cannot be set <= CharTio + 5ms

Name Slave Mode Name RegAmt


I/O Block Type BO I/O Block Type AO
Mapping Info D=54 Mapping Info D=56
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 FALSE / TRUE Range 1..125

23 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
Name BitAmt Name DiscTim
I/O Block Type AO I/O Block Type AO
Mapping Info D=57 Mapping Info D=59
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..2000 Range 5 ..120
Name Suppress Error on Busy Name Error Repetitions
I/O Block Type BO I/O Block Type AO
Mapping Info D=86 Mapping Info D=97
Meaning If Slave sends respond with exception Meaning The max. number of repetitions if no
code 06 (Busy) then the Reliability Error answer or exception code.
can be suppressed:
TRUE: suppressed
FALSE: Not suppressed
Eng. unit --- Eng. unit ---
Default FALSE Default 2
2)
Range FALSE Range -1
2)
TRUE 1..1000
2) No repetition

Name Error Delay Name Intercept


I/O Block Type AO I/O Block Type AO
Mapping Info D=99 Mapping Info D=105
Meaning The max. number of Poll Cycles till an Meaning General adjustable Intercept for AI / AO
Error is reported
Eng. unit --- Eng. unit ---
Default 2 Default 0
3)
Range -1 Range -3.403E38..3.403E38
1..1000
3) No error delay à disabled

4)
Name Offset Name Slope
I/O Block Type AO I/O Block Type AO
Mapping Info D=109 Mapping Info D=115
Meaning General adjustable Offset for MI / MO Meaning General adjustable Slope for AI / AO
Eng. unit --- Eng. unit ---
Default 0 Default 0
Range Integer Range -3.403E38..3.403E38
4) Individual adjustable offset for MI/MO see Chapter 5.1.4

24 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
5 Protocol details
5.1 Protocol Extension

In some slave devices, the Modbus protocol is not fully implemented. Not all the
function codes are supported or there is a restriction about the maximum number
of registers in one telegram.
In order to ensure the efficient integration of these devices, the PX Open Modbus
solution provides the following functions.

5.1.1 Force single telegram

Some slave 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

5.1.2 BitPos function

The Modbus protocol only allows single bits to be read/write with Function Codes
01 (Read Coil Status), 05 (Force Single Coil) and 15 (Force Multiple Coils).
However, some slave devices do not support these function codes.
The Bit information of a 16 bit register can be read/written over the function codes
03 (Read Holding Registers), 04 (Read Input Registers), 06 (Preset Single
Register) and 16 (Preset Multiple Registers).
Example Following an example of the I/O block types "Binary Input" reading bits from Input
Register 1 of slave address1:
Binary Input 1 à M=1(4.0.1.16.0[BOOL])
Binary Input 2 à M=1(4.0.1.15.0[BOOL])
Binary Input 3 à M=1(4.0.1.7.0[BOOL])
Binary Input 4 à M=1(4.0.1.4.0[BOOL])

Example of a Modbus register 1 linked with Function Code 04 (Read Input Register)

25 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
Following an example of the I/O block types "Binary Output" writing bits to Output
Register 1 of slave address1:

Binary Output 1 à M=1(6.0.1.16.0[BOOL])


Binary Output 2 à M=1(6.0.1.15.0[BOOL])
Binary Output 3 à M=1(6.0.1.7.0[BOOL])
Binary Output 4 à M=1(6.0.1.4.0[BOOL])

Example of a Modbus register 1 linked with Function Code 06 (Force Single Register)

Note Following rules has to be considered when using BitPos:


1. Same Function code for bit access in the same register:
M=1(6.0.1.16.0[BOOL])
M=1(16.0.1.15.0[BOOL]) à Wrong, must be as shown in example
M=1(6.0.1.7.0[BOOL])
M=1(6.0.1.4.0[BOOL])
2. Data type in mapping must be BOOL

5.1.3 Feedback function

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.

26 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
Example Modbus master with a data point which contains a value.
This value is to be written to the slave.
A) 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

B) The new value is transmitted to the slave via the Modbus.


01584en

Analog Output Value of 200 is


transmitted to
MODBUS
PgmVal: 200 PrVal: 200

Analog Intput (Feedback)

PrVal: 100

C) The receipt of the value is acknowledged by the slave as "Received".


PresentValue is then updated in FeedbackValue.
01585

Analog Output

Response: Ok
PgmVal: 200 PrVal: 200

Analog Intput (Feedback)

PrVal: 200

Feedback-addressing The Feedback address FbAddr has an offset of 1000 relative to IOAddr:
for the above example

27 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
STOP Exception! In the block "Binary Output" the Feedback address has the data type UINT16
instead of BOOL:

Direct feedback The free syntax / R1 convert the UINT16 to a BACnet conform BOOLEAN.
from a BO
Example of the above direct feedback address:
M=1001(5.0.0.0.0[UINT16])/R1

5.1.4 Adjustable Offset for MI/MO

The adjustable offset for MI/MO can be set over the following individual or general
settings:

Individual settings (Overrides general settings):

M=X(Y.Y.Y.Y.Y[TYPE])/M=Offset

Valid Range for Offset is integer.

General settings:

Set by Diagnostic point D=109 (More details à see Chapter 4.2.

28 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
5.1.5 Multi Register Values (>=32Bit)

The Modbus protocol defines the 16-bit register as the largest data unit. Multi
Register Values >= 32 bit values must therefore be transmitted in two or more
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.

The following table contains the information about how to configure this 64-Bit
function in the free syntax of the mapping points in the CFC editor:

Data type on Modbus Number of CFC mapping


Slave device registers
48Bit unsigned integer 3 1(3.0.2.0.0[UINT16])/x3
1(16.0.2.0.0[UINT16])/x3
or
1(3.0.2.0.0[UINT32])/x1.5
1(16.0.2.0.0[UINT32])/x1.5
48Bit signed integer 3 1(3.0.10.0.0[SINT16])/x3
1(16.0.10.0.0[SINT16])/x3
or
1(3.0.10.0.0[SINT32])/x1.5
1(16.0.10.0.0[SINT32])/x1.5
64Bit unsigned integer 4 1(3.0.2.0.0[UINT16])/x4
1(16.0.2.0.0[UINT16])/x4
or
1(3.0.2.0.0[UINT32])/x2
1(16.0.2.0.0[UINT32])/x2
64Bit signed integer 4 1(3.0.10.0.0[SINT16])/x4
1(16.0.10.0.0[SINT16])/x4
or
1(3.0.10.0.0[SINT32])/x2
1(16.0.10.0.0[SINT32])/x2
Double Float (64Bit) 4 1(3.0.10.0.0[FLOAT])/x2
1(16.0.10.0.0[FLOAT])/x2
half precision Float (16Bit) 1 1(3.0.10.0.0[FLOAT])/x0.5
1(16.0.10.0.0[FLOAT])/x0.5

STOP Exception! For Float, only /x2 and /x0.5 are supported.

29 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
To verify the correct point setting you have to type in the command shell of the
Firmware Download tool the following command PxOpen/IOList:

The following conversion functions are supported for values >32Bit:


- Swap Register à conversion function =1
- Swap Register and Swap bytes in Register à conversion function=9
- MOD10K à conversion function =7 or 8

30 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
5.1.6 Periodic writing

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 examples:

Write Analog Output every hour:


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

New Function:
STOP Important! The writing interval must be defined in the output points in pin Hrtbt à This function
. will be supported from FW version V6.00.116.

For new solutions please do only use the periodic writing over the Hrtbt function in
the output points.

5.1.7 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.

31 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
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).

The direction of data flow determines which combinations are possible. This
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.

32 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
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.

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
Conv.
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 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
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
04 Read Input
6 ACM16 01 Read Coil
02 Read Input
03 Read Holding
04 Read Input
7 01 Read Coil
32BITMOD10000 02 Read Input
03 Read Holding
04 Read Input
8 01 Read Coil
S32BITMOD1000 02 Read Input
0 03 Read Holding
04 Read Input
9 Swap Bytes 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
BitPos 03 Read Holding
04 Read Input

MappingInfo5

33 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
Permissible combinations for output block types with Modbus operating as
Master:
Mapping Info BOOL SINT16 UINT16 SINT32 UINT32 FLOAT
DataType (2 Registers) (2 Registers) (2 Registers)

Mapping Info6
Conv. 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
9 Swap Bytes 16 Preset M.Reg 16 Preset M.Reg 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 Info BOOL SINT16 UINT16 SINT32 UINT32 FLOAT
DataType (2 Registers) (2 Registers) (2 Registers)

MappingInfo6
Conv. 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
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
6 ACM16 16 Preset M.Reg
7 U32BITMOD10000 16 Preset M.Reg
8 S32BITMOD10000 16 Preset M.Reg
9 Swap Bytes 16 Preset M.Reg 16 Preset M.Reg 16 Preset M.Reg
Do not use with Do not use with
Float Float
BitPos 06 Preset
S.Reg
16 Preset
M.Reg

MappingInfo5

34 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
Permissible combinations for output block types with Modbus operating as slave

Mapping Info BOOL SINT16 UINT16 SINT32 UINT32 FLOAT


DataType (2 Registers) (2 Registers) (2 Registers)

MappingInfo6
Conv. 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
9 Swap Bytes 03 Read 03 Read 03 Read
Holding Holding Holding
04 Read Input 04 Read Input 04 Read Input
BitPos

MappingInfo5

35 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
6 Commissioning
The commissioning procedure involves simply downloading the firmware.
See also Data sheet PX Open System controller PXC001 [4]

7 Technical data
For technical data, refer to the following documents:
· PX Open System controller PXC001, data sheet [4]
· PX Modbus solution, data sheet [2]

8 Software and firmware versions


Refer to the Release Notes.

36 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24
Index

Alarm Longitudinal Redundancy Check ........................ 14


suppression ..................................................... 17 Mapping information ........................................... 21
Applications ........................................................ 13 Mapping strings .................................................... 8
ASCII mode .................................................. 13, 14 Message Block MSGBLK ................................... 10
BitPos function.............................................. 21, 25 Modbus
Bus failure .......................................................... 17 functions ......................................................... 13
CFC view .............................................................. 8 master............................................................4, 5
Checking ...................................................... 14, 32 protocol ...................................................... 14, 25
Communication settings ........................................................... 23
monitoring ....................................................... 18 slave ..............................................................4, 5
Communication Block COMBLK.......................... 10 view .................................................................. 8
Cyclic Redundancy Check CRC .......................... 14 Modbus master polling........................................ 15
Data conversion .................................................. 32 Polling ................................................................ 15
Desigo PX Open Monitor ...................................... 4 Project engineering............................................... 6
Discipline I/Os..................................................... 10 PXC001.............................................................. 13
Engineering errors .............................................. 16 PXC001 system controller .................................... 4
Errors ................................................................. 16 Redundancy Check ............................................ 14
Feedback address FbAddr .................................. 27 Reliability Rlb ..................................................... 15
Feedback function............................................... 26 Requirements ....................................................... 5
FLOAT values ..................................................... 32 RTU (Remote Terminal Unit) mode ............ 5, 13, 14
Format conversion .............................................. 31 Serial transmission modes .................................. 14
Function codes ............................................. 13, 14 Third-party Modbus master ................................... 4
Hardware platform .............................................. 13 Topology............................................................... 4
I/O address ......................................................... 20 Transmission
I/OAddress............................................................ 6 32-bit values ................................................... 29
Integration ............................................................ 4 Updating output values ....................................... 16
limitations ............................................................. 5

37/38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies Index 2017-04-24
Siemens Switzerland Ltd
Building Technologies Division
International Headquarters
Gubelstrasse 22
6301 Zug
Switzerland
Tel. +41 41-724 24 24 © Siemens Switzerland Ltd, 2002-2017
www.sbt.siemens.com Subject to change

38 / 38

Siemens Desigo PX Open Modbus CA2Y9772en_06


Building Technologies 2017-04-24

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy