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 overview
Communication principles
3
22 | 351 CM110664en_07
BACnet
BACnet (Building Automation and Control Networks) is a communications protocol for building automation
and control networks. BACnet ensures the interoperability between devices from different manufacturers.
See http://en.wikipedia.org/wiki/BACnet.
VendorID
Each BACnet device has a VendorID to identify the manufacturer. The VendorID for the Siemens BACnet
system devices is 7.
BACnet over Ethernet/IP
Applications on the management level can interact via standard IT network services concurrently to BACnet
services.
Desigo supports BACnet/IPv4 and BACnet/IPv6 (via PXG3.M/L router). IPv6 to IPv4 is NOT compatible.
The parallel operation of IPv4 and IPv6 is possible with the use of a PXG3.L/M BACnet router.
See http://de.wikipedia.org/wiki/IPv6.
Network performance
The performance of the network depends on the following criteria:
● Number of devices on the bus
● Segmentation of the topology via routers (for LonTalk bus)
● Number of simultaneously active clients
● Peer-to-peer communication resulting from distributed PX applications
● Other communications services using the same transmission medium, where, e.g., office
communication on a separate VLAN share the same IP trunk
● Application download on the network
Due to these factors, which can vary widely from project to project, it is not possible to make any
generalized statements about network performance. If the specified product quantities are adhered to,
performance is adequate.
If the network performance is not satisfactory, the following actions may help:
● Use the same automation station for items of equipment with frequent process interaction.
● Divide the network into segments via BACnet router and an Ethernet/IP backbone.
● Isolate the automation station from the network when downloading an application.
BACnet and IP network structuring
BACnet supports various application services which are transmitted to all BACnet devices (broadcasts).
Global broadcasts are blocked by the IP router. BACnet solves this problem by using a BACnet Broadcast
Management Device which ensures that IP broadcasts only appear in one IP segment. The logical BBMD
functionality can be configured in every BACnet router and in every PX automation station with BACnet/IP.
One BBMD can be configured per BACnet/IP port. Devices with BBMD must have a static IP address.
BACnet over MS/TP
MS/TP stands for Master Slave / Token Passing. Each device on the link is considered the master when it
has the token. If it does not have immediate need to use the token, it passes the token along to the next
device. All devices on the link which do not currently have the token are regarded as slaves, and listen to
any messages the current master may have for it. As all devices take turns being master, the link is
effectively peer-to-peer.
Use of other network technologies
IP networks (besides the other technologies mentioned above) provide the network infrastructure Desigo
devices are connected to. In case a Desigo installation is spatially distributed (e.g., several buildings on a
campus, multiple branches in a country) the connection of these local IP networks (LANs) normally is done
using a Wide Area Network (WAN) or a point-to-point transmission line. These can be based on non-IP
technologies but typically are transparent for IP traffic. In this way, all the BACnet devices connected via an
IP network can communicate with each other.