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 195 | 351
192.168.0.0 - 192.168.255.255 Subnet mask: 255.255.0.0
For IPv6, IP addresses and private address ranges are defined differently. See
Ethernet, TCP/IP, MS/TP
and BACnet basics
(CM110666).
IP address
: Host address of the network subscriber.
Subnet mask
: Subnet mask of the IP segment in which the device is located. This value must be aligned
with the other IP devices.
The subnet mask is required for the identification of broadcast messages and for communication across IP
segments. The subnet mask and target IP address enable the transmitting IP device to decide whether the
data packet can be delivered directly to the target device or if it must be forwarded via the default gateway.
For IPv6, the subnet mask corresponds to the network prefix. See
Ethernet, TCP/IP, MS/TP and BACnet
basics
(CM110666).
Default gateway
: IP address of the IP router. This value is relevant for communication across IP segments.
UDP port number
For BACnet/IP to use UDP, a UDP port number must be defined. Only devices with the same UDP port
number can communicate with each other.
Port numbers are divided into the following classes by the IANA (Internet Assigned Numbers Authority):
● Well Known Port Numbers: Fixed port numbers assigned by IANA (0… 1023)
● Registered Port Numbers: Numbers registered with IANA (1024…48151)
● Dynamic and/or Private Ports Dynamically assigned or privately used port numbers (49152…65535)
For BACnet, port number
47808
(0xBAC0) is registered with IANA.
If there are several BACnet internetworks on an IP network, they can be separated by different port
numbers. Using several internetworks can be helpful in very large projects, for migration, and to
encapsulate sections of a plant with different reliability criteria. Since Desigo CC communicates
simultaneously with multiple internetworks, the operation is not restricted.
However, only one port number is registered for BACnet with the IANA. If additional UDP port numbers are
required, we recommend the use of port numbers 47809 to 47823 (0xBAC1...0xBACF). This does not comply
with IANA regulations. This range is reserved for future applications and should not be used. There is only
a very small chance that these ports might be used elsewhere. To avoid clashes, do not use any port
numbers from the range of dynamic or private ports. See www.iana.org/assignments/port-numbers.
BACnet Broadcast Management Device (BBMD)
The BBMD is required as soon as IP routers are used in a BACnet network. IP routers limit broadcast
messages to the local IP segment, that is, they do not allow any broadcast messages to pass through. In
order to distribute BACnet broadcast messages across IP segments irrespective of this limitation, a BBMD
is required in the relevant IP segments. If a BBMD receives a broadcast message, e.g., within the local IP
segment, it transmits this as a unicast message to all other BBMDs. The BBMDs then transmit the received
message to their own local IP segments. BACnet refers to this as two-hop distribution:
1. Hop: BBMD sends a unicast message to all other BBMDs.
2. Hop: They then distribute the message to all BACnet devices in the local IP segment.
One-hop distribution can be implemented with Direct Broadcasts. In this case the BBMD sends a direct
broadcast to all remote IP segments. This broadcast is received by all IP bus subscribers in the relevant
segment. Not all IP routers support Direct Broadcasts.
IPv6 (BVLLv6) only supports two-hop BBMD. Broadcasts are implemented via IPv6 mutlicasts. See
Ethernet, TCP/IP, MS/TP and BACnet basics
(CM110666).
BBMDs ensure that broadcast messages are distributed in a BACnet network. They are grouped by BACnet
network. A maximum of one BBMD is allowed in any one IP segment.
BACnet network #100 is separated by IP routers. The Internet also contains IP routers. This is why different
segments are shown before and after the Internet cloud. BBMDs are required so that BACnet broadcast
messages are available in all IP segments.
BBMD parameters
The BBMD parameters are written to the BBMD or (for Desigo) to the BACnet router during
commissioning. The following information is required for each BBMD in the BACnet network: