BaTemplate

The BaSiteExtension provides the TcHmi with the structure of the PLC in a special form. BaObjects are created from this, which can then be linked to the BaObject property from the BA category of a TcHmiBa template.

The TcHmiBa templates are implemented as TcHmi-FrameworkControls and take all the values required for their function from the BaObject.

Creating such a control requires more effort, but the result is a more performant and comfortable TcHmiBa template for the user.

BaTemplateDescription

TcHmiBa templates are available for almost all TF8040 standard PLC templates. The scope of functions includes a validation of the linked BaObject using the BaTemplateDescription. It defines the symbol names including hierarchy in the delivery state, which a TcHmiBa template requires in BaObject.

In case of changed symbol names, due to project specific peculiarities, the new name can be communicated to the TcHmiBa template via the attribute BaTemplateDescription from the BA category.

Template handling

Explanation of the functionality using the example of the standard TF8040 PLC template FB_BA_AC_ColT_02 for a cooler.

The matching TcHmiBa template FB_BA_AC_ColT_02 expects the following subelements (TF8040 PLC templates) in the linked BaObject in the predefined hierarchy.

Subelements:

Symbol name

PLC template

Description

Fdb

FB_BA_AI_IO

Feedback

Mdlt

FB_BA_AO_IO

Setpoint

MV

FB_BA_AI_IO

Feedback

TFl

FB_BA_SensorAnalog_IO

Flow temperature sensor

TRt

FB_BA_SensorAnalog_IO

Return temperature sensor

Vlv

FB_BA_Vlv

Valve

Hierarchy:

- BAObject

      - TFl

            - MV

      - TRt

            - MV

      - Vlv

            - Fdb

            - Mdlt

States

The states of a TcHmiBa template depend on the BaObject.

No BaObject

The cooler without linked BaObject. All subelements are present, but without value display.

Presentation:

BaTemplate 1:

Subelement missing

The cooler has been assigned a BaObject in which the valve (Vlv) is missing.

The validation registers that a top-level subelement does not exist or has a different symbol name, and therefore hides it.

Hierarchy:

- BAObject

      - TFl

            - MV

      - TRt

            - MV

Presentation:

BaTemplate 2:

Symbol name renamed

In this BaObject the top level subelements are correctly present, but the symbol name for Fdb from the Vlv has been renamed in the PLC template.

Since the deviation occurs in one of the lower levels, the affected subelement is shown with the value display in the error state.

Hierarchy:

- BAObject

      - TFl

            - MV

      - TRt

            - MV

     - Vlv

            - Fdb_Test

            - Mdlt

Presentation:

BaTemplate 3:

In addition, an error message indicates the subelement.

BaTemplate 4:

Customize symbol names

New symbol names can be communicated via the BaTemplateDescription.

BaTemplate 5:

A dialog lists all subelements and allows navigation through the further levels [1]. The identifier refers to the symbol name of the current level [2]. If this specification is no longer possible, then the last level of the subelement is reached [3].

At Feedback the current symbol name for Fdb from the PLC template is to be entered.

BaTemplate 6:

After confirming the input, the TcHmiBa template performs the validation of the BaObject again.

Presentation:

BaTemplate 7:

The cooler is fully functional again.

Using nested BaObjects

If the BaObjects, e.g. for the command of a motor, are not on the level provided by default, but in a lower level, these nested objects can be accessed with the following syntax.

MyView::Motor::Cmd