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
Logical I/O blocks
General functions
19
CM110664en_07 239 | 351
Priority 6
Priority entry 6 is used to forward the switch commands resulting from [PrioArr] to the [PrVal] output after
a delay. This enables you to implement both switch-on and switch-off delays and minimum ON and OFF
times.
For this purpose, the internal block logic imports the Present value [PrVal] into the priority 6 entry. While
the delay times referred to above are running, priority 6 is set to active and so takes priority over priority
levels 7…16. Outside these delay times, priority 6 is always inactive.
Locating this function in the [PrioArr] between priorities 1…5 and 7…16 has the following consequences:
● Commands with a priority level of 1…5 are always executed immediately, irrespective of any currently
active delay times.
● Commands with a priority level of 7…16 are always overridden by any currently active delay times.
Unlike all the other entries in [PrioArr], the commands and information bit for priority 6 are generated
exclusively by the BO, MO, BVAL and MVAL blocks. A priority 6 entry cannot be written from an external
source.
The switch-on and switch-off delay
As soon as one of the commands with a priority of 7…16 determines the [PrVal] which will therefore cause
the present state of [PrVal] to change, the entry for priority 6 is set up as follows:
If the switch-on delay [DlyOn] or switch-off delay [DlyOff] is greater than 0:
1. Priority 6 adopts the still unchanged present value [PrVal].
2. Priority 6 is set to active.
2
5
8
14
16
15
13
9
7
6
3
1
PWR_CTL
CMD_CTL
ValPgm / EnPgm
PrVal
ValCrit / EnCrit
Desigo CC
ValOp / EnOp
BOAO MVAL
e.g. local manual
switch
Local control
e.g. anti-icing
protection
e.g. emergency stop
Priorities 1, 4, 7, 15
via data flow interconnection
Local control
General BACnet command
Life safety
Critical value
Monitoring hours
Manual operation
Program control
Priority 6
Control within block
Priorities 2, 5, 8, 14, 16
via BACnet command
Higher control