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 entries for PXC…-U, PTM and P-Bus
19
CM110664en_07 281 | 351
Module type Signal type Parameters Example
Y420
AO, AOS, AOSL, AOL
- P=34.1 (Y420)
P=36.1 (AOS)
Binary Input D20, D20S
D42, D250 (only PT-I/O)
- P=25.2 (D20)
DI, DIS, DIL, DISL
- P=26.3 (DIS)
Counter Input C - P=38.1 (C)
Info LED Q_LED
PX KNX: D=1001
- C=8.1(Q_LED)
Binary Output Q250_P, Q250A_P 0, 1...600 P=12.1 (Q250_P)
Q250
QD, Q250B, (only PT-I/O)
- P=1.1 (QD)
P=14.1 (Q250)
DO, DOS, DOL, DOSL
- P=15.2 (DOS)
Multistate Input
Multistate Output
D20
D42, D250 (only PT-I/O)
Binary - Mapping P=1.1;1.2 (D20)
Updown - Mapping
1:n - Mapping
DI, DIS, DIL, DISL
Q250
Q250B, QD (only PT-I/O)
Binary - Mapping
P=7.1 (DIS)
P=1.1;1.2;1.3 (Q250)
Updown - Mapping
1:n - Mapping
Q250_P3 0, 1...600 P=1.1 (Q250_P3,120)
Q-M3
QD-M2 (only PT-I/O)
- P=1.1 (Q-M2)
P=1.1 (QD-M2)
DO, DOS, DOL, DOSL
- P=26.3 (DIS)
Signal types shown in
italics
are used to map virtual modules for use with I/O 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 P-bus addresses, not all module types have 16
channels.
Parameter values
Parameter values for the analog output, binary output and multistate output blocks:
Y10S
Failsafe function (emergency control function) if the transfer of data over the P-bus fails (for longer than 4
seconds) or in the event of a power failure. (an operating voltage of AC 24 V must be available).
NO -> Module output signal goes to 0 V.
KEEP -> Module output signal remains at previous value.
0...30 -> Module output signal 0 = 0 V, 1 = 0.33 V, etc. , … 30 = 10 V.
Y250T
1…13, 1…13 Runtime ranges for On/Off signals (the ranges do not need to be the same for On/Off). Values
1…13 correspond to the following runtimes:
1 = 8.5 ...13 seconds
2 = 13 ... 18 seconds
3 = 18 ...25 seconds
4 = 25 ...35 seconds
5 = 35 ... 48 seconds
6 = 48 ... 66 seconds
7 = 1.1 ... 1.6 minutes
8 = 1.6 ... 2.3 minutes