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 sources
9
CM110664en_07 135 | 351
9 Alarm management
Alarms indicate faults in the HVAC plant and building automation and control system, and let you initiate
corrective action, where appropriate. The management of alarms (generation, signaling, acknowledgement)
is in compliance with the BACnet standard.
There are two alarm types:
● OFFNORMAL
● FAULT
OFFNORMAL
OFFNORMAL alarms (process alarms) occur when a process variable assumes an inadmissible value. What
is inadmissible is determined during engineering. The relevant parameters are stored in all alarm-
generating objects. An OFFNORMAL alarm always indicates a fault in a plant, while the automation system
itself works properly.
Examples of OFFNORMAL alarms:
● Temperature in HTHW circuit is too high or too low
● Alarm generated by fire detection system
● A damper-motor feedback signal has not been received
● A time schedule cannot execute a command
FAULT
FAULT alarms are faults in the automation system itself (internal alarms). You cannot define the cause of a
FAULT alarm during engineering. Nor is it possible for the user to suppress or otherwise influence the
monitoring of FAULT alarms. FAULT alarms are intrinsically linked to the system. A FAULT alarm always
takes precedence over an OFFNORMAL alarm from the same alarm source, because in the case of a
FAULT alarm, there is some uncertainty about the reliability of the alarm source.
Examples of FAULT alarms:
● Faulty sensor (open circuit, short circuit, etc.)
● Buffer for storage of non-volatile data full
● Access to an I/O module failed
● Bus open circuit (RX integration)
Alarm detection procedure
Every alarm (OFFNORMAL or FAULT) can be uniquely allocated to a source. The alarm monitoring system
is based on the principle of Intrinsic Reporting or Algorithmic Reporting as defined in the BACnet standard.
Intrinsic reporting
Intrinsic reporting means that alarm monitoring (target-actual comparison) takes place within the alarm-
generating object itself (the alarm source). For this purpose, the function block contains the entire alarm
state machine. Alarm detection does not require any function blocks with external functions. The alarm
behavior of the object is defined by setting variables in the alarm-generating object (function block).
Algorithmic reporting
Algorithmic Reporting means that alarm suppression (target-actual comparison) occurs outside the alarm
source. The alarm state machine is not located in the function block of the alarm source. For alarm
detection, function blocks with external functions are required. The object's alarm response is not
parameterized using variables of the monitored object (function block).
9.1 Alarm sources
The following function blocks can be alarm sources:
● Analog Input / Analog Output / Analog Value
● Binary Input / Binary Output / Binary Value / Pulse Converter
● Multistate Input / Multistate Output / Multistate Value
● Event Enrollment
● Command Control object
2
● Power Control object
2
● Schedulers (Analog / Binary / Multistate Scheduler object)
2