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
Effects of BACnet properties on alarm response
9
142 | 351 CM110664en_07
Alarm enable [EnAlm]
[EnAlm] (Boolean type) is used to enable and disable the monitoring of OFFNORMAL alarms. OFFNORMAL
alarms will only be detected if [EnAlm] is TRUE. This is equivalent to the standard BACnet property
Alarm_Enable.
FAULT alarms are monitored independently of the value of the alarm enable property [EnAlm]. Monitoring
is continuous and cannot be disabled.
If [EnAlm] is changed from TRUE to FALSE during operation, the timer for all deviation monitoring periods
[TiMonDvn] will be reset to zero. As soon as the value of [EnAlm] reverts to TRUE, the associated
[TiMonDvn] timer starts counting to its preset value again from zero.
The value of [EnAlm] can be modified via BACnet clients or using the CFC editor online. During operation, if
[EnAlm] is changed from TRUE to FALSE while an OFFNORMAL alarm is still active, this will result in an
immediate state transition to TO_NORMAL1. In other words, the existing OFFNORMAL alarm condition is
seen as having cleared, and the alarm state of the alarm source is updated accordingly.
Enable event [EnEvt]
[EnEvt] (Boolean type) is used to enable and disable the transfer of OFFNORMAL and FAULT alarms.
OFFNORMAL and FAULT alarms are only transferred if [EnEvt] is TRUE. This is equivalent to the standard
BACnet property Event_Enable.
Enable event detection [EnEvtDet]
[EnEvtDet] (Boolean type) lets you turn the intrinsic/algorithmic reporting on/off. OFFNORMAL and FAULT
alarms are only forwarded when [EnEvtDet] = TRUE. This is equivalent to the standard BACnet property
Event_Detection_Enable.
Event state [EvtSta]
This variable denotes the current alarm state of the object. It can accept three values: NORMAL,
OFFNORMAL (in the case of analog HIGH_LIMIT and LOW_LIMIT values) and FAULT. The value of the
variables is updated immediately after the associated alarm state transition. This is equivalent to the
standard BACnet property Event_State.
Feedback value [FbVal]
[FbVal] is a feedback signal input, configured at a physical input via a separate hardware address. This use
of a physical input can also be the source of reliability errors. [FbVal] can be neither overridden nor
commanded. If [FbVal] is not configured at a physical input, then, by definition, it will be equal in value to
Present Value, in which case no OFFNORMAL alarms can be issued via the output object. This is
equivalent to the standard BACnet property Feedback_Value.
Unlike the binary output and multistate output blocks, the analog output function block does not use
[FbVal] as a criterion for OFFNORMAL alarm conditions. If [FbVal] is used, it can be a source of reliability
errors and can result in FAULT alarms.
Hi limit [HiLm]
This parameter (data type Real) determines the high alarm limit. If [PrVal] exceeds the high limit value
[HiLm] for longer than the period defined under [TiMonDvn], an OFFNORMAL alarm condition prevails,
namely: HIGH_LIMIT.
Enable limit [EnLm]
This variable only exists in the BACnet view of analog blocks (for reasons of compatibility with the BACnet
standard). It has exactly the same meaning as the alarm enable variable [EnAlm] and its current value is
derived from the value of [EnAlm] (that is, [EnLm = EnAlm], Limit enable = Enable alarm). This variable is
equivalent to the standard BACnet property Limit_Enable.
Low limit [LoLm]
This parameter (data type Real) defines the low alarm limit. If [PrVal] exceeds the high limit value [LoLm]
for longer than the period defined under [TiMonDvn], an OFFNORMAL alarm condition prevails, namely:
LOW_LIMIT. This is equivalent to the standard BACnet property Low_Limit.