Overview

There are four main types of data that the EFM Emerson ROC driver is capable of getting from an Emerson ROC device.  These are:

• TLP data
• Alarm Data
• Event Data
• History Data

TLPs are polled at a specified interval based on a poll rate and then made available via the OPC-UA interface.  Alarms, events, and history are made available to MQTT Transmission to be published as immutable record objects to an MQTT server.  Typically these would be received on a central Ignition gateway with the MQTT Engine and MQTT Recorder modules.  Combined those receive the MQTT Sparkplug messages and insert the records into a central DB and be made available to other third party systems or for later use in Ignition.

For the purposes of this document there are some definitions that are explained below.

• Global TLP Definitions
  • These are the global TLP definitions made available to the Ignition instance.  They are uploaded to the Ignition instance in the form of specificly formation CSV file.  These TLP definitions can then be referenced by a specific instance of a ROC device connection to restrict the TLP definitions to those that apply to that device.  For example, lets say you upload four Global TLP definitions.  Lets say these are ROC800.csv, FLOBOSS107.csv, UserProgram1.csv, and UserProgram2.csv.  With these global definitions there could be differing definitions for any specific T/P combination.  This is only allowed if the differing definitions are in different CSV files.  No one CSV file is allowed to have differing definitions of the same T/P combination.
• Device TLP Definitions
  • These are a subset of the global TLP definitions that apply to this specific device.  Continuing with the example from above let's say this is a ROC 800 and has User Program 1 installed.  We would select the ROC800.csv and UserProgram1.csv as the TLP definitions that apply to this specific ROC device.
• TLP Templates
  • TLP templates are groupings of TLPs that represent logical groupings of TLPs.  Generally TLP templates would be created to then can have instances of them created by specifying a poll group with a logical number or the 'L' parameter in a TLP.
• TLP Poll Groups
  • Poll groups use TLP templates in conjunction with a logical number to create a specific set of TLPs to be polled at a specified poll rate.

There are six basic steps to getting all of the data available in a ROC into Ignition

1. Define the global TLP definitions available for all ROC devices in this Ignition instance
2. Create the base device connection to the ROC
3. Specify the subset of TLP definitions that this specific ROC uses
4. Create TLP Template(s) which define groups of TLPs should be polled as a logical group
5. Create TLP Poll Group(s) which specify the logical parameters associated with a given TLP Template
6. Use Ignition designer to pull tags into a tag provider

Global TLP Definitions

Creating a Device Connection

Specifying TLP Definitions for a Device

Creating TLP Templates for a Device

Creating TLP Poll Groups for a Device

Viewing Device Data