Sending ABB Totalflow History to a Central Ignition Gateway

Prerequisites

• Installing the Java Runtime Environment
• Installing Ignition
• Installing the following MQTT Modules on two Ignition systems
  
  • Ignition System 1 (Central Ignition Gateway)
    
    • MQTT Distributor
    • MQTT Engine
    • MQTT Recorder
  • Ignition System 2 (Remote/Edge Ignition Gateway)
    
    • MQTT Transmission
    • EFM ABB Totalflow driver module
      
      

Overview

The EFM ABB Totalflow module is capable of polling history data from an ABB Totalflow device based on a specified polling rate.  With MQTT Transmission, this history data can be published as Sparkplug records to an MQTT server.  Any client subscribed on Sparkplug RECORD messages can receive these objects.  In addition, MQTT Engine when combined with MQTT Recorder can also receive these messages and store these objects in a configured Ignition database.  The following drawing shows the general architecture used to do this.  This tutorial outlines the process of getting history to the central Ignition gateway.

Sending ABB Totalflow History to a Central Ignition Gateway

We must configure a total of five Cirrus Link modules on two different Ignition gateways to get history data flowing from an ABB Totalflow device to a central database.  These are:

• Central Ignition Gateway
  
  • MQTT Distributor
  • MQTT Engine
  • MQTT Recorder
• Remote/Edge Ignition Gateway
  
  • MQTT Transmission
  • EFM ABB Totalflow

The configuration of each of these modules is covered below based on the Ignition gateway they're installed on.