GenEvents - Setting up Value Masking

10th February 2016

Article Introduction

In this blog, we’re going to explore the logical tag structure of GenEvents, the way we recommend configuring value masking in the GENESIS64 lookup files, and the benefit of value masking in general…
Let’s start off with the basics, and define what we mean by Value masking within the context of GenEvents.

One of the key questions customers ask with regards to the audit tracking within GENESIS64 is how to configure the GenEvent messages to add state values to the text. For example a message might read:
“Successfully wrote value 1 to ac:Site1/Build1/Room1/AlarmSystem” Article Content.

Logical Tag Structure

Prior to setting this up it is important that the tag structure follows a logical and human readable structure, as this information will also be presented to the user. The ICONICS AssetWorX module is the logical choice for this.

Tag/Value Lookup mapping

The GenEvent server has two text files which control the Tags which would be written too, and the state values which would be displayed instead, these are as follows:
-    C:\Program Files\Common Files\ICONICS\FWX64\BIN\GenEvent64_Lookups.txt
-    C:\Program Files\Common Files\ICONICS\FWX64\BIN\GenEvent64_Tags.txt
The Tags file would be edited first, and all of the different tags which could be written too would be defined within this. The structure of the file is simple, wherein the tags are defined in groups with a lookup set identifier (in the #LookupIdentifier structure) as the title, and all of the tags underneath.
After the tags are defined then the Lookups file would be edited, and same Lookup Identifier (e.g. #LookupIdentifier) and all of the different variations of values underneath. The values will be any integer number and the state text is separated from the value by one or more spaces.  
When you have finished you should have two items similar to the following:

GenEvent64_Tags.txt

GenEvent64_Lookups.txt

#LookupIdentifier

ac:Site1/Building1/Room1/AlarmSystem

ac:Site1/Building1/Room2/AlarmSystem

ac:Site1/Building2/MainAlarmSystem

#LookupIdentifier

0  Enabled

1  Disabled

2  Maintenance Mode

3  Error

 

After defining the tags and their associated lookups, the ICONICS FrameWorX and ICONICS GenEvent services will need to be restarted. So make sure you factor this in if updating a live system.

Visualising these messages

The primary recipient for these messages will be the AlarmWorX64 Viewer subscribing to the ICONICS GenEvent OPC AE server, as well as this the following fields will need to be subscribed to:

OpcAETrackingEventTypes:ICONICS.GenEvent.1

  • [Virtual] NAME_OF_PARAMETER
  • [Virtual] NEW_VALUE
  • [Virtual] NEW_LABEL

 After the tags are written too, the following values will be exposed:

GenEvents Blog Image 1.png

Virtual Columns

The AlarmWorX64 Viewer supports virtual columns which will be covered in further detail in future blogs. Using this functionality it is possible to create a custom string with these parameters for an easy to understand message:

GenEvents Blog Image 2.png

Which is achieved with the following expression:

x="User: " + {{BaseConditionType.ActorId}} + " Set Mode: " + {{Internal.NEW_VALUE_LABEL}} + " on " + replace({{Internal.NAME_OF_PARAMETER}},"ac:","")

Article Closing

As you can see GenEvent messages are very useful ways of knowing what actions are being undertaken on the system by your users, however the values written to the OPC tags may not always be indicative of the action performed. With these steps the behaviour available in GraphWorX64 via the state field functionality can be easily replicated in the GenEvent viewer.

Further information on GenEvent messages can be found through the Customer Connection Portal https://getconnected.iconics.com.