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
196 | 351 CM110664en_07
Designation Description
IP address IP address of the BBMD.
UDP port UDP port number of the BBMD.
Broadcast mask If the BBMD is to be addressed via direct broadcast (one-hop distribution) the subnet mask of
the BBMD must be specified. Since not all IP routers support this mechanism, direct
broadcasts are not supported by default. Two-hop-distribution is always possible. The
broadcast mask is then 255.255.255.255.
Not required for IPv6.
Foreign device
A foreign device is a (remote) BACnet device in a remote IP segment. It registers with a BBMD in order to
send or receive broadcast messages. Registration with a BBMD involves making an entry in its Foreign
Device Table (FDT). The registration must be renewed at regular intervals.
The foreign device does not send broadcast messages, but passes them as unicast messages to the BBMD
for distribution. The BBMD in turn passes incoming broadcast messages as unicast messages to the
foreign devices in its FDT.
In the Desigo system, Desigo CC, XWP/ABT, and PXM30/40/50-E can be operated as foreign devices. IPv6
does not support foreign devices
Examples from the Desigo topology
● IP Segment 1: Desigo CC 1 does not have to be configured as a foreign device, because this IP segment
contains a BBMD.
● IP Segment 2: Desigo CC 3 does not have to be configured as foreign device, because this IP segment
contains a BBMD.
● IP Segment 3: This segment only contains Desigo CC 2. To enable Desigo CC 2 to receive and send
broadcast messages, it must register with a BBMD as a foreign device. It does not matter with which
BBMD it registers.
Foreign device parameters
If a BACnet device operates as a foreign device, the IP address and UDP port number of the BBMD must
be specified.
Designation Description
IP Address of BBMD IP address of the BBMD with which the foreign device registers.
UDP Port of BBMD UDP port number of the BBMD with which the foreign device is registered. The default is
0xBAC0.
The recording interval (Time-To-Live) for Desigo products is set at 300 seconds (= 5 minutes).
PTP data link layer
The PTP Data Link Layer is used for remote management over the telephone line. Unlike LonTalk and IP,
PTP does not allow the creation of a network. The PTP connection is always between two half routers, and
between two different BACnet networks. Several BACnet networks may be located at each end of the PTP
connection. Only one active communication line can exist between any two BACnet networks or between
any BACnet devices.
The half-router function is implemented in Desigo CC, XWP/ABT and PX.
PTP connections are only possible between Desigo CC, XWP/ABT und PX. PTP connections between PXs
are not permitted.
PX devices which can be reached via PTP always belong to a separate site. With reference to the topology
at the beginning of the chapter, the site named Baar must not be combined with the sites named Zug or
Cham. Several PXs per site can be used as half routers. When establishing a communication, the best-
Application Layer
Network Layer
PTPIPLonTalk MSTP