Page History

...

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 by the MQTT Engine and MQTT Recorder modules running on a central Ignition Gateway and inserted into a database for later use or to be made available to other third party systems.

Common File Exchange (CFX) can also be used for these record data.

Anchor
Prerequistes Prerequistes

Prerequisites

...

1. From EFM Emerson ROC Settings, define/upload the global TLP definitions available for all ROC devices in this Ignition instance
   
   
2. From EFM Emerson ROC Settings, define/upload the EFM Mappings for all ROC devices in this Ignition Instance
   
   
3. From OPC UA Device Connections, create the device connection to the ROC
   
   
4. For this device Connection, specify the subset of TLP definitions that this specific ROC uses
   
   
5. For this device connection, create TLP Template(s) which define groups of TLPs should be polled as a logical group
   
   
6. For this device connection, create TLP Poll Group(s) which specify the logical parameters associated with a given TLP Template

...

You should see the tags being polled from the ROC device as shown below.  You can use these tags as any standard OPC tags in Ignition.

Anchor
ViewRecordData ViewRecordData

Viewing

...

Record Data

Record data can be viewed in a couple of ways:

• Using Common File Exchange (CFX)
• Publishing as an immutable record object

Using Common File Exchange (CFX)

If using Common File Exchange (CFX), the record data will be stored/maintained in CFX.MD5 files on the local Ignition instance. See the Emerson ROC Device Connection configuration for more details. 

These files can be transferred from the Edge device using any method you choose such as FTP but can also be published using the MQTT Transmission File Publishing option.

To do this, you will need to configure an MQTT Transmission File Record and set the CFX File Transfer parameter to point to that File Record and the CFX files can then be automatically published. See the Creating and Publishing Common Exchange File CFX tutorial for details.

Publish as an immutable record object

To publish To view record data which includes ROC alarms, events, and history data you must have MQTT Transmission installed on the instance with the EFM Emerson ROC driver.

In addition, the following must be set up:

At the Central Gateway:

• Setup an SQL database connection
• Configure MQTT Engine
  • Add/update the Server configuration to point to the MQTT server
• Configure MQTT Recorder and configure it to use SQL database connection (previously set up in the Ignition Gateway)

...

• Configure MQTT Transmission

  • If you do not have a Transmitter configured, create an MQTT Transmitter and set the Sparkplug Settings to the unique Group and Edge Node ID values generated by the Device Connection configuration.

  • If a Transmitter already exists, for example to publish the polled/live data, you can edit the Group and Edge Node IDs to match the existing Sparkplug Edge Node created by the Transmitter.Add/update the Transmitter configuration and/or the Tag folders so that an Edge Node is reporting with a Group ID, Edge Node ID, and Device ID (for example: G1, E1, D1)
  • Add/update the Server configuration to point to the MQTT server
  • From Ignition Designer, use the MQTT Transmission 'Refresh' Mechanism to make sure it is connected and reporting.
• Configure EFM Emerson ROC module
  

  • The Alarm, Event, and/or History poll rates in the Emerson ROC driver device configuration must be greater than zero depending on which data you wish to collect.

    Warning
    Must have a Sparkplug Group ID , and Edge Node ID, and Device ID specified in the device Device Connection configuration that matches the a Sparkplug Edge Node /Device that MQTT Transmission is reporting on

    
    

When all of these conditions are met, alarm, event, and/or history data will be collected, published, and stored via MQTT Recorder in the configured database.

...