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
Control concept and control blocks
5
64 | 351 CM110664en_07
Structure control functions
In this way, complex control and monitoring functions of a plant can be logically subdivided to allow for
clear assignment of the function unit or the real element of the plant. The higher-level control concentrates
on the control and monitoring of the overall plant, while the sub-control function units assume internal
control and monitoring of the given elements for the function unit.
Standardization of control functions
Moreover, plant security and available was increased through standardized control and monitoring
functions which would result in considerable expense using conventional methods.
Standardized control and monitoring functions:
● Unambiguous selection of operating mode
● Uniform fault-related shutdown
● Comprehensive status monitoring
● Switching sequence for ventilation systems
● Output stage control for heat generating plant
● Reporting of local intervention
● Avoidance of unnecessary attempts at switching
● Prevention of inadmissible switching operations
● Protection of plant by preventing switch-on or switch-off
Blocks bound by the control concept
Function Block name Task in the control concept
Prioritization of influencing
variables
ENSEL_BO
ENSEL_MS
Collect information for the selection of the resulting plant operating mode. All
superposed information are processed by priority resulting in the plant being
turned on or off, e.g., smoke extraction switch, frost protection, scheduler
program.
The blocks are primarily used on the hierarchy level plant/partial plant, but
may also be reasonably used, e.g., in aggregates.
Command control CMD_CTL Superposed control block for sequence control. The block ensures that
individual plant aggregates are switched on or off sequentially in a certain
order. The block monitors aggregates and can send alarms. It is optimized for
controlling air handling plants, but can be used for other applications. The
block is used on the hierarchy level plant/partial plant.
Power control PWR_CTL Superposed control block for power control. The block is used for control and
monitoring of the performance of a number of energy producers (multiple
boiler systems, refrigeration machines). Depending on the request power
demand, energy produces are switch on or off in stages. PWR_CTL is
optimized for controlling heating and refrigeration plants. The block is used on
the hierarchy level plant/partial plant.
I/O blocks with control
functionality
BO
MO
AO
Output blocks implemented per BACnet standard and therefore including a
priority mechanism (priority array) that is well suited for control tasks. The
priority array [PrioArr] be used through data flow interconnections and BACnet
commanding. Moreover, the block integrate the following control functionality:
- Motor control (pump, burner, etc.), one- to four-speed [BO, MO]
- Fan control, one- to four-speed [BO, MO]
Value blocks with control
functionality
BVAL
MVAL
AVAL
Value objects or value blocks are implemented per BACnet standard and
therefore includes output blocks via the priority mechanism. These blocks are
referred to as data points that can communicate within the system with the
I/O modules via BACnet. These blocks are primarily used as the
communication interface between superposed control [CMD_CTL, PWR_CTL]
and the aggregates.
Rotation block ROT_8 The Rotation block switches the operating mode on and off for a maximum of
eight functional units in accordance with a selected mode of rotation
(sequence or hours run). The change of operating mode is based on demand,
hours run, occurrence of a fault or manual intervention (override).
The block is used to process the functional units (e.g., aggregates or
components) as a function of run-time or faults. These blocks are used, e.g.,
for double pumps, that are changed over based on runtime.