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
Views
3
CM110664en_07 31 | 351
without changing the technical structure. The UD can be used in the management platform in addition to
the TD. The detailed view in the PXM20 operator units shows the UD as information.
User Designation for Desigo room automation
You can define the user view for Desigo room automation as follows:
● Define a structure for the user view
● Copy Desigo room automation objects into the user view
● Define UDs that can be used as object names
System view
The system view shows the standard system hierarchy (BACnet view):
● Network, topology
● Device and third-party device view
● Flat representation (no hierarchy) of all BACnet objects in one device
The system view provides access to all BACnet devices (including third-party BACnet devices) and all
BACnet objects. A third-party client displays this view of a PX device.
The system view is used in the PXM20 only for third-party devices.
Program view
The engineering and program view corresponds to the XWP/ABT view. The structure is matched to the
automation station. Within an automation station, the view is program oriented: nested CFC charts
(compounds) and function block instances.
Views and users
The views reflect the differing needs of their users.
Per User Technical view User view System view Program view
1 Operator (without technical
training)
Main view Main view No access No access
2 Operator (with technical
training)
Main view Main view Occasionally No access
3 Engineer (Desigo CC), User
(PXM...)
Main view Main view Occasionally No access
4 Service engineer, Siemens
service engineer
Main view Rarely Rarely Main view
Flexible object name / device ID engineering
You can flexibly generate the object name during engineering in XWP. This is called the Free Designation
(FD). However, the FD has no inherent hierarchical structure, which makes it tedious to engineer and
lowers its helpfulness to orientate in larger buildings. It should thus be considered as a naming type for
very special purposes only.
Flexible object name engineering causes a greater engineering effort and must thus be requested
specifically by the customer.
Each BACnet object has an object name for identification on the BACnet network. This object name must
be unique within the automation station. The Technical Designation (TD) is used as default for the object
names. The TD is a technical identifier and is used to identify the plant and associated elements in the
technical view.
You can select how the object name is created for each standard BACnet object. This especially applies to
BACnet multivendor projects, where a special object name structure is required.