Page History

...

• Installing the Java Runtime Environment
• Installing Ignition
• Installing the following MQTT Modules
  • MQTT Distributor
    • v1v2.71.1 or greater X if using Ignition 7.7.Xv1.8.1 or greater if using Ignition x or 7.8.Xx
    • v3.1.0 or greater if using Ignition 7.9.X
  • MQTT Engine
    • v1v2.71.3 or greater X if using Ignition 7.7.Xv1.8.3 or greater if using Ignition x or 7.8.Xx
    • v3.1.0 or greater if using Ignition 7.9.X
  • MQTT Transmission
    
    • v1v2.71.0 or greater X if using Ignition 7.7.Xv1.8.0 or greater if using Ignition x or 7.8.Xx
    • v3.1.0 or greater if using Ignition 7.9.X
• A device that supports Modbus over TCP

...

The first step is to configure the tag provider in Ignition in a way that MQTT Transmission understands.  Start by configuring your OPC server, client, and tags.  This can be done using the Inductive Automation documentation here.  Once this is done, the Tag Provider needs to be set up in Ignition via the Ignition Designer.  Using a Web Browser, browse to the Ignition Gateway on your Ignition Gateway.  If it is running on your development machine, that is: http://localhost:8088.  You should see this:

Image RemovedImage Added

Near the upper right corner, click 'Launch Designer'.  This will open the following window after downloading the JNLP file and executing it.  Note the default username/password is admin/password.  Type those into the appropriate fields and click 'Login'.

...

In this example we're going to use the '"default' " tag provider within Ignition Enterprise.  Do so by expanding Expand 'All Providers' in the Tag Browser and select 'default'.  Note that if Ignition Edge is being used, the tag provider will be named 'edge'.

With 'default' (or 'edge') selected, click the 'OPC' icon in the Tag Browser icon list:

...

With our tags set up as we want them, we now must configure MQTT Transmission.  Do so by browsing to the the Configure section of the Ignition Gateway web UI and selecting 'MQTT Transmission -> Settings' on the left:

                                                                                                                               Image Removed

 Image Added

In this example we're usiing the default MQTT Server of MQTT Distributor:

Image RemovedImage Added

Under the General Transmitters tab, we're also using the defaults:

Image RemovedImage Added

Note the Tag Provider Name is the same Tag Provider we build out our Edge Nodes from in the Tag Browser earlier.  Now we can go back to Designer and force MQTT Transmission to update.  MQTT Transmission does not dynamically look for changes in the tag structure and update them.  If it did, you could end up with a lot of improperly structured data while the changes to the tag tree are being made.  So, the update must be forced via 'Refresh'.  This is a tag under the MQTT Transmission tag provider as shown below in the Tag Browser.

...

In addition to the tags being displayed in Engine, they are also writable if this enabled in MQTT Engine.  By default, MQTT Engine blocks command messages from being sent to devices.  To enable this feature, in the Ignition web console browse to the MQTT Engine Module Configuration and make sure 'Block Commands' is not checked Settings.

Image Added

Make sure the "Block Node Commands" and "Block Device Commands" settings are disabled, as shown below:.

Image RemovedImage Added

With this enabled and Designer in read/write and preview mode, you can write to the outputs of the modbus device from the Tag Browser:

...