Iconics Suite - Hyper Historian - single logging data to HH using bit register data trigger [BridgeWorX]

Iconics Suite - Hyper Historian - single logging data to HH using bit register data trigger [BridgeWorX]

This article show how to do single logging data with couple of tags with the same timestamp to Hyper Historian using bit register as data trigger with BridgeWorX transaction

Sample description

In this sample we have 2 machines with 3 tags each one.


Every machine have it's own trigger (bit register in their PLC) which activate the logging transaction of it's own three tags.

Trigger configuration


Configure Data Triggers for every machine. IMPORTANT - keep _1 numeration the same as for the machine e.g. machineName_1 -> triggerName_1





Hyper Historian tag configuration

Tags should be switched off from periodic (Is Collected -> off) logging cause we would like to use trigger logging.


BridgeWorX local variable configuration

Create local variable with additional column MachineNumber (string).

BridgeWorX template configuration

Create new template which will be used for logging to Hyper Historian.
Template should have 3 actions : Real Time Output, Real Time Input, Historical Upload


Real Time Output configuration

In this activity we will read the machine number retrive from the trigger name and put it in BridgeWorX local variable.



Point Name -> bwx:local@MachineNumber.Row[0].Col[1]
Row[0] cause we have only one pair of values in row 0.
Col[1] cause we would like to put data in MachineName column with index 1.

Expression -> substring({{triggerVariable:SourceName}}, indexof({{triggerVariable:SourceName}}, "_")+1, len({{triggerVariable:SourceName}})-indexof({{triggerVariable:SourceName}}, "_"))
In this expression we are looking for machine number which should be located right after "_" (low dash) character. Then we put this machine number into the local variable

Real Time Input

In this activity block is preparing the DataSet of points which values we would like to log in Hyper Historian. We are using the local variable to create dynamic address of tag.

Historical Upload

Please notice that we have to change HDA Tag Point Name to PointName instead of default TagName.


BridgeWorX transaction configuration

Create transaction. It can have the same name as template. Enable transaction and select template to run with this transaction.


Configure triggers to run this transaction.


Our sample have 2 machines that's why we have 2 triggers respectively for every machine.
If we have more machines just create more triggers with keeping name syntax.

    • Related Articles

    • Iconics Suite - Logging every minute with shift in seconds [Hyper Historian]

      This article will show you how to log hyper historian tag every minute with shift in seconds Open asset property options. Configure general tag logging options. Switch to Logging Options. Change Aggregate Type to Most Recent On Time. Set Recur every ...

    • Iconics Suite - Logging once a day every day at selected time [Hyper Historian]

      This articsle will show you how to configure Hyper Historian to log selected tag once a day every day at selected time Open Workbench Create asset property and configure general logging properties of Hyper Historian tag. Remember that the shorter ...

    • Iconics Suite - Universal sample Display to present Hyper Historian data

      This article contains sample GraphWorX Display which can be used with any Iconics project that use Hyper Historian. This sample let you display Hyper Historian data for any actual Hyper Historian tag in your project. Sample display view Sample ...

    • Iconics Suite - Data storage in Hyper Historian Logger

      Summary: this document describes difference in setting in Hyper Historian Logger. Storage Limit Condition, Actions are described. Hyper Historian Logger - Delete Old Files First test was done using the 'Delete Old Files' option. Condition is Minimum ...

    • Iconics Suite - FDA 21 CFR 11

      This article contains information about Iconics funcionalities in compliance with 21 CFR 11. 21 CFR 11 Using Iconics GENESIS64 solutions allows system integrators to create SCADA applications in compliance with FDA 21 CFR Part 11, which is an ...