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
Global objects and func
tions
Examples of global objects
7
126 | 351 CM110664en_07
The primary server transmits the time in UTC format (Coordinated Universal Time) to the other automation
stations (backup servers) and in UTC format or local time format to the third-party BACnet devices.
The backup server then triggers time synchronization of its recipients configured in Xworks Plus (Desigo
room automation server, third-party server, third-party BACnet devices). This can be in either UTC or local
time format.
Periodic synchronization
The time synchronization interval is defined in the property TimeSynchronizationInterval [TiSynIvl] (default
value: 150 minutes). The property can be configured in Xworks Plus (XWP) and adapted to the specific
situation via a switchable [AlgnIvl] offset [IvlOfs]. How these three properties function is defined in the
BACnet standard and implemented accordingly.
Add and delete devices
For time synchronization, the primary server has a list [TiSynRcp] containing the recipients configured in
Xworks Plus (XWP) and all known backup servers of its site.
The primary server automatically adds newly commissioned backup servers on the site to the list
[TiSynRcp].
Backup servers which are removed from the site must be removed manually from the primary server list in
Xworks Plus (XWP).
Link the system time of a site with operator units
The network-capable operator units do not belong to a site. The primary server does not update the time in
the operator units. The client can read and update the time, if required.
Daylight saving time changeover
The daylight saving time changeover does NOT take place in the primary server. Each automation station
makes this switch independently.
The date of the daylight saving changeover is set as a parameter in the primary server. The primary server
replicates the date on the backup server. The official (Central European) changeover date is set as default.
The local time in an automation station is a calculated variable. The calculation is based on the internal
time in UTC format, the property UTC offset [UtcOfs] and the date of the summer and winter time
changeover.
See
Desigo CC User Guide
(A6V10415471).
7.5 Examples of global objects
BACnet device object
Certain properties of the BACnet device object are defined as global, because from the perspective of the
system, they are required to have the same value throughout the site. These properties are set in Xworks
Plus (XWP). Examples:
Global properties
● Date and time for the summer and winter time changeover.
Daylight savings time start date [DsavSdt] (Default: last Sunday in March)
Daylight savings time start time [DsavSti] (Default: 02:00AM)
Daylight savings time end date DsavEdt] (Default: Last Sunday in October)
Daylight savings time end time [DsavEti] (Default: 03:00AM)
● UTC_Offset [UtcOfs]
Difference between UTC and local Winter time in minutes. Default value: – 60 mins (Central Europe). In
Summer, the effective difference [UtcOfs] is –60 mins (Central Europe: –120min).
● Synch.Request Period [SynReqp]
Period between life checks by primary server The load on the communications system generated by the
life check can be controlled with this parameter by adapting it to the site size. Default value: 1800 s.
● Name resolution interval [NamRI]
Periodic repetition for the resolution of references across devices. Default value: 900 s.
● COV resubscription interval [CovRI]
Time within which the automation station resubscribes to a subscribed value. Default value: 1800 s.
Local properties
Local properties which refer to the functionality of the life check / replication: