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
Room automation
Desigo RXB
20
CM110664en_07 305 | 351
● Mapping RXB data to BACnet objects
● Implementing higher-level functions (grouping, time schedules, etc.)
On the BACnet side of the PX KNX system controller, the RXB controllers can be operated and monitored
from a client. Data can also be exchanged with the primary plant.
20.2.4 RXB applications
The existing Desigo RXB applications cannot be modified for a specific project by the user. These
applications are preprogrammed by groups in the controller and are selected and parameterized using the
ETS Professional commissioning and service tool.
Applications of the same type are grouped into application groups. The technical manual contains the
complete range of RXB applications.
See
RXB (KNX) Technical manual
(CM110389).
RXB application library
The RXB application library contains application groups, each of which contains applications of the same
type. The RXB application library has a version number which is defined in the RXB Valid Version Set. This
Valid Version Set also defines the version of each individual RXB application.
Application groups
Similar application types are grouped into application groups. These differ from each other in terms of how
the functions are implemented. Thus chilled ceiling with radiator (CLC02) and chilled ceiling and electric
radiator (CLC03) are two different applications within the CLC group. The first of these two applications
uses water for heating, while the second uses electrical energy. The difference between applications in the
other groups follows a similar pattern.
The following application groups are available for RXB:
● CLC Chilled ceiling applications (not for Synco)
● FNC Fancoil applications
● VAV Variable air volume applications (not for Synco)
Individual applications
The individual application is designed for typical HVAC systems as commonly used in practice in individual
rooms.
Configuring applications
Each application has a defined number of configuration parameters with which the application can be
programmed for a specific project. These parameters consist both of general values (e.g., temperature
setpoints, etc.) and of specific values for the application concerned (e.g., changeover configuration, electric
reheater, etc.).
20.2.5 Mapping RXB in the PX KNX system controller
The RXB system is mapped to the PX KNX system controller with objects. These objects are called
discipline I/Os and are components of the block library.
See
PX KNX, RXB integration – S-Mode
(CM1Y9775).
The following types are available for RXB:
● HVAC: Comprises all the HVAC information
● Shared: Contains shared data points (e.g., time schedules, occupancy status, etc.)