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
Superposed plant controls
5
CM110664en_07 81 | 351
Operating status monitoring is optional and monitors only blocks in a Switched on state. If a referenced
block is found to be switched off during active operating state monitoring, but that the block should have
been in the state Switched on, a process alarm is generated and the plant operating mode changes to
exception value [EcptVal].
The momentary alarm state is visible from the state flag [StaFlg].
Monitoring is active from the point when the corresponding sequence successfully completes the switch on
process, that is, the process value for block [PrVal] is not equal to Off and the transient state is completed
[TraSta] = No.
The [PrVal] of the block will be monitored. Hence, only those events which affect [PrVal] can be detected,
that is:
● Local fault shut down using interconnection of fault [Dstb] to enable safety, manual [EnSfty].
● Local shut down of the block in a higher priority application program.
● Switch-off by manual operation of the output module if the I/O module returns the manual setting
value.
● Block switched off via HMI operation or manual switch in control panel
Command control is only in a position to recognize fault-related deviations and act accordingly when the
interconnection of all relevant faults [Dstb] occur locally on a monitored output of value block to [EnSfty].
Its default value [DefVal] becomes the process value [PrVal], if a referenced output or value block is out of
02:00
01:00
00:30
1 2 3 4 5 6 7 8
00:30 01:00
02:00
Object nr.
State monitoring
Switch-on mode
Switch-on delay
Switch-off mode
Operating states
Stage X
Priority
None None None
None
Delayed
Delayed
Delayed
Delayed
On On On
Not cmd
On On
Spec. cmd
Spec. cmd
Spec. cmd
Spec. cmd
Spec. cmd
Spec. cmd
Spec. cmd
Spec. cmd
Sequence 1
Sequence 2
Sequence 3
Switch-on control of objects:
Check if switch-on time reached
Sequence 1
Switch-on procedure
completed:
Stae monitoring active
Object switch-on:
No check if switch-on
state reached
Switch-on procedure completed:
State monitoring active
Object switch-on:
Check if switch-on
state reached
Sequence 2
Sequence 3
Switch-on procedure completed: State monitoring active
02:00
01:00
00:30
1 2 3 4 5 6 7 8
Object nr.
State monitoring
Switch-on mode
Switch-on delay
Switch-off mode
Operating states
Stage X
Priority
None None None
None
Delayed
Delayed
Delayed
Delayed
On On On
Not cmd
On On
Spec. cmd
Spec. cmd
Spec. cmd
Spec. cmd
Spec. cmd
Spec. cmd
Spec. cmd
Spec. cmd
Sequence 1
Sequence 2
Sequence 3
00:30 01:00 02:00