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
Addressing the I/O blocks
19
268 | 351 CM110664en_07
The multistate value from the program is converted in the Multistate Output block into a switching
command. Addressing is via [IOAddr]. For PX modular, the syntax is as follows:
Syntax: T=Module.channel
Examples:
● Q-M1: T=1.1
● Q-M2: T=1.1
● Q-M3: T=1.1
● Q-M4: T=1.1
● Q250-P3: T=10.1
● DOS: T=24.7
Values with up to four stages can be processed. The signals to be registered, which are addressed via
Module.Channel, must always be of the same hardware signal type. In the case of a multistate output on
the hardware side, there is one address only (this is only possible with PXC modular automation stations).
Error handling
If an automation station does not support a given address (e.g., incorrect syntax) or a given I/O system, this
will lead to a reliability error, which will be displayed at the [Rlb] pin.
Advanced mapping (Multistate Input)
The manual switch can be encoded on the PX Compact in various ways, e.g.:
● (Auto/Off/On) or (Off/Auto/On)
● (Auto/Off/S1/S2) or (Off/Auto/S1/S2)
So avoid having to keep adapting the data types and text groups in the system, the manual switch must
always be represented in the same way within the system:
● (Auto/Off/On)
● (Auto/Off/S1/S2)
A prerequisite for this approach is that it must be possible in the multistate input block to configure the
hardware coding and mapping to the standardized manual switch. This is made possible with parameters in
the address.
1_n-Mapping (Multistate Input and Output)
Syntax:
T = Module.channel
C=Module.channel;Module.channel;Module.channel;Module.channel (signal type, a,b,c,d,e)
a represents [PrVal] for HW-I/O (0,0,0,0)
b represents [PrVal] for HW-I/O (1,0,0,0)
c represents [PrVal] for HW-I/O (0,1,0,0)
d represents [PrVal] for HW-I/O (0,0,1,0)
e represents [PrVal] for HW-I/O (0,0,0,1)
Example: T=2.1
For the TX I/O addressing no additional information in the address string is added. All information (signal
type, mapping table, mapping rules, e.g., up-down, etc.) is configured in the I/O Address Editor and loaded
in the automation station with the IOC file.
Example: C=2.1;2.2;2.3;2.4 (D20,
2
,
1
,
3
,
4
,
5
)
[PrVal] Addr1 Addr2 Addr3 Addr4 Comment / Text
group
2
0 0 0 0 Off
1 1
0 0 0 Auto
3
0
1
0 0 Stage 1
4
0 0
1
0 Stage 2
5
0 0 0
1
Stage 3
Example: C=2.1;2.2;2.3;2.4 (D20,
2
,
1
,
5
,
7
,
9
) ;-- with holes