Special Features for Desigo PX

Integration in FEP not Supported

Do not integrate Desigo PX via a FEP installation (FEP means remote integration on another computer).

Online import is not supported with FEP installation. Therefore, integration must always be performed via the management platform BACnet network.

Scheduling

Object References

The BACnet object references of the ASCHED, BSCHED, and MSCHED function blocks cannot be changed from the management platform, since they are read only. The system does not support writing object references of the corresponding function block using List_Of_Name_Reference.

Interconnected SCHED blocks

The ASCHED, BSCHED, MSCHED, and AnySCHED blocks, embedded in the application program, are automatically displayed in links, if the following conditions are met:

• The SCHED blocks used come from existing application solutions.
• The applications must include a correct function name such as Ahu01, Vnt01, CGrp01, Exg01, CGen01, DhwSol10, DhwDir, DhwEl, DhwHyd, Dsh10, HGrp01, HGen01, HCGrp01, Ahu35, DhwSol.
• The technical address hierarchy level does not exceed 3.

The SCHED blocks, created to supplement application-specific blocks, can be manually linked.

The link is displayed in the Related Items expander under Scheduler.

Regional Modification to Object Links

The function automatically creates related items in the Related Items tab. The function is always used if additional related items are to be created automatically. This is typically the case if a headquarters solution for a Desigo PX application, for example: Ahu01 on a regional or RC standard, is changed to: Ahu01_RC. To this end, the DynamicLinks.txt configuration file must be extended to include the corresponding function name. The modification can be made in the library on level L2-Region, L3-RCs or L4-Project.

Application Variants for Multiple Configuration Files

All created configuration files are evaluated to automatically generate related items. A configuration file generated in the project can be used on any variant but is only depicted here in variant 4.

Description and Syntax of DynamicLinks.txt File

The tables below describe the keywords used and behavior of operators.

The result of the execution list always occurs over all defined levels, but must have the same keyword, for example: PX Schedules.

Example 1: DynamicLinks.txt file by Headquarters

The DynamicLink.txt file supplied by Headquarters is saved in folder [Installation drive:]\[Installation folder]\[Project]\libraries\BA_Device_PX_HQ_2\DynamicLinkProviders.

Link         = PX Schedules

MaxLevel      = 3

Source.Model = GMS_Aggregator, GMS_desigo_px_EOT_BA_PX_Block_10

Source.Function = Ahu01, Vnt01, CGrp01, Exg01, CGen01, DhwSol10, DhwDir, DhwEl, DhwHyd, Dsh10, HGrp01, HGen01, HCGrp01, Ahu35, DhwSol

Target.Model = GMS_desigo_px_EOT_BA_PX_BSCHED_10, GMS_desigo_px_EOT_BA_PX_ASCHED_10, GMS_desigo_px_EOT_BA_PX_MSCHED_10, GMS_desigo_px_EOT_BA_PX_SCHED_10

Example 2: Extension by L2-Region

The L2 region DynamicLink.txt file is saved in folder [Installation drive:]\[Installation folder]\[Project]\libraries\BA_Device_PX_ZN_2\DynamicLinkProviders.

Link         = PX Schedules

Source.Function += HGrp10_ZN

Explanation:

1. The search criterion is extended to the level L2-Region with the additional entry of PX Schedules. The complete basic definition occurs at the HQ level and need not be fully redefined here.
2. The definition is checked at the HQ level if data point HGrp10_ZN is selected in the System Browser.
3. If created correctly, it searches for all Target.Models, available below HGrp10_ZN. Any search that matches is displayed in the Related Items tab.

Example 3: Extension by L3-Countries

The L3 regional company DynamicLink.txt file is saved in folder [Installation drive:]\[Installation folder]\[Project]\libraries\BA_Device_PX_RC_2\DynamicLinkProviders.

Link         = PX Schedules

Source.Function += Ahu01_RC

Link         = PX Common Alarms (Zone)

MaxLevel      = 3

Source.Model = GMS_Aggregator, GMS_desigo_px_EOT_BA_PX_Block_10

Source.Function = Ahu01_RC

Target.Model = GMS_desigo_px_EOT_BA_PX_CMN_ALM_10

Explanation:

1. The definition is checked at the HQ level if data point Ahu01_RC is selected in the System Browser. If created correctly, it searches for all Target.Models, available below Ahu01_RC. Any search that matches is displayed in the Related Items tab.
2. The search criterion is extended to the level L3-RCs with the additional entry of PX Schedules. Overall response is the same as explained in example 2.
3. The search criterion is extended to the level L3-RCs with the additional entry of PX Common Alarms (zone). All keywords must be defined on the level since this search criterion is unavailable on prior levels.

General Information on Implementation

Please comply with the following items:

