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
Alarm management
Alarm suppression
9
CM110664en_07 165 | 351
Alarm suppression by automation station
AS_STA (Device Access) is a Desigo PX function block that allows to suppress all alarms of an automation
station. The function block allows for suppressing BACnet event notifications by means of an application.
Thus, sending of alarms and events during, e.g., maintenance, can be suppressed, e.g., via a key switch.
Alarm suppression is controlled via pin SupEvt. The following values are defined for SupEvt:
● true: The automation station sends NO BACnet event notifications.
● false: The automation station sends BACnet event notifications.
For more information on function block AS_STA, see:
Desigo Firmware blocks, automation level, Overview
(CM110749)
Desigo Vxx Firmware blocks
(CM110729)
Desigo room automation supports the suppression of all alarms of an automation station. To do this, it uses
the device infrastructure objects CommonEvent and CommonEventEnrollment.
Hierarchical alarm suppression
Hierarchical alarm suppression allows for suppressing alarms of a plant, partial plant, aggregate,
component, or subcomponent. Hierarchical suppression is based on suppressing alarms of any part of a
partial tree in the technical structure.
For Desigo PX hierarchical alarm suppression is carried out via the Alarm Collection (CMN_ALM) object.
CMN_ALM comprises all alarmable BACnet objects as a group on the same or lower hierarchies in the
technical view. Thus, CMN_ALM allows for controlling alarm suppression for all alarmable BACnet objects
of a group.
Alarm suppression is controlled via pin SupEvt. The following values are defined for SupEvt:
● true: Alarmable BACnet objects of a group do NOT send BACnet event notifications.
● false: Alarmable BACnet objects of a group send BACnet event notifications.
Desigo room automation supports the hierarchical suppression of alarms. It uses the CommonEvent and
CommonEventEnrollment objects.
The CommonEvent object aggregates the alarm state of all BACnet objects on the same or the lower
hierarchy levels of the technical view.
The CommonEventEnrollment object monitors the CommonEvent object. The hierarchical alarm
suppression can be turned on or off in the CommonEventEnrollment object.
Specific alarm suppression
All alarmable BACnet objects allow for specific suppression. Each alarmable BACnet objects offers pin
EnEvt for this type of alarm suppression.
The following values make sense for EnEvt:
● (False, False, False): The object sends NO BACnet event notification.
● (True, True, True): The object sends BACnet event notification.
Value combinations with True and False for EnEvt should be avoided.
Alarm suppression exceptions
A possible application is to activate alarm suppression during plant maintenance. Vital alarms must be
excepted from alarm suppression.
For Desigo PX exceptions can be defined for hierarchical alarm suppression with CMN_ALM.
Function block CMN_ALM has pin EnSupEcp. This exception specifies if exceptions are possible within the
alarmable BACnet objects of the group. The following values are defined for EnSupEcp:
● true: Exceptions for alarm suppression within the group of alarmable BACnet objects are considered.
● false: Exceptions for alarm suppression within the group of alarmable BACnet objects are NOT
considered.
Each alarmable BACnet object can be exempted from hierarchical alarm suppression with CMN_ALM. To
do this, each alarmable BACnet object has pin SupEcpt. The following values are defined for SupEcpt:
● true: The object is considered as an exception for alarm suppression.
● false: The object is NOT considered as an exception for alarm suppression.