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 ................................................................................................................................
8 8.1 8.2 8.3 8.4 Events and COV reporting ............................................................................................................... 131 Sources and causes of system events ........................................................................................................ 131 Routing system events .................................................................................................................................. 131 Sources and causes of COVs .......................
16.1 16.2 16.3 16.4 16.5 16.6 16.7 16.8 User functions ................................................................................................................................................ 210 Main components .......................................................................................................................................... 212 Access and security.................................................................................................................................
22 22.1 22.2 22.3 22.4 System configuration ....................................................................................................................... 312 Technical limits and limit values .................................................................................................................. 314 Maximum number of elements in a network area ..................................................................................... 315 Desigo room automation system function group limits ...
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 .................................
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 | 351
3 System overview Management level 3.
System overview Management level 3 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 Web interfaces and touch panels The various operator units cover all the various requirements in terms of location and function. PXG3.W100-1 and PXG3.W200-1 web interface The BACnet/ IP Web interface permits local and remote operation of Desigo primary and room automation stations as well as third-party BACnet/IP devices. The products PXG3.W100-1 and PXG3.W200-1 vary in functionality as well as permissible system limits.
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 3 Field level Desigo RXB The RXB room controllers control the room climate in individual rooms and important parameters of the applications can be configured. The RXB room controllers communicate via KNX. The PX KNX system controller connects the room automation devices to Desigo PX and the management level and assumes coordination functions for room automation (grouping, scheduling, demand signal exchange, peer-to-peer, etc.). 3.
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 Topologies ● PX Open MONITOR lets you debug PX Open programs. ● TX Open tool lets you configure and commission TX Open modules.
System overview 3 Topologies Small system on BACnet/LonTalk Desigo Control Point BACnet/LonTalk PXC12/22/36.D PXC50/100/200..D TXM1 TXI... Compact Modular TX-I/O- TX Open Third-party integration Medium system Desigo CC Web client Desigo Control Point BACnet/IP Ethernet DXR1 PXC 12/22/36-E.D PXC50/100/ 200-E.D Compact TXI... PXG3.L PXG3.W100/200-1 PXC001-E.D PXC001-E.
System overview 3 Communication principles Large system E-Mail Desigo CC Pager Web client Desigo Control Point BACnet Third-party system Mobile phone @ DSLModem BACnet/IP PXC12/22/36-E.D TXI... PXC50/100/ 200-E.D Compact TX Open PXG3.W100/200-1 Web interface PXG3.L PXC001-E.D PXC001-E.D PXG3.
3 System overview Communication principles BACnet BACnet (Building Automation and Control Networks) is a communications protocol for building automation and control networks. BACnet ensures the interoperability between devices from different manufacturers. See http://en.wikipedia.org/wiki/BACnet. VendorID Each BACnet device has a VendorID to identify the manufacturer. The VendorID for the Siemens BACnet system devices is 7.
System overview Communication principles 3 Client/Server A BACnet device can assume two different roles within a system, the role as a server and the role as a client. These roles are defined as follows: ● Client: A system or device which uses another device via a BACnet service (service request) for a specific purpose. The client (e.g., Desigo CC, operator unit) requests a service from a server. ● Server: A system or device which responds to a given service request. The server (e.g.
3 System overview Data maintenance ● Desigo CC: AMEV profile MOU-B ● Desigo PX: AMEV profile AS-B Desigo room automation BACnet is used to exchange information between PX automation stations and DXR2 and PXC3 room automations stations and the management platform. Desigo RX The Desigo RXB room automation range communicates via KNX S-Mode (EIB). Restrictions for LonWorks A LonWorks network cannot be segmented with LonWorks routers, as the message length for BACnet is 228 bytes for performance reasons.
System overview Data maintenance 3 All process data and parameter settings, even those that are not mapped to BACnet objects (engineering setting), can be monitored and operated in Xworks Plus (XWP). BACnet clients only see what is available via BACnet. If several clients modify the same process data, the last change is accepted. Volatile and non-volatile process data and parameter settings The majority of the process data is volatile data, which is recalculated when the automation stations are restarted.
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.
System overview 3 Data maintenance ● PXKNX library (RXB) ● PXE library ● PXE SCL library (Structured Control Language) ● PXR library ● 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.
3 System overview 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.
System overview 3 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.
3 System overview Views 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 without changing the technical structure. The UD can be used in the management platform in addition to the TD. The detailed view in the PXM20 operator units shows the UD as information.
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.
Desigo workflow, tools and programming 4 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.
4 Desigo workflow, tools and programming 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.
Desigo workflow, tools and programming Coverage of the system 4 ● 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 engineering and operating, diagnostics and error recovery via an external network connection 4.
4 Desigo workflow, tools and programming 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.
Desigo workflow, tools and programming 4 Main tasks Management Functions Desigo CC Desigo CC Desigo CC GG System Functions Desigo XWP PXCx00-x.D Project Manager Utilities Network Configurator Point Configurator Desigo Configuration Module CFC Hierarchy Viewer Report Viewer Desigo Room Automation DXR2 PXC3 TX-I/O modules ABT 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.
4 Desigo workflow, tools and programming Main tasks ● Sales: Offer preparation and tracking ● Planning/Engineering: Network planning and design, floor plan, cabling, designing control cabinets, designing electrical wiring diagrams, creating rating plates, validating pharma systems ● Project management: Ordering devices, project planning, claim management, project task planning ● Service management: Service database for devices, network planning, remote service platform Sales support Desigo Configuration
Desigo workflow, tools and programming 4 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,
4 Desigo workflow, tools and programming Main tasks 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. Creating a technical hierarchy The technical hierarchy is the BACnet view on the Desigo system. It is based on the plant-related structure in the building. This hierarchy is defined during engineering.
Desigo workflow, tools and programming 4 Tools for different roles – – Control of project data access, through login data Checking project parts in and out for working on engineering data in parallel 4.4 Tools for different roles In a project different roles are responsible for different tasks. Based on these roles, there are various tool packages with different functions and licenses.
4 Desigo workflow, tools and programming Working in parallel and subcontracting HQ libraries There are HQ libraries for every engineering level.
Desigo workflow, tools and programming 4 Workflow for primary systems Working in parallel during service A service technician can connect with the plant by remote and make changes. To do this, data is transferred from the Branch Office Server to the local hard disk. After the technician is done, the changes are transferred back to the Branch Office Server, so that the project database is up-to-date again.
Desigo workflow, tools and programming 4 ● ● ● ● Workflow for room automation classic Program in CFC Define points in the I/O Address Editor Parameterize in the Parameter Editor Define alarming and trending DNT and DPT Test and commission: ● Export data to Desigo CC ● Download firmware (upgrade if necessary) ● Load configurations and programs ● Carry out point test ● Debug in CFC (if necessary) ● Create commissioning documentation (local reports) ● Specialties: – Integration (TX Open Tool, BIM Tool) – A
Desigo workflow, tools and programming Desigo Configuration Module (DCM) 4 ● Program automation stations (ABT Pro) ● Create templates for type-based automation stations (ABT Site > Configuration) ● Create templates for room control units ABT Site > Building Create instances in the building: ● Create automation stations, or rooms, based on the project-specific library per floor ● Edit room parameters ABT Site > Startup Commission: ● Configure and load automation stations (node setup) ● Carry out point te
4 Desigo workflow, tools and programming Desigo Xworks Plus (XWP) Desigo room automation often uses the same structures and functions, you can indicate a multiplier on each sublevel within the Desigo room automation level. Automation level At the automation level you can calculate the required hardware based on specified data points. You can choose and calculate many variants using presettings. Variants include, e.g.
Desigo workflow, tools and programming Desigo Xworks Plus (XWP) 4 Xworks Point Configurator The Xworks Point Configurator lets you define the functions of an automation station. You can insert solutions for the object plant, plant section, aggregate and component into this technical hierarchy. You can configure prebuilt verified solutions using options (leaving out) or variants (options). After you select and configure the solution, the program is automatically created.
4 Desigo workflow, tools and programming 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.
Desigo workflow, tools and programming Desigo Xworks Plus (XWP) 4 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.
4 Desigo workflow, tools and programming Desigo Xworks Plus (XWP) Programming in Xworks Plus When the technical hierarchy and the automation station are defined, and the I/Os are configured and addressed, you can create a program that corresponds to the selected and configured solutions from the Xworks Point Configurator. If you use the solution library, you do not have to program in CFC. Workflow The workflow for creating programs usually runs as follows.
Desigo workflow, tools and programming 4 Desigo Xworks Plus (XWP) The CFC Classic editor shows all blocks that are used in the program, nested plans, all available CFC block libraries and the selected plan with the plan interfaces to other plans. This view is available offline for programming and online for checking the signal flow. The CFC Classic editor lets you compile programs, that is, create loadable programs.
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 Project data storage in a Desigo project is handled by Xworks Plus (XWP), that is, you can create a customer project in XWP and check it in to the Branch 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.
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 The following figure shows a simplified P&I diagram of a partial air conditioning system. The heating coil and its components, including the automation station sequence, are encircled. 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 Programming in ABT for Desigo room automation In Desigo room automation, the application architecture comprises the following elements: ● Hardware configuration: Description of device configurations of the PXC3 automation station ● BACnet description with field device configuration for TX-I/O, KNX PL-Link and DALI ● Automation program: Application description comprising application functions, I/Os and CFC charts This division lets you define ap
Desigo workflow, tools and programming 4 Programming in D-MAP Primary I/O I/O I/O Prim Prim Prim PX Central Central Central PXC3 DXR2 PXC3 DXR2 CenGen CenGen CenGen CenGen CenGen CenGen CenGen CenHvac CenHvac CenHvac CenHvac CenHvac CenHvac CenHvac RCoo RCoo RCoo RCoo RCoo RCoo CenLgt CenLgt CenLgt CenLgt CenLgt CenLgt CenLgt Room Room Room Room Room RHvacCoo RLgtCoo Room RHvacCoo RHvacCoo RHvacCoo RHvacCoo RHvacCoo RLgtCoo RLgtCoo RLgtCoo RLgtCoo RLgtCoo I/O I/O I/O CenShd CenShd CenShd Cen
5 Control concept Programming in D-MAP 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.
Control concept Programming in D-MAP 5 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.
5 Control concept Programming in D-MAP 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).
Control concept Programming in D-MAP Supply chain Consumers Hot water Air treatment and air posttreatment (heating register) 5 Radiators (radiator, convector) Floor heating, domestic hot water heating Cold water Air treatment and air posttreatment (cooling register) Cooling surface (chilled ceiling) Air Air posttreatment (dampers) Electricity HVAC consumers, other consumers Coordinator and dispatcher In addition to the three chain links producer, distributor, and consumer, there are the logical
5 Control concept Programming in D-MAP 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.
Control concept Control concept and control blocks 5 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.
5 Control concept Control concept and control blocks Structure control functions In this way, complex control and monitoring functions of a plant can be logically subdivided to allow for clear assignment of the function unit or the real element of the plant. The higher-level control concentrates on the control and monitoring of the overall plant, while the sub-control function units assume internal control and monitoring of the given elements for the function unit.
Control concept Control concept and control blocks 5 Control hierarchy Control hierarchy is the map of the functional assignment and linking of those function blocks included in the control concept for a plant. The structure of the control hierarchy is subject to certain rules. A distinction is drawn between higher-level plant control and local control of the functional units.
DefVal:Off En AO E,H En BVAL PrVal FbVal En BO Frost EnPgm PrVal TOa ValPgm OpSta En TSu EnSfty On Dstb En On PrVal FbVal KickDmp ValSfty MI E,H AO BVAL En On En E,H M Frost BO Sequence table En OpMSwiCnv Ax: DMUX8_BO OpModSwi Cp:MI EnPgm PrVal MVAL KickDmp OpModMan Cp:MVAL_OP ValPgm OpSta E,U BI EmgOff On En ManSwi Cp:Ml MI E,U BI ErcRo DmpShof On/P14 Open/P14 SmextEh On/P14 DmpShofOa Ag.
Control concept Control concept and control blocks 5 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.
5 Control concept 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.
Control concept 5 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. Plant safety Operator level Local manual intervention The operator level is where components are overridden manually.
5 Control concept Control concept and control blocks Status monitoring [AO, BO, MO, AVAL, BVAL, MVAL] The process is monitored via the feedback signal, and in the case of switching blocks, also via the ramp-up and ramp-down parameters set in [TbTiDly]. If the feedback value deviates from the present value [PrVal] and the delay in [TbTiDly] has not yet expired, the process is in a transitional state. The status monitoring function shows the status at the transient state [TraSta] output.
Control concept 5 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 Dstb PrVal Off Ort Ax:OR P4 Crit CritActv P15 Pgm 13. ValCrit 12. EnCrit 15: ValPgm 14: EnPgm reports the fault and shuts down itself via the back 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.
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 5 OpMod [On/Off] Yes Local control design 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.
Control concept Superposed plant controls 5 block is placed before plant control as illustrated in the following figure. All potential influences are interconnected, prioritized by importance on the block and the corresponding required plant operating mode is determined. Example: ● A fire detector as a high priority (P04) and requires the plant operating mode EmergOff. ● The smoke extraction switch has the highest priority (P01) and demands plant operating mode smoke extraction.
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.
Control concept 5 Superposed plant controls 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., a maintenance switch). This Look Ahead mechanism is described in greater detail in this chapter. This block does not contain interlocks of individual functional units within aggregates.
5 Control concept Superposed plant controls Step 1: Safety function AllLifeSafety If all switch commands for a given plant operating mode have the priority Life safety, it is referred to as the AllLifeSafety plant operating mode. A pending AllLifeSafety plant operating mode in the [ValPgm] is executed immediately in all cases and maintained regardless of previously existing and newly occurring faults in the plant – human life takes precedence over plant safety.
Control concept Superposed plant controls 5 Step 5: Step-up sequence The step-up sequence is then started for the new plant operating mode. The remaining aggregates are switched on per the data in the function table. The switch on takes place in the table sequence from left to right, in other words, the first aggregate in the switch sequence is the switched on first. The parameterized times for the time on delay is active during step-up.
5 Control concept Superposed plant controls Sequence 1 1 Object nr. Sequence 2 2 3 5 None None State monitoring 4 Sequence 3 6 7 8 None 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 Spec. cmd Priority Switch-on 1 On Spec. cmd Spec. cmd Switch-on 2 Not cmd Spec. cmd Spec. cmd Sequence 1 On Stage X Switch-on 3 On Spec. cmd On Spec. cmd Spec.
Control concept Superposed plant controls Sequence 1 Object nr. 1 Sequence 2 2 State monitoring 3 None 5 6 7 None 8 None Delayed Switch-on mode 00:30 Switch-on delay Switch-off mode Sequence 3 4 None 5 01:00 02:00 Delayed Delayed Delayed 02:00 01:00 00:30 Operating states On Stage X On Spec. cmd Priority Spec. cmd On Spec. cmd Not cmd Spec. cmd Spec. cmd On On Spec. cmd Spec. cmd Spec.
5 Control concept Superposed plant controls service [OoServ]. The state monitoring of the plant cannot operate correctly, since [PrVal] no longer reflects the actual state of the aggregate. To reduce the frequency with which aggregates are switched on and off, it is possible to define a minimum switch-off time [TiOffMin] in the aggregates.
Control concept 5 Superposed plant controls A process alarm occurs, when: ● One of the monitored aggregates is not switched on. ● One of the referenced aggregates cannot be switched on. The exception value [EcptVal] becomes the present plant operating mode as a reaction to a process alarm. In addition, an alarm is sent. A system alarm occurs for the following configuration efforts: ● A referenced aggregate is not available. ● A referenced aggregate is not a commandable object.
5 Control concept Superposed plant controls Plant Control Editor The block parameters are set using the Plant Control Editor.
Control concept Superposed plant controls 5 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. If no limit value is required, the maximum power must be set at an appropriately high value.
5 Control concept Superposed plant controls On/Off switching of PWR_CTL When PWR_CTL is switched on [ValPgm = On], the first step in the sequence of the current profile is executed immediately. In this case, the switch-on delay is not valid. If the trigger for default power is on [PwrTrg = On], the aggregate is switched directly to the default power level [DefPwr]. A switch-off command [ValPgm = Off], disables all the energy producers defined in the profile table with Priority 14.
Control concept Superposed plant controls 5 ● When the step-up demand signal [StepUp] persists for longer than the monitoring time deviation [TiMonDev], and there are no further sequence steps to increase the power. ● When the step-up demand signal [StepUp] persists for longer than the monitoring time deviation [TiMonDev] plus the step-up delay time of the next sequence step, AND a step-up would cause the maximum power limit [MaxPwr] to be exceeded.
5 Control concept Superposed plant controls 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.
Control concept Superposed plant controls 5 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.
5 Control concept Closed-loop control strategy 5.
Control concept Closed-loop control strategy 5 The PID_CTR block can be configured as a P, PI or PID controller. The following parameter settings are used to define the control action: ● Gain [Gain] ● Integral action time [Tn] ● Derivative action time [Tv] As an option, the gain [Gain] can be influenced with the [GainFac] input. It can be useful to correct the gain factor in this way when controlling outside air dampers, e.g.
5 Control concept Closed-loop control strategy [Actg] is a characteristic parameter of the controller and indicates the relationship between the setpoint deviation and the change in energy flow. A distinction is made between direct action and indirect [Actg]. ● Direct control [Actg]: As the controlled variable rises, the controller output increases, and as the controlled variable falls, so the controller output decreases.
Control concept Closed-loop control strategy 5 ● Each sequence may include any number of elements ● The setpoint for each element of a sequence can be defined separately, but set points must not be allowed to decrease in the direction from the heating sequence to the cooling sequence.
5 Control concept 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.
Control concept 5 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.
5 ● ● ● ● ● ● Control concept Closed-loop control strategy Low supply air setpoint for the reverse-acting part of the sequence High supply air setpoint for the direct-acting part of the sequence Supply air setpoint for energy recovery Min/Max setpoint limit control (supply air setpoint) Selection of type of operation for heat recovery Initial value for the integrator can be defined Compared with control without a cascade, e.g., cascade control improves the dynamics of the control process.
Control concept Desigo room automation 5 In a humidity control system with various physical control variables, the initial value of the integrator should be predefined. Example: If the humidity of the supply air is measured with an absolute humidity value [g/kg], while the room air humidity is measured in terms of relative humidity [%Hu], an initial value must be defined for the Icomponent, otherwise the mean value from [SpLoR] and [SpHiR] will be used as the initial value.
5 Control concept Desigo room automation All lamps operated/automated together are grouped into a lighting zone regardless of number and type of the installed lamps. A room typically has one or several lighting zones. Shading zone All shading products (blinds) operated/automated together are grouped into a shading zone regardless of number and type of the installed shading products. A room typically has one or several shading zones.
Control concept 5 Desigo room automation ● Controls a scene as per the predefined values ● Changes the predefined values Both are carried out by the room user. Thermal room load analysis Room coordination supports room temperature control via blinds control.
5 Control concept Desigo room automation HVAC plants in a room consume energy. The supply chains outside the room supply air, water, or electricity to the room. Linked existing energy sources and consumers are called supply chain. An air supply chain or a water supply chain thus is an HVAC system with a supply/consumer relationship to the HVAC plant in the room. The supply equipment typically supplies more than one room, and the HVAC plant in the room often is a consumer of multiple supply chains.
Control concept Supply Chain Functions Desigo room automation 5 Room Coordination User Request HVAC Plant Control T WndCont PscDet The HVAC control application in the room consists of two parts: ● Application function for user requirements ● Application function for HVAC plant control The HVAC plant control contains a control module (CFC) that implements the control functions associated with the HVAC device.
5 Control concept Desigo room automation Heating nor Cooling 100% 0% TREff Speed 3 Speed 2 Speed 1 TREff FanSpdMin=Off 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.
Control concept Desigo room automation 5 FanDevMod=Mod HclDevMod=Mod CclDevMod=Mod AND FanSpdMaxH H2 FanSpdMinH AND H1 C1 FanSpdMaxC C2 FanSpdMinC Room temperature control AirFlReqHeat AirFlReqCool FanSpdMin Max FanSpd HclVlvPos CclVlvPos Operating modes The HVAC plants in the room adapt to the room's comfort requirements, e.g.
5 Control concept Desigo room automation Plant operating mode Economy HCSta Heating Heat 2 Neither Cooling Heat 1 Cool 1 Cool 2 100% VlvPos VlvPos 0% HclHw01 CclChw01 AirFlReqHeat AirFlReqCool Speed 3 FanSpd FanMultiSpd01 Speed 2 Speed 1 FanSpdMin=Off TREff SpH SpC The available operating modes determine both operation and basic control strategy in the automation and control system at three different levels: ● The room operating modes determine the operation of HVAC equipment in a room
Control concept Desigo room automation 5 SpC SpH RClmOpMod Eco 00: 00 Cmf t Eco 06:00 18: 00 24:00 The HVAC control applications in the room dynamically enable and disable the setpoints to achieve the desired combination of energy-saving Economy and demand-based Comfort operating mode. Command priorities An HVAC control application simultaneously achieves several goals. Functions with different objects may conflict when they are implemented.
5 Control concept Desigo room automation Priority Purpose assigned to the level Use in HVAC library Emergency mode 1 Manual commands related personal safety None Emergency mode 2 Automatic commands related to personal safety Propagated response to Emergency mode commands Emergency mode 3 Unassigned - additional level for commands related to personal safety None Protection mode 4 Manual commands to avoid damage to equipment None Protection mode 5 Automatic commands to avoid damage to equipm
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 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 Lighting products and their control are the primary means to create optimum lighting conditions for building users: ● Optimum workspace conditions (bright or darkened rooms) ● Optimum lecturing/teaching conditions (presentation) ● Comfort in living spaces ● Mood lighting in entertainment spaces (restaurants, bars, etc.
5 Control concept Desigo room automation Lighting product positioning in a building, room purpose, and allocation of rooms to an organizational unit determine the type of information acting on lamp control. Example: ● A fire alarm acts on the entire building ● A scheduler program acts on all rooms of a renter ● Local manual operation acts on all lighting of a room, or on individual lamps Gray: Complete building Green/yellow: Rooms of a renter, e.g.
Control concept Desigo room automation 5 Grouping by local and central functions for the examples from the figure above Central function Local manual operation Fir alarm Scheduler program n/a Fire alarm reception Commanding of On/Off command in dependence of time Commanding of On-command Local function Commanding of manual brightness Switching on lighting Switch on/off lighting Adapting lighting Control concept The control concept is based on the following: ● Grouping into autonomous functions
5 Control concept Desigo room automation Central function Local function Central safety (fire alarm) Maintenance Manual operation at high priority (button) Manual operation at high priority (button, management station) Selection of priority Scheduler program at high priority Execution of resulting lighting command Scheduler program Manual operation (button, management station) Manual operation (button) Presence-induced influence Automatic control 114 | 351 CM110664en_07
Technical view Standard plant structures 6 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.
6 Technical view Standard plant structures 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.
Technical view Standard plant structures 6 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.
6 Technical view Technical text labels 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. Example: Individual room, hall Room segment: A room segment is a subdivision of a room.
Technical view Technical text labels 6 Each element of the TD is called ShortName. A ShortName is a designation for an individual plant element within the automation station. A ShortName is always linked to a description. This pair is called the Name&Description_Pair. TD rules Item Rule Address structure Comprises at least one hierarchical object and one function object Has a variable length (site + 1..
6 Technical view Technical text labels Function block pin attributes 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. Example: Process input ● Data Type: Data type of the pin. Example: Multistate For a complete list of attributes, see CFC Online Help.
Technical view Technical text labels CM110664en_07 6 121 | 351
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 Primary Server Backup Server Backup Server 10664Z19en_07 Desigo PX 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 primary server transmits the time in UTC format (Coordinated Universal Time) to the other automation stations (backup servers) and in UTC format or local time format to the third-party BACnet devices. 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.
Global objects and functions Examples of global objects 7 ● 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). ● Last engineering time, global object [GOEngTi] Time stamp of the last structure modification of the global objects by Xworks Plus (XWP).
7 Global objects and functions Examples of global objects Reasons for replication: Keeping the setting parameters consistent for all automation stations of a site when modifications occur (adding or deleting configured recipients from recipient list, changing priorities). 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.
Global objects and functions Examples of global objects 7 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. Local calendar object: Individual (unique) object that exists only on a particular automation station. Local processing: Schedule objects in an automation station may reference the replicated calendar objects in the device.
7 Global objects and functions Examples of global objects Desigo CC 10664Z07en_07 130 | 351 CM110664en_07
Events and COV reporting Sources and causes of system events 8 8 Events and COV reporting Events System events are messages which inform a client (e.g.
8 Events and COV reporting Sources and causes of COVs 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. SimpleAck SimpleAck t t t Event texts Each system event has a message text assigned to it. For the system events related to the operating hours counter, a user-specific text can be set up in Xworks Plus (XWP).
Events and COV reporting COV reporting 8 To ensure that the COV service is maintained over a long period, a maximum time period without COV reporting can be set in the BACnet Device Info Object via the BACnet property COV Resubscription Interval [CovRI]. The client must subscribe with SubscribeCOV again before [CovRI] expires.
8 Events and COV reporting COV reporting 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. A COV connection ends when the subscription period expires and is not renewed, or when the COV client can no longer be contacted, causing the COV server to stop sending notifications.
Alarm management Alarm sources 9 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.
9 Alarm management Alarm sources ● 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. Both function blocks can transmit more than one system alarm.
Alarm management 9 Alarm example State transitions between alarm states Transition Trigger Action / Event state TO_OFFNORMAL A new OFFNORMAL alarm condition has been detected. OFFNORMAL TO_NORMAL1 The current OFFNORMAL alarm condition has disappeared, and there is no other alarm condition present. NORMAL TO_FAULT A new FAULT alarm condition has been detected. FAULT TO_NORMAL2 The current FAULT alarm condition has disappeared, and there is currently no other alarm condition.
9 Alarm management Alarm example Ⓐ State machine Ⓑ CFC program Ⓒ Desigo CC plant graphic page Ⓓ Desigo CC popup Ⓔ PXM… Values (in a PXM10 alarm handling is only possible for connected PXCs or PXRs) Ⓕ PXM… Popup (in a PXM10 alarm handling is only possible for connected PXCs or PXRs) Time sequence in the example: 1. Ventilation system on (e.g., in automatic mode, Cmd.ValPgm = 1), single-speed extract air fan running, fan blades rotating 2.
Alarm management Effects of BACnet properties on alarm response 9 6. The fault has been cleared. When DPMon.Dstb = 0, then Cmd.EnSfty → 0 and hence Cmd.PrVal → Cmd.ValPgm=1, that is, the fan motor is enabled. Then, with Cmd.TraSta = 1 (transient state), the fan ramp-up time is 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.
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 Message text [MsgTxt] For Desigo PX, the variables [MsgTxt] or [EvtMsg] contain the message text of the last event notification associated with TO_OFFNORMAL, TO_FAULT and TO_NORMAL alarms. Deviation monitoring period [TiMonDvn] This refers to a delay before generating the alarm if an alarm condition is detected without a prior change in switch command (that is, without a set point change).
9 Alarm management Effects of BACnet properties on alarm response Given the feedback signal [FbVal] Fully open, the Open and Close commands follow the time sequence shown below, making use of all three deviation monitoring times [TiMonDvn]. Since the BO block can handle the feedback of two different addresses, the fire-protection damper solution can be further simplified by direct connection of the Closed switch (Addr. 1) and Open switch (Addr. 2).
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 blocks (including the BACnet Device Info Object) are only monitored in the operational status RUN. Corresponds to the standard BACnet Property Out_of_Service. 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.
Alarm management Alarm response of the function blocks 9 9.4 Alarm response of the function blocks Alarm Collection The default value of [EnEvt] for the Alarm Collection object is FALSE, that is, [EvtSta] transitions are not notified. An OFFNORMAL alarm is generated when: ● The following applies to one or more alarm collection members: [EvtSta] <> NORMAL and applies simultaneously for all these members: [StaFlg].Fault = false.
9 Alarm management Alarm response of the function blocks alarm mechanism. The alarm state machine and the alarm-related variables are essentially the same as for all the other alarm-generating block types. The difference lies in the possible causes of the alarm: The alarm conditions described below cause the generation of an OFFNORMAL alarm in the BACnet Device Object: Battery low The battery in an automation station is checked periodically.
Alarm management Alarm response of the function blocks 9 Binary Output The alarm handling process in the binary output function block is essentially different from that of the binary input and binary value blocks. ● An OFFNORMAL alarm occurs when the current values of the variables [PrVal] and [FbVal] differ from each other for a time period at least equivalent to the delay time specified in [TiMonDvn], [TiMonOff] or [TiMonOn].
9 ● ● ● ● ● ● Alarm management Alarm response of the function blocks A referenced object is not found A referenced object is not a commandable object (output object or value object) Invalid priorities are used for the referenced object (valid priorities are Priority 2, 5, 14 and 16) ProgramValue or ExceptionValue are outside the permissible range The referenced objects have a different number of operating modes The function table is empty Discipline I/Os and Group Alarm response Alarm handling is identic
Alarm management Alarm response of the function blocks 9 ● An OFFNORMAL alarm occurs when the current values of the variables [RwVal] and [FbVal] differ from each other for a time period at least equivalent to the delay time specified in [TiMonDvn]. ● An existing OFFNORMAL alarm will disappear when the current [PrVal] und [FbVal] are again identical and remain so for a period at least equivalent to the time specified in the variable [TiMonDvn].
9 Alarm management Alarm response of the function blocks ● 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. ● A FAULT alarm will disappear as soon as the [Rlb] property of the function block changes from a value not equal to NO_FAULT_DETECTED back to the value NO_FAULT_DETECTED.
Alarm management Alarm functions 9 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_Of_Alarm_Values list
9 Alarm management Alarm functions ● 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.
Alarm management Alarm management by notification class 9 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 alarm-generating object is managed within the object itself. The state machines above illustrate this for each of the alarm functions. Simple message The alarm function simple message is the same function as the simple alarm. State transitions, however, are not indicated as events, but alarms.
9 Alarm management Alarm management by notification class Each alarm-generating object is assigned one notification class [NotifCl] only, but one notification class can be used by more than one alarm-generating object. This makes it possible to create a Notification Class object for each group of alarms (e.g., HVAC alarms, fire alarms etc.). Each alarm source in a given alarm group is assigned to the [NotifCl] for that group.
Alarm management Alarm management by notification class AlarmClass AlarmFunction Priority (default values) To-Offnormal To-Fault To-Normal UrgentAlarm Extended 1, 1, 5 Uses 9 NotificationClass# (derived) 13 Critical alarms HighPrioAlarm Simple 2, 2, 6 21 HighPrioAlarm Basic 2, 2, 6 22 HighPrioAlarm Extended 2, 2, 6 23 Normal alarms NormalAlarm Simple 3, 3, 7 31 NormalAlarm Basic 3, 3, 7 32 NormalAlarm Extended 3, 3, 7 33 Non-critical alarms LowPrioAlarm Simple 4, 4, 8 4
9 Alarm management Alarm management by notification class Remote-Area_Site "Luzern" Device Name "CC 01" Remote-Area_Site "Bern" Device Name "CC 02" Device Name "CC 03" Site "Muri" BACnet PTP BACnet PTP Device Name "CC 04" Router Site "Suhr" Site "Emmen" Site "Sempach" Operator units: ● Permanently connected operator units (and hence, alarm receivers) are addressed by their Device Name.
Alarm management Alarm routing over the network 9 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.
9 Alarm management Alarm routing over the network Preconfigured alarm receivers The preconfigured alarm receivers are entered in the notification class object: ● In the [DestList] for Desigo PX ● In the [RecpList] for Desigo room automation Time response in the network The routing of all alarm and acknowledgement ,messages between the alarm server and the alarm clients takes place over the BACnet network using special BACnet services.
Alarm management Alarm queuing 9 SimpleAck SimpleAck t t t Acknowledge and reset The alarm can be acknowledged by any alarm client. The AcknowledgeAlarm data record contains information as to which alarm is being acknowledged and other details related to this alarm and the acknowledging alarm client. The alarm acknowledgement is confirmed with a SimpleAck message by the alarm server which generated the alarm.
9 Alarm management Alarm queuing ● Default = 100 (PXC) or 150 (PXR) ● Range = 10…500 depending on the available memory space Record count [RecCnt] This BACnet property represents the number of entries currently stored in the queue. The alarm queue can be deleted by writing the value 0 to this property. A write of a value not equal to 0 results in an error message. If the queue is deleted, this information is entered as a system event in the queue and transmitted to the receivers.
Alarm management Common alarms 9 9.9 Common alarms The BACnet object alarm states InAlarm, Unacked and Unreset are grouped in the following blocks: ● The CommonAlarm block for Desigo PX ● The CommonEvent block for Desigo room automation The difference between CommonAlarm and CommonEvent is, that the CommonAlarm block supports Intrinsic Reporting. The alarm detection and notification of the CommonEvent block is handled by a special Event Enrollment object called CommonEventEnrollment.
9 Alarm management Alarm suppression 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.
Alarm management Alarm suppression 9 Alarm suppression by automation station AS_STA (Device Access) is a Desigo PX function block that allows to suppress all alarms of an automation station. The function block allows for suppressing BACnet event notifications by means of an application. Thus, sending of alarms and events during, e.g., maintenance, can be suppressed, e.g., via a key switch. Alarm suppression is controlled via pin SupEvt.
9 Alarm management Alarm message texts 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.
Alarm management Alarm message texts 9 System alarms and events of the BACnet Device Info Object use text messages which cannot be configured, e.g., Battery low. Predefined, language-dependent text System alarms and events of the BACnet Device Info Object use non-configured text messages whose contents are language-dependent. These language-dependent texts are organized into text groups with a predefined server system text scope, and can be translated.
10 Calendars and schedulers Alarm message texts 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.
Calendars and schedulers Schedule 10 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.
10 Calendars and schedulers Schedule ● 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.
Calendars and schedulers Schedule 10 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.
10 Calendars and schedulers Schedule Variable DefVal Variable EnDef Property Schedule_Default Value True Value Don't care False NIL (= Release) The NIL value in the Schedule_Default property is the release value for the active priority of the object controlled by the scheduler. Do not confuse it with the NIL value in the exception schedule used to prioritize the time entries.
Calendars and schedulers Schedule 10 The information flows inside one automation station or across several automation stations. The scheduler object recognizes the flow of information and knows where to send information and what data type is required by the group members. The information transmitted covers only the present value [PrVal] or the values for the Optimum Start/Stop functions [PrVal], [NxVal] and [NxTi].
10 Calendars and schedulers Calendar Processing order At start-up, when delta loading and when adjusting the date and time, the order of processing is a key factor in ensuring that from the first processing cycle on, the correct output values of a schedule function block are determined and transmitted to the output. The temporary transmission of incorrect switch values can be avoided in this way. The order of processing of the individual function blocks is determined in the CFC Editor (manual/automatic).
Calendars and schedulers Alarm messages 10 If a date contains a wildcard in the month or year, the last day of the month is used for the day, if the value of the day is greater than the maximum number of days in the month. Week and day with wildcards The following table shows an example of entering a week and day (WeekNDay) using wildcards. During the evaluation, a wildcard is replaced by the corresponding value of the current date.
11 Trending Trend functions 11 Trending Trend data provide important information about the processes in a building automation and control system, e.g.
Trending Trend functions 11 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.
11 Trending Editing parameters Triggered Sampling 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.
Trending Processing trend data in Desigo CC 11 – 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.
12 Reports 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.
Data storage Data categories 13 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.
13 Data storage Libraries ● 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.
Data storage Project data 13 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. Project data is created during project engineering, when you create a project program using library components.
13 Data storage Plant data 13.5 Plant data Plant data is process data from the operation of a customer plant, that is permanently saved from the time of commissioning. Process data represents process variables in a building. The data is continuously changed by the environment, automation station and, in the event of physical outputs, the operator. Most process data is volatile.
Data storage Data transfer processes 13 ● 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. The delta download helps prevent unintentional parameter changes. Online changed process data and settings parameters are protected against unintentional overwriting, provided the process data was not changed in the tool.
13 Data storage Texts 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. Project-specific texts that are not from the text database cannot be automatically translated.
Network architecture BACnet architecture (MLN & ALN) 14 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 IP segment 3 IP segment 2 IP segment 1 BACnet Network #1 BACnet Network #2 BACnet Network #3 PXG3.
14 Network architecture BACnet architecture (MLN & ALN) Key B Bridge, e.g., IP router, LonWorks router R Repeater, e.g., LonWorks physical repeater RT Router, e.g., PXG3 ½ Half router, e.g., PX..-T RT 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.
Network architecture BACnet architecture (MLN & ALN) 14 networks are automatically created, which must be connected to the PXG3 BACnet router. Multiple BACnet internetworks can be created on an IP segment by using different UDP port numbers. Desigo establishes PTP connections only between operator units and a network. Operator units duplicate a virtual network since PTP connections demand a network at both ends. Desigo CC does not use PTP.
14 Network architecture BACnet architecture (MLN & ALN) ISO/OSI Layers 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 Ethernet ISO8802-3 (IEEE802.3) PTP LonTalk (EIA 709.1) EIA-485 EIA-232 TP/FT 10 (EIA-709.1) ZigBee ISO8802-2 Type 1 (IEEE802.2) Physical Layer MS/TP Ethernet ISO8802-3 (IEEE802.3) ARCNET IEEE 802.15.
Network architecture BACnet architecture (MLN & ALN) 14 The device name is the object name of the BACnet device object. 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.
14 Network architecture BACnet architecture (MLN & ALN) 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.
Network architecture BACnet architecture (MLN & ALN) 14 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 BACnet/LonTalk networks via (half)router: 1...
14 Network architecture BACnet architecture (MLN & ALN) 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.
Network architecture BACnet architecture (MLN & ALN) 14 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). IP address: Host address of the network subscriber. Subnet mask: Subnet mask of the IP segment in which the device is located. This value must be aligned with the other IP devices.
14 Network architecture BACnet architecture (MLN & ALN) Designation Description IP address IP address of the BBMD. UDP port UDP port number of the BBMD. Broadcast mask If the BBMD is to be addressed via direct broadcast (one-hop distribution) the subnet mask of the BBMD must be specified. Since not all IP routers support this mechanism, direct broadcasts are not supported by default. Two-hop-distribution is always possible. The broadcast mask is then 255.255.255.255. Not required for IPv6.
Network architecture BACnet architecture (MLN & ALN) 14 performing connection is always selected. Redundancy is not allowed, that is, several simultaneously active connections in a given BACnet network are not allowed. With Desigo CC, a separate, independent, internal BACnet internetwork is created for each Data Link Layer type. Routing between LonTalk, IP or PTP is therefore not possible.
14 Network architecture BACnet architecture (MLN & ALN) ● 0-127 reserved for master devices ● 0-254 reserved for slave devices ● 255 reserved for broadcasts The MAC address can be set via DIP switch (hardware) or related configuration tools (software) for each device. Structuring MS/TP is transmitted via two-core cables as per EIA-485/RS-485. The maximum length of a segment is 1200 meters. 64 devices are allowed on a segment.
Network architecture LonWorks architecture (ALN) Designation 14 Description MS/TP: 1 octet, MAC address (master 0-127, slave 0254, broadcast 255) BACnet device address Each BACnet device has a device address. This address is written to the device during the network commissioning process. The BACnet device address is unique within the BACnet internetwork. The term BACnet device address is an in-house term rather than an official BACnet term.
14 Network architecture KNX architecture (ALN) 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.
Network architecture KNX architecture (ALN) 14 KNX can use twisted pair cables, radio frequency (RF) or data transmission networks in connection with the Internet Protocol for communication between the devices. KNX has links and interfaces for connection to Ethernet/IP, RF, lighting control with DALI and building automation and control systems. Structure The following figure shows the structure of the KNX network: ● KNX: KNX devices, e.g., third-party KNX ● PX KNX: Automation station PXC001.
Network architecture 14 KNX PL-Link architecture (FLN) The system controller must be positioned correctly in relation to the topology and the load on the bus caused by the devices and connections (group addresses). Bus power supply Each line and each area must include a bus power supply. 14.
Network architecture DALI architecture (FLN) 14 14.5 DALI architecture (FLN) DALI (Digital Addressable Lighting Interface) is a dedicated protocol for lighting control. See www.daliag.org. DALI is tailor made for modern lighting solutions. A DALI system can be as small as a single luminaire, or can encompass multiple systems across one or more buildings. DALI systems can be connected using lighting hubs/routers. DALI features: ● Max. 64 devices per subnet (hub/routers) ● Max. 300m cabling ● Max.
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 ● The DSL line in parallel can be used for telephone calls. ● If you want to use telephony on the same line, you need a splitter in addition to the DSL modem. 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.
15 Remote access Technical details The different access technologies are available with different bandwidth, e.g., DSL (o/+) can be fast or relatively slow. 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 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. You can get the best signal strength when the nearest base station of the mobile network you want to use is not too far away and there are no large obstacles between the base station and the modem's antenna (line of sight).
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 Desigo CC is a flexible, full client-server architecture allowing scalability from small and medium to large and complex systems. The platform provides customizable and market-specific distributions. Desigo CC can be installed on one single computer, with full server and client functionality. Furthermore, Installed, Web, and Windows App Clients can also be added on separate hardware.
16 Management platform User functions documentation in the Internet Explorer browser. It also represents the endpoint of the communication with the system server. Front End Processor A Front End Processor (FEP) is a computer that provides additional connections between building level devices (such as field panels) and Desigo CC. By providing additional connections to the building level network, an FEP enables load balancing for the network-based processing for a Desigo CC system.
Management platform User functions 16 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 Main components The Log Viewer application provides an historic log of all user and system events and activities that have occurred. You can retrieve these historic events and activities for further analysis and investigation using sorting and filtering. Log views can be saved and exported if required. Detailed log The detailed log allows users to view the most recent records for any selected object.
Management platform Main components 16 System Browser The System Browser displays objects in the building control system through various views. You can search and filter objects, display object names and descriptions, and drag objects into Trends, Schedules, and Reports. History Database (HDB) Historical data is stored in an access-controlled MS SQL Server database.
16 Management platform Access and security 30 days is exceeded, then the server shuts down. Unless new licenses are made available, after a manual restart the system again goes into courtesy-mode exceeding and shut down. Any unauthorized attempt to modify system license data directly in the database (e.g., changing the remaining time of a specific license mode) shuts down the system. 16.
Management platform Installation, setup and engineering 16 Event Bar When using profiles for critical event management, you can collapse the Event List into a condensed list of event buttons in an area called the Event Bar, that remains docked on the desktop for easy access. This lets you keep an eye on the current situation at all times.
16 Management platform Installation, setup and engineering for Desigo CC. The operating state of Desigo CC, the number of seats, the point count, and all functions are controlled through the LMU. Each Desigo CC management platform must be licensed locally. Licenses can be activated, repaired, returned and renewed through the LMU.
Management platform Graphics libraries 16 OLE for Process Control (OPC) is a widely accepted industrial communication standard that enables the exchange of data between multi-vendor devices and control applications without any proprietary restrictions. OPC is a client-server technology and Desigo CC can acts as the server providing data to third party clients.
16 Management platform Graphics engineering An object type is associated with a symbol in the Models & Functions application. When you drag-and-drop the symbol onto a graphic, the symbol displays the system object values in runtime mode and in the Graphics Viewer. Animation is supported through a series of graphics. Pre-defined symbols are stored in library folders. These symbols are visible and editable from the Graphics Library Browser. Advanced users can create their own symbols.
Management platform Graphics engineering 16 The Graphics Editor lets you create dynamic graphical representations of your plants, buildings or equipment. You can test and simulate your dynamic graphics before going online with them. See Desigo CC Graphics Editor (A6V10415487). Graphics Library Browser The Graphics Library Browser lets you toggle between a view that displays all the available symbols and graphic template objects in your project libraries.
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 PXG3.W100-1 and PXG3.W200-1 BACnet/IP web interfaces The BACnet/IP web interface permits local and remote operation of Desigo primary and room automation stations as well as third-party BACnet/IP devices. The products PXG3.W100-1 and PXG3.W200-1 vary in functionality as well as permissible system limits. Use: ● Remote access to the plant. ● Local operation using third-party devices. 17.1 Functions User management ● ● ● ● User logon function to protect access.
Desigo Control Point Functions 17 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. Reports ● Filter data points by alarm state, operating state, or object type. ● Manually export reports via CSV file. ● Transmission of reports via email or saving to an FTP server.
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 Commissioning and service ● Integrated commissioning on all PXM touch panels and PXG3 web interfaces. ● No tool for commissioning required. Commissioning via standard HTML5.0 compatible web browser or directly on the touch panel. ● Online device discovery and data refresh. ● Generic operation of all objects and object properties of assigned devices. ● Workflows are the same as the introduced room automation stations (e.g., firmware update or upload of configuration data).
17 Desigo Control Point Functions 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) 226 | 351 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 The serial number in the row Serial number SN=150120C61487 consists of: ● 15 = Year ● 01 = Month ● 20 = Day ● 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 When a critical hardware or software error occurs, the automation station tries to restart. If the same error is detected three times within 15 minutes, the automation station switches to the COMA operating state. If the Fault LED is lit, the automation station is in the COMA operating state. Online properties for diagnostics The values in the Online Properties window in Xworks Plus (XWP) give clues about the operation of the automation station. 18.
Automation stations 18 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.
Automation stations Operating states 18 ● BACnet communication with Desigo CC and PXM20: ReadProperty, WriteProperty, Who-Has, COVs, EventNotification, AcknowledgeAlarm GetEventInformation.
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. The STOP state is reached when the I/O scan is finished. 7 Restart Restart of the automation station due to software error.
Automation stations Data storage 18 16 Power restoration - COMA Power restored. Operating state before power failure was COMA. Actions (cold start response): ● Stop I/O scan ● Stop BACnet communication ● Stop XWP communication D-MAP processing is stopped. Summary Every time the automation station restarts (Powerfail, Reset) a cold start is carried out. The operating state is stored as a non-volatile variable.
18 Automation stations Data storage PXM20 XWP D-MAP Application Communication Flash RAM Downloading the D-MAP program 1. The D-MAP program (code and data blocks) is copied to the flash memory (1a). A copy of the data blocks is created in the RAM (1b) for later modification by the D MAP program. Read/Write via communication system 2. When writing data, the data is written to the RAM (2a) and the flash memory (2b). Read access to the data is via the RAM (2c). Processing the D-MAP program 3.
Logical I/O blocks General functions 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 Priority mechanism Basic function In order to evaluate the various defined setpoints received from the BACnet command system and via the data flow connections, the AO, BO, MO, AVAL, BVAL and MVAL blocks each incorporate a priority array [PrioArr]. All external sources write their defined setpoint and information bit (enable signal) into this [PrioArr]. The block then evaluates these entries continuously, in order to determine the valid present value [PrVal].
Logical I/O blocks General functions Priorities 1, 4, 7, 15 Priority 6 Priorities 2, 5, 8, 14, 16 Local control Control within block Higher control via data flow interconnection 19 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 3. The switch-on or switch-off delay timer starts. 4. After expiry of [TiOnMin] or [TiOffMin], priority 6 is set to inactive. If the delay times [DlyOn] or [DlyOff] are equal to 0, no action is taken. If the new value which determines [PrVal] is the same as the current [PrVal], then, here too, no action is taken.
Logical I/O blocks General functions Prio Meaning Use Access via 5 immediately to the [PrVal] output. It is not subject to the delay times defined for priority 6. Higher-level monitoring of critical plant states: BACnet command system. 6 Access via the CMD_CTL block. - Frost in ventilation system (close dampers, stop fans, switch pump on and open valve) Minimum switch-on/off time No access! Prevent unnecessary switching operations. Commands are only generated internally in the block.
19 Logical I/O blocks General functions 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. 2 At the same time, the switch-on delay [DlyOn] starts.
Logical I/O blocks General functions 19 Prio Use 4 Prio 7…16 n/a Prio 6 The minimum switch-on time [TiOnMin] has expired. Priority 6 is released. [PrVal] When priority 6 ceases to take effect, the [PrVal] output is once again determined by the effective switch command from priority (7…16). [PrVal] remains at Stage 2. 5 Prio 7…16 None of the information bits for priorities (7…16) is active. The resulting switch command is therefore determined by the default value [DefVal].
19 Logical I/O blocks General functions Prio Use [PrVal] When priority 6 ceases to take effect, the [PrVal] output is once again determined by the effective switch command from priority (7…16). The [PrVal] output remains at Stage 2. 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.
Logical I/O blocks General functions Prio 19 Use Prio 6 Priority 6 adopts the new present value [PrVal=Stage 1] and is set to active. At the same time, the minimum switch-on time [TiOnMin] starts without waiting for the delay time [DlyOn]. Note: Entries for priorities (1…5) initialize only the minimum switch-on or switch-off times [TiOnMin] and [TiOffMin] respectively, but not the switch-on and switch-off delays.
19 Logical I/O blocks General functions Prio Use 11 Prio 1…5 n/a Prio 6 The minimum switch-off time [TiOffMin] 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 output value [PrVal] remains at Off. Switch types [SwiKind] Blocks: BO, MO, BVAL, MVAL All switching I/O blocks have a configurable switching response.
Logical I/O blocks General functions 19 Trigger In the Trigger setting, the source of the last command takes precedence. The valid value is written from the [PrioArr] to the [DefVal] and transmitted to the output. The priority is then released again. In this setting, Priorities 7…16 are treated equally; Priorities 1…5 have a blocking effect. 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.
19 Logical I/O blocks General functions The ramp-up/down times (run-up/-down times) can be defined in a table for each stage. These times apply to the two switch types [SwiKind] Normal and Motor. The ramp-up time is the time taken by a motor when changing from a lower speed to the next higher speed, to reach the new speed. This limits the current consumption of the motor. The ramp-down time is the time taken by the motor when switching down from a higher speed, to reach the lower speed.
Logical I/O blocks General functions 19 Limit monitoring Blocks: AI, AO, AVAL In the case of the analog I/O blocks, the present value [PrVal] can be monitored for a high/low limit. If the alarm monitoring feature is enabled, a deviation alarm is generated after a configurable time period, and the block status changes to In Alarm. When the present value is within the limits again and the configured time period has expired, the alarm and status are reset.
19 Logical I/O blocks General functions 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]. The default value [DefVal] is automatically set to the same value as [PrVal]. (You can also overwrite [DefVal], in which case [PrVal] is automatically used instead).
Logical I/O blocks General functions 19 BACnet clients BACnet Service: WriteProperty [PrVal], Value, [Prio] WriteProperty [PrVal], NULL, [Prio] ReadProperty [PrioArr] Desigo PX [PrioArr] [OoServ] [DefVal] [EnOp] [ValOp] Online test mode in PX Design [PRVal] [StaFlg] [Rlb] [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.
19 Logical I/O blocks General functions 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).
Logical I/O blocks General functions 19 A maintenance message (event) can be generated either after a specified period of operation or on a specified date. The operating hours limit value and the maintenance date [OphLm]/[MntnDate] can be configured for this purpose. An event message is generated when the limit value is exceeded or at 13:00 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.
19 Logical I/O blocks Input blocks 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., manual switch on I/O module).
Logical I/O blocks Input blocks 19 [Icpt] = (Intercept SignalTransducer / Slope SignalTransducer ) + Intercept SignalType [Slpe] is calculated on the basis of: [Slp] = (InterpolationPoint_y2 – InterpolationPoint_y1) / (InterpolationPoint_x2 – InterpolationPoint_x1) Binary Input (BI) The binary input block is the logical image, or memory map, of a binary switch value and describes its properties.
19 Logical I/O blocks Input blocks 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. Applications include: Establishing 24-hour/7-day/monthly meters, transmission by the minute of meter values to peak load programs, etc. Precision and round off error based on real arithmetic is possible.
Logical I/O blocks Output blocks 19 19.3 Output blocks An output block is the logical image or memory map of a command, and describes its properties. Within the program, the Present Value is made available to the block as a program value. The block converts the program value and transmits the raw data to the physical I/O. If an output is deleted from an existing system in the course of a modification, the I/O module will retain the last valid value which it received from the system.
19 Logical I/O blocks Output blocks OPEN end switch -> Feedback polarity [FbPol] set to NORMAL CLOSED end switch -> Feedback polarity [FbPol] set to INVERTED Feedback monitoring for dampers with two end switches The monitoring of dampers with two feedback signals (Open/Closed) is implemented via the address string of the Feedback Address [FbAddr]. The first address in the string must be that of the end switch which indicates that the damper is closed.
Logical I/O blocks Output blocks 19 Analog Output (AO) The analog output is the logical image, or memory map, of an analog control command and describes its properties. Within the program, the Present Value is made available to the block as a program value. The block converts the program value and transfers the raw data to the physical I/O, where it is converted into a 0…10 V signal, e.g., to drive a field device.
19 Logical I/O blocks Value objects 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.
Logical I/O blocks Value objects 19 DmpShofEh Ag:DmpShof FanSu Ag: V(A,C-F) Fan1St On EnCrit DmpShofOa Ag.
19 Logical I/O blocks Value objects ● 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).
Logical I/O blocks Value objects for operation 19 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.
19 Logical I/O blocks Addressing the I/O blocks In Desigo, they are as follows: ● Physical I/Os ● Values in a Desigo room unit, accessible via the PPS2 interface ● Data in the same or in another automation station, referenced by its Technical Designation and accessed without a connection, peer-to-peer via BACnet services. Address prefix The addressing syntax indicates the origin of the raw value. The syntax must correlate with the actual physical inputs.
Logical I/O blocks Addressing the I/O blocks Module type Signal type Example Y250T T=3.1 (Y250T) 19 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.1(Q_LED) Binary Output Q250_P, Q250A_P T=12.1 (Q250_P) Q250 T=1.1 (250) QD, Q250B, (only PT-I/O) T=14.1 (Q250) + T =15.1(D20) DO, DOS, DOL, DOSL T=15.2 (DOS) D20 T=1.1 (D20) + T=1.
Logical I/O blocks 19 Addressing the I/O blocks PX compact UIO Universal I/O with Q250 4 PXC12.D PXC12-E.D PXC22.D PXC22-E.D PXC36.D PXC36-E.D Module Channel Module 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.D housing with address ranges DO1 U1 U2 U3 U4 U9 U10 U11 U12 U17 U18 U19 U20 HMI / TOOL U5 U6 U7 U8 U13 U14 U15 U16 U21 U22 U23 U24 See Automation stations, compact model PXC..D (CM1N9215).
Logical I/O blocks Block 19 10664-24z03en Addressing the I/O blocks I/O module Analog input Solution 2 The multiple use function can be implemented with a BACnet reference to the first analog input block (Partial plant 1). In other words, the first block will receive the island bus address at the [IOAddr] pin. The second analog input block (Partial plant 2) references the first AI (B=…) via the technical designation.
19 Logical I/O blocks Addressing the I/O blocks The multistate value from the program is converted in the Multistate Output block into a switching command. Addressing is via [IOAddr]. For PX modular, the syntax is as follows: Syntax: T=Module.channel Examples: ● Q-M1: T=1.1 ● Q-M2: T=1.1 ● Q-M3: T=1.1 ● Q-M4: T=1.1 ● Q250-P3: T=10.1 ● DOS: T=24.7 Values with up to four stages can be processed. The signals to be registered, which are addressed via Module.
Logical I/O blocks Addressing the I/O blocks 19 [PrVal] Addr1 Addr2 Addr3 Addr4 Comment / Text group 2 0 0 0 0 On 1 1 0 0 0 Off 5 0 1 0 0 Comfort 7 0 0 1 0 Eco 9 0 0 0 1 StandBy UpDown Mapping (Multistate Input and Output) Syntax: Application: Connecting/disconnecting further stages. Example: Electric heating registers, multi-stage burners. T=Module I/O point C=Module.channel;Module.channel;Module.channel;Module.channel (signal type, UPDOWN) Example: T=2.
19 Logical I/O blocks Addressing the I/O blocks BACnet addressing Peer-to-peer communication Data can be exchanged via peer-to-peer communication. The exchange takes place using the BACnet services defined in the BACnet standard. The process employs mechanisms engineered in CFC which can be tracked in online test mode, but which are based on BACnet objects and BACnet services.
Logical I/O blocks Addressing the I/O blocks 19 PPS2 addressing A PPS2 address is required when values are to be transmitted via the PPS2 interface. Addressing takes place via the input/output address [IOAddr] and always starts with the prefix "Q=". Address syntax Up to five room units can be connected to one Desigo PX automation station and addressed via the PPS2 interface. The addressing syntax is as follows: Q=RoomUnitNumber.Object(Profile) Example: Q=1.
19 Logical I/O blocks Discipline I/Os In principle, the profile can be attached to any other object. This configuration applies only to the QAX33.1 and QAX34.1 room units. Configuration of the object ConfigLCD is only relevant in the case of the QAX34.1, as this is the only unit with a display in °C or °F. The configuration of the object EnableOperatingMode is only relevant in the case of the QAX33.1 or QAX34.1, as only these two room units have the option of selecting Fan1, Fan2 or Fan3.
Logical I/O blocks Reliability table 19 The input value can be connected via the data flow. In the engineering tool, this is preceded by a function block or compound, e.g., a Scheduler. However, if the input value is not connected, it can also be modified via BACnet client. The subsystem registers a change in the input value by comparing the value with the process image and transferring it to the field devices.
19 Logical I/O blocks Slope [Slpe] and Intercept [Icpt] Value (decimal) Text 74 Destination device unknown. 75 Feedback device unknown. 76 Destination object unknown. 77 Feedback object unknown. 78 Unsuitable destination type. 79 Unsuitable feedback type. 80 Unreliable destination object. 81 Unreliable feedback object. 82 Invalid subsystem (syntax error). 83 Invalid feedback subsystem (syntax error). 84 Memory full. 85 Unreliable target device.
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 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.005 0 I25/020 TX-I/O* DC 0 ... 20mA*) 0 ... 20 mA* 1/1000 mA 0 ... 20000 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 19 PPS2 interface 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 Pt100_4 is a four-wire type integration TX-I/O modules with BIM integration 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-wire
Logical I/O blocks 19 Slope [Slpe] and Intercept [Icpt] Solution examples: BSG61 0 ... 5 V U10 U10 10563A22 U10 Zener diode Voltage divider Active setpoint adjuster BSG61 (Datasheet CE1N1992) Slope must be adapted to 0...5 V (0.01 -> 0.005) Precision resistance, e.g., VISHAI MBB/SMA 0207 Switch position 1 (Setpoint limit control) Setpoint 100% [Icpt] and [Slpe] for BT devices Note for all U10 inputs The physical inputs are designed for 0 -10V with narrow high and low tolerance limits.
19 Logical I/O blocks Addressing entries for PXC…-U, PTM and P-Bus 19.10 Addressing entries for PXC…-U, PTM and P-Bus 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 Y420 - P=34.1 (Y420) AO, AOS, AOSL, AOL Binary Input D20, D20S 19 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.1 (QD) D42, D250 (only PT-I/O) PX KNX: D=1001 Binary Output QD, Q250B, (only PT-I/O) Multistate Input P=14.
19 Logical I/O blocks Addressing entries for PXC…-U, PTM and P-Bus 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.5 seconds and then 1 = 1 second, 2 = 2 seconds etc. up to 600 (=600 seconds).
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 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 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. The addresses must be on the same module for TX-I/O. Simple mapping Syntax: P=Module.Channel;Module.Channel;Module.Channel;Module.Channel (Signal type) Examples: ● P=1.
Logical I/O blocks Addressing entries for PXC…-U, PTM and P-Bus 19 c represents [PrVal] for HW-I/O (0,1,0,0) d represents [PrVal] for HW-I/O (0,0,1,0) e represents [PrVal] for HW-I/O (0,0,0,1) Example: P=1.1;1.2;1.3;1.
20 Room automation Desigo room automation 20 Room automation Desigo room automation Desigo room automation offers solutions with greater functionality and flexibility allowing for energyoptimized 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. In addition, the DXR2 can be extended with lighting and shading functions by adding devices with KNX PL- Link.
Room automation Desigo room automation 20 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. The stations communicate with each other and other system components, depending on the type, via BACnet/IP (DXR1.E../DXR2.E..) or BACnet MS/TP (DXR1.M../DXR2.M..).
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 °C AQR25.. AQR25.. Room sensor Room sensor QMX3... 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 ● ● ● ● Room dehumidification control Air volume flow control Rapid ventilation Green leaf Variable air volume ● Supply and extract air control ● 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 co
20 Room automation Desigo room automation Application ● Green leaf Four light groups ● ● ● ● ● ● ● ● ● 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 Two blinds ● ● ● ● Manual control Automatic control with anti glare function and energy efficiency function Green Leaf - RoomOptiControl Collision det
Room automation Desigo room automation 20 Application – – – – – – the central plant.
20 Room automation Desigo room automation Compact room automation stations DXR1 and DXR2 automation stations DXR2 compact room automation stations Communication BACnet/IP DXR2.E DXR2.E DXR2.E DXR2.E DXR2.E 10PL- 10PLX1009T09102B 102B 101A 101A 101A BACnet MS/TP1 DXR2. M09101A DXR2. M09T101A DXR2. M10101A DXR2.E DXR2.E DXR2.E DXR2.E 1812PX- 1812P102A 102A/B 101A 102A DXR2. DXR2. DXR2. M10PL M10PL M11-102B X-102B 101A DXR2. M12P102A DXR2. DXR2. M12PX M18101A 102A/B DXR2.
Room automation Desigo room automation Flat • • • • • • 20 •2 •2 • • • • • • • Operating voltage 230V 24V Inputs and outputs onboard Digital inputs 1 1 1 1 1 1 1 1 2 2 Universal inputs 2 2 2 2 2 2 2 2 4 4 Relay outputs 3 1 3 4 4 4 4 6 6 6 8 8 1 1 2 2 2 4 4 1 1 1 1 Triac outputs Analog outputs (DC 0...
20 Room automation Desigo room automation Room operating • • Heated / Chilled ceiling radiator VAV system • • • • • • • • • •2 •2 •2 •2 •2 • • • • • 1 1 Central functions1 Housing DIN Flat Operating voltage 230V 24V Inputs and outputs onboard Digital inputs Universal inputs 2 2 2 2 Triac outputs 4 4 4 4 Analog outputs (DC 0...
Room automation Desigo room automation 20 See Compact actuating room automation stations, BACnet/IP, AC 24 V (Actuating DXR) DXR1.E09PDZ112, DXR1.E09PDZ-113 (A6V11393931) See Compact actuating room automation stations, BACnet/IP, AC 24 V (Actuating DXR) DXR1.E10PL-112, DXR1.E10PL-113 (A6V11393933) See Compact actuating room automation stations, BACnet MA/TP, AC 24 V (Actuating DXR) DXR1.M09PDZ-112, DXR1.
20 Room automation Desigo room automation Components for room pressurization and fume hood control Component DXR2.E17C.. Room automation station, BACnet/IP, 24VAC, 17 I/Os, 30 data points DXR2.E17CX.. Room automation station, BACnet/IP, 24VAC, 17 I/Os, 60 data points QMX3.P87-1WSC Operating display panel, wall mounted (KNX) QMX3.
Room automation 20 Desigo room automation See Range Description Desigo Room Automation (BACnet), Programmable Room Automation - Emergency Lighting (A6V10640596), Programmable Room Automation - Room Operation (A6V10640597), Programmable Room Automation - Distributed Functions and Scenes (A6V10640598) and Programmable Room Automation - Lighting Controls and DALI (A6V10640599). Topology Desigo CC Desigo Control Point BACnet/IP Ethernet PXG3.L Router BACnet MS/TP Modules PXC3.E16A Lighting DXR2.E..
20 Room automation Desigo room automation PXC3.E72 PXC3.E72A PXC3.E75 PXC3.E75A PXC3.
Room automation Desigo room automation 20 ● TXM1.6R: Relay module for up to 6 data points. ● TXM1.8U: Universal module for up to 8 data points. See TX-I/O Assortment overview (CM2N8170). Compact room automation stations Communication BACnet/IP DXR2.E09 -101A DXR2.E09 T-101A DXR2.E10 -101A DXR2.E12 P DXR2.E18 -1..A BACnet MS/TP DXR2.M09 DXR2.M09 DXR2.M10 DXR2.M11 DXR2.M12 DXR2.M18 -101A T-101A -101A -101A P -1..
20 Room automation Desigo room automation Example: Centralized lighting installation without HVAC installation ● One PXC3.E16A is centrally installed per DALI line ● Optional PXC3.E7..A – To integrate buttons via KNX PL-Link – To use TXM1 modules – Three-phase power installation possible 20.1.
Room automation Desigo room automation 20 A room segment is the smallest indivisible element. A room comprises at least one or several adjacent room segments. A room segment is defined and created only once. Room segments are typically combined several times to rooms over the course of a building's lifecycle. 20.1.
20 Room automation Desigo RXB Various sources are available for forming these central superposed functions: ● External system or third-party device ● System user via BACnet client ● Building user via BACnet client or local operator unit ● Scheduler or reaction program ● Superposed office based on grouping function They are distributing after evaluating signals and commands via a Grouping function.
Room automation Desigo RXB 20 Desigo CC PXM20 BACnet/IP PXC50/100/200...D TX-I/O PX KNX System controller TX-I/O RXB RXB Synco 700 Group address / Binding A group address / binding is a connection of network variables of the same type between different nodes. The group addresses / bindings are generated using ETS (EIB tool software) when designing the KNX/EIB network. The bound network variables communicate when changing the value and using a heartbeat.
20 Room automation Desigo RXB to suit their field of application. The HVAC functions are operated with standard room units or controllers in a room-style housing. Desigo RXB software Each controller is loaded with a selection of application software which contains the control program for the associated room or area within a room. The ETS commissioning and service tool is used for the engineering and commissioning of a network incorporating the Desigo RXB range.
Room automation Desigo RXB 20 ● Mapping RXB data to BACnet objects ● Implementing higher-level functions (grouping, time schedules, etc.) On the BACnet side of the PX KNX system controller, the RXB controllers can be operated and monitored from a client. Data can also be exchanged with the primary plant. 20.2.4 RXB applications The existing Desigo RXB applications cannot be modified for a specific project by the user.
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.
Desigo Open Integration on management level Desigo Open system Desigo Open application Data points Desigo management platform Desigo CC 1,000 - 10,000 21 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.
21 Desigo Open Integration on automation level An OPC server option provides a freely configurable set of data points for integration in any enterprise system, using the OPC DA standard. Each data point (object) is represented by several OPC items, providing the relevant readable and writable object property information. See OPC DA Server Manual (A6V10415485). The Desigo CC OPC server is officially tested and certified by the OPC foundation (https://opcfoundation.org/products/view/251).
Desigo Open Integration on automation level 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 21 The platform for integrating LonWorks compatible third-party devices consists of: ● System controller PXC00.D and automation station PXC50.D, PXC100.D or PXC200.
21 Desigo Open Integration on field level The PXC001.D system controller can integrate SCL via BACnet/LonTalk. The PXC001-E.D system controller can integrate SCL via BACnet/IP. The PXA40-RS1 and PXA40-RS2 option modules support additional data points. The regional companies develop the necessary protocols themselves. The hotel management system Fidelio can be integrated into Desigo via PX SCL. See PX SCL (CA2N9773).
Desigo Open Integration on room level 21 TX M-Bus TX M-Bus supports templates for meters. The regional companies can create templates. You need a level converter for TX M-Bus. TXI2.OPEN supports 160 data points. They may be distributed in any fashion to the devices for the M-bus system. The number of devices is only limited by the 160 data points. See TX M-Bus Engineering Guide (CM110572). TX G120P TX G120P supports the integration via the Modbus and USS protocol.
22 System configuration Integration on room level 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..
System configuration Integration on room level 22 BACnet internetwork A BACnet internetwork consists of one or several BACnet networks. Individual BACnet networks are connected to BACnet routers. 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).
22 System configuration Technical limits and limit values 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. A PX site cannot be extended beyond the limits of a BACnet internetwork. This is particularly important in the case of BACnet PTP internetworks.
System configuration 22 Maximum number of elements in a network area This limit type… …is shown like this Example Technical limit verified Limit* 60* Technical limit NOT verified [Limit*] [50*] Recommended limit verified Limit 64 Recomended limit NOT verified [Limit] [1'000] Limit subject to proviso (refer to footnotes) (Limit) (10)9 22.
22 System configuration 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 n/a n/a n/a n/a [6,000] Data points and BACnet objects Physical data points [100,000] [100,000] [3,000] [20,000] Total BACnet objects [500,000] [100,000] [30,000] [100,000] [3,000] [30,000] n/a n/a [50,000]
System configuration Desigo room automation system function group limits 22 22.3 Desigo room automation system function group limits A Desigo room automation system function group comprises parts of the Desigo room automation stations on the BACnet internetwork. Grouping occurs based on Desigo room automation stations assignment to PX system function responsible for the Desigo room automation subsystem functions.
22 System configuration Devices 22.4 Devices 22.4.1 PXC..D automation stations / system controllers 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 PXC50-E.D PXC100-E.D PXC200-E.D PXC00-E.D PXC22.D PXC22.1E.D PXC22-E.D PXC36.1.D PXC001-E.D PXC001-E.D + PXA40RS.. PXC-NRUF PXC36.1E.
System configuration Devices PX Compact Item PX Modular PXC00.D PX Open10 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 22 PXC-NRUF PXC36.1.D PXC36.1E.
22 System configuration Devices 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.
System configuration Devices 22 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.
22 System configuration Devices 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. number of data points per PX Modbus. SCL data points [250*] Max. number of data points per PX SCL.
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 22 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.
22 System configuration Devices ASN Product description Data points Description 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.P70 Freely configurable operator unit, wall mounted 3 Fixed count QMX3.
System configuration Devices 22 – 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 TX-I/O data points. A PXC3.E.75 supports max.
System configuration 22 Devices ASN Max. number of data points Description DXR1.E02PLZ112 2 n/a DXR1.M04PDZ112 n/a 2 UI DXR1.M09PDZ112 16 2 UI, 4 DO, 1 AO DXR1.
System configuration 22 Devices 22.4.13 PXM20 operator unit Item Limit Description PX (no PXC3) 50 Number of PX that can be operated. The visibility of the PX automation stations can be limited on the BACnet network. This is only useful if the site is restricted to one BACnet network. For hardware series A devices (1 MB memory), the number of PX automation stations per site should be limited to 30.
System configuration 22 Devices 22.4.15.2 Memory management PXM30.E PXM40.E PXG3.W100-1 PXG3.W200-1 PXM50.E 3 GB 3 GB 3 GB 3 GB Max. number of DPs that can be integrated for graphical operation 1,500 kB (500 DP) 2,500 kB (1,000 DP) 2,500 kB (1,000 DP) 5,000 kB (2,000 DP) Max.
System configuration Devices 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. number of assigned devices BACnet/IP BACnet MS/TP *) BACnet LonWorks *) n.a. Number of simultaneously connected operator clients 1 50 10 10 50 10 10 n.a. 5 5 Max number of devices connected to one BACnet device n.a. 5 5 Data points per plant graphic n.a. 40 40 Data points (in a table) n.a.
22 System configuration Devices The times are slower for a restart. The following limits and constraints must be considered if the MS/TP devices do not support COV, i.e. only polling: ● Disable the list view core function (user profile setting in ABT Site) ● Limit to one concurrent operating client (limit your network topology) ● Set baud rate to 38400 or higher ● Only use the online trends functionality very limited ● Limit the points per graphic to 15 22.4.15.6 LonWorks limits Use the router PXG3.
System configuration Devices 22.4.17 22 SX OPC Item Limit Description SX OPC applications 1 SX OPC application per PC. The performance depends on the PC hardware. OPC server [10] Max. number; OPC data access 2.x or 3.0 specification. BACnet objects 20,000* Maximum number of BACnet objects. Configured alarm recipients 3* Temporary alarm receiver 20* Minus configured alarm recipients. [2,000] Alarm-generating objects (of total 20,000 BACnet objects).
22 System configuration Devices 3. Go to Tools > Settings > Compilation download and select the Compress check box. 4. Recompile the data. 5. Perform a full download. 22.4.21 Desigo Automation Building Tool (ABT) Item Limit Description Function blocks [8,000] Max. number of function blocks per application function.
System configuration Applications 22 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).
23 Compatibility Desigo version compatibility definition 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.
Compatibility Desigo system compatibility basics ● ● ● ● ● 23 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.
23 Compatibility Desigo system compatibility basics The BACnet client ensures the backwards compatibility. Desigo CC should thus have a BACnet revision that is at least the same as all of its connected BACnet servers. Usually, BACnet devices of a specific BACnet protocol revision fully support earlier revision functions. However, since this is not true in all cases, we recommend that you verify the compatibility in each case.
Compatibility Desigo system compatibility basics Product 23 Compatibility with Microsoft server operating systems Branch Office Server (BOS) Windows Server 2012 R2 Standard Windows Server 2016 Standard Windows Server 2019 Standard 64-bit 64-bit 64-bit Yes Yes Yes Unlisted Microsoft server operating systems/editions are not supported. They can, however, be used for stand-alone SQL servers and file hosts.
Compatibility 23 1 Desigo system compatibility basics Support of of HTML5-capable browsers with native SVG format. Desigo CC For notes on Desigo CC web client running in a browser shell, see Desigo CC System Description (A6V10415500). 23.2.6 Compatibility with ABT Go ABT Go is a mobile tool for commissioning and maintenance tasks of Siemens devices used in building automation and control systems. Operating system Version Android Version 4.
Compatibility Desigo system compatibility basics 23 TX-I/O A firmware update or upgrade from TX-I/O modules is not possible (except for TXI1.OPEN, TXI2.OPEN, and TXI2-S.OPEN). To load firmware, protocol applications, and the configuration to the TX Open modules, use the TX Open Tool, which is available as a part of XWP. See Desigo Xworks Plus Online Help (CM111006). 23.2.10 Backward compatibility Desigo software and libraries are downwards compatible.
Compatibility 23 Desigo Control Point RXT10.x project data All Desigo software and LibSets must be on the same PC and have the same system version. 23.2.15 Compatibility with TX-I/O TX-I/O modules Product range TXM1. TXM1. TXM1. TXM1. TXM1. TXM1. TXM1. TXM1. TXM1. TXM1. TXM1. TXM1. 8D 16D 8U 8U8X 8X6R 6R-M 8P 6RL 8RB 8T ML ML Modular room automation stations PXC3 (from index D) • • • - - - • - - • • • Modular room automation stations PXC..
Compatibility Desigo Control Point 23 PXM20-E ● ● ● ● PXM20-E PXM30.E The dimensions for the cut out are the same as for mounting in the panel. Supply voltage AC/DC 24 V. Ethernet connection for communication. No Power over Ethernet (PoE) connection on PXM30.E. PX web PXA40-W0 PXA40-W1 PXG3.W100-1 PXA40-W2 PXG3.W200-1 ● PX web graphics are not compatible with graphics for the new web interface PXG3.Wx00-1. ● No workflow is currently available to automate migration of PX web graphics.
Compatibility 23 Upgrading from Desigo V6.2 Update (or Update 2) to V6.2 Update 3 23.3.3 Supported browsers The following browsers support graphics and operation: 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.
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 Siemens WEoF clients For details, contact your local Tool Manager. ● You have the project data and the credentials for the project you want to work on. ● The project data conversion from V6.2 Update (or Update 2) to V6.2 Update 3 happens automatically. – When you open an XWP project, the XWP project is converted automatically. – When you open an automation station in XWP, the CFC data is converted automatically. – When you navigate to ABT Site, the conversion is done automatically.
Compatibility Migration compatibility Minimum user level required Desigo product Standard User Desigo Configuration Module (DCM) Permanent Open User Desigo Xworks Plus (XWP) including PX firmware library (FW), Automation Building Tool (ABT) and additional tools Permanent Open User Branch Office Server (BOS) Permanent Open User RXT10 (including RX library) Permanent Open User Headquarter (HQ) and Regional Company (RC) libraries 23 Third-party engineering software For information about ETS, see:
Compatibility 23 Hardware requirements of Desigo software products 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.
Compatibility Hardware requirements of Desigo software products 23 ● 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.0 or higher (optional installation with tool installation) ● WinZIP ● .NET Framework >= V3.5 (version 3.
24 Desigo PXC4 and PXC5 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 348 | 351 CM11
Compatibility of Desigo V6.2 Update 3 with PXC4 and PXC5 25 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.
25 Compatibility of Desigo V6.2 Update 3 with PXC4 and PXC5 Building A 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.
Issued by Siemens Switzerland Ltd Smart Infrastructure Global Headquarters Theilerstrasse 1a CH-6300 Zug +41 58 724 2424 www.siemens.com/buildingtechnologies © Siemens Switzerland Ltd, 2015 Technical specifications and availability subject to change without notice.
