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
Desigo Open
Integration on management level
21
CM110664en_07 307 | 351
Desigo Open system Desigo Open application Data points
Desigo management platform Desigo CC
Energy monitoring, fire security, access
control and security
1,000 - 10,000
Desigo PX PX Open
Power distribution, refrigeration machines
50 - 2,000
Desigo TX-I/0 TX Open
Pumps, variable speed drives, meters, etc.
Max. 160
Desigo room automation / RX PXC3
Lighting and blinds
16 DALI groups
SDKs
If a solution is not supported by HQ and RCs need a specific solution, HQ offers Software Development Kits
(SDKs) for experts. The regional companies can develop their own solutions using Software Development
Kits (SDKs).
The following SDKs are available:
● PX Open platform SDK
● TX Open platform SDK
21.1 Integration on management level
The integration of third-party devices and systems on the management level is appropriate:
● For monitoring and operating plants that are not time-critical
● When process communication with other automation stations is not needed
Desigo CC
BACnet
BACnet is a widely used communication protocol for building automation and control networks. It defines a
number of objects, services and data link layers. It is an essential part of Desigo CC's openness for
integrating any third-party devices, using the BACnet/IP protocol. An online auto-discovery and
alternatively an offline EDE import are available for integrating third-party devices.
See
BACnet 3rd party Integration Guide
(A6V10446271).
BTL
For more information about compliance and interoperability of Desigo products, go to
http://www.bacnetinternational.net/btl and search for Desigo.
Modbus-TCP
A native Modbus-TCP driver lets you integrate a Modbus TCP server and subsequent Modbus RTU devices
via a protocol converter. An offline importer supports the engineering workflow for integrating Modbus data
points.
See
Modbus Integration Guide
(A6V10438039).
OPC
OLE for Process Control (OPC) is a communication standard for exchanging data between windows based
software applications and process control hardware without any proprietary restrictions. It is a client/server
technology, where one application acts as the server providing data, and another acts as a client using
data. The most common specification
Data Access
(DA) defines a set of objects, interfaces and method to
facilitate the interoperability. OPC has been extended to become a cross-platform communication
standard, named OPC Unified Architecture (OPC UA).
For more information about OPC, see the documentation by the OPC Foundation (www.opcfoundation.org)
and the OPC Training Institute (www.opcti.com).
OPC DA client
An OPC client interface lets you integrate any OPC server, using the Data Access specification. An offline
Importer supports the engineering workflow to integrate OPC items.
See
OPC Server Integration Guide
(A6V10415483).
OPC DA server