Issue
Creating binding templates.
Product Line
EcoStruxure Building Operation
Environment
Binding templates for Script and Function block programs.
Binding template examples:
- Type Binding Template Examples
- Path Matching Binding Templates and Syntax
- Path Matching Binding Template Examples
Cause
1 - Output points need to be bound to the Requested Value attribute, but the default name matching template only matches the value attribute.
2 - Binding a Graphic which contains several controllers which all have the same names in the system tree structure, using a binding template.
3 - Binding Template Types examples
Resolution
1 - Output points need to be bound to the Requested Value attribute, but the default name matching template only matches the value attribute.
Under the system folder of the AS or ES there is a folder called "Binding Templates".
In here you can create custom templates by right clicking and selecting "New", "Binding Template".
To create a generic template that will bind both inputs, outputs, values and other object types follow these steps:
Press Next and the following screen appears:
Select All Types and press Next:
Click twice on the Add Rule icon (Green +) then enter the three rules as follows:
Press create and the new IO Binding template will be created.
If you have used a common naming convention in your points and within the programs, you will be able to use this template to bind all the points and values to your programs.
Drag the AS across to the IO Binding template (as below) and it will match all of the point names and use Requested value attribute for the output points.
This example shows 2 IO Binding templates, as one was created at the AS level and another at the ES level. Only 1 is actually required to provide this functionality.
You can subsequently edit the binding template and it will show as follows:
2 - Binding a Graphic which contains several controllers which all have the same names in the system tree structure, using a binding template.
It is common for a system to consist of many controllers that have been created from the same import file. This will mean that there are many instances of the same names being used, but this is not an issue until a graphic containing several controllers are to be bound.
Create a "Path Matching Binding Template" as shown above and configure as shown in the following screen shot. Notice that the Binding candidate has /Application/ between the "Unit" and "Point" to match the tree structure.
The screen shot below shows the site system tree structure, with part of the graphic binding page. Note that for the binding template to work, the bind names used in the graphic must be unique. eg. L6W1_CHB_006 (Unit) and ReturnAirTemp (Point).
For an Export of this template, click Binding Template Export 2013-08-15 083240.zip.
3 - Binding Template Types examples see the Online Help.
An additional resource is the Exchange Community in particular the following Knowledge Reinforcement Session
Also check out the SmartStruxure-Binding Templates-Lesson 1-7 Quick-Help video on the Exchange.