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
264 | 351 CM110664en_07
In Desigo, they are as follows:
● Physical I/Os
● Values in a Desigo room unit, accessible via the PPS2 interface
● Data in the same or in another automation station, referenced by its Technical Designation and
accessed without a connection, peer-to-peer via BACnet services.
Address prefix
The addressing syntax indicates the origin of the raw value. The syntax must correlate with the actual
physical inputs.
The prefixes for the various subsystems are as follows:
● "T=" for TX-I/O modules on an island bus-capable automation station PXC....D
● "C=" for on-board I/Os of the Desigo PX compact automation stations
● "B=" for referencing to BACnet objects
● "Q=" for QAX room units
● "L=" for LonWorks addressing
● "M=" for PX-OPEN addressing
● "D=" for PX Open Diagnostic Addressing
For addressing with "P=", see
Addressing Entries for PXC…-U, PTM and P-Bus
.
For addressing with "S=", "M=" and "D=", see the corresponding expert documentation.
For more information on TX-I/O, see
TX-I/O Assortment overview
(CM2N8170) and
TX-I/O Functions and
operation
(CM110561).
Addressing entries PX Modular (PXC100/200..D)
For PX compact, the TX-I/O module at the [IOAddr] pin start with a "T" (prefix: "T=").
Address syntax:
T= Module.I/O point (signal type)
Example: T=2.1 (Y10S)
The parameters no longer appear in the I/O address string for direct island bus integration, but rather in
the IOC (I/O configuration).
The only exception is the Info LED which must have the prefix "C=", because the fixed address, 8.1, which
is used for the Info LED may also be used by an I/O module.
The Info LED for PX KNX and PX Open can also be addressed with C=8.1.
Required address entries when using the modular series automation station in
conjunction with TX-I/O-I/O modules
Signal types shown in
italics
are used to map virtual modules for use with TX OPEN at module level. Signal
types AIS, AOS, DIS and DOS deliver a 16 bit value with status information, while signal types AISL, AOSL,
DISL and DOSL deliver a 32 bit value with status information. All other signal types deliver a 16/32 bit
value without status information.
While all the module types listed may be connected to any island bus addresses, not all module types have
16 points.
Type Module addressing I/O point
Desigo TX-I/O 1...120 1...16
PX Info LED 8 1
Module type Signal type Example
Analog Input R1K, P1K, P100, U10, I25, I420
R2500, R250 (only TX-I/O)
T1, NTC10K, NTC100K (only TX-I/O)
T=1.1 (R1K)
AI, AIS, AIL, AISL
T=2.1 (AIS)
Analog Output Y10S T=2.1 (Y10S)