Data maintenance - Basic Documentation - DXR2.E09-101A - DXR2.E09-101A/BP - DXR2.E09-101A/TB - DXR2.E09-301A - DXR2.E09T-101A - DXR2.E09T-101A/BP - DXR2.E09T-301A - DXR2.E10-101A - DXR2.E10-101A/BP - DXR2.E10-301A - DXR2.E12P-102A - DXR2.E12P-102A/BP - DXR2.E12P-102B - DXR2.E12P-102K - DXR2.E12P-302A - DXR2.E12PX-102A - DXR2.E12PX-102B - DXR2.E12PX-102K - DXR2.E18-101A - DXR2.E18-101A/BP - DXR2.E18-101B - DXR2.E18-101K - DXR2.E18-102A - DXR2.E18-102A/BP - DXR2.E18-301A - DXR2.M09-101A - DXR2.M09-301A - DXR2.M09T-101A - DXR2.M09T-301A - DXR2.M10-101A - DXR2.M10-301A - DXR2.M11-101A - DXR2.M11-101B - DXR2.M11-101K - DXR2.M11-301A - DXR2.M12P-102A - DXR2.M12P-102B - DXR2.M12P-102B-GDE - DXR2.M12P-102K - DXR2.M12P-302A - DXR2.M12PX-102A - DXR2.M12PX-102B - DXR2.M12PX-102K - DXR2.M18-101A - DXR2.M18-101B - DXR2.M18-101K - DXR2.M18-102A - DXR2.M18-301A - DXR2.T12P-102B - DXR2.T18-101B - PXC

A running Desigo system contains various categories of data, each with different requirements in terms of consistency, period of useful life and visibility. The data is distributed throughout the system, with each category having a unique origin. There is no central data maintenance in the Desigo system. The system data is distributed on all devices throughout the network, but is primarily located in the automation stations.

During the sales, planning, engineering and commissioning phases, project data is created. Part of the data is loaded into the system, while another part is tool-specific and used, e.g., for documentation of the project.

System data is:

• Process-data and parameter settings
• Archived data
• Configuration and description data
• Metadata
• D-MAP program
• Graphics and masks
• Libraries
• Offline trend object values

Process-data and parameter settings

Process data

Process data is data generated by the physical process in the building using a process control algorithm. Process data represents the process variables, such as a temperature or a damper position.

Parameter settings

Parameter settings are function parameters, settings, setpoints, etc. which are defined for each plant or project and which affect the way in which an application works. Parameter settings can be modified during operation.

Process data and parameter settings can be accessed within the system via BACnet objects, e.g., Present Value [PrVal] and Status [StaFlg], if the associated mapping is enabled in the engineering phase.

If process data is used by several automation stations, the data origin is the location where the physical variable is measured (e.g., outdoor temperature) or generated (e.g., the control signal from a time schedule). Copies are updated on an event-driven basis after a short delay.

Displaying process data and parameter settings

To display process data and parameter settings mapped to BACnet on clients, only one copy of the data needed for current operation and monitoring is stored. The Desigo system does not store complete copies of process data or parameter settings. The data (copy) required by a client is normally updated via the BACnet protocol on an event-driven basis and with a short time delay.

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. However, certain process data is retained even after an automation station restart, e.g., self-adaptive control parameters, run-time totalizers, etc., which are specifically identified as such in a function block. Even in the event of a program change, this non-volatile process data remains in memory and can be read back with XWP.

All parameter settings are non-volatile, that is, they are retained in the event of a power failure.

Readback

All non-volatile PX process data and parameter settings can be read back into XWP. However, parameter settings in the operator unit cannot be read back into a tool.

Global parameter settings

Some parameter settings are identical in all automation stations, e.g., date and time, calendar function blocks and Notification Class function blocks. To ensure consistency, they are held in global objects which are automatically replicated in the system.

Archived data

Setting parameters can be logged and archived. Archived data illustrates the response of process or system variables or events over a time period, e.g., trend data can be moved from the trend database into archive files. Archived data are typically lists of one or more of the aforementioned variables and are preferably stored and processed on the management level. Only small amounts of data are archived at the automation level. Such data is normally forwarded to the management level.

Ensuring consistency

Archived data only requires a consistency check in cases where it has been moved from one application to another, e.g., from the automation level to the management level. The data origin is not deleted until a check has been carried out to ensure that the data has been transferred in full. This data is stored in the non-volatile memory.

Irregularities in the logging of archived data are recorded in the data itself.

The life of the data is determined either by the user or by a configurable application which automatically condenses or deletes this archived data.

Configuration and description data

Configuration and description data is data which is defined for a specific system or project and only affects the appearance and response of the plant for operation and monitoring purposes. Some configuration parameters are tool-specific and control the options in XWP (e.g., connection allowed / not allowed, etc.). Most configuration parameters, however, are mapped to BACnet and are available to the clients. Typical data in this category is COV increment, operating limits, access level, descriptive text, engineering unit, etc.

This data is defined during engineering and always originates in the tool itself. Normally, the data is predefined with likely default values or even generated automatically from the context. This data is static and cannot be modified during operation. It is therefore not subject to consistency problems, and may be duplicated elsewhere in the system to improve performance. If engineering changes are made, you must ensure manually (through data import) that the copies are identical to the original data in the engineering tool.

This data cannot be read back from the automation stations, and must therefore be stored with the project data.

Metadata

Metadata is project-independent data from standard BACnet objects (e.g., analog input, schedule, etc.) which needs to be known by a tool or a client, e.g., texts for predefined BACnet enumeration, maximum size of arrays, data-type information, fixed operating limits, etc. The metadata is loaded into the relevant clients or tools at HQ and (except texts) cannot be modified after delivery. Text, like the text for BACnet enumeration referred to above, must be localized (language translation) and distributed to the clients and tools. This is part of the localization process.

D-MAP program

The D-MAP program 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.

The D-MAP program is generated in XWP/ABT from the information in the program charts, compiled and downloaded into the automation station.

Libraries (LibSet)

The Desigo Library Set (LibSet) is a set of mutually interdependent libraries that belong to a given Desigo system version.

The library contents are continuously extended. Every LibSet Extension of Desigo (LED) is a comprehensively tested collection of solutions covering all the necessary parts of the Desigo system.

The LibSet version number defines which LED runs on which system version. The first part of the version number represents the applicable system version.

A LED includes the latest library per automation station type (PXC, PXC00(-E).D, PXX-L11/12, PXKNX) for the latest Valid Version Set.

New LEDs are delivered at regular intervals. The individual LEDs are consecutively numbered (LED0 to LED16).

LibSet version number

Desigo LibSet consists of various libraries for all system levels:

• Shared text library for PXC, PX KNX, PXE, PXR
• PXC library
• 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.: Desigo-LibSet-HQ-410080-10 > Desigo-LibSet-HQ-410080-20

The remaining numerical values in the decade (e.g., 11 to 19) can be used by the RCs for localization versions.

If the version number changes, the LibSet number is reset to 10 again. If the scope of the Desigo application changes, the LED number is also incremented, e.g.: LED02 > LED03

Desigo LibSet

Key

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).