User Manual
Table Of Contents
- 1 Cyber security disclaimer
- 2 Preconditions of this document
- 3 System overview
- 4 Desigo workflow, tools and programming
- 4.1 Coverage of the technical process
- 4.2 Coverage of the system
- 4.3 Main tasks
- 4.4 Tools for different roles
- 4.5 Working with libraries
- 4.6 Working in parallel and subcontracting
- 4.7 Workflow for primary systems
- 4.8 Workflow for room automation classic
- 4.9 Workflow for Desigo room automation
- 4.10 Desigo Configuration Module (DCM)
- 4.11 Desigo Xworks Plus (XWP)
- 4.12 Desigo Automation Building Tool (ABT)
- 4.13 Programming in D-MAP
- 5 Control concept
- 6 Technical view
- 7 Global objects and functions
- 8 Events and COV reporting
- 9 Alarm management
- 9.1 Alarm sources
- 9.2 Alarm example
- 9.3 Effects of BACnet properties on alarm response
- 9.4 Alarm response of the function blocks
- 9.5 Alarm functions
- 9.6 Alarm management by notification class
- 9.7 Alarm routing over the network
- 9.8 Alarm queuing
- 9.9 Common alarms
- 9.10 Alarm suppression
- 9.11 Alarm message texts
- 10 Calendars and schedulers
- 11 Trending
- 12 Reports
- 13 Data storage
- 14 Network architecture
- 15 Remote access
- 16 Management platform
- 17 Desigo Control Point
- 18 Automation stations
- 19 Logical I/O blocks
- 20 Room automation
- 21 Desigo Open
- 22 System configuration
- 22.1 Technical limits and limit values
- 22.2 Maximum number of elements in a network area
- 22.3 Desigo room automation system function group limits
- 22.4 Devices
- 22.4.1 PXC..D automation stations / system controllers
- 22.4.2 LonWorks system controllers
- 22.4.3 Automation stations with LonWorks integration
- 22.4.4 PX Open integration (PXC001.D/-E.D)
- 22.4.5 PX Open integration (PXC001.D/-E.D + PXA40-RS1)
- 22.4.6 PX Open integration (PXC001.D/-E.D + PXA40-RS2)
- 22.4.7 PX KNX integration (PXC001.D/-E.D)
- 22.4.8 TX Open integration (TXI1/2/2-S.OPEN)
- 22.4.9 Number of data points on Desigo room automation stations
- 22.4.10 Number of data points for PXC3
- 22.4.11 Number of data points for DXR1
- 22.4.12 Number of data points for DXR2
- 22.4.13 PXM20 operator unit
- 22.4.14 PXM10 operator unit
- 22.4.15 Desigo Control Point
- 22.4.16 PXG3.L and PXG3.M BACnet routers
- 22.4.17 SX OPC
- 22.4.18 Desigo CC
- 22.4.19 Desigo Insight
- 22.4.20 Desigo Xworks Plus (XWP)
- 22.4.21 Desigo Automation Building Tool (ABT)
- 22.5 Applications
- 23 Compatibility
- 23.1 Desigo version compatibility definition
- 23.2 Desigo system compatibility basics
- 23.2.1 Compatibility with BACnet standard
- 23.2.2 Compatibility with operating systems
- 23.2.3 Compatibility with SQL servers
- 23.2.4 Compatibility with Microsoft Office
- 23.2.5 Compatibility with web browsers
- 23.2.6 Compatibility with ABT Go
- 23.2.7 Compatibility with VMware (virtual infrastructure)
- 23.2.8 Compatibility of software/libraries on the same PC
- 23.2.9 Hardware and firmware compatibility
- 23.2.10 Backward compatibility
- 23.2.11 Engineering compatibility
- 23.2.12 Compatibility with Desigo Configuration Module (DCM)
- 23.2.13 Compatibility with Desigo PX / Desigo room automation
- 23.2.14 Compatibility with Desigo RX tool
- 23.2.15 Compatibility with TX-I/O
- 23.2.16 Compatibility with TX Open
- 23.3 Desigo Control Point
- 23.4 Upgrading from Desigo V6.2 Update (or Update 2) to V6.2 Update 3
- 23.5 Siemens WEoF clients
- 23.6 Migration compatibility
- 23.7 Hardware requirements of Desigo software products
- 24 Desigo PXC4 and PXC5
- 25 Compatibility of Desigo V6.2 Update 3 with PXC4 and PXC5
Control concept
Superposed plant controls
5
74 | 351 CM110664en_07
The operating state [OpSta] for both aggregates are formed within the compounds as illustrated in the
previous example from the AND link for [PrVal] and [TraSta].
5.3 Superposed plant controls
Two blocks are available in Desigo for superposed plant control:
● CMD_CTL command control for sequence control
● PWR_CTL power control for stepped control
Both blocks are based on the standard BACnet Command Object. They have both tables that define the
operating modes and switching response of the underlying aggregates. The commandable blocks in the
aggregates must have a BACnet [PrioArr] to use the following output and value blocks: AO, BO, MO, AVAL,
BVAL und MVAL.
PWR_CTL may only be communicated using the MVAL blocks based on the specialized task – controlling
steps.
Referencing
Referencing is used exclusively for communications by the superposed control blocks with the output and
value blocks in the aggregates to be commanded. The references are derived from the Technical
Designation (TD) of the block. The reference is defined relative to the control block to the command block.
The aggregate does not have to be in the same hierarchy; cross-plant communications is possible.
Example for a reference: B = \...\...\PreHcl’CmdVal
Where CmdVal is the designation for a BVAL object in the PreHcl aggregate. More than one block can be
referenced for each aggregate.
As the project-specific root is not part of the address, the references do not need to be modified if the root
changes. This simplifies project-specific name changes and the copying of library solutions into a project.
The references, that is, the technical designations with relative addresses are resolved in the controller at
runtime. Any addressing errors will therefore only be apparent during runtime. The cause of the error can
largely be eliminated, however, when parameterizing the controls blocks with the help of the Plant Control
Editors.
The figure shows that the [PrioArr] can communicate directly with the referenced blocks. You can
command switch and positioning values and enable them. A commanded command remains valid until the
priority entry is enabled again. The control blocks automatically enables all commanded priorities, when the
block commands the aggregates to the new plant operating mode. The entries for the [PrioArr] are deleted
in the commanded blocks when restarting the PX controller, with the exception of local, manual
interventions to priority 8.
Determining plant operating mode
A superposed plant control generally has different sources such as plant switch, scheduler program or
important fault messages, from which the resulting plant operating mode must be determined.
The ENSEL_MS (Enable Selector Multistate) and ENSEL_BO (Enable Selector Boolean) blocks are
available for evaluating the resulting plant operating mode in the firmware library of Desigo. As a rule, the
BACn
e
t
R
e
f
e
r
e
n
c
e
DmpShofOa
Ag: DmpShof
FanSu
Ag: Fan1St
Open
V
a
l
C
r
i
t
E
n
C
r
i
t
O
p
S
t
a
E
n
C
r
i
t
V
a
l
C
r
i
t
O
p
S
t
a