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 189 | 351
networks are automatically created, which must be connected to the PXG3 BACnet router. Multiple BACnet
internetworks can be created on an IP segment by using different UDP port numbers.
Desigo establishes PTP connections only between operator units and a network. Operator units duplicate a
virtual network since PTP connections demand a network at both ends.
Desigo CC does not use PTP.
Segment
Large networks are structured, that is, divided into several (logical) network segments for reasons of
security, performance, size and (limited) address range of network devices. The segments must then be
connected to routers of the corresponding transport protocol (e.g., LonWorks router, IP router).
In most cases it is not necessary to divide a BACnet/LonTalk network into several LonWorks segments
(ALN). However, if it does prove necessary, it is not possible to use a LonWorks router, because this limits
the length of the data packets. An L-switch (Loytec) can be used as a router on the ALN.
BACnet MS/TP networks cannot be segmented, because there are no associated routers.
With BACnet/IP some IP segments may be connected by IP routers. Since the IP router prevents
broadcasting, the connection must be activated with the BACnet Broadcast Management Device (BBMD).
Physical segment
Physically, (cable) networks cannot be expanded as desired. Depending on electrical transmission
properties and the data link layer based on it, repeaters must be added at specific cable lengths to amplify
the signal. This divides the network into multiple, physical segments. A repeater does not impact the
transmission protocol; it merely electrically connects two physical networks.
Dividing up the network into several physical segments may be necessary in LonWorks technology.
The physical segments are connected with physical or logical repeaters. Due to the limited buffer size of
logical repeaters, only physical repeaters may be used on the ALN. Only one physical repeater may be
located between any two nodes.
MS/TP is transmitted on a two-wire cable as per EIA-485/RS-485*. The length of the physical segment can
be max. 1,200 m and can be extended with EIA-485 repeaters.
*TIA standard (Telecommunications Industry Association): TIA-485-A Electrical Characteristics of
Generators and Receivers for Use in Balanced Digital Multipoint Systems (ANSI/TIA/EIA-485-A-98)
(R2003)
Desigo site
A site is an independent and self-contained logical entity within the building automation and control
system. This type of structuring is not defined by BACnet, and is therefore largely independent of the
BACnet network topology. The BACnet devices bound to a site can therefore be placed anywhere within a
BACnet internetwork. A site cannot extend across a PTP connection. Communication occurs only within the
site, but data can be exchanged with any device on the BACnet internetwork.
Only automation stations (PXC/PXC3) and LonWorks system controllers (PXC...D+PXX-L11/12)) are
assigned to the sites, by special structuring of the Device ID and Device Name. These products are
considered third-party devices for the purposes of a site.
Protocol layer model
Desigo supports:
● BACnet/IP
● BACnet/LonTalk (LonWorks technology)
● BACnet/PTP
● BACnet MS/TP
● BACnet/IPv6 (only via PXG3 BACnet router)