Any new point created in the DB Builder App can have any of these properties (type-specific excepted):
The navName will be set in the first field.
Allows you to choose the point type: sensor, setpoint, command.
The disMacro represents the display name of the point. By default, it is set to: $equipRef $navName.
The default value can be changed by clicking the text-field.
The kind property allows you to choose the kind of point to add from the drop-down menu:
This property allows you to set the point to be schedulable and at what level the schedule writes.
- To enable Schedule, click the toggle bar to make the schedule active.
- Click Save.
If you want to change the schedule level, make sure Advanced view has been activated.
- Select the text box Scheduleable to change the schedule level.
- Click Save.
- Select .
- The Property Editor dialog box displays.
- Navigate to the property tag schedulables and change the level number by selecting on the text-field.
- Click Apply.
Depending on how you are creating the point, it can be a local (does not get data from an actual device) or connected point (from an actual device).
Connected points are created by dragging and dropping the points from the connector inside the DB Builder instead of manually creating a point and the references to the connector.
The following table outlines the types of history mechanisms that you can choose from.
Allows you to create a point with history.
The history will be constantly synchronized with the device that the point originated from; no extra settings needed.
The history will be collected on the FIN Stack server, respecting the seated scheme. You can then set the collect scheme: the time interval for the collect, and the COV more than what value the collect will happen.
The history will be imported from the device and then it will switch to collect on the local FIN Stack server - no extra settings needed.
The history will be collected on the FIN Stack server based on the function selected. You can select the function based on need (hisFunc).
Attempting to do so may result in the following error message: "Errors with the following tags: his CollectCov."
Failure to remove inherited aux tags on the graphic will result in malfunction.
Failure to remove inherited aux tags from the program will result in malfunction.
In this section, you can add all the necessary marker tags to the record.
- Click , select a tag and click OK.
- Select the Haystack tags bar to see all the tags.
- The last section is represented by the Property tags, that add the type to the tag capability, meaning you can create:
- boolean tags
- string tags
- URI tags
- numeric tags
- refID tags
- date tags
- time tags
- dateTime tags
Adding a Property Tag
- Click to add a property tag.
- The following tags display:
- Type of Property
- Tag Name
- Tag Value
- Click √ to make the changes.
- To change the type of property, select the dot directly.
- A dialog box with a selection of Properties displays to assign the property tag.
The following Essentials Icons are available:
- Property Editor
- Point Debug Info
- Show Trend
The Property Editor is an advanced editor that allows you to see all the available tags on the selected record. You can also add or modify applicable tags.
For more information, see Property Editor.
Tools displays a drop-down list of all available tools at this level.
For more info, see Tools.
Point Debug Info
Point Debug Info is only available for connected points.
This allows you to troubleshoot connection issues.
Show Trend is only available if the History toggle is selected.
Show Trend displays a quick preview of the history and allows you to jump to the Historian App.
Action is only available if the Is Writable option is checked.
The set of actions depend on the type of point.
- To apply an action, select it.
- The New Point Action dialog box displays.