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 overview
Data maintenance
3
24 | 351 CM110664en_07
● Desigo CC: AMEV profile MOU-B
● Desigo PX: AMEV profile AS-B
Desigo room automation
BACnet is used to exchange information between PX automation stations and DXR2 and PXC3 room
automations stations and the management platform.
Desigo RX
The Desigo RXB room automation range communicates via KNX S-Mode (EIB).
Restrictions for LonWorks
A LonWorks network cannot be segmented with LonWorks routers, as the message length for BACnet is
228 bytes for performance reasons. Commercially available LonWorks routers do not have sufficiently large
buffers for this length. No other media (power lines, infrared, etc.) can be used either.
For performance reasons, we do not recommend the operation of LonWorks and BACnet devices on the
same LonTalk cable.
3.9 Data maintenance
A running Desigo system contains various categories of data, each with different requirements in terms of
consistency, period of useful life and visibility. The data is distributed throughout the system, with each
category having a unique origin. There is no central data maintenance in the Desigo system. The system
data is distributed on all devices throughout the network, but is primarily located in the automation
stations.
During the sales, planning, engineering and commissioning phases, project data is created. Part of the data
is loaded into the system, while another part is tool-specific and used, e.g., for documentation of the
project.
System data is:
● Process-data and parameter settings
● Archived data
● Configuration and description data
● Metadata
● D-MAP program
● Graphics and masks
● Libraries
● Offline trend object values
Process-data and parameter settings
Process data
Process data is data generated by the physical process in the building using a process control algorithm.
Process data represents the process variables, such as a temperature or a damper position.
Parameter settings
Parameter settings are function parameters, settings, setpoints, etc. which are defined for each plant or
project and which affect the way in which an application works. Parameter settings can be modified during
operation.
Process data and parameter settings can be accessed within the system via BACnet objects, e.g., Present
Value [PrVal] and Status [StaFlg], if the associated mapping is enabled in the engineering phase.
If process data is used by several automation stations, the data origin is the location where the physical
variable is measured (e.g., outdoor temperature) or generated (e.g., the control signal from a time
schedule). Copies are updated on an event-driven basis after a short delay.
Displaying process data and parameter settings
To display process data and parameter settings mapped to BACnet on clients, only one copy of the data
needed for current operation and monitoring is stored. The Desigo system does not store complete copies
of process data or parameter settings. The data (copy) required by a client is normally updated via the
BACnet protocol on an event-driven basis and with a short time delay.