Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A Tag represents a register to poll from the End Device. The tag contains different options shown below.

Configuration

...

Property

Description

Name

This is the name the Tag will be given when it is published via MQTT

Register

This is the register Edge ACM will poll from the End Device

Back Fill

Enable Backfill

If

enabled

checked, all value changes, obeying deadband, for this tag are stored and published based on the type of backfill selected.

NOTE: Currently

Only

only works with Sparkplug B Publishing

Backfill Type

This allows you to specify when Backfill should be recorded for this tag.

  • Always : Backfill will be recorded whenever a value changes, obeying deadband.

  • When Triggered : Backfill will be recorded when the tag is in a triggered state (i.e. when a trigger condition is met). An additional way this option will cause back fill recording is when the AUTOSOL MQTT Publish Schedule object has the option ‘Backfill on Every Tag when Triggered’ enabled. With this option enabled, if any tag in the publish group is in a triggered state, any tag with the When Triggered option selected and Back Fill Enabled will have Back Fill recorded.

NOTE: This field is only editable when “Enable Back Fill” is checked.

Deadband Type

This allows you to enable a Deadband for the Tag. There are 4 options available:

  • None : will make the current value of the tag publish on any change from previous value.

  • Every Scan : will make the current value of the tag publish on any poll, even where the value has not changed.

  • Absolute : will make the tag update only if the current value is greater or less than the previous value plus/minus the Deadband.

  • Percentage : will make the tag update only if the current value is greater or less than the previous value plus/minus the Deadband divided by 100.

Deadband

This sets how much the current value must differ from the previous value to be published again

Trigger Conditions

If any exist, the triggers are evaluated on value change and if met, the quality of the tag is updated and Deadband is ignored

Trigger Conditions: Condition

This sets how the current value will be compared to the preset value. There are 5 options available:

  • Equals :will return true if the current value is equal to the preset value in the trigger.

  • Greater Than :will return true if the current value is greater than the preset value in the trigger.

  • Less Than :will return true if the current value is less than the preset value in the trigger.

  • Greater Than or Equal to :will return true if the current value is greater than or equal to the preset value in the trigger.

  • Less Than or Equal to : will return true if the current value is less than or equal to the preset value in the trigger.

  • Percent Change : will return true if the previous value polled and the current value polled have a difference greater than the specified percentage in the trigger.

Trigger Conditions: Value

This sets the value to which the current value will be compared.

NOTE: For Percent Change, A value of 5 means a percent change of 5% or greater will return true.

Trigger Conditions: Quality

This sets the quality the tag will take if a trigger is met. There are 3 options available:

  • Triggered : will set the quality to 196.

  • High : will set the quality to

193
  • 194.

  • Low :will set the quality to

194
  • 193.

Trigger Conditions: Duration

The Duration extends the time that the quality set by the trigger will be assigned to the tag once the condition is no longer met. By default, the duration is 0 seconds, so the quality set by the trigger will last for just that poll cycle. A duration of >0 seconds, for example 10 seconds, means that the quality will extend for a total of 10 seconds after no longer meeting the triggered condition. If the triggered condition is met again within that duration, the duration is reset.  

NOTE: This duration will expire if a higher priority trigger condition is met.

Trigger Conditions: Priority

The Priority is determined by the row order and drives the order that trigger conditions are followed. For example, if a tag has three trigger conditions, the first trigger listed has the highest priority, the second trigger has a lower priority than the first but a higher priority than the third, and the third trigger has the lowest priority. If multiple conditions are met at the same time, the condition with the highest priority will be followed.

NOTE: When a condition with a duration > 0 is triggered, it will only be interrupted by a condition with a higher priority, or if it’s own conditions are met for a second time.

Tag Group

The parent tag group for this tag.