Introduction

System Topology

The system offers a wide range of topologies, so that it can be adapted to an unlimited number of individual requirements. For this reason, this document only provides a description of a general system topology. The topology is valid for Desigo version 6.3.

Terms Used

Compatibility list

Exception list of functions in Desigo devices

The list describes the functions from Desigo devices that are partially handled in a different manner from the point of view of Desigo CC.

Multiple Languages for Data Import

Automated support for multiple languages is based on the project settings on the System Management Console. The associated languages are imported during import if a project is set up as multilingual. The requirement is that engineering was conducted using SDU standard texts (The System Definition Utility is the tool for creating meta data).

The following example illustrates a standard solution in various languages in the System Browser.

NOTES:
− During data import, the period is converted to an underscore; a period is not permitted in the description text.
− Project-specific data point texts, for example: Northeast wing cannot be automatically translated. These texts must be translated after the fact using the object configurator.
− Always create a project with an additional language. This permits you to use it as a multilingual project at a later date.

Supported BACnet Object Types

Object Types

Exported BACnet object types associated with a Desigo automation station:

• Automation Station (Devices): Controls system components and equipment controllers. An automation station samples and processes field data, initiates control actions, communicates with its operators, and generates reports, displays, and warnings.
• Commands (CMD): An object that writes to a group of object properties through action code(s) inside the Present_Value property. The Command object starts a sequence of actions in the BACnet devices during this write action.
• Event Enrollment (EE): The management of events for a BACnet system. Events are changes in the value of any property concerning any object that meets specific criteria. Compiles individual event enrollment alarms as a system alarm.
• I/O Objects:
• Inputs: The input block acquires a value from an external data source and converts it to a process value
• Outputs: The output block calculates the present switching value from several, prioritized setpoints (priority array) and transmits the switching value to an external data.
• Loop (LOOP): The Loop block is a universal PID controller (P, PI, PD, or PID), with external tracking. It supplies a modulating manipulated variable.
• Schedules: Acts as a bridge between scheduled times and dates, and the writing of certain values to specific properties and objects concerning the schedule.
• Trend Logs (TLOG): Monitor a property for a specific object. When certain conditions are reached, a log is produced with the property value and a date/time stamp which is placed into a buffer for future retrieval.
• Object structure view: Is needed to display underlying objects in a defined hierarchy.

Dynamic objects

Dynamic objects are not supported on PXC3, PXC4, PXC5, and DXR automation stations.

Hierarchies/Views

BACnet objects are depicted hierarchically per the various views:

• Logical View: Displays BACnet data points, aggregators and subpoints that are in the database. The visual layout of these objects is based on the point naming convention (technical designation) of the object.
• User View: Displays the objects as per the user designation of the company. Only objects with a user designation (UD) are displayed. This view is optional and can be populated at import time.
• Application View: Displays various applications, for example, central functions, scheduler, reports, documents, trends, etc.
• Management View: Displays the system view for networks, management functions (servers, drivers), system settings (libraries, security, users) and all data points on one device.
• User View: Displays the customized views of objects or functions using views. Multiple views can be created.

Import Data

The Desigo Automation program data can be imported by an offline or online data import to the project.

NOTE:
The management platform periodically checks the consistency of the system information against information from room automation station. In the event of an inconsistency, you must conduct an offline data import.

Offline data import

You use a file from ABT Site for the import function. This is the typical procedure for new contracts where all preparatory work – creating graphics, setting up networks, etc. – is done prior to going to the actual site (offline commissioning).

Online Data Import

An Online data import is supported by most Desigo automation stations. The appropriate field network must be selected. In the Network devices tab, all the discovered Desigo automation stations can be imported online.

Auto Discovery

The Desigo automation station does not support the Auto-Discovery function.

BACnet Backup and Restore

BACnet Backup and Restore uploads saved program data (application program) for a BACnet device to the management platform and then restores it as needed to the same or a new BACnet device.

Alarm Response for Different Versions

Version 5.1

One common alarm per room is evaluated to keep the number of system alarms to a minimum. Room coordination records the state information (Normal/Alarm) of each zone and all electrical and mechanical installations and determines from them the room-wide alarm state as a common alarm. The alarm is evaluated on the Desigo PX automation station. The actual automation station has no alarmable objects.

Version 6

Event Enrollment (EE) as a component of the Desigo automation station as of Version 6. The application is designed for the following objects to send an alarm to the management platform in the event of a fault:

• Automation Station
• I/O bus
• KNX PL-Link bus
• Room
• Segment

Alarm monitoring occurs in various ways depending on the hardware in use. Alarming and alarm acknowledgement are, however, the same for the user.

Template Project Information

User Groups in the Template Project

The following user groups are predefined in the system and cannot be changed:

• DefaultAdmins
• DefaultUsers
• FallbackPolicy
• OPCGroup

The template project contains the following preconfigured user groups and rights. They can be changed, deleted, or extended by new user groups:

• Administrators
• Engineering
• Maintenance Grp
• Operators Grp 1
• Operators Grp 2
• Operators Grp 3

Scope Rights

Scope rights define what a user can display or command in his or her project. The template project sets discipline, subdiscipline, object type, and object subtype to All. The write rights (W) and read rights (R) are configured differently and described in the following tables.

Application Rights

Application rights specify which application a user can display and configure.

User Profile in the Template Project

The following users are predefined in the system and cannot be changed:

User Profile Response between Server and Client

The user profile specifies the number of alarm buttons in the Event bar. The corresponding discipline profiles as well as the default profile can be selected from the template project. The user profile can be defined in the server or at the corresponding user, whereby the server has higher priority (see table below).

List Sequence on the Lite User Interface

The list sequence determines the sequence of the symbols on the lite user interface.