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 253 | 351
A maintenance message (event) can be generated either after a specified period of operation or on a
specified date. The operating hours limit value and the maintenance date [OphLm]/[MntnDate] can be
configured for this purpose. An event message is generated when the limit value is exceeded or at 13:00
hours on the preset date. At the same time, the binary output [MntnInd] (maintenance indication) is set to
active for further use in the program. After the operating hours reset, this output reverts to inactive. At the
same time, the time stamp of the last reset is stored in the time stamp operating hours reset pin
[TiStmOph].
Feedback value
The following applies to output blocks: When a feedback is configured, operating hours count is done
based on the feedback value and not based on present value.
The maintenance interval can be further connected via the output present total operating hours limit
[PrOphLm].
Value range for run time totalizing
The hours run are registered in 32-bit format, giving a maximum value of 4,294,967,296. With a resolution in
seconds, this gives a value range of over 49,000 days (more than 136 years).
Out of Service [OoServ]
The physical input/output is disconnected from the I/O block via the out-of-service pin [OoServ]. This out
of service function is normally used in cases where a hardware module is faulty or temporarily not required,
e.g., sensor not connected or faulty. This is a way of suppressing reliability problems and the associated
FAULT alarms.
Input block
If the out-of-service property of an input block is set [OoServ=True], the physical input is disconnected
from the present value ([PrVal] = [DefVal]) and any changes in the physical input will not be transmitted to
[PrVal]. Furthermore the reliability [Rlb] and status flag [StaFlg] are also disconnected from the physical
input. In this state, the properties [PrVal] and [Rlb] can be modified for test purposes.
Output block
If the out-of-service property for an output block is set [OoServ=TRUE], the physical output is
disconnected from [PrVal]. Changes in [PrVal] will not be transmitted to the physical output, which retains
its last value. Furthermore, the reliability [Rlb] and status flag [StaFlg] are also disconnected from the
physical output. In this state, [PrVal] and [Rlb] can be modified for test purposes. Other functions that
depend on these properties are not dependent on the [OoServ] property. The [PrVal] is set in accordance
with the priority array [PrioArr], but the value is not transmitted to the physical output.
Alarm and event functions
Each input, output and value block can be enabled and disabled as an alarm source. The blocks are
configured by setting the relevant values at the block pins. See Alarm Strategy.
Reliability [Rlb]
The reliability of the present value and of the physical input/output is represented by the reliability pin
[Rlb]. This makes it possible to detect and signal faults and errors, such as addressing errors, sensor
problems (short-circuit or open circuit) and module faults (missing or incorrect modules). See Reliability
Table.
Commissioning State [ComgSta]
The state of the I/O can be entered at [ComgSta], the commissioning state pin, in the commissioning
phase. The setting does not affect the program; it merely serves as a kind of notepad for commissioning
purposes.
The following states are available for selection:
● Checked
● Not Checked [DefVal]
● Periphery Defect or Missing
● Cable Defect or Missing
● I/O Defect or Missing
As these states are static, they must be set manually during commissioning.