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
Control concept and control blocks
5
70 | 351 CM110664en_07
Status monitoring
[AO, BO, MO, AVAL, BVAL, MVAL]
The process is monitored via the feedback signal, and in the case of switching blocks, also via the ramp-up
and ramp-down parameters set in [TbTiDly]. If the feedback value deviates from the present value [PrVal]
and the delay in [TbTiDly] has not yet expired, the process is in a transitional state. The status monitoring
function shows the status at the transient state [TraSta] output. This output can be used to switch on any
subsequent components.
Feedback monitoring
[BO, MO]
Monitoring feedback may be based on a data point or a purely internal to the block based on the feedback
time parameter.
● Feedback data point available [FbAddr:] = Address
Monitoring is based on the feedback signals. The delays can be defined with the time parameters for
switch-on [TiMonOn], switch-off [TiMonOff] and open-circuit [TiMonDvn]. If the feedback signal
[FbVal] deviates from the output value [PrVal], an OFFNORMAL alarm will be triggered (provided the
alarm function is switched on).
● No feedback data point available [FbAddr:] = empty
Based on the feedback time parameter [TiMonOn/TiMonOff], the output [FbVal] is delayed by [PrVal].
The output [TraSta] signals transition state.
Alarm value monitoring
[AI, AO, AVAL, BI, BVAL, MI, MVAL]
Alarm monitoring is optional and can be enabled using [EnAlm]. Analog limit or switching values can be
monitored depending on the block type. The tolerance time [TiMonDvn] to trigger a process alarm can be
set. Deviations for switch on and off procedures can be distinguished for switching blocks.
Alarm monitoring can be enabled based on the process or time. You can switch off frost protection for
monitoring in summer e.g..
Reliability monitoring
[AI, AI_RED, AO, AO_RED, AVAL, BI, BI_RED, BO,BO_RED, BVAL, MI, MI_RED, MO, MO_RED, MVAL]
The blocks monitor the reliability of input and output sources and configuration errors. A system alarm is
generated, e.g., when a source no longer communicates and the cause is displayed on output [Rlb]. The
disturbance output [Dstb] changes to yes. This output, e.g., can return to the block for the local
disturbance to achieve a more secure position using a higher priority. Reliability monitoring can be
switched off using [OoServ], which may make sense for defective or faulty hardware.
Reliability monitoring is always active for the RED blocks since no [OaServ] is available. Superposed
control does not distinguish this state and plant safety is not provided under certain circumstances.
Minimum switching times
[BO, BVAL, MO, MVAL]
The minimum time on [TiOnMin] and the minimum time off [TiOffMin] may be defined to reduce switching
frequency. For a switch on or off command, is written to [PrioArr] as priority 6 and maintained there during
the defined switching period. No lower priority can change the switching value during this time frame.
Switch-on and switch-off delay
[BO, BVAL, MO, MVAL]
To delay switch on or off for elements [DlyOn/DlyOff], e.g., to implement a pump run-on to extract residual
heat. For a switch on or off command, the corresponding switching value is written to [PrioArr] as priority 6
and maintained there during the defined switching period. No lower priority can change the switching value
during this time frame.
Ramp-up/down time
Runtimes for ramp-up and down
[BO, BVAL, MO, MVAL]