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
CM110664en_07 271 | 351
PPS2 addressing
A PPS2 address is required when values are to be transmitted via the PPS2 interface. Addressing takes
place via the input/output address [IOAddr] and always starts with the prefix "Q=".
Address syntax
Up to five room units can be connected to one Desigo PX automation station and addressed via the PPS2
interface. The addressing syntax is as follows:
Q=RoomUnitNumber.Object(Profile)
Example: Q=1.40 (1)
The functions available in the room unit are mapped directly to the I/O blocks. The following elements of
the address are predefined:
Type (standard BACnet objects) Room unit
number
Object Object description Profile
1
Example
Analog input 1…5 24 Setpoint correction – Q=1.24
Analog output 1…5 24 Setpoint correction – Q=2.24
Analog input 1…5 40 Room temperature 0, 1…6 Q=1.40
1
Analog output 1…5 195 Room temperature display – Q=5.195
Multistate input 1…5 205 Mode – Q=4.205
Multistate output 1…5 205 Mode – Q=2.205
Multistate output 1…5 206 Heating/Cooling display – Q=3.206
Key
1
The Profile relates to the configuration number shown in the next table.
The room unit is configured with this configuration number and appended to the Room temperature object.
Other objects are not assigned a configuration number. Only the relevant operating and process values are
mapped in the I/O blocks, rather than all objects of a room unit.
Six profiles have been defined to keep both the memory requirements and the demands placed upon the
user in practice to a reasonable level. If no profile information is supplied, the predefined device-specific
default value [DefVal] is used. As an exception in the case of the QAX units, Profile No. 5 is used.
Configuration Profile
1 2 3 4 5 6
Enable operating mode
StandBy ON ON ON ON ON ON
Auto ON ON ON ON ON ON
Fan1 ON ON ON ON ON ON
Fan2 OFF OFF ON ON ON ON
Fan3 OFF OFF OFF OFF ON ON
KonfLCD
Symbol Standby ON ON ON ON ON ON
Symbol Auto ON ON ON ON ON ON
Symbol Fan1 ON ON ON ON ON ON
Symbol Fan2 OFF OFF ON ON ON ON
Symbol Fan3 OFF OFF OFF OFF ON ON
TempUnit °C °F °C °F °C °F
This profile (or configuration number) is always valid for one room unit only. It is used to configure the
objects ConfigLCD and EnableOperatingMode and to define how the room unit is to operate (e.g., °C or
°F).