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
Network architecture
BACnet architecture (MLN & ALN)
14
CM110664en_07 191 | 351
The device name is the object name of the BACnet device object.
Guidelines
Different rules for object names apply for configuring TD (Technical Designation), UD (User Designation),
or FD (Free Designation):
● The TD is generated from predefined partial names, separated by an apostrophe ('), that show the
technical hierarchy with plant, partial plant, and component. The TD is supplemented by site name and
pin name.
● The names may consist of upper- and lowercase letters and numbers 0 to 9. The site name is
separated by a colon (:) and the pin name by a period (.). The maximum total length is 30 characters.
● The UD is formed similar to the TD based on partial names. However, users determine the partial
names, structure, and separators. The names consist of upper- and lowercase letters, numbers 0 to 9,
and separators, such as _-;=’, etc. The maximum total length (including site name and pin name) is 80
characters.
● The FD is a freely assigned name consisting of letters, numbers and a few special characters, limited
within the system only by uniqueness and length. The maximum total length is 80 characters, ten of
which, plus one separator, are reserved for the site name.
Category Device name Description
Unconfigured ““ Empty string for unconfigured devices
Class A No rules
Class B1 Meaningful text for the user (this text is used as a
reference for the alarm recipient)
Class B2 Model name + device ID Model name + “ “ + 8 character device ID (hexadecimal).
The device name for temporary devices is generated
automatically.
Class B3 Max. 25 characters
Class C Site name + automation station name Site name + “:“ + automation station name
Examples from the topology at the beginning of the chapter:
Category Site number Device
number
Device ID Site name Device name Device name
A – 1 0x02000001 – Third-party 1 Third-party 1
B1 – 1 0x02100001 – Desigo CC 1 Desigo CC 1
B2 – 15 0x02100401 – – PXM20TMP0210040f
C 1 1 0x02200401 Cham PXC #1 Cham:PXC #1
C 1 2 0x02200402 Cham PXC #2 Cham:PXC #2
C 1 3 0x02200403 Cham PXC... #1 Cham:PXC... #1
C 2 1 0x02200801 Zug PXC #1 Zug:PXC #1
C 2 2 0x02200802 Zug PXC... #1 Zug:PXC... #1
C 3 1 0x02200C02 Baar PXC #1 Baar:PXC #1
BACnet device parameters
The BACnet device parameters are written to the devices during commissioning. These parameters include
the following values: