Page History

...

...

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 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.

...

• Knowledge of Ignition and Cirrus Link Module Installation process
• Knowledge of MQTT Engine and MQTT Transmission configurations
• Installation of MQTT Engine, MQTT Transmission and MQTT Recorder (v4.0.x if using Ignition 8.1.x)
• Installation of latest EFM Emerson ROC module

...

The global TLP definitions made available to the EFM Emerson ROC module.  They are uploaded to the Ignition instance in the form of specifically formatted CSV files.  These TLP definitions can be reference by the configurations of the individual ROC devices that they apply to. A single Ignition Gateway may contain multiple global TLP definitions files that are used to configure different device types where the actual point types & parameters of the individual TLPs may differ across the different files and device types.

...

The configuration mapping files are used for building up EFM Configuration Records. They define which TLPs map to which fields (columns) in an EFM Configuration Record.  Additionally they can provide bit and/or value mappings for the TLP values. They are uploaded to the Ignition instance in the form of specifically formatted CSV files. 

...

These are a subset of the global TLP definition files that apply to a specific device.

...

TLP templates are logical groupings of TLPs.  Generally TLP templates would be created so that instances of them can be used by specifying a poll group with a logical number (the 'L' parameter in a TLP).

...

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 from a ROC into Ignition

...

At this point the ROC device should be fully configured.  To view data in Ignition launch Ignition Designer and open the OPC Tag Browser as shown below. 

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.

Image Removed

...

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)

At the Edge Gateway

...

• 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.

...

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.

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.

...