This is a helpful engineering tool that will automatically apply history grouping tags to your histories based on your points folder structures.
This is intended for use by those with some coding knowledge. Take the time to read the code to know exactly how it works. I will write a proper tutorial at some point in the future.
This is intended for use by those with some coding knowledge. Take the time to read the code to know exactly how it works. I will write a proper tutorial at some point in the future.
In a future build of the ddctCommunity-rt Module we will be integrating the history tagger as part of our plugin library.
In a future build of the The program object is within this bog. Drag it into your N4 station.
HistoryTaggerAdvancedV3.bog (23.6 KB)
Example of what I mean by history grouping:
Usage Instructions
-
Define History Group: Create a history group in your Niagara station with sufficient levels to cover the number of folder levels used for your points.
-
Configure the program object like shown in the example below (your configuration might be different):
Configuration Parameters:
- Point Type: Specify the point types for the BQL query, with each point type on a new line.
- Stop At Folder: Indicate the folder levels where the program should stop tagging. Multiple folders can be specified, each on a new line.
- History Groupings: Define the history groupings exactly as they were created in the history group setup, with each level on a new line.
- Base Ord: Set the entry point for the BQL query.
- Custom Groups: Name/value pairs for adding custom tags not defined by the history group. This is optional and typically not needed.
- Config Type: Specify the history extension type to search for.
Comments from the code:
This can be seen when viewing the code on the program object and may provide some more insight…
_ _ _ _ _____
| || (_)__| |_ ___ _ _ _ _ |_ _|_ _ __ _ __ _ ___ _ _
| __ | (_-< _/ _ \ '_| || | | |/ _` / _` / _` / -_) '_|
|_||_|_/__/\__\___/_| \_, | |_|\__,_\__, \__, \___|_|
|__/ |___/|___/
- pointType = A list of point types to query for. Each point type is separated by a new line
- stopAtFolder = A list of folder levels to stop tagging at. Each stop is separated by a new line
- baseOrd = The base for the BQL query (allows you to narrow the extent of the query)
- customGroups = A list of name:value pairs that define custom grouping to be added to each object
For Example, if the stopAtFolder is {ACSys} the program will query all points of the selected pointTypes list
that are a chilled to ACSys and then tag them from 0 to x folder levels. There is no limit to the depth
however you must make sure you have enough depth to your history grouping under the history service.
|ACSys (Level0)
|-L2 (Level1)
|--AHU (Level2)
|--AHU1 (Level3)
|--ZnTmp1 (Level4)
After configuring these parameters, right-click on the program object and select “Execute”. This will run the tagging job and tag your history extensions based on your folder structure and defined history group levels.
maybe some sort of UI to assists in selecting the histories you want to tag. Also we could have the program automatically generate the Niagara history group definition to remove a step or a drop down to select an existing history group to use.
