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 co
nfiguration
Devices
22
330 | 351 CM110664en_07
The times are slower for a restart.
The following limits and constraints must be considered if the MS/TP devices do not support COV, i.e. only
polling:
● Disable the list view core function (user profile setting in ABT Site)
● Limit to one concurrent operating client (limit your network topology)
● Set baud rate to 38400 or higher
● Only use the online trends functionality very limited
● Limit the points per graphic to 15
22.4.15.6 LonWorks limits
Use the router PXG3.L / PXG3.M with HW Index C only.
Data point integration: LonWorks devices take a lot longer than IP devices due to the lower network speed.
Reference value: Approximately 30 times longer (depending on the project setup).
To avoid timeout problems,
● Use the workflow: Data point integration.
● Integrate at the standard user level
● Avoid the "Cache" dialog
● Create templates for individual data point selection for LON devices on IP devices.
These templates can then be imported to the LON devices.
22.4.16 PXG3.L and PXG3.M BACnet routers
Item Limit Description
BDT (Broadcast Distribution Table) [50*] Max. number of BBMDs (BACnet Broadcast Management Devices)
in a BACnet internetwork. If a BACnet router is in its own IP
segment, it must be configured as a BBMD.
FDT (Foreign Device Table) [50*] Maximum number of foreign devices which can register with the
BACnet router.
Desigo CC in a remote IP segment counts as a foreign device.
Ethernet bit rate 10/100 Mbit/s The router supports 10/100 Mbps.
MS/TP telegrams [100 - 140] pkt/s
@115,200 bps
[-120] pkt/s
@76,800 bps
Max. [~4,5] KB/s
The BACnet router integrates BACnet MS/TP not as a field bus in
the network. The router operates transparently and routes all data
traffic addressed to the subnet. This is why global broadcast
telegrams negatively impact transmission performance of the
router and end devices.
Recommendation: Do not carry out time and security-critical
process controls using BACnet MS/TP.
Depends on baudrate, number of nodes and maximum number of
data frames (N max_info_frames).
BACnet/LonTalk [100 - 120] pkt/s
@78 KB/s
Max. [~4,5] KB/s
The BACnet router integrates one (1) BACnet/LonTalk network.
The router operates transparently. The same restrictions apply to
global broadcast telegrams as for MS/TP.
BACnet/IPv4 [~2500] pkt/s
Max. [~500]
KB/s
The BACnet router can route between two BACnet/IP networks.
The BACnet/IP networks have different UDP ports.
BACnet/IPv6 1 The BACnet router integrates one (1) BACnet/IPv6 network. The
router works transparent, but when connection ports for
BACnet/IPv4 and BACnet/IPv6 are used simultaneously, make sure
that no unintentional ethernet loops are created on the IT side.