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 197 | 351
performing connection is always selected. Redundancy is not allowed, that is, several simultaneously active
connections in a given BACnet network are not allowed.
With Desigo CC, a separate, independent, internal BACnet internetwork is created for each Data Link Layer
type. Routing between LonTalk, IP or PTP is therefore not possible.
The following parameters are required for each half router:
Designation Description
Local network number The BACnet network number to which the half router belongs.
With PX, the local network number is the same as the device's own network number.
Desigo CC supports all three different Data Link Layers (IP, LonTalk and PTP). They are
handled internally as independent BACnet internetworks. This means that routing between
the different Data Link Layers is not possible. Therefore, the local network number can be
allocated to IP and/or LonTalk independently of the networks. However the local network
number must be unique among all networks which could possibly be reached from Desigo CC
via a PTP connection.
Recommendation:
If Desigo CC has an additional Data Link Layer (IP and/or LonTalk), the local network number
of this network should be used (example in the beginning of the chapter: For Desigo CC 2, the
local network number of BACnet network #4 should be adopted).
In Desigo CC with only one PTP connection, the local network number must be in the range
1000 to 1099. (Example: Desigo CC 3 -> #1000).
COM parameter For the PX half router, the COM port to which a modem or null modem is connected must be
specified.
Modem parameters The modem parameters contain individual settings for the relevant modem types. Predefined
parameter sets are available for the PX half router.
The following parameters are required for each PTP connection starting from a PX half router:
Designation Description
Remote network number This network number determines the BACnet network in which the remote partner device is
located. In the Desigo system this is the local network number of Desigo CC.
Remote area name The remote area name stands for a peer-to-peer remote network number of the network
containing Desigo CC.
During configuration, the remote area number lets you assign a clear name to the (remote)
alarm recipient rather than a network number.
Telephone number The telephone number for access to the remote device.
Performance index The performance index refers to the quality of the router data connection. If multiple PX half-
routers are available in a PX site, and if a connection to a remote network is to be established,
the router with the best performance index is selected. If no connection is established, the
router with the next best performance index automatically tries to connect.
Range: 0...255 (0= best / 255 = worst connection)
For each PTP connection in Desigo CC, only the telephone number needs to be defined.
Data link layer MS/TP
Data Link Layer Master/Slave Token Passing MS/TP is another protocol variant for BACnet. Desigo
supports this variant via a specific router that connects BACnet MS/TP to BACnet/IP.
MS/TP is based on the physical layer EIA-485/RS-485 and supports baud rates up to 76.8 kbps. Up to 256
devices can be connected to one MS/TP segment (in theory, dependent on their unit load).
Addressing MS/TP devices
Each device has its own unique MAC address. The MAC address is one octet long and defined as follows:
Application Layer
Network Layer
PTPIPLonTalk MSTP