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 configuration
Integration on room level
22
CM110664en_07 313 | 351
BACnet internetwork
A BACnet internetwork consists of one or several BACnet networks. Individual BACnet networks are
connected to BACnet routers.
Each BACnet device can communicate with another BACnet device in the internetwork. A BACnet device in
one internetwork cannot communicate with a device in another internetwork.
A Desigo management station can be used to integrate the operation of several BACnet internetworks and
other systems (see Desigo system).
When defining the system configuration, FLN integrations (LonWorks, KNX) are also added to the BACnet
internetwork. In this way, the Desigo system can be seen as a combination of several BACnet
internetworks. Technically, the individual FLN devices are not BACnet devices. They do not communicate
via the BACnet protocol.
BACnet PTP internetwork
BACnet PTP communication uses modem (telephony) or null-modem (RS232) connections. Owing to the
slow rate of data transfer via these connections, the limits are lower for a BACnet PTP internetwork.
Modem-based PTP connections are considered obsolete and are therefore no longer used. The BACnet
PTP communication connects BACnet networks via BACnet half routers.
BACnet network
A quantity of BACnet devices connected within an IP or LonTalk or MS/TP network with specific (that
means, the devices are in the same BACnet Broadcast Domain) limits. In the case of the LonTalk or MS/TP
network, the limit is physical. In the case of an IP network, the network can be physically the same, but the
limit is determined by different UDP ports.
Local communication between two BACnet devices in a BACnet network is not visible in another BACnet
network.
IP segment
Sub-area of an IP network. IP segments are connected by IP routers.
In order to ensure that BACnet communications (Broadcasts) can always take place across IP routers,
BBMDs (BACnet Broadcast Management Devices) are required. PXG3.L/M and PXC…-E.D over IP can be
configured as BBMDs. Individual BACnet devices in an IP segment can register with a BBMD as foreign
devices.
LonWorks segment (ALN)
Sub-area of a BACnet/LonTalk network. LonWorks segments are connected by LonWorks routers. In most
cases it is not necessary to divide a BACnet/LonTalk network into several LonWorks segments (ALN).
It is not possible to use a LonWorks router because of the restricted length of the data packets. An L-
Switch can be used as a router on the ALN.
LonWorks segment (FLN)
Sub-area of a LonWorks network. LonWorks segments are connected by LonWorks routers.
An L-Switch or a LonWorks router can be used as a router on the FLN.
LonWorks trunk (FLN)
Comprises all the devices connected on the FLN side of the PXC00.D/-E.D + PXX-L1…. Consists of one or
several LonWorks segments (FLN).
A LonWorks trunk (FLN) is the equivalent of a LonWorks network (FLN).
PX KNX integration
Comprises the integration of KNX devices that are connected on the FLN side of the PXC001.D/-E.D.
PX site
A Desigo PX automation system site.
The PX BACnet devices which control the plant in a PX site are interconnected via the global objects and
the primary copy procedure.