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
CM110664en_07 85 | 351
The upper part of the dialog box serves primarily to provide a quick online overview of the block. The
maximum power controlled by the block is set with the maximum power parameter [MaxPwr]. The value
must be greater than 0 kW in order for the block to work. Any changes in this limit value have a direct effect
in online mode. If no limit value is required, the maximum power must be set at an appropriately high value.
The Aggregates tab is used to set the control variables of the aggregates (boiler, refrigeration machine).
● Enable: Activation/deactivation of an entry if they are not released, aggregates in the Profile table will
be ignored.
● Command object reference: Reference (relative addressing) to multistate value blocks [MVAL] of the
relevant energy producer. During the configuration process, all MVAL blocks at the same and at lower
hierarchical levels are displayed.
● Aggregate description: The reference to the value object provides access to (and hence, knowledge of)
all information in a special dialog box via the referenced object in the control command.
● Switch-on delay: Delay time when switching from OFF to Stage 1.
● Switch-off delay: Delay time when switching from Stage n to OFF.
● Step-up delay: Delay time when switching from Stage n up to Stage n+1.
● Step-down delay: Delay time when switching down from Stage n to Stage n–1.
● Switch-on stage power: Power in [kW] at the lowest (that is, first) stage.
● Next power stage: Additional power at the next stage(s) in [kW].
The control sequences for the aggregates (boiler, refrigeration machine) are defined under the Aggregates
tab. Each profile describes the order in which the energy producers are to be switched and the maximum
stage in each case. A total of 8 profiles each with 15 sequence entries can be defined.
The active profile table is defined by entering the profile number [PrfNr] as an input parameter, or by
selecting it from the Profile dropdown list in the Plant Control Editor. This input parameter can be
interconnected, so that the profile can be changed as a function of other events (faults, summer mode,
boiler operating hours, etc.). If the profile is changed during operation, the power output [PrPwr] is
switched in accordance with the power profile in the new profile table.
The profile definition determines the order in which individual aggregates are to be switched on or off. The
following information must be entered for every sequence entry:
● Object: Selected from the previously referenced aggregates.
● Stage limitation: Limit up to which the aggregate may be enabled.
● Control type: Specifies whether the enabled stages are to be switched permanently or released to the
control system.
– Fixed: The total power provided by a given switch stage is switched on or off permanently. This
option can be used, e.g., for a specific base load which is required to be present at all times. The
command is implemented with Priority 14.
– Enable: The power actually required from the released switch stage is determined by local control of
the aggregates. The command is implemented with Priority 16.
For each sequence step, the function block only ever releases the last aggregate marked Release to the
control system. It displays this released object [RlsObj], with the released object stage [RlsObjSt], at the
output. All other aggregates are fixed at the released stage value. If none of the aggregates is marked
Release, the aggregate of the current sequence step is released to the control system.