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
System configuration
Devices
22
320 | 351 CM110664en_07
Key
1
PXM20, PX-Web and XWP are temporary alarm receivers.
2
Desigo CC is a configured alarm receiver. The number of entries in the notification class is limited to 20. The total number of
different configured alarm receivers across all notification classes is limited to 30.
3
Max. number of BACnet references, COV servers: SubscribeCOV requests which can be accepted. Example: 1400: 1 client and
1400 values or 2 clients and 700 values.
4
Max. number of BACnet references, COV client resources, i.e. values read from or written to (commanded) your own
automation station or a remote automation station.
BACnet client references are used in Input, Output, Scheduler, Trendlog and Group objects (all NameRef_Type inputs with
AddrKind = B). The configured alarm receivers of the Notification Class objects do NOT require any BACnet client references.
The available number of BACnet client references shall address not more than 50 different remote automation stations. If this
value is exceeded the number of BACnet broadcast messages on the network will increase.
Example: 400: 1 client and 400 values or 2 clients and 200 values.
5
Every active Trendlog object needs a BACnet reference.
Trends need 12 bytes per entry (irrespective of data type). Max. 64 KB can be allocated to the log buffer (approx. 5,000
entries) for each Trendlog object. These log buffers are assigned in D-MAP RAM. If the log buffer size is changed and there is
insufficient D-MAP RAM available, the Reliability property of the Trendlog object is set to Memory limit reached.
8
The address of the PPS-2 devices QAX84.1 and RXZ90.1 is always 1 (no address selection).
9
PX KNX = PXC001.D / PXC001-E.D and loaded PX KNX firmware.
10
PX Open = PXC001.D / PXC001-E.D with option module PXA40-RS1/RS2 and loaded PX Open firmware.
14
Maximum 30 calendar entries.
15
The number of physical data points influences the reaction time of the application. If minimum reaction times are specified,
the number of physical data points may have to be reduced.
The following relationship between reaction times and the number of physical data points can be assumed:
- up to 150 physical data points = Reaction times < 1s
- up to 250 physical data points = Reaction times 1…2 s
- up to 350 physical data points = Reaction times 2…3 s
17
Number of switching times per day: 10; max. 5 BACnet references.
18
Number of switching times per day: 20; max. 5 BACnet references.
19
Every active trendlog multiple object needs a BACnet reference per logged value.
5 logged values are assumed for the number of trendlog multiple objects (number of Trendlog / 5).
Trends need 12 bytes per entry (irrespective of data type).
Max. 64 KB can be allocated to the log buffer (approx. 5,000 entries) for each trendlog object.
These log buffers are assigned in D-MAP RAM.
If the log buffer size is changed and there is insufficient D-MAP RAM available, the Reliability property of the Trendlog object
is set to Memory limit reached.
20
Dynamic objects are counted the same as non-dynamic objects for total limits.
* Limit* = Technical limit verified.
[ *] [Limit*] = Technical limit not verified.
[ ] [Limit] = Recommended limit not verified.
( ) (Limit) = Limit subject to proviso. Refer to footnotes.