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
CM110664en_07 329 | 351
Function Touch panel BACnet/IP web interface
TCP/IP BACnet/IP
PXM50-1
PXM40-1
PXM30-1
PXM50.E
PXM40.E
PXM30.E
PXG3.W100-1
PXG3.W200-1
Max. number of assigned devices
BACnet/IP
BACnet MS/TP *)
BACnet LonWorks *)
n.a.
50
10
10
50
10
10
Number of simultaneously connected operator clients
1
n.a. 5 5
Max number of devices connected to one BACnet device
n.a. 5 5
Data points per plant graphic
n.a. 40 40
Data points (in a table)
n.a. 40 40
Number of defined users
n.a. 8 8
Trend chart, max. number of entries
(Max. 5 trends, with 10,000 each)
50,000 50,000 50,000
Max. entries per online trend
2
10,000 10,000 10,000
Max. entries per BACnet trendlog object
3
5000 5000 5000
Trend export: Max. number of entries per trend
10,000 10,000 10,000
Max. alarm History entries
10,000 10,000 10,000
*) see specific MSTP and LonWorks section for more specific limitations
1
5 is the recommended number. More clients can be connected, but performance deteriorates when the same operations are
performed simultaneously. Example: Simultaneous load of the same plant graphic to 10 clients.
2
Trend data management must be configured according as part of the online trend configuration.
10,000 trend entries can be recorded from:
● 1 trend entry daily over a minimum of 25 years
● 1 trend entry every hour over a minimum of 1 year
● 1 trend entry every 15 minutes over a minimum of 3 months
3
The time to read a BACnet trendlog object depends on the number of entries and the data link.
Desigo Control Point is optimized for BACnet/IP devices which are supporting COV communication. The
objects of an assigned device will automatically be polled if the device does not support COV. Polling
causes a higher network communication load. This can decrease the overall performance of the Desigo
Control Point device, depending on the BACnet device and on the type of communication (MS/TP,
LonWorks). Such topologies must be tested individually and project specifically.
22.4.15.5 Limits for MS/TP
Use the router PXG3.L / PXG3.M with HW Index C only.
Data point integration: MS/TP devices are considerably slower than IP devices due to the lower network
speed. Reference value: Approximately 15 times slower (depending on the project setup).
MS/TP is tested with 10 devices that support COV (e.g. DXR2). Recommendation: Assign or integrate a
maximum of 10 MS/TP devices on one network branch. More devices and/or network complexity are
permitted, but they may result in longer and inconsistent times and degraded performance.
● Assign devices offline/online:
More than 10 devices degrade performance in ABT-SSA.
Additional network branches degrade performance in ABT-SSA.
● Device learning offline/online:
More than 10 devices takes longer.
The times are slower with additional network branches.
● Device restart (e.g., after the power returns):
More than 10 devices takes longer.