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 queuing
9
162 | 351 CM110664en_07
● Default = 100 (PXC) or 150 (PXR)
● Range = 10…500 depending on the available memory space
Record count [RecCnt]
This BACnet property represents the number of entries currently stored in the queue.
The alarm queue can be deleted by writing the value 0 to this property. A write of a value not equal to 0
results in an error message.
If the queue is deleted, this information is entered as a system event in the queue and transmitted to the
receivers. This causes the value to change to 1 as soon as [RecCnt] is set to zero.
Notification threshold [NotifThd]
This BACnet property defines the dial-out threshold, and the number of alarms to be deleted in the event of
a queue overflow.
If [RecCnt] is greater than or equal to [NotifThd], a connection is established with any alarm recipients
connected by cable (modem) which are destined to receive alarms and events from the queue. The
connection is established provided that the remote alarm recipient concerned is listed in the notification
class object.
The message threshold also defines how many alarms are to be deleted in the event of a queue overflow.
As many alarm entries are deleted as necessary until [RecCnt] is equal to [NotifThd]. This function does
not distinguish between local and remote alarm recipients in the notification class object.
To avoid deleting too many alarms, it is recommended that [NotifThd] be set to approximately 80% of the
[BufSize].
Alarm queue message threshold [NotifThd]:
● Default = 80 (PXC) or 130 (PXR)
● Range = 5…495
Alarm priority limit [PrlmAlm]
This BACnet property defines another independent threshold for dial-out.
An alarm priority which is less than or equal to [PrlmAlm] results in a connection with any alarm recipients
connected by cable (modem) which are destined to receive alarms and events from the queue. The
connection is established provided that the remote alarm recipient concerned is entered in the list of
Notification Class objects.
Alarm priority limit [PrlmAlm]:
● Default = 2 (HighPrioAlarm or UrgentAlarm)
● Range 0…255
If the notification class object contains only local alarm recipients, then the optimum results are achieved
by use of the default values for control of alarm queuing. The default values should therefore not be
changed.
If the notification class object contains remote alarm recipients, then it may be appropriate to modify the
default values for control of alarm queuing.
The values for [NotifThd] and [PrlmAlm] determine when a remote cable connection (modem) is to be
established, in order to inform the user of the occurrence of alarms.
If low-priority alarms are to be forwarded immediately, the [PrlmAlm] value must be increased (the higher
the number, the lower the alarm priority). The value for [NotifThd] must not be modified.
The value for [NotifThd] can be reduced, however, in cases where a connection is to be established when
there is a smaller number of alarms in the alarm queue. It is important to ensure, however, that the
difference between [BufSize] and [NotifThd] does not become too great, as this is the value that controls
the deletion of alarms in the event of a queue overflow.
Note that modifying these values also affects connection costs.
It takes time to establish a connection by cable (modem). If it is likely that further alarms will occur during
this time, thereby causing the queue to overflow, the difference between [BufSize] and [NotifThd] should
be increased.
The following settings are recommended:
● Buffer size [BufSize] = 120
● Notification threshold [NotifThd] = 80
In cases of doubt, the default values should be left unchanged.