Search

User Manual

GETTING STARTED


MODULES AND PLATFORM


APPENDIX


TUTORIALS & HELPFUL TRICKS


GLOSSARY


STRATEGIC PARTNER LINKS

Sepasoft - MES Modules
Cirrus Link - MQTT Modules

RESOURCES

Inductive University
Ignition Demo Project
Knowledge Base Articles
Forum
IA Support
SDK Documentation
SDK Examples

ALL MANUAL VERSIONS

Ignition 8
Ignition 7.9
Ignition 7.8

Deprecated Pages

Skip to end of metadata
Go to start of metadata



Scripts can be attached to Tags. When you edit a Tag, you can navigate to the Tag Events section and click on the Edit icon to see a list of all of the available events. Those events are

  • Value Changed
  • Quality Changed
  • Alarm Active
  • Alarm Cleared
  • Alarm Acknowledged

Each event is unique and can have specialized arguments depending on the event.  Also, because Tags are stored in the Gateway, all these scripts fire in the Gateway scope

Because these scripts are Gateway scoped, certain things like print statements will not print to the Designer console, but will print instead to the wrapper log file in Ignition's installation directory. Keep that in mind when doing any testing.

On this page ...

IULocgo


Tag Scripts


Event Options

Once an event has been selected, note that the top of the text area is defining a function. As a result, all code that should execute when this event occurs should be indented at least once to be included in the definition. 



Value Changed

The Value Changed event is fired whenever the value of this particular Tag changes. This event has a variety of arguments available for use in the script:

  • String tagPath - The full path to the Tag.
  • Object previousValue - The previous value. This is a qualified value, so it has value, quality, and timestamp properties.
  • Object currentValue - The current value. This is a qualified value, so it has value, quality, and timestamp properties.
  • Boolean initialChange - A boolean flag indicating whether this event is due to the initial subscription or the first execution after a Tag update.
  • Boolean missedEvents - A flag indicating that some events have been skipped due to an event overflow.

 

The currentValue and previousValue arguments are qualified values: objects that contain a value, timestamp, and quality. This means that to get to the value of the currentValue, your script would need to access currentValue.value

Quality Changed

The Quality Changed event is fired whenever the quality of this particular Tag changes. Since Tags use a 'qualified value', which include a value, quality, and timestamp, this script will fire whenever any of those change. This event has a variety of arguments available for use in the script:

  • String tagPath - The full path to the Tag.
  • Object previousValue - The previous value. This is a qualified value, so it has value, quality, and timestamp properties.
  • Object currentValue - The current value. This is a qualified value, so it has value, quality, and timestamp properties.
  • Boolean initialChange - A boolean flag indicating whether this event is due to the initial subscription or the first execution after a Tag update.
  • Boolean missedEvents - A flag indicating that some events have been skipped due to an event overflow.

Alarm Active

The Alarm Active event fires whenever a new active alarm event occurs. This event has a variety of arguments available for use in the script:

  • String tagPath - The full path to the Tag.
  • String alarmName - The name of the alarm. This does not include the full alarm path.
  • Object alarmEvent - The full alarm event object. The properties available to this object are:
    • id
    • source
    • name
    • priority
    • displayPath
    • displayPathOrSource (the display path if it is set, otherwise the source)
    • state (the current state, active/cleared + acked/unacked)
    • lastEventState (the last transition, active, clear, acknowledged)
    • cleared (a boolean if the alarm is currently cleared)
    • acked (a boolean if the alarm is currently acknowledged)
    • shelved (a boolean if the alarm is currently shelved)
    • notes 
  • String alarmPath - The full alarm path.
  • Boolean missedEvents - A flag indicating that some events have been skipped due to an event overflow.

Alarm Cleared

