Skip to content

(Event Binding) Event trigger

Stephan Stricker edited this page Dec 19, 2018 · 9 revisions

Event triggers

Events can be trigger by different sources. The following sources are possible.


OPC UA variable

OPC variables are typically PLC variables. In most cases this variable is coming from the PLC but it can also be a remote OPC variable. Use ::Program:Variable1 for local variable and ::AsGlobalPV:Variable1. OPC variables can be a source or a target.

  <Source xsi:type="opcUa.Event" refId="::Program:boolVariable" event="ValueChanged" />

The trigger creates the two internal variable newValue and oldValue. The values can be used later for conditions.


Session variable

Session variables exist for each client connection as individual set of data. Session variables can be a source or a target.

Variable

  <Source xsi:type="session.Event" refId="variable1" event="ValueChanged"/>

Timer

  <Source xsi:type="session.Timer.Event" refId="AutoLogOutTimer" event="Elapsed"/>

The trigger creates the two internal variable newValue and oldValue. The values can be used later for conditions.


Client System

Client variables are similar to session variables. The session variables represent the panel side of a session where the client variables represent the client side. Client variables can be browser information or IP address of the connected client. In this case the client is the source of the data. It can also be the target for example to show a dialog box.

The following client system events are possible

  • KeyBoard Events
<Source xsi:type="clientSystem.Event" event="KeyPress" />
<Source xsi:type="clientSystem.Event" event="KeyUp" />
<Source xsi:type="clientSystem.Event" event="KeyDown" />

The trigger creates the two variable keyASCII and key. The value can be used later for conditions.

<EventHandler condition="keyASCII = 97" >
<EventHandler condition="key = &quot;ArrowLeft&quot;" >
  • Gesture Events
<Source xsi:type="clientSystem.Event" event="SystemSwipe" />

The trigger creates one variable direction. The value can be used later for conditions.

<EventHandler condition="direction=&quot;fromTop&quot;">
  • ContentLoaded Event
<Source xsi:type="clientSystem.Event" event="ContentLoaded" />

The trigger creates the two variables contentId and visuId. These values can be used later for conditions.

<EventHandler condition="contentId=&quot;Content1&quot;">
  • DisabledClick Event
<Source xsi:type="clientSystem.Event" event="DisabledClick" />

The trigger creates the three variables contentId, widgetId and hasPermission. These values can be used later for conditions.

<EventHandler condition="contentId=&quot;Content1&quot;">
  • DialogOpened Event
<Source xsi:type="clientSystem.Event" event="DialogOpened" />

The trigger creates one variable dialogId. This value can be used later for conditions.

<EventHandler condition="dialogId=&quot;Dialog1&quot;">
  • DialogClosed Event
<Source xsi:type="clientSystem.Event" event="DialogClosed" />

The trigger creates one variable dialogId. This value can be used later for conditions.

<EventHandler condition="dialogId=&quot;Dialog1&quot;">

Widget

These are events triggered by widgets. See the Automation Studio help for details what events can be triggered by each widget.

<Source xsi:type="widgets.brease.Button.Event" contentRefId="Content1" widgetRefId="Button1" event="Click"/>
Clone this wiki locally