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
248 | 351 CM110664en_07
The ramp-up/down times (run-up/-down times) can be defined in a table for each stage. These times
apply to the two switch types [SwiKind]
Normal
and
Motor
.
The ramp-up time is the time taken by a motor when changing from a lower speed to the next higher
speed, to reach the new speed. This limits the current consumption of the motor.
The ramp-down time is the time taken by the motor when switching down from a higher speed, to reach
the lower speed. This prevents feedback to the mains supply network and protects the fan belt and the
motor.
As a rule, the ramp-up and ramp-down times depend on the centrifugal mass involved, and must be
determined separately for each project.
Especially with single-speed motors, the times can be used as Open/Close runtimes (e.g., damper actuator
from 0…100%). A moving damper can thus be mapped in the system and the transition signal can, if
required, be used for control purposes.
Monitoring periods
Feedback monitoring / process value monitoring
Blocks: BI, MI, BO, MO, BVAL, MVAL
The I/O objects have a monitoring function. The output objects monitor the feedback signal from the plant.
For this purpose, an address string must be entered for the [FbAddr] feedback parameter [FbAddr] and the
alarm function must be enabled.
The input and value objects can monitor reference values. For this purpose, the relevant reference values
must be configured and the alarm function must be enabled.
Deviation monitoring
If the feedback value deviates from the output value [PrVal], a deviation alarm is generated after a
configurable time period, and the block status changes to
In Alarm
. When the two values match again, and
the configured time period has expired, the alarm and status are reset. There is otherwise no automatic
block reaction, that is, if a switch response in the plant is required as a reaction to this alarm, this response
must be programmed in CFC via the Disturbance output [Dstb].
Switch-on/off feedback monitoring
It is also possible to configure the time period during which the maximum deviation of the feedback signal
may occur after a switch-on/off operation. If the deviation persists after the monitoring time has expired,
an alarm is generated and the status of the block changes to
In alarm
. When the two values match again,
and the configured time period has expired, the alarm and status are reset. There is otherwise no
automatic block reaction, that is, if a switch response in the plant is required as a reaction to this alarm,
this response must be programmed in CFC via the Disturbance output [Dstb].
No feedback monitoring
If no feedback monitoring is required, and the address string is left blank, the monitoring periods are used
by the block for the internal generation of the transient state [TraSta]. This means that the transient state
signal for the switch-on/off operation is set for the preset period of time. This is how a moving actuator,
e.g., a damper, is displayed in the system.