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
78 | 351 CM110664en_07
Step 1: Safety function AllLifeSafety
If all switch commands for a given plant operating mode have the priority Life safety, it is referred to as the
AllLifeSafety plant operating mode.
A pending AllLifeSafety plant operating mode in the [ValPgm] is executed immediately in all cases and
maintained regardless of previously existing and newly occurring faults in the plant – human life takes
precedence over plant safety.
If the AllLifeSafety mode includes switch-on commands, then the preset delay times (Delay and Timeout)
will be observed. However, in the case of the Timeout setting, the switching sequence will continue even in
the absence of any feedback signal. Interlocks cannot therefore be guaranteed, with the exception of local
interlocks implemented via Priority 1 (life safety, manual).
Priority 1 (life safety, manual) cannot be overwritten in the AllLifeSafety.
Step 2: Preview Look Ahead
Before changing to a different plant operating mode, in which referenced blocks are to be enabled, block
CMD_CTL checks to ensure that all the aggregates can actually be enabled. For this purpose, the entries in
the priority array [PrioArr] for the switching sequence blocks are checked in advance. If switch commands
of a higher priority are found to be active (e.g., a minimum switch-off time or the OFF-command of a repair
switch), then CMD_CTL waits to implement the new plant operating mode until the full switching sequence
can be implemented. Only referenced blocks, for which a switch-on command exists in the new plant
operating mode, are checked, and only if the operating-state monitoring feature has been enabled.
The following priorities are checked:
● Priority 1 [EnSfty/ValSfty], life safety, manual.
● Priority 7 [EnSwi/ValSwi], manual operation, e.g., manual switch.
● Priority 8 [EnOp/ValOp], manual operation, operating unit.
● Priority 6 [TiMinOff], minimum switch off time.
Priority 6 is checked only for a switch on command to determine whether the aggregate is still within the
minimum switch off time. In this case, it waits until the switch off time expires and only then switches on.
There is no Look Ahead for Desigo 7.
Priority 4 (plant safety, manual [EnCrit/ValCrit]) is not considered during the check, since local mutual
locking via data flow interconnection, such as depicted in the figure
Cross-aggregate interlocking of
damper/fan
, would change this value during the switch-on process.
The present operating mode remains until it is certain that all impacted aggregates with active operating
state supervision can be switched to the new set state. A process alarm is triggered in CMD_CTL of a
monitored block is not switched on. The exception value [EcptVal] is active as the new plant operating
mode in this case. The online diagnostics for the Plant Control Editors determines which element is the
cause of the fault.
Step 3: Abort sequence
On-going switch sequences are aborted when delay times are still active. Exception: An alarm is generated
when a fault occurs as part of internal monitoring of the block. The demanded plant operating mode is
determined in this cased by the exception value [EcptVal]. If the switch sequence is active, but not
completed, it is NOT aborted, but rather is completed.
Step 4: Ramp-down sequence
The ramp-down sequence is started first for the new plant operating mode. This shuts down all aggregates
that must be switched off per the new plant operating mode. The shut down takes place in the table
sequence from right to left, in other words, the last aggregate in the switch sequence is the shut down first.
The parameterized times for the time off delay are active during ramp down to off. The time off delay can
be activated using a fixed delay time or a maximum timeout or deactivated using the immediate option. The
length of the delay for timeout depends on the switch off state of the monitored sequence elements.
Transition to the next sequence occurs as soon as it reports switched off, that is, the process value of the
block [PrVal] = Off. It switches after the timeout time expires when the shut-down message is not sent.
If a sequence element with a life-safety or plant-safety priority is switched off, the preset delay times will
be ignored.