• The implementation is a generic feature and can also be used for other related links (see Example 2). It requires installation of the Desigo System extension.
• Is searches for only entries in the libraries with system names PX, TRA and Desigo.
• Objects are only searched in the Logical View.
• The folder DynamicLinkProvider must be created with Desigo CC.
• The processing sequence for DynamicLinks.txt files is Headquarters > Region > RCs > Project.
• Only complete and correct entries are evaluated.
• You must restart the client after making changes to the DynamicLinks.txt file as the levels are only checked once (at start up) and compiled in a single rules set.

Creating Configuration File

Backing up the Configuration File

NOTE:
The created DynamicLinks.txt file need to be recreated at a later date if not backed up.
As manager of the region or RC, you must ensure that the new or edited library type must be available on the installation DVD for the current and future versions.

Time Property Displayed Incorrectly

The Desigo PX Property time is always displayed as 1/1/2014 1:00:00 AM and cannot be changed from the management platform. This applies to the following Desigo PX functions:

• KickFnct
• PrdvHCtl
• OssCSolPos
• I/O blocks (operating hours maintenance)

Workaround: Change the format of this TIME property via the BACnet Browser or ABT Site.

Desigo PX BTL libraries

The Desigo PX standard library enables all BACnet properties required for operation and monitoring. There are individual cases where it may be necessary to display all the properties for a BACnet object in Desigo CC. An extended Desigo PX library can be imported for just such cases. This includes:

• BTL compliance testing
• A cuustomer requires a display of all mandatory and optional BACnet properties on the management platform.
  NOTE: The extended Desigo PX library cannot be used if a project has more than 17,500 physical data points. Use the BACnet Object Browser instead.

Library BA_Device_PX_HQ_2.gms replaces BA_Device_PX_HQ_2_BTL.gms by default as part of the upgrade. Proceed as follows:

Use the following workflow to change the Desigo PX library:

1. Check the number of data points.
2. Import the extended library.
3. Import localized texts for extended library.
4. Enable the standard library for operating phases in the building.
5. (Optional) Import the standard library if the extended library is no longer used.
6. (Optional) Import localized texts for the standard library.

NOTE:
Desigo PX projects are updated with the standard library when upgrading to a higher version unless the config file is modified. On quality updates as part of the same version, it depends on whether the PX library is part of the update (or not). If yes, the project is updated with the standard library. Additional information is available at Procedures for PX Libraries

Assign Access Rights to Object Model

A set pattern is used to assign Desigo object properties to a Desigo CC object model. Decisive are the read and write rights as defined in the SDU (System Definition Utility is the tool for creating Meta data). This information is taken over when manually creating the library on the object model (see Assignment Concept).

We distinguish between two different groups of SDU data for assignment to the object model:

• Objects with only read rights
• Objects with read and write rights

NOTES:
‒ Read and write rights are not considered when importing a data point instance. The assignment is made per the data point type information for the corresponding object model.

‒ If project-specific modifications are required, it must be done by changing the library type.

Object Property with Read Rights Only

In the SDU, the object property is defined with read rights from 1 to 7 only. The write rights are defined as 0 (No access). In the object model for Desigo CC, assignment occurs in this case in the Property Group, with the option Status. Display levels are assigned as per the table below.

Object Property with Read/Write Rights

For object properties with read and write access, assignment for the Property Groupdisplay level and Command Groupcommanding are made per the definitions in the following tables.

Property Group

The read right is evaluated and assigned for the display level accordingly.

Write access 1 to 7 is always assigned to the BACnet Editor.

Command Groups

A Command Group control the buttons on the corresponding operating dialog boxes. The option Standard or Advanced is assigned depending on the defined write access.

NOTES:
− There is another group for alarms on the Command Group. The group controls the buttons for acknowledging and resetting alarms.

- The assignments listed in the tables are standard assignments. There are, however, exceptions to the rules. Exceptions can only be viewed on the object model and not listed here.

Assignment Concept

The following diagram demonstrates a possible configuration, starting with SDU data up to actual operation in Desigo CC.

Display convention in the diagram:

• Each user group is defined its own scope, instead of predefined Scope rights.
• For each object property, the state is individually identified on Property Groups (read and write access) and Command Groups (active or inactive). Settings for Scope Rights are only defined once in the system.

Reading Out Project Information

The installed project base can be read out with iBase. The iBase and Scripting extension modules must be installed. Refer to the iBase description for additional information.

Online Device Functions

The management platform provides several online functions to help you in maintenance and optimization. The following table lists these functions:

NOTE 1:
These tools require extensive knowledge of your plant, as well as knowledge of Desigo and BACnet.
NOTE 2:
When using online tools, remember that different responses may occur depending on the BACnet system supplier.