Desigo™ Building automation system 6.
Copyright Copyright Delivery and technical specifications subject to change. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this document is strictly prohibited unless permitted expressly. Infringements will lead to compensation. All rights, including rights created by patent grant or registration of a utility model or design are reserved. Published by: Siemens Switzerland Ltd.
Table of Contents 1 Cyber security disclaimer ........................................................................ 9 2 Preconditions of this document ............................................................ 10 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 System overview .................................................................................... 11 Management level ............................................................................................ 12 Automation level..................
| 353 8 8.1 8.2 8.3 8.4 Events and COV reporting ................................................................... 126 Sources and causes of system events ........................................................ 126 Routing system events .................................................................................. 126 Sources and causes of COVs ....................................................................... 127 COV reporting.................................................................
16.1 16.2 16.3 16.4 16.5 16.6 16.7 16.8 User functions ............................................................................................... 208 Main components.......................................................................................... 211 Access and security ...................................................................................... 212 Event management .......................................................................................
22 22.1 22.2 22.3 22.4 System configuration........................................................................... 311 Technical limits and limit values ................................................................. 313 Maximum number of elements in a network area ..................................... 314 Desigo room automation system function group limits ............................ 316 Devices.........................................................................................................
23.3 Desigo Control Point ..................................................................................... 340 23.3.1 Compatibility with earlier systems.............................................. 340 23.3.2 Compatibility with earlier devices ............................................... 340 23.3.3 Supported browsers...................................................................... 341 23.4 Upgrading from Desigo V6.2 Update (or Update 2) to V6.2 Update 3 ... 342 23.4.
Cyber security disclaimer 1 1 Cyber security disclaimer Siemens provides a portfolio of products, solutions, systems and services that includes security functions that support the secure operation of plants, systems, machines and networks. In the field of Building Technologies, this includes building automation and control, fire safety, security management as well as physical security systems.
2 Preconditions of this document 2 Preconditions of this document IT security Building automation and control systems such as Desigo are increasingly integrated into a building's IT infrastructure and will often also be remotely accessible. Besides using the IT security features of the various products, it's very important to implement an IT secure integration into the site's IT infrastructure. For guidelines for such an IT secure integration, see IT Security in Desigo Installations (CM110663).
System overview 3 Management level 3 System overview The Desigo building automation and control system has three levels: ● Management level ● Automation level ● Field level Management level Management platform Desigo CC Desigo Control Point Automation level Desigo PX System controller Automation stations BACnet/IP Room automation Desigo Room Automation Desigo RXB KNX Field level Sensors Valves CM110664en_07 Symaro Acvatix 11 | 353
3 System overview Management level 3.
System overview 3 Management level Management platform Desigo CC can be installed on one computer, with full server and client functionality, or on several separate computers. Web Clients, Windows App (ClickOnce) Clients and installed Clients can be added. Remote management Desigo CC can operate and monitor the automation level via a public network.
3 System overview Automation level 3.2 Automation level The Desigo PX automation system meets all the requirements for the control and monitoring of heating, ventilation, air conditioning systems and other building services. Desigo PX with its programmable automation stations and graded range of operator units is a scalable and open system.
System overview Automation level 3 ● Up to 52 physical I/Os ● Integration of up to 5 subsystems, such as Modbus, M-bus, with up to 400 data points PX Open PX Open system controllers let you integrate third-party devices via Modbus, M-Bus, KNX and other protocols. System functions, such as alarm management, time schedules, trend data storage and flexible programming are available.
3 System overview Room automation 3.3 Room automation The room automation is part of the automation level. The room automation includes devices for the control functions within a room. There are RX room controllers and Desigo PXC3/DXR2 room automation stations.
System overview Field level 3 The room automation stations communicate with each other and other system components via BACnet/IP (DXR2.E…) or BACnet MS/TP (DXR2.M...). The room automation stations support different I/O mixes, protocols (KNX SMode and KNX PL-Link for IP and KNX PL-Link for MS/TP) and power supplies (240/24V). Operating devices, buttons, sensors, and actuators for lighting and shading can be connected to the room automation stations via KNX PL-Link.
3 System overview Desigo Open See Engineering Instructions Document (A6V11572317). Compound The most sophisticated solution for new projects is provided with Desigo V6.2 Update because it supports the complete workflow including the new Compound {IngtVlv1} for the Desigo PX Primary controllers. This compound offers a pre-engineered solution representing the most important datapoints, a trending of selected datapoints and an evaluation of the Intelligent Valve error indication used for alarming.
System overview 3 Workflow and tools Integration on the automation level PX Open system controllers let you integrate third-party devices on Modbus, M-Bus, KNX and other protocols, by converting all data into standard BACnet objects. Integration on the field level TXIx.OPEN lets you integrate third-party systems, such as M-Bus meters, pumps (Grundfos, Wilo) and variable speed drives (Siemens G120P), and connect intelligent aggregates, e.g., chillers, via the Modbus protocol. 3.
3 System overview Topologies 3.7 Topologies Small system on BACnet/IP Web client Desigo Control Point @ BACnet/IP Ethernet PXC50/100/200-E.D PXC12/22/36-E.D DXR1 Modular Compact TXM1 TXI... TX Open TX-I/O- iValve PXG3.W100/200-1 Web interface Third-party integration Small system on BACnet/LonTalk Desigo Control Point BACnet/LonTalk PXC12/22/36.D Compact PXC50/100/200..D Modular TXM1 TXI...
System overview 3 Topologies Medium system Desigo CC Desigo Control Point Web client BACnet/IP Ethernet DXR1 PXC 12/22/36-E.D TXI... PXC50/100/ 200-E.D Compact PXG3.L Router TX Open PXG3.W100/200-1 PXC001-E.D PXC001-E.D Web interface System controller System controller Modular iValve LONWORKS Third-party integration Third-party integration Third-party devices PXM30/40/50 Touch panel DXR2.E... Room automation BACnet/LonTalk KNX °C °C QMX3 Room units PXC12/22/36.D AQR25..
3 System overview Communication principles The primary server carries out system functions, such as time synchronization, life check and the distribution of global data: ● Time synchronization: The primary server distributes the current time to the backup devices. ● Life check: The backup servers detect the failure of the primary server and the primary server detects the failure of the backup servers. If a server fails, an alarm message is sent.
System overview Communication principles 3 ● Other communications services using the same transmission medium, where, e.g., office communication on a separate VLAN share the same IP trunk ● Application download on the network Due to these factors, which can vary widely from project to project, it is not possible to make any generalized statements about network performance. If the specified product quantities are adhered to, performance is adequate.
3 System overview Communication principles BACnet server BACnet client D-MAP program Process and configuration data Application process (Visualisation) 10660Z37_01_en BACnet objects BACnet protocol BACnet standard device profile The BACnet standard defines several device profiles that simplify to judge (and test) a device's capabilities against a specified function set.
System overview Data maintenance 3 For performance reasons, we do not recommend the operation of LonWorks and BACnet devices on the same LonTalk cable. 3.9 Data maintenance A running Desigo system contains various categories of data, each with different requirements in terms of consistency, period of useful life and visibility. The data is distributed throughout the system, with each category having a unique origin. There is no central data maintenance in the Desigo system.
3 System overview Data maintenance All parameter settings are non-volatile, that is, they are retained in the event of a power failure. Readback All non-volatile PX process data and parameter settings can be read back into XWP. However, parameter settings in the operator unit cannot be read back into a tool. Global parameter settings Some parameter settings are identical in all automation stations, e.g., date and time, calendar function blocks and Notification Class function blocks.
System overview 3 Data maintenance D-MAP program The D-MAP program is an executable program, and contains instances of the function blocks with the associated process data and parameter settings, the configuration and description data and the interconnection and order of processing of function blocks. The D-MAP program can be modified during operation either by reloading the complete program including any changes, or by delta (differential) loading. Delta loading only reloads the changes.
3 System overview Data maintenance ● Library to monitor primary plants ● Library for collaboration between Desigo PX and Desigo room automation ● ABT library (Desigo Room Automation Solution Library) LibSet version number and LED When a LibSet version number is released (new LED), the incremental part of the version number is increased accordingly, e.g.: Desigo-LibSet-HQ-410080-10 > Desigo-LibSet-HQ-410080-20 The remaining numerical values in the decade (e.g.
System overview 3 Data maintenance LED Description LibSet version number Date LED16 PXC: CAS21 (HVAC) Desigo-Libset-HQ-500204-10 March 2012 Desigo-Libset-HQ-500260-10 October 2012 Desigo-Libset-HQ-510xxx-10 Summer 2013 Desigo-Libset-HQ-51SPx-10 March 2014 Compound for Desigo room automation demand signals, compounds for pumps and fans based on PTM16.
3 System overview Data maintenance LED Description LibSet version number Date LED 22 PXC: CAS26 Desigo_Libset_LED21-HQ510212-10 May 15 Desigo-Libset_LED23-HQ600xxx-xx August 15 Desigo-Libset_LED24-HQ610172-10 July 17 Fits with Desigo V6.
System overview Views 3 Desigo CC The application libraries for Desigo CC are delivered as extension modules for the respective system versions. For information about compatibility, see Desigo CC System Description (A6V10415500). 3.
System overview 3 Views You can define the user view for Desigo room automation as follows: ● Define a structure for the user view ● Copy Desigo room automation objects into the user view ● Define UDs that can be used as object names System view The system view shows the standard system hierarchy (BACnet view): ● Network, topology ● Device and third-party device view ● Flat representation (no hierarchy) of all BACnet objects in one device The system view provides access to all BACnet devices (including
System overview 3 Views Flexible name selection (TD, UD, FD) for each object Technical Designation (TD) B’Ahu10'TSu ObjectName = TD B’Ahu10'TSu User Designation (UD) Areal_Geb1'L10-B01 ObjectName = UD Areal_Geb1'L10-B01 Free Designation (FD) My’’Crazy/Name1 ObjectName = FD My’’Crazy/Name1 Defaults and rules The following defaults and rules apply when you engineer the object name in the XWP Hierarchy Viewer: ● The Free Designation (FD) can be max.69 characters.
4 Desigo workflow, tools and programming Coverage of the technical process 4 Desigo workflow, tools and programming The Desigo tools cover parts of the technical process and parts of the Desigo system.
Desigo workflow, tools and programming 4 Coverage of the technical process USA Sales Planning STST • DCM • Engineering Installation Commissioning Service ABT • • • • Apogee tools • • • • Desigo tool set • • • Sales DCM supports system design and quantity determination during the sales process. Price calculation, offer preparation and tracking, and invitation of tenders are supported by country-specific tools.
4 Desigo workflow, tools and programming Coverage of the system ● ● ● ● Commissioning of the systems (loading programs, program function test) Online trending during commissioning Diagnostics during commissioning Parallel working of several commissioning engineers in the project Service XWP and ABT allow the following: ● Data access to Branch Office Server (central engineering data management of the regional companies) ● Data security (reading system data in the engineering database) ● Remote engineerin
Desigo workflow, tools and programming 4 Coverage of the system Management Functions Desigo CC Desigo CC Desigo CC GG BACnet router Desigo XWP Project Manager Automation Functions PXC..D PXC modular + TX-I/O modules PXC compact Network Configurator Point Configurator Utilities Desigo Configuration Module CFC incl.
4 Desigo workflow, tools and programming Main tasks Management Functions Desigo CC Desigo CC Desigo CC GG System Functions Desigo XWP PXCx00-x.D Project Manager Point Configurator Desigo Configuration Module CFC Utilities Network Configurator Hierarchy Viewer Report Viewer Desigo Room Automation ABT DXR2 PXC3 TX-I/O modules ABT SIte ABT Pro ETS KNX PL-Link VAV FNCL Switch Presence QMX3 KNX S-Mode > ABT-SSA for KNX PL-Link > ABT-SSA/ETS for KNX S-Mode DALI DALI > ABT-SSA for DALI 4.
Desigo workflow, tools and programming Main tasks 4 Sales support Desigo Configuration Module (DCM) supports the calculation of the Desigo configuration for the sales process.
4 Desigo workflow, tools and programming Main tasks Standard High flexibility Level Description Library Example Engineering effort A Solution Browser in XWP Locked CAS solutions AHU10 Low B Solution Configurator CAS solutions, in CFC, CAS library aggregates, components AHU10, fan, valve C CFC programming, CFC library Charts, blocks CAS library with charts D CFC programming, solution creation Charts, blocks, LMU RC library (Library Maintenance Utility), simulation E CFC programming,
Desigo workflow, tools and programming 4 Main tasks Level E This level offers full flexibility, but requires detailed knowledge of the application's structure and the programming tools. You must ensure that the functions of the program work. You must ensure that the programs you develop fit together with all elements in the library and that they are well tested and documented. You must take care of the compatibility, the versioning and the library packaging.
4 Desigo workflow, tools and programming Tools for different roles ● Local documents (work documents, simple templates, Excel exports) can be used to, e.g., verify results. You can, e.g., export them to Excel and add additional data to them. ● Project documentation (template with logo, author, table of contents, etc.) can be attached to the customer documentation either in printed form or as a PDF.
Desigo workflow, tools and programming 4 Working with libraries Tool Tasks Application / Adv.
4 Desigo workflow, tools and programming Workflow for primary systems make changes to the same automation station. This way no inconsistent data can be created. To quickly transfer project data, the data is compressed before it is sent from the computer to the server. The data is managed on the Branch Office Server. The project creator transfers the data from his local hard disk to the server. In large projects the data can be moved in two steps: 1.
Desigo workflow, tools and programming 4 Workflow for room automation classic ● Create project ● Check project in on Branch Office Server (BOS) and define access to project ● Define project defaults ● Create control cabinet topology (local specification of the automation station, e.g.
4 Desigo workflow, tools and programming Workflow for Desigo room automation 4.
Desigo workflow, tools and programming 4 Desigo Configuration Module (DCM) Field of application DCM calculates the required materials for an installation from raw system data, such as data points, panels, and building and plant structures. You can use DCM to conduct analysis of variants after defining and completing the installation structure by generating copies and then subsequently changing the hardware specifications.
4 Desigo workflow, tools and programming Desigo Xworks Plus (XWP) 4.11 Desigo Xworks Plus (XWP) You can edit project data in the Xworks Plus Editors. See Getting Started: Desigo Xworks Plus (CM110629). Xworks Project Manager The Xworks Project Manager lets you: ● Create, open and archive projects ● Check in/out project data for parallel engineering from the Branch Office Server (BOS) ● Define PXC automation stations, control units and Desigo CC.
Desigo workflow, tools and programming 4 Desigo Xworks Plus (XWP) The Solution Browser lets you select and configure a plant. ● The tree view shows all selected objects of the plant. ● The configuration view shows all possible options and variants for the selected object. ● The data point window shows all I/Os of the selected object. You can configure I/Os and I/O modules and connect I/O channels with the I/Os. You can design the integration of the room automation and the third party integration.
4 Desigo workflow, tools and programming Desigo Xworks Plus (XWP) The Xworks Hierarchy Viewer shows the technical hierarchy per PX and the technical hierarchy as it is shown, e.g., in the generic view in Desigo CC. You can define the user designation (UD) and the free designation (FD). You can define the structure of the user designation with the field lengths and the separators and assign the data points in the structure of the user designation.
Desigo workflow, tools and programming Desigo Xworks Plus (XWP) 4 ● Carry out commissioning ● Test programs ● Create documentation: data point lists, device plaques, commissioning lists, print parameter lists, etc. CFC Classic editor The CFC Classic editor (Continuous Flow Chart) is a graphic tool tor creating plans. The CFC Classic editor lets you create and change programs. A CFC plan consists of function blocks and connections.
4 Desigo workflow, tools and programming Desigo Automation Building Tool (ABT) You can select one or more automation stations for the documentation, per automation station, plant or system node. You can select document templates and verify reports in a preview. Desigo Point Test (DPT) Desigo Point Test lets you test data points during commissioning of a Desigo PX automation station.
Desigo workflow, tools and programming Desigo Automation Building Tool (ABT) 4 Office Server (BOS) using Xworks Project Manager. XWP is also used in the Desigo room automation project to carry out the network check and to create the network documentation. Some project reports, which also encompass the Desigo room automation stations are created in XWP. ABT Site > Projects In ABT Site > Projects you create projects and define project settings.
4 Desigo workflow, tools and programming Programming in D-MAP ABT Site > Configuration In ABT Site > Configuration you configure preloaded application types or project-specific types. ABT Site > Startup In ABT Site > Startup you scan networks, load configurations and read back parameters. ABT-SSA In ABT-SSA (Setup & Service Assistant) you commission I/Os and carry out the point test. See Desigo TRA - Setup & Service Assistant (CM11105).
Desigo workflow, tools and programming Programming in D-MAP 4 XWP XWP is the programming tool for the PX automation station and incorporates all system elements. XWP shows the structural view of the system with the plant, partial plant, aggregates, and components, and, e.g., the compound functional unit for a valve.
4 Desigo workflow, tools and programming Programming in D-MAP The program view describes the basic concepts and elements for programming for Desigo room automation: Libraries, CFC charts, blocks, variables, data types, configuration extensions and attributes. In Desigo room automation, a program contains the application function (e.g., the lighting function), the associated CFC charts (e.g., the chart for manual control), and the I/O blocks (e.g., the luminaries and buttons).
Control concept Programming in D-MAP 5 5 Control concept Supply chain model In building automation and control, media, such as warm water, cold water, warm air, and cold air are generated using energy, such as oil, gas, and electricity, and distributed to consumers. Each medium can be assigned a supply chain. The supply chain starts at the generation or handling of the medium. The distribution system then transports the medium to one or several consumers.
5 Control concept Programming in D-MAP A tree structure opens to the right for the individual supply chains. In other words, one or more generators supply multiple primary controllers and each primary controller for its part supplies one or more consumers or other primary controllers. From the air supply chain point-of-view, air treatment is a part of production (handling). From the hot water and cold water point-of-view, air treatment (or air heater/cooler) belongs to consumption.
Control concept Programming in D-MAP 5 Producer In practice, however, there are often multiple producer units, e.g., boilers with the same or similar power, or a mixture of different units, e.g., boiler combined with a solar plant and cogeneration plant (usually with additional storage units).
5 Control concept Programming in D-MAP Supply chains for a room You can define different consumer needs for a room, such as heat, refrigeration and fresh air. Heat demand The hot water supply chain exists for heat demand. The medium hot water is prepared in hot water generation and distributed via a heating circuit. The heat is emitted to the room as needed via a heating surface. If air is the carrier of heat, this is done via pre-control and air posttreatment.
Control concept Programming in D-MAP 5 Plant A plant consists of partial plants, aggregates, and components, which, as a rule, form a supply chain with the chain links producer (here: boiler), distributor (pre-control, heating circuit), and consumer (radiator). Operator interventions Commands are executed at each link of the chain through operating interventions via HMI commands. The impact on the plant (or the process) takes place via the corresponding function unit and automation station.
5 Control concept Control concept and control blocks 5.1 Control concept and control blocks The Desigo control concept is a set a rules that determine in general terms the principles governing all control, reporting and monitoring operations and the switching interventions in the Desigo system. The rule applies to block-internal control (priority array) and to functional interactions among participating blocks.
Control concept Control concept and control blocks 5 Standardization of control functions Moreover, plant security and available was increased through standardized control and monitoring functions which would result in considerable expense using conventional methods.
5 Control concept Control concept and control blocks control hierarchy is subject to certain rules. A distinction is drawn between higher-level plant control and local control of the functional units. Superposed control Within the hierarchical structure, higher-level control functions are typically assigned to the partial plant level. All the variables which are influencing factors on the overall plant are weighted and combined to give the effecting plant operating mode.
AO E,H DefVal:Off En BVAL PrVal FbVal En BO Frost EnPgm PrVal TOa ValPgm OpSta En TSu EnSfty En KickDmp ValSfty En On MI E,H AO BVAL En On En E,H M Frost BO Sequence table En OpMSwiCnv Ax: DMUX8_BO EnPgm PrVal On Dstb PrVal FbVal OpModSwi Cp:MI KickDmp MVAL ValPgm OpSta E,U BI EmgOff On En MI ManSwi Cp:Ml E,U BI En SmextEh DmpShofOa Ag.
5 Control concept Control concept and control blocks Main functions and interfaces of I/O blocks Function Inputs Description Stop transmission of input signal OoServ Out of service Priority mechanism DefVal AI AVAL BI • • • • • • • • • • • • • • • • • • • • • • • • Upper limit • • • LoLm Lower limit • • • Nz Neutral zone • • • RefVal(s) Reference value • • • • • TiMonOn Monit. time switch-on • • • • • TiMonOff Monit.
Control concept 5 Control concept and control blocks Function Inputs Description Stop transmission of input signal OoServ Out of service DefVal Default value • • • Priority mechanism PrioArr Priority array • • • Local override Ovrr Override • • • OvrrVal Override value • • • EnAlm Alarm enable HiLm Upper limit - Reference values LoLm Lower limit - Monitoring periods Nz Neutral zone RefVal(s) Reference value TiMonOn Monit. time switch-on TiMonOff Monit.
5 Control concept Control concept and control blocks Level Application Description Safety level Life safety The safety level is assigned the highest priority and is used for the protection of people and equipment. This is where local safety switches and emergency OFF buttons are wired or superimposed commanded, e.g., smoke extraction control or frost control.
Control concept 5 Control concept and control blocks Feedback monitoring [BO, MO] Monitoring feedback may be based on a data point or a purely internal to the block based on the feedback time parameter. ● Feedback data point available [FbAddr:] = Address Monitoring is based on the feedback signals. The delays can be defined with the time parameters for switch-on [TiMonOn], switch-off [TiMonOff] and open-circuit [TiMonDvn].
5 Control concept Local control design The runtime of a damper or the coasting time for a multi-speed motor can be defined in table [TbTiDly] to display or evaluate a transient state [TraSta]. The time parameter can also influence the switching response depending on the switch kind [SwiKind] used. Plant fault The block independently recognizes faults and reports them to the defined alarm class [AlmCl], which for its part is responsible for distributing the alarms to alarm receivers.
Control concept 5 Local control design P15 Pgm Off Ort Ax:OR Dstb P4 Crit CritActv PrVal 13. ValCrit 12. EnCrit 15: ValPgm 14: EnPgm wired output [Dstb]. The pump can only be switched on again only after the fault is eliminated and the alarm message is reset as required. The following figure shows a local fault-related shutdown related to superposed plant control. The compound mapped here as an example was reduced to make is easier to recognize the structure of the local control.
Control concept Val En Val En TraSta SftyActv CritActv PfmActv Dstb Val En E,H Damper Cp:BO Off Val En Val En Val E,H PfmActv Dstb TraSta P4 Crit P15 Pgm PrVal Val P4 Crit SftyActv En Val En OpMod [On/Off] Yes PrVal P15 Pgm CritActv En OpMod [On/Off] Local control design Yes 5 Fan Cp:BO Local interlocks A command to ramp-up the plant [OpMod] =On, the damper output changes to [TraSta] = Yes, indicating that a transient state is now active, in other words, the damper is mov
Control concept 5 OpSta EnCrit Open ValCrit BACnet Reference Superposed plant controls ValCrit FanSu Ag: Fan1St EnCrit OpSta DmpShofOa Ag: DmpShof The operating state [OpSta] for both aggregates are formed within the compounds as illustrated in the previous example from the AND link for [PrVal] and [TraSta]. 5.
5 Control concept Superposed plant controls Determining plant operating mode A superposed plant control generally has different sources such as plant switch, scheduler program or important fault messages, from which the resulting plant operating mode must be determined. The ENSEL_MS (Enable Selector Multistate) and ENSEL_BO (Enable Selector Boolean) blocks are available for evaluating the resulting plant operating mode in the firmware library of Desigo.
Control concept 5 Ccl Ag: CclT PltCtl Cp: CMD_CTL Superposed plant controls Tsu DmpShofEh Ag:DmpShof FanSu Ag: V(A,C-F) Fan1St On On En En DmpMx Ag: DmpMx Sequence table On On Frost DefVal:Off SttUpMod Cp: V(A) StupPrg En En En O&M En En On TOa E,H OpMSwiCnv Ax: DMUX8_BO On TSu OpModMan Cp:MVAL_OP TOa Sched Cp:BSCHED TSu OpModSwi Cp:MI En EmgOff On/P14 DmpShofOa Ag.
5 Control concept Superposed plant controls switch-on sequence. Independent switch-on and switch-off sequences are not implemented in this block. Switched on block can be monitored for their states. There is no monitoring of the OFF status. Prior to switching on a block a test is made to see if the conditions for executing a command are given. The switch-on process is not even available for active switch on delay, minimum switch off times or a switch command with a higher command (e.g.
Control concept Superposed plant controls Stage Function Action 1 Safety function Check AllLifeSafety plant operating modes. 2 Preview Checks if the aggregates in question can be switched. 3 Abort sequence Incomplete sequences are interrupted. 4 Reset sequence Switch off unneeded aggregates. 5 Step-up sequence Switch on the newly needed aggregates. 6 Monitor switch-on states Start monitoring of countdown of delay period.
5 Control concept Superposed plant controls Step 3: Abort sequence On-going switch sequences are aborted when delay times are still active. Exception: An alarm is generated when a fault occurs as part of internal monitoring of the block. The demanded plant operating mode is determined in this cased by the exception value [EcptVal]. If the switch sequence is active, but not completed, it is NOT aborted, but rather is completed.
Control concept Superposed plant controls Sequence 1 1 Object nr. Sequence 2 2 3 None State monitoring 5 Sequence 3 4 5 None None 6 7 8 None Delayed Switch-on mode 00:30 Switch-on delay Switch-off mode 01:00 02:00 Delayed Delayed Delayed 02:00 01:00 00:30 Operating states On On Spec. cmd Priority Switch-on 1 On Spec. cmd Not cmd Spec. cmd Switch-on 2 Spec. cmd Spec. cmd Sequence 1 Stage X Switch-on 3 On On Spec. cmd Spec. cmd Spec.
5 Control concept Superposed plant controls Switched on, a process alarm is generated and the plant operating mode changes to exception value [EcptVal]. The momentary alarm state is visible from the state flag [StaFlg]. Sequence 1 Object nr. 1 State monitoring Sequence 2 2 3 None 4 5 None None Switch-on mode 6 7 8 None Delayed Switch-on delay Switch-off mode Sequence 3 00:30 01:00 02:00 Delayed Delayed Delayed 02:00 01:00 00:30 Operating states Stage X Priority On Spec.
Control concept Superposed plant controls Sequence 1 1 Object nr. Sequence 2 2 3 None State monitoring Sequence 3 4 5 None None Switch-on mode 5 6 7 8 None Delayed 00:30 Switch-off delay Switch-off mode 01:00 02:00 Delayed Delayed Delayed 02:00 01:00 00:30 Operating states On On Switch-off 8 Spec. cmd Spec. cmd Switch-off 7 Spec. cmd Spec. cmd Sequence 1 Spec. cmd Priority Switch-off 6 Spec. cmd Spec. cmd Spec. cmd Objects 8, 7 and 6 are switched off in parallel.
5 Control concept Superposed plant controls The block is not alarmable for Desigo 7. Out of service The block can be taken out of commissioning using [OoServ]. The following occurs when switching [OoServ] to On: ● Immediately abort of switch on and off sequences and monitoring.
Control concept Superposed plant controls 5 Plant Control Editor The block parameters are set using the Plant Control Editor. The upper part of the dialog box serves primarily to provide a quick online overview of the block. The maximum power controlled by the block is set with the maximum power parameter [MaxPwr]. The value must be greater than 0 kW in order for the block to work. Any changes in this limit value have a direct effect in online mode.
5 Control concept Superposed plant controls output [PrPwr] is switched in accordance with the power profile in the new profile table. The profile definition determines the order in which individual aggregates are to be switched on or off. The following information must be entered for every sequence entry: ● Object: Selected from the previously referenced aggregates. ● Stage limitation: Limit up to which the aggregate may be enabled.
Control concept Superposed plant controls 5 Power display The block has two outputs at which it displays the current total power of the energy producers. This consists firstly of the controlled power output [CtldPwr]. This output represents the total power switched by the PWR_CTL block. The other output, the present power output [PrPwr], shows the additional power output of energy producers that are not directly switched by PWR_CTL.
5 Control concept Superposed plant controls The power data in the object table and the sequence entries in the profile table in Figure Example of aggregate table together give the power profile illustrated in Figure Example of profile entries with a drop in power (Profile 2). Profile 1 In the main application of the PWR_CTL function, a new energy producer is added for each sequence entry in the profile table. For this purpose, an aggregate only needs to be entered in the sequence table once.
Control concept Superposed plant controls 5 Profile 2 Profile 2 shows that the order in which boiler stages are to be enabled has been changed, and that sequences which will cause a drop in the power output have been defined in the power profile. In the example illustrated, Boiler 3, which is currently delivering 200 kW, is switched OFF via sequence entry 2. Boiler 1, which could achieve a power output of 150 kW with its enabled stages, is defined as the next object in the sequence.
5 Control concept Closed-loop control strategy Online diagnostics A diagnostics screen for the PWR_CTL block is available online in Xworks Plus (XWP). The following states are displayed: ● Present value: Operating state at the block output pin [PrVal] ● Action: Transient state [TraSta] depending on actual switching conditions: Up, down or hold ● Present power: Value at the block output pin [PrPwr] ● Status flag: In accordance with the BACnet definition, the value of [StaFlg] is always Overridden.
Control concept Closed-loop control strategy 5 ● Programmable offset (for P and PD controllers) ● Programmable initial integrator value (for PI or PID controllers) ● Programmable runtime for control variable (0 – 100%, 100 – 0%) and positioning speed ● Type of operation (direct acting or reverse acting) can be selected A sequence controller can be implemented by interconnecting several PID_CTR blocks. The sequence linker SEQLINK can also be used, where appropriate.
5 Control concept Closed-loop control strategy Neutral zone [Nz] measured value [Xctl] is less than half of the [Nz], the output is driven for a further 7 cycles, so that the measured value [Xctl] is as close as possible to the middle of the [Nz]. The output signal [Yctr] then remains constant. The output signal is only re-adjusted when the parameters move outside the [Nz] again.
Control concept Closed-loop control strategy Inversion [Inv] 5 [Inv] of the output signal is required, e.g., for air dampers. The outside air and exhaust air damper must close in response to an increasing heating demand. The inversion of the manipulated variable affects only the output signal [Yctr] and not the action of the controller. Sequence controller Sequence controllers are used primarily in ventilation and air conditioning systems to control the temperature and humidity.
5 Control concept Closed-loop control strategy ● ● ● ● ● ● ● temperature) or equivalent to the setpoint of the first cooling element (if the extract air temperature is lower than the outside air temperature). The gain of each sequence element can be influenced individually. In this way, e.g.
Control concept 5 Closed-loop control strategy The lowest sequence-controller element (Low) corresponds to control sequence 1, and the highest (High) to control sequence n. The lowest sequence-controller element controls a reverse-acting aggregate (if used). The type of operation may also be reversed during normal operation, (e.g., for energy recovery) but the order of the sequences must not be affected.
5 Control concept Closed-loop control strategy The connection is made between the pins of block PID_CTL and a location on the SEQLINK block. The order in which the PID_CTR blocks are connected must be the same as that of the sequence. The connections to the SEQLINK block need not be continuous: connected pins and unused pins may be interspersed. For example, 1 = Re-heater, 2 = Pre-heater, 3 = Dampers, 6 = Cooling coil.
Control concept Closed-loop control strategy 5 Cascade control The CAS_CTR block integrated into the Desigo system is a PI master controller for room supply air cascade control. It delivers three supply air set points on the basis of the difference between the measured room temperature and the room setpoint.
5 Control concept Desigo room automation To save energy in the ventilation plant, various room set points are selected for different types of air handling (heating/cooling and humidification/dehumidification). The master controller in the cascade must therefore be able to generate different supply air set points, depending on how the kind of air treatment (heating/cooling or humidification/dehumidification).
Control concept 5 Desigo room automation coordination of the individual technical installations must be optimized while considering that the same type of installation may exist several times in one room. Room featuring: 1. HVAC zone (blue) 2. Lighting zones (yellow) 3. Shading/blinds zones (green) 3 3 2 1 2 HVAC zone The room typically is considered 1 HVAC zone influenced via a common automation and control strategy regardless of number and type of installed HVAC plant components (e.g.
5 Control concept Desigo room automation ● Cross-technical installation coordination to ensure smooth functional interplay of the various installations ● Centralized, room-wide access point to operate and monitor a room Cross-technical The application functions of the individual technical installations contain installation coordination functionality required for technical installation-specific control.
Control concept Desigo room automation 5 HVAC room control HVAC plants and their HVAC devices in the room influence the climate in closed rooms.
5 Control concept Desigo room automation An HVAC control application in the room is connected to the following: ● HVAC plant in the room via sensors and actuators ● Room coordination application ● Centralized coordination application for HVAC supply chain(s) ● Building operator via BAC workstations ● Building automation and control functions for scheduling ● Room user Supply Chain Functions HVAC control structure Room Coordination User Request HVAC Plant Control T WndCont PscDet The HVAC control a
Control concept Desigo room automation Heating nor 5 Cooling 100% 0% TREff Speed 3 Speed 2 Speed 1 FanSpdMin=Off TREff SpH SpC Individual temperature sequence controllers are assigned to each heating and cooling element. They intercommunicate to achieve required sequencing. Open-loop control Additional interactions between HVAC devices implemented via open-loop control functions are required in an HVAC plant in the room.
5 Control concept Desigo room automation The following illustrations show sequence control for an HVAC plant in the room for operating modes Comfort and Economy. Sequence control acts on heating and cooling equipment and a multi-speed fan.
Control concept 5 Desigo room automation Plant operating mode Fan operating mode Heating coil operating mode Cooling coil operating mode Economy Modulating Two-position Two-position Protection Modulating Two-position Off Heat up Modulating Two-position Off Cool down Modulating Off Two-position In addition, setpoints and setpoint limits define room and device operating modes. They can vary depending on the selected HVAC plant operating mode.
5 Control concept Desigo room automation The BACnet objects in the system support 16 priority levels.
Control concept Desigo room automation 5 Often, more must be done than merely adding or removing components (CFCs). If, an HVAC device, e.g., is to be added, the following must be added or removed: ● Information in the operating mode table ● Corresponding BACnet objects to operate the new device Shading control Products and requirements CM110664en_07 Suitable façade products and intelligent control allow for optimum satisfaction of various requirements for shading.
5 Control concept Desigo room automation Influences on blinds control Blinds control requires much information on environmental influences and user interactions to be able to best satisfy requirements. The blinds control can be influenced by, e.g.
Control concept Desigo room automation 5 ● Gray: Complete building ● Blue: Façade or part of a facade ● Green: Rooms of a renter, e.g., one floor ● Orange, red: Local, manual operation The functions are grouped into local and central functions depending on whether the function acts on one or multiple blinds in a room, or on an entire group of blinds, e.g., on all blinds of a facade.
5 Control concept Desigo room automation Function Description Product protection, local Risks impacting a blind only, e.g., protection against collision with a service door opening outward, are included in local product protection. Product protection, central Environmental influences impacting a group of blinds are included in the central functions for product protection. A common function in this category is protection of blinds against damage from strong winds.
Control concept Desigo room automation 5 ● Energy savings ● Lighting of objects, products ● Façade lighting ● Intrusion protection Lighting products control in addition must ensure the safety of persons.
5 Control concept Desigo room automation The functions are grouped into local and central functions depending on whether the function acts on one or multiple lamps in a room, or on an entire group of lamps, e.g., on all lamps of a renter.
Control concept Desigo room automation 5 Function Description Scheduler program Lighting can be switched on/off at specific times using a scheduler program. Furthermore, automatic control can be activated or deactivated via scheduler program. Another priority may need to be commanded depending on purpose. If, e.g., automatic control should be activated at noon, manual operation must be overridden by allowing the scheduler program to act on the priority for manual operation.
6 Technical view Standard plant structures 6 Technical view The technical view illustrates the technical building services equipment, such as HVAC systems and associated elements, in the building automation and control system. Area Gubelstrasse Heat generation Heat distribution Group N Group S Air handling, 3rd floor Burner Sensor KNG:ABdb6'AHU3Fl'FanSu The technical view helps organize measured and controlled physical variables from specific, technical installations in a building.
Technical view Standard plant structures 6 Primary plants with Desigo PX Structure Site Plant Partial plant, Aggregate, Component Total max. 6 recursions (max. 7 levels) Elements Site: A site is a self-contained area in terms of location, function and organization, usually a building or a group of buildings (facility). A site can comprise several plants. Example: Building 6 Plant: A plant consists of partial plants, aggregates and components. A plant can comprise several partial plants.
6 Technical view Standard plant structures Global objects Structure Site Global area Component Elements Site: A site is a self-contained area in terms of location, function and organization, usually a building or a group of buildings (facility). Example: Building 6 Global area: The global area contains all the global components of the site. There is one global area per site. Global objects are data objects which exist simultaneously in several automation stations at the automation level, e.g.
Technical view Technical text labels 6 Room automation with Desigo room automation Structure Building Floor Room Room segment Functional unit Component Elements Building: A building is a locally, functionally and organizationally defined area. Example: Building 6 Floor: A floor in a building can contain various rooms. Example: Floor Room: A room is a section of a building that is delimited by walls, ceilings, floors, windows and doors.
6 Technical view Technical text labels GUB:AGeb6‘Ahu3St‘FanSu = Gubelstreet facility / ventilation plans building 6 / Air handling third floor / supply air fan Technical designations are linguistically neutral (mnemonic). They are based on mnemonic texts set up in the library, with additional project-specific details. The TD is defined by Siemens. The User Designation (UD) can be defined by the customer. Name&Description_Pair Each element of the TD is called ShortName.
Technical view Technical text labels 6 ● Element type: Block in plant-engineering terms. Example: Component ● Main value: Main value of the function block. It is set during engineering. Example: PrVal Function block pin attributes CM110664en_07 The main attributes of the pins are: ● Name: Pin name, based on the key of the TD. Example: PrVal ● Description: Description of the pin name. Example: Present value ● Value: Current value of PrVal. Example: Normal ● Parameter Kind: Application pin type.
7 Global objects and functions Ensuring data consistency 7 Global objects and functions Every automation station contains all the data necessary for stand-alone operation, including, e.g., date and time, calendar function blocks and Notification Class function blocks. The system functions of individual automation stations do not depend on a central server.
Global objects and functions Roles in the system PXM30/40/50 Desigo PX Desigo PX Desigo PX Primary Server Backup Server Backup Server 10664Z03en_07 Desigo CC 7 Xworks Plus (XWP) and all BACnet clients can only modify the data of global objects in the primary server. 7.2 Roles in the system The role of the primary server Server/Function Function and description Primary server (Desigo PX) One automation station of a site acts as the primary server.
7 Global objects and functions Life check The role of the Desigo room automation server and third-party BACnet device Server/Function Function and description Desigo room automation server / The Desigo room automation server acts like a standard BACnet device. Third-party BACnet device Life check The Desigo room automation server / third-party BACnet device is monitored by the primary server or the backup server. Start-up No coordinated start-up. Replication No global objects to be replicated.
Global objects and functions Time synchronization Desigo CC 7 PXM30/40/50 Desigo PX Desigo PX Backup Server Backup Server 10664Z19en_07 Desigo PX Primary Server Add and delete devices For life check and replication the primary server has a list [BckUpSrv] of all known devices of a site. The primary server automatically adds newly commissioned devices on the site to this list. Devices which are removed from the site must be deleted manually in Xworks Plus (XWP) from the list in the primary server.
7 Global objects and functions Examples of global objects The backup server then triggers time synchronization of its recipients configured in Xworks Plus (Desigo room automation server, third-party server, third-party BACnet devices). This can be in either UTC or local time format. Periodic synchronization The time synchronization interval is defined in the property TimeSynchronizationInterval [TiSynIvl] (default value: 150 minutes).
Global objects and functions Examples of global objects Local properties 7 Local properties which refer to the functionality of the life check / replication: ● Server type [SvrTyp] Defines if the device acts as a primary server or a backup server. Default: backup. ● Primary device [PrimDev] Device object ID of the primary server of the site or an invalid value if the primary server is not known (read-only, set automatically by the primary server).
7 Global objects and functions Examples of global objects Desigo CC PXM20 10664Z05en_07 The number of global Notification Class objects is limited to 18 (six alarm classes each with three possible alarm functions). Calendar object There are global and local calendar objects. Desigo CC 10664Z06en_07 Global calendar object: A logical object at site level. It exists in identical form (as a replicated object) on each automation station of a site.
Global objects and functions Examples of global objects 7 Reasons for replication: Global exceptions (bank holidays, general holidays, etc.) can be modified centrally in one location for the entire site. Ensures continuity of operation if the master fails. User profile object Global user profile object: A logical object at the site level. It exists in identical form (as a replicated object) on each automation station of a site. There must be at least one user profile object.
8 Events and COV reporting Sources and causes of system events 8 Events and COV reporting Events System events are messages which inform a client (e.g.
Events and COV reporting Sources and causes of COVs Comparison with the alarm strategy 8 System events cannot be acknowledged or reset. A Confirmed Event Notification message is sent to all alarm recipients. The Notify_Type data field in the message defines that the event is a system event and not an alarm. Each alarm recipient that receives the Confirmed Event Notification is required to respond with a SimpleAck. If the SimpleAck is not received, the same mechanism comes into operation as for alarms.
8 Events and COV reporting COV reporting COV notifications received, the transmitting device tries to send the information again (three times). For system limits, see chapter System Configuration. Connection terminated If a COV client cannot be contacted, the COV server ceases to send COV notifications to that client. The transmission of COV notifications to a COV client is resumed when the COV client re-subscribes.
Events and COV reporting COV reporting 8 receipt of the value with a SimpleAck acknowledgement. The COV connection between the COV server and COV client is now established, and ConfirmedCOVNotifications are sent whenever a trigger for the subscribed COV occurs. The BACnet service SubscribeCOV includes a time limit for the COV connection. However, the COV client re-registers with the COV server before this limit expires, thus ensuring that the connection is maintained.
9 Alarm management Alarm sources 9 Alarm management Alarms indicate faults in the HVAC plant and building automation and control system, and let you initiate corrective action, where appropriate. The management of alarms (generation, signaling, acknowledgement) is in compliance with the BACnet standard. There are two alarm types: ● OFFNORMAL ● FAULT OFFNORMAL OFFNORMAL alarms (process alarms) occur when a process variable assumes an inadmissible value.
Alarm management Alarm sources 9 ● ● ● ● ● ● ● ● ● Event Enrollment Command Control object2 Power Control object2 Schedulers (Analog / Binary / Multistate Scheduler object)2 AlarmCollection object Discipline I/O1, 2 Trend Log / Trend Log Multiple Group1, 2 Device Info object, which models the properties of an automation station as a complete entity ● Loop object Key 1 Discipline I/Os, Groups, Time Scheduler and Trend Log Multiple support only system alarms, that is, only alarms of the FAULT type.
9 Alarm management Alarm example With analog blocks, the OFFNORMAL state is explicitly subdivided into the substates HIGH LIMIT and LOW LIMIT, which are described in detail further below. The current state of the alarm state machine in an alarm-generating block is displayed externally in the form of the output variable [EvtSta] (event state) of the block concerned.
Alarm management 9 Alarm example PXC - Programm Ventilator Zustandsmaschine D? 3 3 RefVal 1 4 Belt disturbed PrVal 2 PrVal 7 disturbance appears 6 OR Exhaust Air FAN 1 St. BL MntnSwi PrVal Cmd_CNTL ON OFF Auto Pop Up Notification Class ( =23) 1 5 .. ..... High Pro Alarm ........ Extendet Alarm ........ Receiver = DI Name Desigo CC Txt:........................ 3 ACK 5 RESE Auto ON OFF Pop Up Txt:........................
9 Alarm management Alarm example Time sequence in the example: 1. Ventilation system on (e.g., in automatic mode, Cmd.ValPgm = 1), singlespeed extract air fan running, fan blades rotating 2. The V-belt breaks, the pressure drops, the differential pressure monitor responds (delta p < X) and DPMon.PrVal goes to zero. This activates the alarm monitoring function in the DP monitoring block, and the [TiMonDvn] timer starts counting down. 3.
Alarm management Effects of BACnet properties on alarm response 9 allowed to expire, that is, DPMon.RefVal is held at 1 during the transient state. Only after expiry of the ramp up time does DPMon.RefVal revert to 0. 7. The ventilation system is already running (from step 6 on), that is, the fan blades start rotating, the pressure builds up and the differential pressure monitor detects delta p = X again, that is, DPMon.PrVal → 1. The alarm monitoring function is active again.
9 Alarm management Effects of BACnet properties on alarm response SBT designations BACnet property Function blocks (BACnet objects) Other Binary Analog Multistate I/O/V I/O/V I/O/V I/O/V I/O/V I/O/V I/O/V I/O/V I/O/V O O O Long name Ref.
Alarm management Effects of BACnet properties on alarm response SBT designations Long name Ref.
9 Alarm management Effects of BACnet properties on alarm response Alarm enable [EnAlm] [EnAlm] (Boolean type) is used to enable and disable the monitoring of OFFNORMAL alarms. OFFNORMAL alarms will only be detected if [EnAlm] is TRUE. This is equivalent to the standard BACnet property Alarm_Enable. FAULT alarms are monitored independently of the value of the alarm enable property [EnAlm]. Monitoring is continuous and cannot be disabled.
Alarm management Effects of BACnet properties on alarm response 9 value of [EnAlm] (that is, [EnLm = EnAlm], Limit enable = Enable alarm). This variable is equivalent to the standard BACnet property Limit_Enable. Low limit [LoLm] This parameter (data type Real) defines the low alarm limit. If [PrVal] exceeds the high limit value [LoLm] for longer than the period defined under [TiMonDvn], an OFFNORMAL alarm condition prevails, namely: LOW_LIMIT.
9 Alarm management Effects of BACnet properties on alarm response and Close. The first end switch, the Open switch delivers the signals Fully open or Not fully open. The second end switch, the Closed switch delivers the signals Fully closed or Not fully closed.
Alarm management Effects of BACnet properties on alarm response 9 Fire protection damper timing with BO and two feedback addresses: Fire protection damper timing with BO and two feedback addresses: Error condition: The damper does not close quickly enough. Neutral zone [Nz] [Nz] (data type Real) can be used to define a switching hysteresis for the state transition TO_NORMAL1. This is equivalent to the standard BACnet property Deadband.
9 Alarm management Effects of BACnet properties on alarm response Present value [PrVal] OFFNORMAL alarms are monitored exclusively on the basis of the current value of [PrVal] the present value variable. The source of this present value (whether a process value, operator value, replacement value or commanded value) is irrelevant. This is equivalent to the standard BACnet property Present_Value. Reliability [Rlb] The value under [PrVal] is only plausible if [Rlb] = NO_FAULT_DETECTED.
Alarm management Alarm response of the function blocks 9 associated alarm state transition. This is equivalent to the standard BACnet property Event_Time_Stamps. Notification function selector [NotifSel] This variable specifies if the alarm function is executed as per default pattern (Simple-/Basic-/Extended alarm) or as per a customized alarm function. 9.
9 Alarm management Alarm response of the function blocks BACnet Device Info Object OFFNORMAL alarms All the alarm-generating objects described so far model specific types of individual data points (physical or virtual). The BACnet device object by contrast, models the properties of an automation station as a complete entity. Alarm-relevant faults which cannot be allocated to a data point can be generated in an automation station (see the examples further below).
Alarm management Alarm response of the function blocks 9 Alarm response of the BACnet Device Object is also parameterized or depicted by the number of variables, but the display differs: The BACnet Device Object is not displayed by a D-MAP function block, but rather only visible via BACnet. The variables described are therefore only accessible as properties of the BACnet Device Object.
9 Alarm management Alarm response of the function blocks In the case of the binary output, [Rlb] errors may originate both from the [PrVal] (or associated physical output) and from the [FbVal] (or associated physical input). ● A FAULT alarm will disappear as soon as the variable [Rlb] changes from a value not equal to NO_FAULT_DETECTED back to the value NO_FAULT_DETECTED.
Alarm management Alarm response of the function blocks 9 The subsystem indicates an inadmissible response from a device e.g. in the case of faulty QAX… room unit. These alarms are indicated by the shared function block. Multistate Input and Multistate Value The alarm handling process is identical for the function blocks Multistate Input and Multistate Value.
9 Alarm management Alarm response of the function blocks Power Control An OFFNORMAL alarm is generated: ● The UP command is issued but the maximum stage has already been reached ● The UP command causes MaxPower to be exceeded ● Table_No is set outside the admissible range A FAULT alarm is generated when: ● A referenced object is not found ● A referenced object is not a multistate value object ● Object_No.
Alarm management Alarm response of the function blocks 9 Trend Log Alarm response The Trend Log function has an Intrinsic Reporting mechanism, but does not issue OFFNORMAL alarms. ● A FAULT alarm is generated as soon as the [Rlb] property of the function block assumes any value other than NO_FAULT_DETECTED. In particular, this is the case when [Rlb] changes from a value not equal to NO_FAULT_DETECTED to another value not equal to NO_FAULT_DETECTED.
9 Alarm management Alarm response of the function blocks Event_Type Event_State Event_Parameters Data type FLOATING_LIMIT NORMAL Time_Delay Unsigned HIGH_LIMIT Setpoint_Reference BACnetDeviceObjectPropertyRe ference Low_Diff_Limit REAL High_Diff_Limit REAL Deadband REAL NORMAL Time_Delay Unsigned HIGH_LIMIT Low_Limit REAL LOW_LIMIT High_Limit REAL Deadband REAL Notification_Threshold Unsigned Previous_Notification_Count Unsigned NORMAL Time_Delay Unsigned OFFNORMAL List
Alarm management Alarm functions 9 9.5 Alarm functions Depending on the type and degree of urgency of the alarm, the system user may be required to acknowledge a change in the alarm state with an explicit operator action. Acknowledgement There are two types of acknowledgement: ● Acknowledgement: Confirmation of an incoming alarm ● Reset: Confirmation that an alarm is no longer present This type of interaction can be carried out locally or with clients, via the network.
9 Alarm management Alarm functions The alarm remains locked until the fault has disappeared and has been acknowledged and a reset has been carried out, e.g.: The burner system is restarted when the service engineer has acknowledged the alarm, cleared the fault and reset the alarm. The alarm state of every alarmgenerating object is managed within the object itself. The state machines above illustrate this for each of the alarm functions.
Alarm management Alarm management by notification class 9 9.6 Alarm management by notification class Intrinsic reporting With intrinsic reporting, the alarmable object itself assumes alarm identification and state machine for alarm handling. However, the subsequent distribution of alarm messages to alarm clients and the alarm management is no longer the responsibility of the alarm source itself, but of a Notification Class object assigned to the alarm source.
9 Alarm management Alarm management by notification class ● AlarmFunction [Simple(1), Basic(2), Extended Alarm(3)] ● AlarmClass [UrgentAlarm (1), HighPrioAlarm (2), NormalAlarm (3), LowPrioAlarm (4), UserDefinedAlarm (5) and OffLineTrend (6)] The notification class number is calculated as follows: NotificationClass# := 10 * AlarmClass + AlarmFunction This gives the following notification classes: Formula AlarmClass AlarmFunction Priority (default values) To-Offnormal To-Fault To-Normal Uses Notifica
Alarm management Alarm management by notification class 9 Priority [Prio] This defines the alarm priority on the basis of which alarm and system events are to be transmitted to the receivers. Every transition can be described individually with this BACnet property, data type ARRAY of INTEGERS [TO_OFFNORMAL; TO_FAULT; TO_NORMAL]. Priority levels can range in value from 0 to 255. The lower the value, the higher the priority. In Desigo only priorities 1 to 9 are used.
Alarm management 9 Alarm routing over the network B= DeviceIdentifier Permanently connected alarm receiver DeviceIdentifier Alarm receiver with PTP connection and Desigo PX half router DeviceIdentifier Alarm receiver with PTP connection and third-party half router RemoteAreaSite Not case-sensitive A..Z a..z 0..9 Alarm receiver syntax: Element Description DeviceName Device name. In plain text so that the user can understand it. Example: CC 01 DeviceIdentifier Device Identifier.
Alarm management Alarm routing over the network 9 irrespective of when it was connected – displays the current alarm status of the system. After making these entries, the temporary alarm receiver, while connected, will receive all alarm messages from the automation station in accordance with the routing mechanisms described below. If an automation station cannot transfer an alarm message to a temporary alarm receiver (e.g.
9 Alarm management Alarm queuing ● Alarm text ● Other technical details Based on this information, the alarm client can present the alarm in a comprehensible way; it may also read additional information automatically from the alarm server, and if required, return any acknowledgement to the correct address.
Alarm management Alarm queuing 9 If the queue is full to overflowing, the oldest entries are deleted automatically, and a system event message is generated. Entries are deleted irrespective of alarm priority. Alarm queuing has no effect on the alarm state of the alarm source. Alarms destined for a temporary alarm recipient are not saved in the automation station.
9 Alarm management Common alarms If the notification class object contains remote alarm recipients, then it may be appropriate to modify the default values for control of alarm queuing. The values for [NotifThd] and [PrlmAlm] determine when a remote cable connection (modem) is to be established, in order to inform the user of the occurrence of alarms. If low-priority alarms are to be forwarded immediately, the [PrlmAlm] value must be increased (the higher the number, the lower the alarm priority).
Alarm management Alarm suppression 9 9.10 Alarm suppression Alarm suppression refers to suppression of alarm and event notifications in the Desigo system. Thus, sending BACnet event notifications is suppressed. Alarm suppression does NOT prevent detection of alarm states. Alarm suppression types The following types of alarm suppression exist in Desigo: ● Alarm suppression by automation station using function block AS_STA allows for implementing alarm suppression at the automation station level.
9 Alarm management Alarm suppression For more information on function block AS_STA, see: Desigo Firmware blocks, automation level, Overview (CM110749) Desigo Vxx Firmware blocks (CM110729) Desigo room automation supports the suppression of all alarms of an automation station. To do this, it uses the device infrastructure objects CommonEvent and CommonEventEnrollment.
Alarm management Alarm message texts 9 Combination of multiple alarm suppressions The above options to suppress alarms can overlap. For an object impacted already by multiple types of suppression, the following rule applies: One type of alarm suppression cannot be overridden by another type of alarm suppression. AS_STA. SupEvt CMN_ALM. SupEvt CMN_ALM. EnSupEcp FB.SupEcpt FB.
9 Alarm management Alarm message texts Predefined, languagedependent text 164 | 353 language-dependent texts are organized into text groups with a predefined server system text scope, and can be translated. The translated text groups are loaded into the automation station via BACnet description information.
Calendars and schedulers Alarm message texts 10 10 Calendars and schedulers Standard BACnet objects The standard BACnet objects Schedule and Calendar are used for time scheduling functions in the Desigo system. These objects can be used to configure and operate time scheduling functions at different operating levels within the system and via BACnet-compatible operator units from other manufacturers.
10 Calendars and schedulers Schedule 10.1 Schedule Weekly schedule [WeekSchd] The weekly schedule [WeekSchd] consists of seven 24-hour profiles, one for each day of the week. By default, the priority level assigned to the weekly schedule is 16 (the lowest priority). The weekly schedule is active unless there is an exception schedule. For system limits, see chapter System Configuration. 24-hour profiles A 24-hour profile is a list of time-and-value pairs.
Calendars and schedulers Schedule 10 ● Switch value exception schedule: If an active switch value exists for a specific time, the exception schedule determines the resulting Present_Value. ● Daily profile switch value: If an active switch value from a daily profile exists for a specific time, the daily profile determines the resulting Present_Value.
10 Calendars and schedulers Schedule Key ① An exception profile applies to more than one day. On the second day, the exception profile is inactive, because another profile with a higher priority is active for the whole day. ② An exception program without the entry NULL. This exception profile is active for the whole day and ends automatically in the automation station at 24:00 hours by the NULL entry. ③ Several exceptions with the same priority on the same day, but without overlapping times.
Calendars and schedulers Schedule 10 The switching value is output to [PrVal] and to the objects to be switched (commanded objects list). A schedule block can only contain switching values of the same data type (binary or analog or multistate or boolean or unsigned or real or enumerated). It is therefore not possible to switch two different data types in sequence. In Desigo PX the CAL (calender) and SCHED (schedule) function blocks can be created online.
10 Calendars and schedulers Schedule Effective period [EfPrd] You can define the period for which the schedule is to be active, e.g., you can configure separate schedules for summer and winter operation. If the current day is outside the active period, the [PrVal] output is equal to the default value [DefVal]. Time resolution The smallest unit in the scheduler program is one minute and in the calendar one day. The schedule may be dependent on the calendar.
Calendars and schedulers Calendar 10 10.2 Calendar Function block Calendar The calendar object is a function block from the firmware library. It contains a list of dates [DateList] with, e.g., a date or a date range. The date list [DateList] uses Boolean logic to control the calendar outputs. [PrVal] activates an exception profile if the calendar object is referenced by a schedule object. The outputs tomorrow [Tmw] and day after tomorrow [DayAfTmw] support the optimum start/stop control of the plant.
10 Calendars and schedulers Alarm messages Day of the week Meaning January/2/Monday Monday in the second week of January */1/Tuesday Every first Tuesday of a month February/*/Wednesday Every Wednesday in February 10.4 Alarm messages The scheduler object cannot directly generate alarms when, e.g., a commanded object cannot be found.
Trending Trend functions 11 11 Trending Trend data provide important information about the processes in a building automation and control system, e.g.
11 Trending Trend functions Single Run The trend data is saved until the available memory area is full. You can define the buffer size [BufSize] within the range 2 to 5,000 entries. You can define the Single Run function with the parameter Stop when full. Logging Type The parameter Logging Type [LogTyp] defines the logging type.
Trending Editing parameters Triggered Sampling 11 In Triggered Sampling an application (e.g., via data flow interconnection) determines when values are acquired/logged and saved. Triggered Sampling is supported by the Trendlog object and the Trendlog Multiple object. 11.
11 Trending Processing trend data in Desigo CC In this state, only the following parameters can be configured: – Start time [TiStt] and stop time [TiStp] – Record count [RecCnt] (can only be overwritten with 0: delete log buffer) – Notification threshold [NotifThd] The record count [RecCnt] can only be overwritten with 0. This deletes all the log data. After a write operation of 0, there is one entry showing the log status (record count = 1). It is not possible to reload sampled data into the CFC Editor.
Reports 12 12 Reports You can create reports in Desigo CC about the functioning of the building automation and control system. You can configure: ● The elements in the report (such as tables, plots, logos, form controls, text and so on), and their layout. ● Filters (such as name, condition, time, and/or row) to populate the elements of the report with information, e.g.
13 Data storage Data categories 13 Data storage Large volumes of data are created in the Desigo system during engineering, commissioning and plant operation. The data is processed, saved, and archived as needed in accordance with type, generation, and meaning in the various system components. 13.
Data storage Libraries 13 ● System blocks for controlling the plant ● System interfaces which are implemented in every component and which control the data traffic between the components Product components Product components are the local subroutines responsible for the internal consistency of setup, startup, shutdown, navigation and display, etc. among the individual components.
13 Data storage Project data Graphics libraries the elements of the application libraries. Any changes to the application libraries must therefore also be made to the graphics libraries. The graphics libraries for Desigo PX and PXC3/DXR2 are identical. 13.4 Project data There are three types of project data: ● Project data that is saved locally and then loaded into the system. ● Data on the Branch Office Server (BOS). ● Data that is loaded into the system with ABT Site and is not saved locally.
Data storage Plant data 13 ● The PX automation station must be connected and available (online). ● The PX automation station must support backup and restore. ● The building automation and control system must work smoothly. You can restore data backed up on Desigo CC to the corresponding PX automation stations. The restored PX automation station automatically restarts after data restoration. Restore 13.
13 Data storage Data transfer processes ● Improves performance ● Is faster than full code generation Online loading Full download The full download transfers all loadable units into the automation station. Delta download The delta download: ● Copies additional blocks into the automation station ● Deletes blocks which are no longer valid ● Updates parameter settings The delta download is faster than a full download. You do not need to interrupt the operation of the automation station.
Data storage Texts 13 3. Compile 4. Download Offline import You can import configuration and description data for the plant into Desigo CC. This is the same as the data downloaded to the automation station. 13.7 Texts If you work with HQ or RC libraries, the texts are from a text database. These texts can be automatically translated, because they have a unique ID. Projectspecific texts that are not from the text database cannot be automatically translated.
14 Network architecture BACnet architecture (MLN & ALN) 14 Network architecture The Desigo system is divided into three network levels: ● Management Level Network (MLN) ● Automation Level Network (ALN) ● Field Level Network (FLN) BACnet Internetwork BACnet Network #100 RemoteArea: Zürich Management Level Network Desigo CC 2 Desigo CC 1 BACnet Network #1 BACnet Network #2 BACnet Network #3 PXG3.W100 IP segment 6 IP segment 5 PXC00-U BACnet Network #4 Desigo CC 3 PXC #1 PXG3.
Network architecture BACnet architecture (MLN & ALN) 14 Key B Bridge, e.g., IP router, LonWorks router R Repeater, e.g., LonWorks physical repeater RT Router, e.g., PXG3 ½ RT Half router, e.g., PX..-T Internetwork In BACnet, the BACnet internetwork is defined as the largest BACnet unit. It consists of one or more BACnet networks. Only one active connection can exist between any two BACnet devices in a BACnet internetwork.
14 Network architecture BACnet architecture (MLN & ALN) Segment Large networks are structured, that is, divided into several (logical) network segments for reasons of security, performance, size and (limited) address range of network devices. The segments must then be connected to routers of the corresponding transport protocol (e.g., LonWorks router, IP router). In most cases it is not necessary to divide a BACnet/LonTalk network into several LonWorks segments (ALN).
Network architecture BACnet architecture (MLN & ALN) ISO/OSI Layers 14 BACnet Layers Application Layer Application Layer Network Layer Network Layer VMAC BVLL Data Link Layer UDP/IP BZLL BVLLv6 ISO8802-2 Type 1 (IEEE802.2) UDP/IPv6 PTP LonTalk (EIA 709.1) EIA-485 EIA-232 TP/FT 10 (EIA-709.1) ZigBee ISO8802-2 Type 1 (IEEE802.2) Ethernet ISO8802-3 (IEEE802.3) Physical Layer MS/TP Ethernet ISO8802-3 (IEEE802.3) ARCNET IEEE 802.15.
14 Network architecture BACnet architecture (MLN & ALN) Guidelines Different rules for object names apply for configuring TD (Technical Designation), UD (User Designation), or FD (Free Designation): ● The TD is generated from predefined partial names, separated by an apostrophe ('), that show the technical hierarchy with plant, partial plant, and component. The TD is supplemented by site name and pin name. ● The names may consist of upper- and lowercase letters and numbers 0 to 9.
Network architecture BACnet architecture (MLN & ALN) 14 Designation Description Max APDU Length Accepted Maximum length of application message (Application Protocol Data Unit) supported for this device. The length depends on the transport medium used, and the capacity of the device buffer. The length of the APDU must always be less than the length of the smallest NPDU (Network Protocol Data Unit) between the different bus subscribers. Beispiel There are two IP networks linked by a PTP connection.
14 Network architecture BACnet architecture (MLN & ALN) Range/Value Description 0 Reserved for applications with only one BACnet network in a BACnet internetwork, that is, where there are no BACnet routers. 1...65280 Network number for stationary BACnet networks. You can select any network number in this range. We recommend that you form categories, e.g.: 65281...65534 Router parameters BACnet/LonTalk networks via (half)router: 1...
Network architecture BACnet architecture (MLN & ALN) 14 Domain ID: The domain ID is the highest unit in the LonWorks addressing system. Data can only be exchanged within a domain. A gateway is required for inter-domain communication. The domain ID can be 0, 1, 3 or 6 octets in length. A domain can consist of up to 255 subnets. Subnet ID: The subnet is a logical collection of up to 127 nodes within a domain. The bus traffic within a subnet can be kept local by using BACnet routers.
14 Network architecture BACnet architecture (MLN & ALN) RFC1918 defines three specific address areas for private networks. IP addresses within these ranges are not routed: 10.0.0.0 - 10.255.255.255 Subnet mask: 255.0.0.0 172.16.0.0 - 172.31.255.255 Subnet mask: 255.240.0.0 192.168.0.0 - 192.168.255.255 Subnet mask: 255.255.0.0 For IPv6, IP addresses and private address ranges are defined differently. See Ethernet, TCP/IP, MS/TP and BACnet basics (CM110666).
Network architecture BACnet architecture (MLN & ALN) 14 IPv6 (BVLLv6) only supports two-hop BBMD. Broadcasts are implemented via IPv6 mutlicasts. See Ethernet, TCP/IP, MS/TP and BACnet basics (CM110666). BBMDs ensure that broadcast messages are distributed in a BACnet network. They are grouped by BACnet network. A maximum of one BBMD is allowed in any one IP segment. BACnet network #100 is separated by IP routers. The Internet also contains IP routers.
14 Network architecture BACnet architecture (MLN & ALN) The half-router function is implemented in Desigo CC, XWP/ABT and PX. Application Layer Network Layer LonTalk IP PTP MSTP PTP connections are only possible between Desigo CC, XWP/ABT und PX. PTP connections between PXs are not permitted. PX devices which can be reached via PTP always belong to a separate site.
Network architecture BACnet architecture (MLN & ALN) 14 For each PTP connection in Desigo CC, only the telephone number needs to be defined. Data link layer MS/TP Data Link Layer Master/Slave Token Passing MS/TP is another protocol variant for BACnet. Desigo supports this variant via a specific router that connects BACnet MS/TP to BACnet/IP. MS/TP is based on the physical layer EIA-485/RS-485 and supports baud rates up to 76.8 kbps.
14 Network architecture LonWorks architecture (ALN) router. The router can be configured either via XWP or the integrated web server. BACnet address Every BACnet device in the BACnet internetwork can be accessed via its BACnet address. The BACnet address is defined by the BACnet standard and comprises the following elements: Designation Description Network number Network number of the BACnet network in which the device is located.
Network architecture LonWorks architecture (ALN) 14 Key R Repeater, e.g., LonWorks physical repeater B Bridge, e.g., L-Switch (Loytec) RT Router, e.g., LonWoks router GW Gateway, e.g., PXC..., RXZ03.1 See LonWorks networks Checklist (CA110335). Trunk A trunk holds all devices that can communicate with each other directly or via repeater, bridge or router. The term trunk is specific to the Desigo system. One trunk corresponds to one LonWorks project. Trunks can be connected via gateways.
14 Network architecture KNX architecture (ALN) L-Switch (Loytec) The L-Switch filters the package on the basis of the subnet/node ID or group ID. It automatically learns the topology and forwards the data packets accordingly. The L-switch does not have to be configured. Unlike the router, there is no need to take account of any addressing limits (allocation of Subnet ID or Group ID). Physical repeater LonWorks has physical and logical repeaters.
Network architecture KNX PL-Link architecture (FLN) 14 Area Up to 15 lines can be connected to a main line via line couplers (LC). This is called an area. Backbone line The topology can be expanded by means of a backbone line. Up to 15 areas can be connected to the backbone line via backbone couplers (BC). Technically, these are the same devices as line couplers. Line/Backbone couplers Couplers separate the areas and lines. Couplers keep the bus traffic within bounds.
14 Network architecture DALI architecture (FLN) BAC network Automation station KNX PL-Link network Room Power supply concept Room Room The PXC3 and DXR2 room automation stations have an integrated KNX power supply to supply their trunks with the corresponding KNX PL-Link devices. This allows simple installations, e.g., an automation station with one or a few room units, without an extra device for power supply to the KNX PL-Link network.
Network architecture DALI architecture (FLN) 14 Structure A DALI system can be made up of control gear, control devices and bus power supplies. Control gear Control gear usually contains the power control circuit to drive lamps, or some other type of output, such as on/off switching or 1 to 10 V analog signals. Control devices Control devices can provide information to other control devices, such as light intensity information, and can send commands to control gear.
15 Remote access Remote access methods 15 Remote access The remote access is an access to resources via the internet or a point-to-point connection. The remote access is used to: ● Connect a remote location to Desigo CC, e.g., for on-call service, managing different locations or support by a specialist ● Remotely access Desigo CC ● Make a change, create an extension or search for errors using an engineering tool ● Forward alarms as text messages or emails from Desigo Control Point or Desigo CC 15.
Remote access Choosing a suitable access technology 15 TV cable-based access ● This access is similar to DSL. You can access the system remotely via a cable modem provided by the cable network operator. Other cable-based networks, such as metro ethernet Characteristics of other cable-based networks, such as metro ethernet: ● Connections with very high bandwidth are available. ● A metro ethernet connection is usually not implemented as part of a BACS project.
15 Remote access Technical details Costs The costs are divided into monthly basic costs and usage costs. To optimize costs, analyze your usage profile, that is, how many times per month do you use it and how much data do you exchange per use. A data flat rate ensures that the costs are capped. Choosing an inappropriate rate plan for a mobile subscription could result in high costs.
Remote access Technical details 15 Use of mobile telephone networks (GPRS/UMTS/LTE) Several suppliers offer GPRS/UMTS/LTE modems, e.g., modems for private use and modems for industrial applications (also top-hat rail). Because of the attenuation of the walls and ceilings, the signal inside a building can be weak, that is, an antenna must be placed on the exterior of the building, preferably on the roof.
16 Management platform Technical details 16 Management platform A building automation and control system encompasses all control functions of one or more buildings. In addition to typical HVAC systems, there is a need to integrate other areas of the building, such as lighting and blind control systems, fire alarm systems and access systems.
Management platform Technical details 16 For more information on the Desigo CC management platform, see Desigo CC System Description (A6V10415500). Architecture The Desigo CC management platform presents a single point of entry for users to operate, monitor and optimize building automation, fire safety and security systems or a combination thereof. Desigo CC is a flexible, full client-server architecture allowing scalability from small and medium to large and complex systems.
16 Management platform User functions Windows app client (ClickOnce) App Client runs in its own pane, without the overhead of the internet browser application and menus. Web server To use the Desigo CC Web and Windows App Clients, you must install the web server. To install the web server, you must first install Microsoft IIS on the web server computer. Usually the web server is on the Desigo CC server.
Management platform User functions 16 Scheduling The Scheduler allows you to schedule events for Desigo CC and field panels at your facility. You can create daily or weekly schedules for Desigo CC and BACnet devices. You can fully configure and monitor standard BACnet schedules, calendars, command objects, and workstation-based schedules that can be used to support systems without built-in scheduling capabilities.
16 Management platform User functions Event management Event management allows you to manage events throughout the system. You can monitor and manage the progress of each event from initiation through resolution. The full history of each event issue is recorded, and you can generate event-related reports that you can view, save, and print. Log Viewer The Log Viewer application provides an historic log of all user and system events and activities that have occurred.
Management platform Main components Document management 16 Desigo CC can handle the different types of document templates used in the project. You can configure document templates in PDF, RTF, TXT, XLS, and HTML format. 16.2 Main components System Manager The System Manager lets you navigate the system, view and override current conditions, analyze historical operations, and configure the system.
16 Management platform Access and security License Manager Licensing ensures the operation of the system within the agreed system limits. Only the system is allowed to change license data. If a license becomes temporarily unavailable (e.g., due to network connection issues) the system continues to run fully operational for a grace period. The system continues to check for the license and shuts down at the end of the grace period, if none of the license checks succeed.
Management platform Event management 16 Summary Bar The Summary Bar contains a summary of the events occurring in the system and lets you quickly access functions, such as the Event List. It also displays information, such as the system status, the logged in user, etc. Depending on the client profile in use, the Summary Bar can be docked on the desktop or freely opened and closed as needed. Event List The Event List provides a complete and easily filtered list of events under control of Desigo CC.
16 Management platform Installation, setup and engineering Assisted treatment alarm, fill-in a treatment form, or automatically print the information of the event). 16.5 Installation, setup and engineering License Management Utility (LMU) The installation program installs the Siemens License Management Utility (LMU) on every management platform in a Desigo CC network. The LMU enables and manages licenses and holds the installed licenses for Desigo CC.
Management platform Installation, setup and engineering 16 ● Video through Milestone Video Management System ● Mass Notification System (see MNS documentation) ● Third-party Building Automation and Fire Safety systems based on BACnet/IP ● Third-party subsystems through OPC ● Third-party subsystems through Modbus/IP ● Integration through SNMP ● APOGEE Building Automation system ● XNET FireFinder XLS and MXL fire safety systems ● Desigo Fire Safety FS20 UL systems Auto discovery Auto discovery lets you dis
16 Management platform Graphics libraries ● The entire customer project data, including all libraries, configurations, object data (project backup). ● The historic data collected in the history databases (HDB backup). Backups can be done either manually or by applying a macro in combination with a management platform scheduler. See Desigo CC System Management Console (A6V10415497). 16.6 Graphics libraries Desigo CC contains libraries with symbols and graphic templates for easy plant graphics engineering.
Management platform Graphics engineering 16 16.7 Graphics engineering Desigo CC graphics are built using smart objects that know how they are used and how to represent themselves graphically. Smart objects let you create graphics by dragging objects onto a page, without manually binding an object to graphical symbols. The Graphics application allows you to create, view, store, and command large graphics representing equipment, floors, buildings, facilities, and entire campuses.
16 Management platform Virtual environment 16.8 Virtual environment Desigo CC is compatible with following Virtualization software packages: ● VMware®: – Virtualization platform: VSphere 6.0 – Fault-tolerant software: ESXi 6.0b (build 2809209) managed by VCenter Server Appliance v6.0.0 (build 2793784) ● Stratus®: – Virtualization platform: KVM for Linux CentOS v7.0 – Fault-tolerant software: everRun Enterprise 7.2 – Virtualization platform: Citrix XenServer 6.0.2 – Fault-tolerant software: everRun MX 6.
Desigo Control Point Virtual environment 17 17 Desigo Control Point Desigo Control Point is an embedded building management station for operating and monitoring building automation and control systems on BACnet/IP. Additionally room applications can be operated by the end user (using QMX7 widgets). The functionality can be adapted to any user profiles – from room users to facility managers.
17 Desigo Control Point Functions ● Very small projects: One touch panel for on-site operation of a primary plant. Remote access occurs directly via the integrated web interface on the touch panel. ● Large project with multiple, decentralized touch panels. The central, crossbuilding operation takes place on Desigo CC. PXG3.W100-1 and PXG3.
Desigo Control Point Functions 17 ● Manual export of trend data via CSV file. ● Automatic transmission of trend data via email or save to an FTP server, pursuant to a schedule. Schedulers ● ● ● ● Operate BACnet schedulers and calendar programs. Supported scheduler program objects: Analog, binary, and multistate. Operate local and global calendars on Desigo PX automation stations. Create and copy efficient exception programs easily.
17 Desigo Control Point Functions Plant graphics ● Animate 2D and 2D+ symbol. ● Look & feel follows Desigo CC style. End user room operation ● Operate lighting, shading, and HVAC components. ● User interface optimized for the end user to efficiently operate office, meeting, conference rooms, etc. ● User interaction design matches QMX7.E38. ● All QMX7.E38 operating elements are available for operation. ● Standard templates for meeting and office rooms.
Desigo Control Point Functions 17 Northbound integration ● External access to IT application on BACnet objects of a Desigo system via Haystack tagging or Haystack REST API. ● Project Haystack is an initiative to simplify handling data from the Internet of Things (IoT) and to optimize it for building automation and control (http://project-haystack.org/). ● Application examples: Data access to third-party devices with HTML5.0 Browser, customized apps, SAP systems, etc.
17 Desigo Control Point Functions – – Templates for technical primary plants and rooms, meeting and office environments, energy dashboards RC-specific localization possible For more information about Desigo Control Point, see: ● Desigo Control Point Planning and Installation Manual (A6V11170804) ● Desigo Control Point Engineering Manual (A6V11211560) ● Desigo Control Point Operation Manual (A6V11211557) 224 | 353 CM110664en_07
Automation stations Functions 18 18 Automation stations The Desigo PX range is based on freely programmable automation stations. They provide the infrastructure to accommodate and process system-specific and application-specific functions. The PX range of automation stations comprises the compact and modular series. See Desigo PX - Automation system for HVAC and building services - System overview (CM110756). See Automation stations modular series PXC..D, PXC..-E.D, PXA40-.. (CM1N9222).
18 Automation stations Device object AI AO Read Write Frozen values Process image buffer Current values I/O scan Values read in cycle 1 are processed in cycle 2. Output values calculated in cycle 1 are transferred to the peripherals in cycle 2. 18.1 Device object Each automation station contains a device object.
Automation stations Device info object 18 ● C = Hardware version ● 61487 = Consecutive number Division into groups The properties of the device object can be divided into groups based on category, e.g.
18 Automation stations Error sources and monitoring functions Properties for system alarms and system events The device object has an alarm mechanism, because system alarms and system events, which cannot be assigned to a data point, may occur in an automation station. The alarm state machine and alarm-relevant connections are mapped to the BACnet properties of the device object. 18.3 Error sources and monitoring functions There are various error sources, e.g.: Error Effect Memory error, e.g.
Automation stations Operating states 18 18.4 Operating states A PX automation station has the following operating states: ● STOP: The D-MAP program is stopped. ● RUN: The D-MAP program runs. ● KOMA: The automation station is in a prolonged sleep mode.
18 Automation stations Operating states 1: Power failure 1: Power failure Mains OFF 2: Power restored COMA 2: Power restored RUN 1: Power failure 2: Power restored STOP STOP RUN BACnet: Download required 14: Load BACnet: Operational 12: Reanimation COMA 13: Master reset 4: RUN Cmd 15: Delta loading BACnet: Operational 5: STOP Cmd 16: Delta loading 10: Fatal Error 11: Fatal Error 7: Restart 9: Reset 7: Restart 9: Reset Operating states Mains off ● No power supply STOP ● I/O scan active
Automation stations Operating states 18 ● Primary server in the RUN state: Primary server is active, that is, life check, time synchronization and replication of global objects ● Backup server in RUN state: The backup server is active, that is, time synchronization and replication of global objects by primary server. The backup server does not accept changes of global objects by a client.
18 Automation stations Operating states ● Cold start I/O scan: Default values for output modules ● Cold start function block variables: Volatile variables are initialized with initial value. Non-volatile variables retain their last value. ● System event: Restart D-MAP processing starts when the first I/O scan is finished. 8 Reset Explicit reset of automation station via hardware push button.
Automation stations Data storage 18 The operating state is stored as a non-volatile variable. The operating state is mapped as follows to the system status [SysSta] property of the device object: Operating mode System status property [SysSta] STOP (no D-MAP program loaded) DOWNLOAD_REQUIRED STOP (D-MAP program loaded) NON_OPERATIONAL RUN (D-MAP program loaded) OPERATIONAL 18.
18 Automation stations Data storage Processing the D-MAP program 3. The D-MAP program code is read from the flash memory (3a). The program data is modified in the RAM (3b). Non-volatile process variables (e.g., adaptive control parameters, hours run, etc.) are written by the function blocks into the flash memory (3c) at regular intervals (once per day) or saved in the battery supported RAM. Starting the automation station 4.
Logical I/O blocks Data storage 19 19 Logical I/O blocks I/O blocks are used to register and transmit raw data to and from the plant, and to convert, process and integrate it into the program. The following options are supported: ● Raw data from or to the input or output modules.
19 Logical I/O blocks General functions 19.1 General functions Blocks: AO, BO, MO, AVAL, BVAL, MVAL This section describes the general functional scope shared by many of the I/O blocks. Each subsection includes a list of the blocks to which that subsection applies. Any block-specific details which are not shared by other blocks are described together with the block concerned.
Logical I/O blocks General functions 19 Priorities 1, 4, 7, 15 Priority 6 Priorities 2, 5, 8, 14, 16 Local control Control within block Higher control via data flow interconnection via BACnet command AO BO MVAL CMD_CTL e.g. emergency stop 1 PWR_CTL Life safety 2 3 e.g. anti-icing ValCrit / EnCrit protection Critical value 6 e.g.
19 Logical I/O blocks General functions The minimum on/off time For each change at the output [PrVal] from OFF to Stage n or from Stage n to OFF, the entry for priority 6 is set up as follows: If the minimum ON-time [TiOnMin] or OFF-time [TiOffMin] is greater than 0: 1. Priority 6 adopts the new present value [PrVal]. 2. Priority 6 is set to active. 3. The timer for the minimum on-time or off-time is started. 4. After expiry of [TiOnMin] or [TiOffMin], priority 6 is set to inactive.
Logical I/O blocks General functions Use 19 Prio Meaning 6 Minimum switch-on/off time No access! Prevent unnecessary switching operations. Commands are only generated internally in the block. Switch-on/off delay 7 Access via Can be used to ensure that run-on delay times are implemented. The timer periods [TiOnMin], [TiOffMin], [DlyOn] and [DlyOff] can be configured in blocks BO, MO, BVAL and MVAL. Operating value Local manual operation, e.g.: Reserved for manual operation.
19 Logical I/O blocks General functions Example: Effect of priorities 7...16 on [PrVal] Prio Use 1 Prio 7…16 Assumption: The effective switch command from priority (7…16) is Off and is set to active. Prio 6 Assumption: Priority 6 is not active. [PrVal] Assumption: The [PrVal] output is set to Off. Prio 7…16 The effective switch command from priority (7…16) switches from Off to Stage 2. Prio 6 Priority 6 adopts the (still unchanged) present value [PrVal=Off] and is set to active.
Logical I/O blocks General functions Prio 19 Use Prio 6 The block starts the switch-off delay [DlyOff]. Throughout this monitoring time, priority 6 is set to active – the associated value remains at Stage 2. [PrVal] Since priority 6 overrides the effective switch command [DefVal], the [PrVal] output remains at Stage 2. 6 Prio 7…16 n/a Prio 6 1. After expiry of the switch-off delay [DlyOff], priority 6 is released. 2. The effective switch command Off from [DefVal] is transmitted to [PrVal]. 3.
19 Logical I/O blocks General functions Example: Effect of priorities 1...5 on [PrVal] Prio Use 1 Prio 1…5 Assumption: All information bits for priorities 1…5 are inactive. Prio 6 Assumption: Priority 6 is not active. [PrVal] Assumption: The [PrVal] output is set to Off. Prio 1…5 At least one of the information bits for priorities (1…5) is active again. The effective switch command from priority (1…5) is Off. Prio 6 Since the effective switch command for priority (1...
Logical I/O blocks General functions 19 Prio Use 5 Prio 1…5 n/a Prio 6 The minimum switch-on time [TiOnMin] has expired. Priority 6 is released. [PrVal] Since neither priority 6 nor any entries for priorities (1…5) are active, the output [PrVal] is now again determined by the effective switch command from priorities (7…16). The [PrVal] output remains at Stage 2. Note: Switching from Stage 1 to Stage 2 does not re-start the minimum switch-on time [TiOnMin].
19 Logical I/O blocks General functions ● Normal: Direct switching in stages taking into account runtimes (e.g., motors, burners, dampers, etc.). ● Motor: Switching in stages for rotating aggregates taking into account ramp-up and ramp-down times (fan-belt protection). ● Trigger: Event-driven switching, last command takes precedence; integration of a data point (EIB, LONMARK) ● Switch: Generation of an ON/OFF pulse of a defined duration.
Logical I/O blocks General functions 19 The trigger function is used, e.g., for the integration of LON data points. Owing to the event mechanism, this function is not used for P-bus objects. Switch The Switch setting is used to generate an ON or OFF pulse of a predefined duration. A command via BACnet, or the activation of an Enable signal in one of Priorities 7…16 via the data flow connection initiates an associated pulse (event).
19 Logical I/O blocks General functions The I/O objects have a monitoring function. The output objects monitor the feedback signal from the plant. For this purpose, an address string must be entered for the [FbAddr] feedback parameter [FbAddr] and the alarm function must be enabled. The input and value objects can monitor reference values. For this purpose, the relevant reference values must be configured and the alarm function must be enabled.
Logical I/O blocks General functions 19 Override via client The input, output and value blocks can be overridden via BACnet clients or in XWP (CFC) in online test mode. User override of an input value Web client PXM20 PXM30/40/50 Online test mode in PX Design There are two options: 1. Override via a BACnet client: A BACnet client is overridden with a BACnet service. Input objects are overridden by setting the out-of-service parameter [OoServ] and writing the desired present value [PrVal].
19 Logical I/O blocks General functions User override of an output value BACnet clients BACnet Service: WriteProperty [PrVal], Value, [Prio] WriteProperty [PrVal], NULL, [Prio] ReadProperty [PrioArr] Desigo PX [PrioArr] [OoServ] [DefVal] [PRVal] [EnOp] [Rlb] [StaFlg] [ValOp] Online test mode in PX Design [EnPgm] [ValPgm] There are two options: 1. Override via a BACnet client: The override of an output or value object is based on the priority array [PrioArr] in the object.
Logical I/O blocks General functions 19 Function With a binary input object, the operating hours are determined on the basis of the ON state of [PrVal] (that is, by measuring the time for which this value is active). For multistate blocks, you can configure how many states are to be totalized. These are combined and added in a totalizer (the various states cannot be evaluated individually).
19 Logical I/O blocks General functions Maintenance message 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].
Logical I/O blocks Input blocks 19 As these states are static, they must be set manually during commissioning. Status Flag [StaFlg] The status flag [StaFlg] indicates the state of the I/O block. This pin consists of four Boolean values: ● IN_ALARM: Logic 1 (TRUE) if the event state pin [EvtSta] does not display NORMAL as its value. ● FAULT: Logic 1 (TRUE) if the [Rlb] pin does NOT display the value NO_FAULT_DETECTED. ● OVERRIDDEN: Logic 1 (TRUE) if the block point was overridden locally (e.g.
19 Logical I/O blocks Input blocks The values for slope [Slpe] and intercept [Icpt] must be defined specifically for the application concerned in accordance with the I/O system in use and the signal type. For slope and intercept values for SBT products, see Slope [Slpe] and Intercept [Icpt]. For sensors not listed, the following applies: Calculating [Slpe] and [Icpt] The values for [Slpe] and [Icpt], which are to be entered in the block, must first be calculated.
Logical I/O blocks Input blocks 19 ● Change of state messages (events / system events) ● Runtime totalization and maintenance messages ● Hardware mapping Pulse converter (pulse counter) The pulse converter object cumulates pulses for a meter. The Pulse converter object is used where meter values already manipulate in a meter object or where changes of values are required to further process control programs.
19 Logical I/O blocks Output blocks Accumulator object (counter value) The accumulator object can map counter states unchanged and free of errors due to rounding off or add the counter pulse without loss and scale the same. The accumulator object is suitable to displaying meter values that justify monetary performance. For this type of counter values, manipulations such as monthly values, etc., must never be made directly in the meter object.
Logical I/O blocks Output blocks 19 Feedback monitoring for dampers with one end switch To monitor the damper position of dampers with one end switch, the switch position must be set by defining the polarity of the feedback signal [Bop].
19 Logical I/O blocks Output blocks ● ● ● ● ● ● ● Reliability monitoring [Rlb] (FAULT alarm) Change of state messages (events / system events) Configurable switch type (Normal, Motor, Trigger) Runtimes and monitoring periods Hardware mapping (refer to Section 0) Runtime totalization and maintenance messages Process monitoring [StaFlg] Analog Output (AO) The analog output is the logical image, or memory map, of an analog control command and describes its properties.
Logical I/O blocks Value objects 19 Analog Output [PrioArr] [PrVal] [FbVal] [FbVal] := Feedback Raw Value *Feedback Slope+ Feedback Intercept If [FbAddr] Feedback_Raw_Value The value [PrVal] from the program is converted into the physical positioning value by use of a conversion curve.
19 Logical I/O blocks Value objects DmpShofEh Ag:DmpShof FanSu Ag: V(A,C-F) Fan1St On On EnCrit MI ManSwi Cp:Ml EmgOff On On/P14 DmpShofOa Ag.
Logical I/O blocks Value objects 19 ● An alarm is to be created within the CFC chart as a commandable interface of an aggregate (e.g., limit monitoring of an output value of an aggregate).
19 Logical I/O blocks Value objects for operation 19.5 Value objects for operation To simplify operation, use the value objects BVAL_OP, AVAL_OP and MVAL_OP. The blocks are specifically intended for the operation of setpoints via BACnet clients. They do not require a manual override from the operator unit. Value objects look like all other blocks, and can be connected with other blocks. The blocks do not include alarm generation or runtime totalization. 19.
Logical I/O blocks Addressing the I/O blocks 19 The logical I/O blocks are designed for universal use in various I/O systems. The specific address structures and hardware definitions are determined by the I/O system, e.g., the failsafe control value for the island bus.
19 Logical I/O blocks Addressing the I/O blocks Module type Signal type Example Analog Input R1K, P1K, P100, U10, I25, I420 R2500, R250 (only TX-I/O) T=1.1 (R1K) T1, NTC10K, NTC100K (only TX-I/O) Analog Output AI, AIS, AIL, AISL T=2.1 (AIS) Y10S T=2.1 (Y10S) Y250T T=3.1 (Y250T) PWM Binary Input Y420 T=34.1 (Y420) AO, AOS, AOSL, AOL T=36.1 (AOS) D20, D20S T=25.2 (D20) D42, D250 (only PT-I/O) DI, DIS, DIL, DISL T=26.3 (DIS) Counter Input C T=38.1 (C) Info LED Q_LED C=8.
Logical I/O blocks Addressing the I/O blocks PX compact PXC12.D PXC12-E.D PXC22.D PXC22-E.D PXC36.D PXC36-E.D Module Channel Module 19 UIO Universal I/O 1 1..4 U5..U8 1 1..12 U5..U1 6 1 1..18 U7..U2 4 R1K, U10, T1, N1K, P1K, C, D20, D20S UIO Universal I/O with Q250 4 1..4 U1..U4 4 1..4 U1..U4 4 1..4 U1..U6 R1K, U10, T1, N1K, P1K, C, D20, D20S, Q250 Layout of PXC36.
Logical I/O blocks Addressing the I/O blocks Solution 1 Many systems include a requirement for the multiple use of sensors. A typical example of this is an outdoor air temperature sensor shared across systems. The following example illustrates the simplest form of the multiple use of sensors: In CFC the current value is transmitted for further use in the program by interconnecting the blocks.
Logical I/O blocks Addressing the I/O blocks 19 procedure, to enable the multistate input to interpret the current binary signals correctly, only one binary signal may be present at any one time. If several binary signals are present at once, this is displayed as an error at the [Rlb] pin. The examples below show a possible application for multistate input blocks in conjunction with the physical I/O modules.
19 Logical I/O blocks Addressing the I/O blocks [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.
Logical I/O blocks Addressing the I/O blocks 19 [PrVal] Addr1 Addr2 Addr3 Addr4 Comment / Text group 1 0 0 0 0 Off 2 1 0 0 0 Stage 1 3 0 1 0 0 Stage 2 4 1 1 0 0 Stage 3 5 0 0 1 0 Stage 4 6 1 0 1 0 Stage 5 1 1 1 1 Stage 15 ... 16 With binary mapping, more than one hardware input or output may be active. BACnet addressing Peer-to-peer communication Data can be exchanged via peer-to-peer communication.
19 Logical I/O blocks Addressing the I/O blocks The BACnet Device as BACnet Server supports a maximum of 400 subscriptions from BACnet clients or from other BACnet devices via the BACnetReference. A BACnet device operating as a BACnet client can also accommodate a maximum of 100 subscriptions to other values via the BACnetReference. If the COV procedure is selected, COVIncrement is used for analog objects to define the value by which the present value must change to initiate a COV event.
Logical I/O blocks 19 Addressing the I/O blocks Configuration Profile 1 2 3 4 5 6 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 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 Enable operating mode KonfLCD T
19 Logical I/O blocks Discipline I/Os Addressing via standard L= DeviceType DeviceNo.GroupIndex(3RD[NVIndex.FieldIndex]) I/O ● DeviceType: M (Master). There are no slaves (S) with third-party devices There is only ever one device. ● DeviceNo: Field device identification number ● GroupIndex: Group identification: Up to 4 similar groups of an application unit may exist in the field device (e.g., lighting or window-blind groups). The group index number is optional.
Logical I/O blocks Reliability table 19 Only analog commandable values can be used. 19.8 Reliability table Value (decimal) Text 0 No error recognized. 1 No sensor. 2 Above the range. 3 Below the range. 4 Continuous loop. 5 Short circuit. 6 No output. 7 Unreliable other. 8 Process error 9 Multistate fault. 64 Subsystem not supported. 65 Subsystem feedback not supported. 66 Invalid address (syntax error). 67 Invalid feedback address (syntax error). 68 Invalid address value.
19 Logical I/O blocks Slope [Slpe] and Intercept [Icpt] Value (decimal) Text 92 Reference object cannot be commanded. 93 Actual operating mode not found in command list. 94 Invalid priority set for command (valid : 2,4,14,16). 95 Invalid object number configured in sequence table. 96 Invalid object type configured in sequence table. 97 Invalid step control configured in sequence table. 98 Neighboring object not reachable. 99 Command lists indicate different variables.
Logical I/O blocks Slope [Slpe] and Intercept [Icpt] 19 Siemens Building Technologies field devices: XWP automatically enters the combined values [Slpe] and [Icpt] (for the signal type, the field device and its measurement or positioning range) on the I/O block. Third-party field devices: You can calculate the value [Slpe] and [Icpt] using the Intercept Calculator.
19 Logical I/O blocks Slope [Slpe] and Intercept [Icpt] Signal type measurement Description Standard measuring range Resolution on the bus Value range on the bus [Slpe] [Icpt] I25/020 (Shunt 200 DC 0 ... 25mA Ohm) 1 … 5 mA 1/1000 V 0 ... 5000 0.001 0 I25/020 (Shunt 100 DC 0 ... 25mA Ohm) 0 … 10 mA 1/500 V 0 ... 5000 0.002 0 I25/020 (Shunt 50 Ohm) DC 0 ... 25mA 0 … 20 mA 1/250 V 0 ... 5000 0.004 0 I25/020 (Shunt 40 Ohm) DC 0 ... 25mA 0 … 25 mA 1/200 V 0 ... 5000 0.
Logical I/O blocks Slope [Slpe] and Intercept [Icpt] Signal type positioning Description Standard measuring range [Slpe] [Icpt] Y10S DC 0…10 V 0 … 10 V 1000 0 PPS2 interface 19 Transfer of an analog control command to a room unit connected via the PPS2 interface. Only Object 195 (= Room temperature display) can be used in the analog output block. As the value is already available as a converted or referenced value, no conversion is required, that is, [Slpe] must be defined as 1 and [Icpt] as 0.
19 Logical I/O blocks Slope [Slpe] and Intercept [Icpt] * PT-I/O modules P100 is a four-wire type Default line resistance = 0 Ohm Line resistance not compensated TX-I/O modules with island bus integration TX-I/O modules with BIM integration Pt100_4 is a four-wire type Default line resistance = 0 Ohm Line resistance not compensated R250 is a two-wire type Default line resistance = 1 Ohm Pt100_4 is a four-wire type Default line resistance = 0 Ohm Line resistance not compensated R250 is a two-wir
Logical I/O blocks Slope [Slpe] and Intercept [Icpt] 19 Power surges on U10 inputs The U10 inputs are designed for DC 0 ... 10 V with a narrower high / low tolerance range. The input reports an error when a value is stored that outside this range. A transient voltage suppressor can prevent an error message. A faulty response from the analog signal supplied by the automation station can no longer be detected. Solution examples: BSG61 0 ...
19 Logical I/O blocks Addressing entries for PXC…-U, PTM and P-Bus 19.10 Addressing entries for PXC…-U, PTM and PBus Addressing entries PX modular (PXC…-U) For the PX modular series, the P bus I/O modules at the Input-Output address pin [IOAddr] start with the prefix: "P=". Address syntax: P= Module.Channel (Signal type, parameter) Example: P=2.1 (Y10S,15) The exception is the Info LED which must have the prefix "C=" because the fixed address 8.
Logical I/O blocks Addressing entries for PXC…-U, PTM and P-Bus Module type Signal type Parameters Example Y250T 1...13, 1...13 P=3.1 (Y250T,8) 19 P=3.1 (Y250T,8,10) Y420 - AO, AOS, AOSL, AOL Binary Input D20, D20S P=34.1 (Y420) P=36.1 (AOS) - P=25.2 (D20) DI, DIS, DIL, DISL - P=26.3 (DIS) Counter Input C - P=38.1 (C) Info LED Q_LED - C=8.1(Q_LED) Q250_P, Q250A_P 0, 1...600 P=12.1 (Q250_P) Q250 - P=1.
19 Logical I/O blocks Addressing entries for PXC…-U, PTM and P-Bus 5 = 35 ... 48 seconds 6 = 48 ... 66 seconds 7 = 1.1 ... 1.6 minutes 8 = 1.6 ... 2.3 minutes 9 = 2.3 ... 3.2 minutes 10 = 3.2 ... 4.5 minutes 11 = 4.5 ... 6.3 minutes 12 = 6.3 ... 9.0 minutes 13 = 9.0 ... 11 minutes The PTM1.2Y250T(-M) module can only implement one runtime. It therefore uses the opening-command runtime for closing commands. Q250_P, Q250A_P, Q250_P3 …. 0, 1…600 -> Pulse times, where 0 = 0.
Logical I/O blocks 19 Addressing entries for PXC…-U, PTM and P-Bus Desigo PX compact PXC10-TL1 PXC12 PXC22 PXC36 PXC12-T PXC22-T PXC36-T PXC52 Signal type Module Channel Module Channel Module Channel Module Channel Module Channel Manual switch2 (only PXC36S) – – – – – – 7 1…4 – – D_M3 LEDs 8 2…5 – – – – 8 2…7 – – Q_LED Info LED 8 1 8 1 8 1 8 1 8 1 Q_LED PPS-2 signal3 3 1..5 3 1..5 3 1..5 3 1..5 3 1..
19 Logical I/O blocks Addressing entries for PXC…-U, PTM and P-Bus Addressing multistate I/Os with PTM Multistate input The multistate value is made up of several separate binary measured values. Addressing is via the input/output address [IOAddr]. In both the modular and the compact series, the logical and physical I/O must be located in the same automation station, but they do not need to be contiguous. The addressing cannot extend across automation stations.
Logical I/O blocks Addressing entries for PXC…-U, PTM and P-Bus 19 ● (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: P=Module.channel;Module.channel;Module.channel;Module.
20 Room automation Desigo room automation 20 Room automation Desigo room automation Desigo room automation offers solutions with greater functionality and flexibility allowing for energy-optimized plant operation without loss of comfort (efficiency class A). The DXR1 and DXR2 room automation stations are perfectly suited to exclusively automate heating, ventilation, and air conditioning in a room.
Room automation Desigo room automation 20 KNX PL-Link KNX PL-Link (Peripheral Link) connects communicating room and field devices (room devices, sensors, actors) with the room automation station. DALI DALI (Digital Addressable Lighting Interface) helps control lighting. 20.1.1 Configurable DXR2.. can automate up to two rooms for heating, ventilation, air conditioning, shading, and lighting, whereas DXR1 can automate one room and heating, ventilation, and air conditioning only.
20 Room automation Desigo room automation Compact DXR2 room automation stations for BACnet MS/TP Desigo CC BACnet/IP Ethernet PXG3.M PXC..-E.D KNX PL-Link KNX PL-Link Router °C °C °C AQR25.. Room sensor °C AQR25.. QMX3... Room sensor Room operator units Detector QMX3... Room operator units Applications The tables below show the functions of the different applications of the DXR2 room automation stations.
Room automation Desigo room automation 20 Application CM110664en_07 volume ● External flow control for VAV with integrated flow controller and differential pressure sensor ● Internal flow controller and differential pressure sensor for damper actuator control ● Internal flow controller and velocity sensor for damper actuator control ● Chilled water cooling coil ● Heating/Cooling coil ● Hot water heating coil ● Electric heating coil modulating, single stage or two stage ● Room temperature control by two
20 Room automation Desigo room automation Application ● Room air quality control ● Rapid ventilation ● Green leaf Four light groups ● ● ● ● ● ● ● ● ● Two blinds Manual switched control Manual dimmed control Automatic presence control Automatic brightness control Constant light control Multi group constant light control LED support on push buttons Green Leaf - RoomOptiControl Burn-in & operating hours function ● Manual control ● Automatic control with anti glare function and energy efficiency function ●
Room automation Desigo room automation 20 Application dehumidify Override function allows a technician or balancer to override the VAV applications for balancing and commissioning ● 1x Demand controlled pressure control by either: – Supply VAV position evaluation helps to optimize fan speed by averaging the 10 highest supply damper positions and providing this information to the central plant – Extract VAV position evaluation helps to optimize fan speed by averaging the 10 highest extract damper positions
20 Room automation Desigo room automation Application – Annual shading calculates the glare protection state for all facade by in-formation from annual shading computer – Thermal protection for unoccupied rooms by central global radiation sensor on weather station – Three delayed distribution groups for central blind commands for big buildings ● 2x Shading manual central operation with 3 delayed distribution groups for big buildings ● 1x Shading service ensures central commanding of blind group with high
Room automation Desigo room automation 20 Applications Room operating • • • • • • • • • • Heated / Chilled ceiling radiator • • • • • • • • • • Fan coil unit • • • VAV system • • • • • • • Lighting • • • • • • • • • • Shading • • • • • • • • • • • • Central functions1 Housing DIN Flat • • • • • • • • • • •2 •2 • • • • • • • Operating voltage 230V • 24V Inputs and outputs onboard Digital inputs 1 1 1 1 1 1 1 1 2 2 Univ
20 Room automation Desigo room automation points4 Integrated power supply for KNX (mA) 50 50 50 50 50 50 50 50 50 50 Key 1 Cannot be combined with other applications. 2 Mounting via damper shaft. 3 Cannot be extended by KNX PL-Link inputs and outputs. 4 Total number of data point used by TX-I/O, KNX PL-Link and DALI. For details, see chapter System Configuration. See Compact room automation stations, BACnet/IP, 230 V DXR2.E10.., DXR2.E09.., DXR2.E09T.. (N9204).
Room automation Desigo room automation Universal inputs 20 2 2 2 2 Triac outputs 4 4 4 4 Analog outputs (DC 0...10 V)3 1 1 1 1 Pressure sensor 1 1 1 1 1 16 16 22 19 2 50 50 Relay outputs Maximum configuration Number of I/O data points4 Integrated power supply for KNX (mA) Key 1 Cannot be combined with other applications. 2 Mounting via damper shaft. 3 Cannot be extended by KNX PL-Link inputs and outputs. 4 Total number of data point used by TX-I/O, KNX PL-Link and DALI.
20 Room automation Desigo room automation Applications for DXR1 Application Functions Variable air volume ● Supply and extract VAV with integrated damper actuator and heating/chilled ceiling ● Room temperature control ● Air quality control ● Relative humidity monitor ● Room temperature and rapid ventilation operation via KNX PL-Link room operator unit with temperature, air quality & relative humidity measurement ● Supply VAV with integrated damper actuator and staged electric reheater ● Su
Room automation 20 Desigo room automation Component DXR2.E17CX.. Room automation station, BACnet/IP, 24VAC, 17 I/Os, 60 data points QMX3.P87-1WSC Operating display panel, wall mounted (KNX) QMX3.P88-1WSC Operating display panel, thin and flush mounted (KNX) n/a Room condition monitor (BACnet/IP) Accessories for room pressurization and fume hood control Accessory device 20.1.2 n/a Sash wire sensor DXA.S04P1 Air flow pressure sensor (SCOM) DXA.
20 Room automation Desigo room automation Applications A comprehensive block library for room automation is provided as part the scope of delivery. The library contains predefined application functions for room climate, lighting, shading, and superimposed room functions. The applications can be combined with operating and display functions as required. The individual application functions can be adapted to customer needs and are programmable.
Room automation 20 Desigo room automation PXC3.E72 PXC3.E72A PXC3.E75 PXC3.E75A Bus for I/O module • • • • KNX PL-Link1 / KNX S-Mode • • • • • DALI PXC3.E16A • • Maximum configuration Number of I/O data points2 140 140 280 280 64 Inputs/Outputs for TX I/O modules 72 72 200 200 0 Devices on KNX PL-Link 64 64 64 64 0 64 64 160 n/a 64 DALI ballasts Integrated power supply for KNX (mA) 160 160 160 Key 1 Dedicated devices with KNX PL-Link.
20 Room automation Desigo room automation Operating voltage • 230V • • 24V • • • Inputs and outputs onboard Digital inputs 1 1 1 1 1 2 Universal inputs 2 2 2 2 2 4 Relay outputs 3 1 3 4 4 6 6 8 2 2 4 Triac outputs 3 Analog outputs (DC 0...
Room automation Desigo room automation 20.1.3 20 Rooms and room segments There are two methods to structure a building: ● Rooms (with fixed walls) ● Room segments (typically based on movable walls) One of the two methods or a mixture thereof is possible depending on the building structure or required flexibility (e.g., during the usage phase). A room segment is the smallest indivisible element. A room comprises at least one or several adjacent room segments.
20 Room automation Desigo RXB ● Room operating mode (occupancy and use in room) ● HVAC control via various setpoint requirements depending on the room operating mode ● HVAC setpoints via a weather-dependent adjustment ● Lighting control ● Shading control (blinds) Grouping can be used to coordinate demand, operating, and forced signals, that is: ● Request signals for hot water distribution (heating circuit) ● Request signals for chilled water distribution (cooling circuit) ● Record demand, operating, and f
Room automation Desigo RXB 20 The range consists of controllers, operator units and predefined applications. The applications are configured and downloaded with the ETS Professional commissioning and service tool. See Working with ETS (CM1Y9779). RXB topology The Desigo RXB room automation system is based on KNX/EIB technology. To integrate Desigo RXB into the automation level, the RXB data is mapped to BACnet. Desigo CC PXM20 BACnet/IP PXC50/100/200...
20 Room automation Desigo RXB 20.2.1 Product range overview Desigo RXB is an innovative range of controllers and room units. Data communication is based on KNX/EIB technology. Desigo RXB hardware The range comprises compact controllers, easy-to-operate room units and controllers in room-style housings. The input and output configurations of the controllers, and the housing style are fully optimized to suit their field of application.
Room automation Desigo RXB 20.2.2 20 RXB and the management level Generic and engineered operation is available at the management level. See Desigo CC System Description (A6V10415500) 20.2.3 RXB and the automation level Desigo RXB is integrated into the automation level with the PX KNX system controller. The main tasks of the system controller are: ● Mapping RXB data to BACnet objects ● Implementing higher-level functions (grouping, time schedules, etc.
20 Room automation Desigo RXB 20.2.5 Mapping RXB in the PX KNX system controller The RXB system is mapped to the PX KNX system controller with objects. These objects are called discipline I/Os and are components of the block library. See PX KNX, RXB integration – S-Mode (CM1Y9775). The following types are available for RXB: ● HVAC: Comprises all the HVAC information ● Shared: Contains shared data points (e.g., time schedules, occupancy status, etc.
Desigo Open 21 Desigo RXB 21 Desigo Open Desigo Open lets you integrate devices and systems from different manufacturers into the Desigo system. Integration with Desigo Open offers: ● Standardized automated functions, operating and monitoring of the entire building ● Single-station operation, common view and display. Simplified multidisciplinary operation, common reporting and common alarm management.
21 Desigo Open Integration on management level Which plant sections can be integrated into Desigo on which level? Desigo Open system Desigo Open application Data points Desigo management platform Desigo CC 1,000 - 10,000 Energy monitoring, fire security, access control and security Desigo PX PX Open 50 - 2,000 Power distribution, refrigeration machines Desigo TX-I/0 TX Open Max. 160 Pumps, variable speed drives, meters, etc.
Desigo Open Integration on automation level 21 OPC DA client An OPC client interface lets you integrate any OPC server, using the Data Access specification. An offline Importer supports the engineering workflow to integrate OPC items. See OPC Server Integration Guide (A6V10415483). OPC DA server An OPC server option provides a freely configurable set of data points for integration in any enterprise system, using the OPC DA standard.
21 Desigo Open Integration on automation level ● ● ● ● PX SCL PX RS-Bus PX Pronto PX Open Platform (SDK) Data points PXC001.D PXC001-E.D PXA40-RS1 PXA40-RS2 PX KNX 2,000 2,000 n/a n/a PX Modbus 250 250 800 2,000 PX M-Bus 250 250 800 2,000 PX SCL 250 250 800 1,000 PX RS-Bus 2,000 2,000 n/a n/a PX Pronto 2,000 2,000 n/a n/a The platform for integrating LonWorks compatible third-party devices consists of: ● System controller PXC00.D and automation station PXC50.D, PXC100.
Desigo Open Integration on field level 21 ● Alarm handling, device monitoring ● Trend storage to record meter readings The PXC001.D system controller can integrate M-Bus via BACnet/LonTalk. The PXC001-E.D system controller can integrate M-Bus via BACnet/IP. The PXA40RS1 and PXA40-RS2 option modules support additional data points. See PX M-Bus (CM2N9774). PX SCL PX SCL lets you quickly develop simple protocol solutions.
21 Desigo Open Integration on room level Bus/GENIbus/G120P data points can be made available to all the devices and applications in the Desigo system. The PXC50..D, PXC100..D and PXC200..D automation stations support TX Open. You can attach up to five TX Open modules to one PXC automation station. Xworks Plus (XWP) is used to engineer all solutions. Various compounds are available, e.g., for pumps, variable speed drives and heat meters. Predefined solutions allow for simple commissioning.
System configuration Integration on room level 22 22 System configuration System overview Desigo CC Internet BACnet Internetwork (BAC0) BACnet/IP PX Site PX Site PXG3.L PXC..D PXC..D PXG3.Wxxx-1 BACnet/LonTalk PX Room integration PXC..D PXC..D RX Room solution Room automation PXC..D PXC..
22 System configuration Integration on room level Each BACnet device can communicate with another BACnet device in the internetwork. A BACnet device in one internetwork cannot communicate with a device in another internetwork. A Desigo management station can be used to integrate the operation of several BACnet internetworks and other systems (see Desigo system). When defining the system configuration, FLN integrations (LonWorks, KNX) are also added to the BACnet internetwork.
System configuration Technical limits and limit values 22 PX site A Desigo PX automation system site. The PX BACnet devices which control the plant in a PX site are interconnected via the global objects and the primary copy procedure. A PX site is independent of the limits affecting the BACnet network. A site can extend over several BACnet networks. One BACnet network may include several sites. All the associated limits must be maintained simultaneously.
22 System configuration Maximum number of elements in a network area The limits are defined to ensure the full and correct functioning of the system. Consult Headquarters before exceeding the recommended limits. HQ can modify the recommended limits on the basis of new findings at any time. Changes are notified in Facts bulletins. Certain limits cannot be verified (for reasons of cost or quantity).
System configuration 22 Maximum number of elements in a network area Number of elements / Per network area Desigo system BACnet internetwork BACnet PTP internetwork BACnet/ IP network BACnet MS/TP network BACnet/ LonTalk network LonWork s trunk (FLN) PX KNX integration PX site PXG3.
22 System configuration Desigo room automation system function group limits 20 These limits apply only to IP-based DXR2 devices. 21 These limits apply to MS/TP-based DXR2 devices. 23 Multiple IP segments per BACnet internetwork. 24 One IP segment per BACnet internetwork. For more information about networks, see Application Guide for IP Networks in Building Automation Systems (CM110668). 22.
System configuration Devices 22 Desigo room automation stations with own alarming Item Limit Description Trend per room 5 It is assumed that a maximum of 5 trend points are logged on average. Assumption for the trend interval: 15 minutes. Number of external BACnet references 500 Maximum number of external BACnet references that support a Desigo room automation system function PX.
22 System configuration Devices PX Compact Item PX Modular PXC00.D PX KNX9 PXC001.D PXC001.D PXC12.D PXC22.1.D PXC50.D PXC100.D PXC12-E.D PXC22.1E.D PXC50-E.D PXC100-E.D PXC200-E.D PXC00-E.D PXC001-E.D PXC001-E.D + PXA40RS.. PXC22.D PXC200.D PX Open10 PXC-NRUF PXC36.1.D PXC36.1E.
System configuration Devices 22 Key 1 PXM20, PX-Web and XWP are temporary alarm receivers. 2 Desigo CC is a configured alarm receiver. The number of entries in the notification class is limited to 20. The total number of different configured alarm receivers across all notification classes is limited to 30. 3 Max. number of BACnet references, COV servers: SubscribeCOV requests which can be accepted. Example: 1400: 1 client and 1400 values or 2 clients and 700 values. 4 Max.
22 System configuration Devices D-MAP RAM If the whole D-MAP RAM is taken up with trendlog objects, a delta (differential) download will no longer be possible. The overall size of the free and used D-MAP RAM can be viewed with XWP, Desigo CC or PXM20. The information concerned is stored in the device object under the memory statistics property [MemStc]. Access rights management Access rights are managed via USPRF. You can define a maximum of 10 user groups and 20 users.
System configuration Devices 22 The following values can be assumed for reaction times depending on the number of physical data points: Reaction times depending on number of physical data points Without LonWorks devices Up to 5 LonWorks devices 5 to 20 LonWorks devices Max. 150 data points < 1s 1-2s 3-4s Max. 250 data points 1-2s 2-3s 4-5s Max. 350 data points 2-3s 3-4s 5-6s 22.4.4 PX Open integration (PXC001.D/-E.D) Item Limit Description Modbus data points [250*] Max.
22 System configuration Devices 22.4.8 TX Open integration (TXI1/2/2-S.OPEN) Item Limit Description TXI1.OPEN 100* Max. number of data points per TX Open. TXI2.OPEN 160* Max. number of data points per TX Open. TXI2-S.OPEN 40* Max. number of data points per TX Open. 22.4.9 Number of data points on Desigo room automation stations Number of data points on the TX-I/O subsystem Every used data point on TX-I/O is counted. ASN Product description Data points Description TXM1.
System configuration Devices 22 ASN Product description Data points Description QMX3.P30 Freely configurable operator unit, wall mounted 1 Fixed count QMX3.P36 Freely configurable flush-mounted room unit 3 Fixed count QMX3.P34 Freely configurable operator unit, wall mounted 3 Fixed count QMX3.P37 Freely configurable operator unit, wall mounted 7 Fixed count QMX3.P40 Room operator unit without display, with temperature and humidity sensor 2 Fixed count QMX3.
22 System configuration Devices ● Max. number of devices: – 64 on PXC3.xx – 32 on DXR2.xx ● The range of the Individual Address (IA) can be defined as follows in Desigo room automation: – KNX S-Mode: 1 … 179 – KNXnetIP: 180 und 181 – KNX PL-Link devices: 182 … 250 – Desigo room automation station: 251 – Max. number of KNX S-Mode group addresses: 238 22.4.10 Number of data points for PXC3 A PXC3.E72x supports max. 4 rooms or 8 room modules and is limited to 72 TXI/O data points. A PXC3.E.75 supports max.
System configuration Devices 22.4.11 22 Number of data points for DXR1 ASN Max. number of data points Description DXR1.E04PDZ112 n/a 2 UI DXR1.E09PDZ112 16 2 UI, 4 DO, 1 AO DXR1.E09PDZ113 16 2 UI, 4 DO, 1 AO DXR1.E10PL-112 22a2 2 UI, 1 DI, 4 DO, 1 AO b2 DXR1.E10PL-113 19 2 UI, 1 DI, 4 DO, 1 AO DXR1.E02PLZ112 2 n/a DXR1.M04PDZ112 n/a 2 UI DXR1.M09PDZ112 16 2 UI, 4 DO, 1 AO DXR1.M09PDZ113 16 2 UI, 4 DO, 1 AO Key 22.4.
22 System configuration Devices Web clients for room operation Item Limit Description 1 3 Recommended number of web clients that can simultaneously access a DXR2. Templates with standard background pictures2 2 Maximum number of different templates which are using the default background pictures. Customized background pictures2 1.5 MB Maximum total size of all customized background pictures (the PNG file format is used as a reference). QMX7.E38 and standard web clients Key 22.4.
System configuration 22 Devices 22.4.15.1 Device-related limits Function Touch panel BACnet/IP PXM30.E BACnet/IP web interface PXM40.E PXM50.E PXG3.W100-1 PXG3.W200-1 All data points of all assigned devices Generic operation Graphical operation (BACnet objects) 500 1,000 1,000 2,000 Haystack interface (BACnet objects) 500 1,000 1,000 2,000 Online trends 20 20 20 50 Graphics (average complexity) 20 20 20 50 PXM40.E PXG3.W100-1 PXG3.W200-1 22.4.15.2 Memory management PXM30.
22 System configuration Devices 22.4.15.4 * The selection of integrated data points can be optimized and individually customized with the Advanced Tool in the data point integration function. ** Primary plants: Per hardware I/O some 2.5 BACnet objects are integrated on average. Technical limits The following limits are recommended and verified. Function Touch panel BACnet/IP web interface TCP/IP BACnet/IP PXM50-1 PXM50.E PXG3.W100-1 PXM40-1 PXM40.E PXG3.W200-1 PXM30-1 PXM30.E Max.
System configuration Devices 22 Data point integration: MS/TP devices are considerably slower than IP devices due to the lower network speed. Reference value: Approximately 15 times slower (depending on the project setup). MS/TP is tested with 10 devices that support COV (e.g. DXR2). Recommendation: Assign or integrate a maximum of 10 MS/TP devices on one network branch. More devices and/or network complexity are permitted, but they may result in longer and inconsistent times and degraded performance.
22 System configuration Devices Item Limit Description MS/TP telegrams [100 - 140] pkt/s @115,200 bps The BACnet router integrates BACnet MS/TP not as a field bus in the network. The router operates transparently and routes all data traffic addressed to the subnet. This is why global broadcast telegrams negatively impact transmission performance of the router and end devices. [-120] pkt/s @76,800 bps Max.
System configuration Devices 22.4.19 22 Desigo Insight For the system configurations of the Desigo Insight management station V6.0 SP2, see Desigo Building Automation System 6.0 SP, Technical Principles (CM110664 / 2016-09-20). 22.4.20 Desigo Xworks Plus (XWP) Item Limit Description Length of site name 9 Max. 9 characters.
22 System configuration Applications 22.5 Applications 22.5.1 Peak Demand Limiting (PDL) Item Limit Comment Monitored loads [28*] Max. number of monitored loads. Tariff limits 4* Max. number of configurable tariff limits. Cycle time [ms] 500 Minimum cycle time required to ensure the functioning of the PDL application. To guarantee the cycle time, use a PX modular automation station (PXC 100/200…D, PXC12/22/36…D).
Compatibility Desigo version compatibility definition 23 23 Compatibility For information on the system compatibility of the Desigo CC management platform, see Desigo CC System Description (A6V10415500). For information on the system compatibility of the Desigo Insight management station V6.0 SP2, see Desigo Building Automation System 6.0 SP, Technical Principles (CM110664 / 2016-09-20). For the current state of the Valid Version Set (VVS), see the document Desigo_VVS_6.10.48x.pdf.
23 Compatibility Desigo system compatibility basics ● ● ● ● ● ● ● ● ● Desigo V2.37 Desigo V4.0 Desigo V4.1 Desigo V5.0 Desigo V5.1 Desigo V6.0 Desigo V6.1 Desigo V6.2 Desigo V6.2 Update 23.2 Desigo system compatibility basics 23.2.1 Compatibility with BACnet standard Desigo supports the following BACnet protocol revisions: ● Desigo CC: 1.15 ● Desigo room automation stations: 1.13 ● Desigo PX, PXM20: 1.12 ● Desigo Control Point PXG3.Wxxx and PXMx0: 1.13 ● PXG3 router: 1.
Compatibility Desigo system compatibility basics ① Desigo CC ② Desigo devices with a lower revision or the same revision as Desigo CC ③ Third-party BACnet devices with a higher revision than Desigo CC 23 Properties from earlier BACnet protocol revisions can be read by a BACnet device even if the device supports a higher BACnet protocol revision than Desigo CC. New properties from a BACnet protocol revision higher than Desigo CC cannot be read or changed, because they are not recognized by Desigo CC.
23 Compatibility Desigo system compatibility basics Version in parentheses () for DWP client (Siemens internal) only. Note Windows 7 and Windows 8.1 are not supported. For more information about certificates, see IT Security in Desigo Installations (CM110663). Unlisted Microsoft client operating systems/editions (especially Home Premium or 32-bit versions) are not supported. Branch Office Server (BOS) only supports server operating systems. LMS/LMU supports several Microsoft client operating systems.
Compatibility Desigo system compatibility basics 23.2.5 23 Compatibility with web browsers Product Tested compatibility with web browsers Microsoft Edge as of Google Chrome 80.0.361 (Chromium) Firefox Safari 10 SSA 1 / Web Interface as of V4.0 Yes Yes Yes Yes ABT Site online help as of V4.0 Yes Yes Yes No Desigo Control Point See chapter Desigo Control Point Key 1 Support of of HTML5-capable browsers with native SVG format.
23 Compatibility Desigo system compatibility basics BACnet peer-to-peer communication between Desigo PX devices from the earliest version to the current version is guaranteed. Restrictions As soon as an automation station or a system controller with the newest Desigo firmware is used in a runtime system, all operating clients and Desigo Control Point must be upgraded to the same version. Otherwise, only limited operation is available.
Compatibility Desigo system compatibility basics 23.2.13 23 Compatibility with Desigo PX / Desigo room automation The modular Desigo PX automation stations / system controllers PXC00/50/100/200-E.D are supported as Desigo room automation system function controllers for the PXC3 room automation stations. For performance reasons, use PXC00-E.D where possible. The local operator unit PXM10 cannot be used together with the following devices: ● PXC3 room automation stations ● PX KNX (PXC001.D/PXC001-E.
23 Compatibility Desigo Control Point 23.3 Desigo Control Point 23.3.1 Compatibility with earlier systems System compatibility PXM50-1 PXM50.E PXM40-1 PXM40.E PXM30-1 PXM30.E PXG3.W100-1 PXG3.W200-1 Desigo PX primary plants n.a. as of Desigo V4.0 Desigo room automation PXC3 n.a. as of Desigo V5.0 Desigo room automation DXR2 n.a. as of Desigo V6.0 BACnet third-party devices n.a. as of BACnet revision 1.05 (≙ Desigo V4.0) 23.3.
Compatibility Desigo Control Point 23 Desigo Touch and Web PXM40 / PXM50 PXG3.W100 FW Update ① PXM40-1 / PXM50-1 PXG3.W100-1 PXG3.W200-1 Same dimensions for the cut out as for mounting in the panel Supply voltage AC/DC 24 V Ethernet connection Similar look and feel 23.3.3 ② PXM40-1 and PXM50-1 panels are backward compatible with PXG3.W100 (PXG3.W100 FW updated required). For engineering, see ABT SSA User's guide (A6V10429119), Section 4.4.
23 Compatibility Upgrading from Desigo V6.2 Update (or Update 2) to V6.2 Update 3 Graphics editor Google Chrome* Graphics can be created and edited without a tool using this browser. Grade A Google Chrome on desktop* Recommended web browser for standard operator units. Google Chrome on Android tablet* Google Chrome on Surface tablet* Microsoft Edge on Surface tablet ● Fully tested and supported browser. ● All functions are available and can be executed as documented.
Compatibility Upgrading from Desigo V6.2 Update (or Update 2) to V6.2 Update 3 23.4.2.1 23 Project case 1: Maintenance Cases where you want to maintain your data and your site/project: ● Edit an existing site/project. Edit an existing site/project without adding automation stations or new features. ● Extend the site with new devices of the same type, while keeping the same old application version, and not using new features.
23 Compatibility Upgrading from Desigo V6.2 Update (or Update 2) to V6.2 Update 3 ● Extend the site with new devices from the latest version (recently introduced). ● Benefit from new features both on firmware and applications (recently introduced). ● Replace an automation station type with another automation station type, which does not have the possibility to fully reuse the application program, and needs to be reprogrammed. Prerequisites for upgrading from Desigo V6.2 Update (or Update 2) to V6.
Compatibility Siemens WEoF clients 23.4.3 23 Upgrading restrictions Branch Office Server (BOS) Desigo V6.2 Update 3 is compatible with Branch Office Server (BOS) V6.1, but we recommend that you upgrade to BOS V6.2. Desigo PXR / LonWorks system controller A migration of previously programmed and operational V2.2 - V2.37 system controllers PXR11/12 to Desigo V6.2 Update using PXC00(-E).
23 Compatibility Migration compatibility Described in Requirements CM110496 Unigyr tools V7.61 with Unigyr automation level V7.64 Migration of Integral Described in Requirements CM110499 NCRS from V3.1 (only automation level) CM110498 NITEL from V1.31 (only automation level) For replacing Integral RS modules (NRUA, NRUB, NRUC, and NRUD) with PXC automation stations and PXC-NRUD modules, Desigo supports the use of PXCNRUD modules with PXC100/200(-E).D and PXC50(-E).D.
Compatibility Hardware requirements of Desigo software products 23 23.7 Hardware requirements of Desigo software products Product CPU Frequency Storage Hard disk Other ABT Site Compatible with Intel and AMD technology > 2.0 GHz 8 GB RAM (> 3 GHz recommended) (> 16 GB RAM recommende d) > 100 GB SSD or HDD with very good performance. The greater the number and size of the projects, the more additional memory is required. An ABT project size may be anywhere between 250 MB and 30 GB.
23 Compatibility Hardware requirements of Desigo software products ● LonWorks interface card or LonWorks dongle ● Ethernet interface ● Connection cable for automation stations ● USB port for P-bus BIM and SSA Discovery Network Tool (DNT) connection The following software is required: ● Operating system: See chapter Compatibility with Operating Systems ● Microsoft Office: See chapter Compatibility with Microsoft Office ● Acrobat Reader 6.
Desigo PXC4 and PXC5 24 24 Desigo PXC4 and PXC5 PXC4 & PXC5 Range Overview (A6V11973782) Description of the range for a small system with: ● Desigo Control Point embedded management station ● Desigo Control Point touch panel range ● PXC4 automation station with I/O extension modules ● PXC5 system controller PXC4 & PXC5 Planning Overview (A6V11973797) Includes the following topics: ● Planning guidelines ● Overview of compatible products ● Various typical topologies ● Technical limitations CM110664en_07
25 Compatibility of Desigo V6.2 Update 3 with PXC4 and PXC5 25 Compatibility of Desigo V6.2 Update 3 with PXC4 and PXC5 Overview Online system Desigo V6.2 Update 3 with PXC4 and PXC5 ● Full BACnet communication between the Desigo CC management platform and the Desigo V6.2 Update 3 system. ● Full BACnet communication between the Desigo CC management platform and the Desigo PXC4 and PXC5 system. ● BACnet communication between Desigo V6.2 Update 3 and Desigo PXC4 and PXC5: Via COV's.
Compatibility of Desigo V6.2 Update 3 with PXC4 and PXC5 Building A 25 BACnet Internetwork 1 (BAC0) System-wide Scope CC Client CC Server Desigo CC Desigo CC IP Subnet 192.168.102.x VLAN ID2 Foreign Device Building Scope: Central Functions BACnet Communication Path PXC3 DXR2 Desigo PX BBMD BACnet/IP UDP Port: BAC0 IP Subnet 192.168.103.x VLAN ID3 IP Subnet Floor Scope: Flexible Rooms PXC3 DXR2 PXC3 DXR2 PXG3/PX BBMD BACnet/IP UDP Port: BAC0 IP Subnet 192.168.104.
25 Compatibility of Desigo V6.2 Update 3 with PXC4 and PXC5 For more information, see XWP Online Help.
Issued by Siemens Switzerland Ltd Smart Infrastructure Global Headquarters Theilerstrasse 1a CH-6300 Zug +41 58 724 2424 www.siemens.com/buildingtechnologie s CM110664en_07 © Siemens Switzerland Ltd, 2015 Technical specifications and availability subject to change without notice.
