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 83 | 351
A process alarm occurs, when:
● One of the monitored aggregates is not switched on.
● One of the referenced aggregates cannot be switched on.
The exception value [EcptVal] becomes the present plant operating mode as a reaction to a process alarm.
In addition, an alarm is sent.
A system alarm occurs for the following configuration efforts:
● A referenced aggregate is not available.
● A referenced aggregate is not a commandable object.
● Impermissible priorities are used (priorities 2, 5, 14, 16 are allowed).
● [ValPgm] or [EcptVal] are outside the permissible range.
● The referenced aggregates have a different number of operating modes.
The command control attempts for a system alarm to enable all referenced blocks for local control. The
four commandable priorities are commanded – in other words enabled to Not commanded: Life safety (2),
plant safety (4), specific command control (14) and system control (16).
The response of the block to an alarm can be defined. The following mechanisms have been incorporated
to prevent hunting in the plant.
● Basic and standard: When the block goes into alarm, the exception value [EcptVal] is switched. When
all the aggregates are ready for switching again, CMD_CTL automatically tries to implement the present
plant operating mode [PrVal]. If all the aggregates are ready for direct switching immediately after
implementation of the exception value [EcptVal], hunting is likely to occur. In this case, CMD_CTL
prevents any further switch-on attempt, and the required plant operating mode [PrVal] must be
changed.
● Extended: When the block goes into alarm, the exception value [EcptVal] is switched. The alarm has to
be reset by the user, and there is therefore no risk of hunting.
The block is not alarmable for Desigo 7.
Out of service
The block can be taken out of commissioning using [OoServ]. The following occurs when switching
[OoServ] to On:
● Immediately abort of switch on and off sequences and monitoring.
● All objects are commanded with a release of the priorities: Life safety (2), plant safety (4), specific
command control (14) and system control (16)
Superposed power control PWR_CTL
The power control function block PWR_CTL is used for control and monitoring of the performance of a
number of energy producers (multiple boiler systems, refrigeration machines, etc.). As is the case for
command control CMD_CTL, the data is exchanged bilaterally between power control and the individual
energy producers (boiler, refrigeration aggregate, among others), via referencing. Since the energy
producers are generally implemented in the form of logical aggregates, and contain local logic, the
PWR_CTR block communicates only with MVAL blocks.
The control strategy is based on the use of tables and is designed for multi-stage energy producers.
Additional energy-producer stages are connected or disconnected in accordance with the actual power
demand. For modulating energy producers, a stepped output is converted into a proportional output within
the aggregate. This makes it possible to handle the full power range (0…100%) in one stage, or to divide
the power range into several stages (e.g., Stage 1: 0…20%; Stage 2: 20…40%; etc.).