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
Control concept
Desigo room automation
5
CM110664en_07 109 | 351
● Gray: Complete building
● Blue: Façade or part of a facade
● Green: Rooms of a renter, e.g., one floor
● Orange, red: Local, manual operation
The functions are grouped into local and central functions depending on whether the function acts on one
or multiple blinds in a room, or on an entire group of blinds, e.g., on all blinds of a facade.
Grouping by local and central functions for the examples from the figure above
Local manual operation Automatic shading Wind speed monitoring Scheduler program
Central function n/a Determination of optimal
shading position in
dependence of sun
position
Measuring of wind speed
Monitoring of wind speed
Commanding of wind
protection position
Commanding of a
position in dependence of
daytime
Local function Commanding of manual
position
Positioning of blinds
Decision on which
position is commanded
automatically
Positioning of blinds
Positioning of blinds Positioning of blinds
Control concept
The control concept is based on the following:
● Grouping into autonomous functions determining a set position for the blinds
● Priority assignment to individual functions
● Evaluation of all functions and decision in favor of specific blinds position based on priorities
Overview of autonomous functions to control blinds
Priorities depend on plant requirements. The table shows the typical priorities in ascending format.
Function Description
Automatic shading Automatic determination of optimum blinds position based on current room use, solar
radiation, outdoor brightness, solar position, and HVAC status. In simple terms, this
function prevents glare in occupied rooms and uses solar energy for heating in
unoccupied rooms, or protects the building against undesired heat-up.
Manual operation (room, central) Manual operation allows users to themselves determine the blinds position via
buttons. If manual operation overrides a lower-priority function, a scheduler program
or local presence information will reactivate the function.
Presence-based influence
(room)
Locking of automatic operation upon entering a room, and activation of automatic
operation upon leaving a room. The presence-based function generally acts on the
same priority as manual operation.
Scheduler program A scheduler program opens, closes blinds at specific times, or commands them to a
specific shading position. Furthermore, automatic operation can be activated or
deactivated via scheduler program. Another priority may need to be commanded
depending on purpose. If, e.g., automatic operation should be activated at noon,
manual operation must be overridden by allowing the scheduler program to act on the
priority for manual operation. If the blinds are to be closed at night without allowing for
manual operation, a higher priority must be commanded.
Automatic shading at high priority For example, to prevent overheating it may be necessary to use automatic shading at
higher priority, which limits or prevents manual operation in certain situations.
Manual operation at high priority
(room, central)
Manual operation at high priority allows for positioning blinds and overriding low-
priority functions. For example, local operation can be overridden during, e.g., a
presentation. Or it can be ensured that neither automatic shading nor a scheduler will
drive the blinds up or down at an undesired time.