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 247 | 351
Trigger
In the
Trigger
setting, the source of the last command takes precedence. The valid value is written from the
[PrioArr] to the [DefVal] and transmitted to the output. The priority is then released again.
In this setting, Priorities 7…16 are treated equally; Priorities 1…5 have a blocking effect.
The trigger function is used, e.g., for the integration of LON data points. Owing to the event mechanism,
this function is not used for P-bus objects.
Switch
The
Switch
setting is used to generate an ON or OFF pulse of a predefined duration. A command via
BACnet, or the activation of an Enable signal in one of Priorities 7…16 via the data flow connection initiates
an associated pulse (event). The minimum switch-on time [TiOnMin] and/or minimum switch-off time
[TiOffMin] must be set. Setting both times can prevent fast switching operations. Priorities 1…5 have a
blocking effect.
Pushbutton with delay (time extension)
The
Pushbutton with delay
function is like the
Switch
function, except an active pulse can be extended by
another pulse at any time.
Runtimes and monitoring periods
The I/O function blocks are designed for the runtimes and monitoring periods required in HVAC
engineering, and can therefore be used directly as components (motors, dampers, fans, etc.).
Different runtimes and monitoring periods can be set, depending on the function concerned.
Runtimes:
● Switch-on/off delay
● Minimum switch-on/off time
● Ramp-up/-down time
Monitoring periods:
● Feedback time with switch-on/off
● Feedback signal deviation during operation
Runtimes
Switch-on/off delay
Blocks: BO, MO, BVAL, MVAL
The switch-on/off delay when applied to the switching I/O blocks causes a delayed output if the switch
command was written via Priority 7…16. The delay time affects Priority 6 as described. Switch commands
via Priorities 1…5 are executed without a delay.
Minimum switch-on/off time
When applied to the switching I/O blocks, the minimum switch-on/switch-off time causes the output to be
blocked for a period of time if the switch command was written via Priority 7…16. The minimum switch-
on/off time affects Priority 6 as already described in Section 24.2.1.3. However, switch commands via
Priorities 1…5 are executed immediately irrespective of the minimum switch-on/off time.
Ramp-up/down time