Contents
Cirrus Link Resources
Cirrus Link Website
Contact Us (Sales/Support)
Inductive Resources
Ignition User Manual
Knowledge Base Articles
Inductive University
Forum
...
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:
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'.
...
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:
In this example we're usiing the default MQTT Server of MQTT Distributor:
Under the General Transmitters tab, we're also using the defaults:
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.
...
...