The Alarm Cleared event fires whenever an alarm becomes cleared on the Tag.This event has a variety of arguments available for use in the script:

  • String tagPath - The full path to the Tag.
  • String alarmName - The name of the alarm. This does not include the full alarm path.
  • Object alarmEvent - The full alarm event object. See the Alarm Active alarmEvent object for the full list of available properties.
  • String alarmPath - The full alarm path.
  • Boolean missedEvents - A flag indicating that some events have been skipped due to an event overflow.

Alarm Acknowledged

The Alarm Acknowledged event fires whenever an alarm event becomes acknowledged on the Tag.This event has a variety of arguments available for use in the script:

  • String tagPath - The full path to the Tag.
  • String alarmName - The name of the alarm. This does not include the full alarm path.
  • Object alarmEvent - The full alarm event object. See the Alarm Active alarmEvent object for the full list of available properties.
  • String alarmPath - The full alarm path.
  • String ackedBy - The full path to the user that acknowledged the alarm.
  • Boolean missedEvents - A flag indicating that some events have been skipped due to an event overflow.


Using the Project Library in a Tag Event Script

Scripts defined in a project script can be called from a Tag Event Script. However, only scripts defined in the Gateway Script Project may be used. For more information on configuring the Gateway Scripting Project, please see the Project Library page. 


UDT Parameters in Tag Event Scripts

Parameters on UDTs can be interacted with from Tag Event Scripts. There are two main approaches.

Modern Approach

This feature is new in Ignition version 8.0.7
Click here to check out the other new features
As of 8.0.7, parameters values can be accessed as dictionary values. The benefit of this approach is that value changes to UDT parameters will be reflected in subsequent calls. In most cases, this modern approach is preferable. Thus, if the script needs to access the most recent parameter values on a UDT, and the parameters can change thought a means other than editing the UDT (which would restart the tag), then this approach should be used. 

If trying to access the value of a parameter named "myParam" from a Tag Event Script within the UDT, the script would look like:

# Reminder: "tag" is a built-in argument on all Tag Event Scripts. Accessing the "parameters" key on the tag argument will 
# provide access to all UDT parameters.
paramValue = tag['parameters']['myParam']

Legacy Approach

In 7.9 and prior, UDT parameters could be access in Tag Event Scripts with the familiar curly brackets approach. Thus, if trying to access the value of a parameter named "myParam" from a Tag Event Script within the UDT, the script would look like:

paramValue = {myParam}

A large caveat with this approach is that value changes made to the parameter ("myParam", in the example above) would not be reflected in scripts until the UDT was restarted. UDT parameters are pre-compiled, which in this case means value changes are mostly ignored until the UDT is restarted. 

In all cases, the modern approach above is preferred. 


Tag Script Examples


Printing all parameters
# This script will fetch all of the possible parameters in the tag changed script. 
# Note that this will not print out to the console, but it will print to the wrapper logs located on the gateway.

path = tagPath
prev = previousValue
cur = currentValue
init = initialChange
missed = missedEvents
print path, prev.value, cur.quality, init, missed
Automatic Reset
# This code can be used on a Value Changed script, and will automatically reset the value of the tag to 0 after it goes above 3000.
# This can be useful for counter tags.
if currentValue.value > 3000:
		system.tag.write("IntegerCounterTag", 0) 
Copy to another Tag
# This code can be used on a Value Changed script, and will record the highest value of the current tag onto another memory tag.
# This can be useful for recording the highest temperature.
highestRecordedTemp = system.tag.read("HighestTempTag").value
if currentValue.value > highestRecordedTemp:
	system.tag.write("HighestTempTag", currentValue.value)
Automatically reacting to an alarm
# This code can be used on an Alarm Active script, and can be used to automatically react to an alarm to prevent a disaster from occurring, 
# if personnel were not able to react in time.
if alarmName == "Tank Pressure Critical":
	system.tag.write("PressureReleaseValveTag", 1)
if alarmName == "Tank Pressure Too Low":
	system.tag.write("TankFillTag", 1) 

 

  • No labels