Actually, Opto 22 groov EPIC, RIO, and EMU support MQTT and Sparkplug B directly from the devices.
Versions of these devices also support Ignition Edge. See here for more info:
Yes but if you are using a different PLC then you have to go thru the Ignition Edge and OPC to connect to the PLC and MQTT
Correct, PRAMANJ. I was addressing your comment that "You can't connect MQTT directly to PLCs." While true for many PLCs, there are some that do just that.
For the use cases where you'll need to communicate with non-MQTT PLCs, we embed Ignition into these products as well. So, both native MQTT and Ignition MQTT are available onboard this particular "PLC." I hope that makes sense.
3 Likes
Agreed. More and more PLCs are offering native support for MQTT client, OPC server etc. More the merrier, as it eliminates the extra layer of edge devices.
However to connect to Ignition you need the CirrusLink's MQTT modules on Ignition side, but you can connect any MQTT device on client side with or without SparkPlugB support. With sparkPlugB you get plug and play functionality with complete tags metadata from client to server. You can use any commercially available MQTT servers or CirrusLinks own servers.
Feel free to add/delete/correct anything in the above understanding of mine.
You got it!
For Ignition to subscribe to MQTT messages from any MQTT 3.1.1 compliant broker (many available, including Cirrus Link's MQTT Distributor module that runs within Ignition), you only need Cirrus Link's MQTT Engine module.
Thank you for the dialogue! -Benson
Try it yourself in 15 minutes as detailed at
and shown in this 3-minute video
Hi All
Thanks for your suggestion and Information. I'm Trying to connect the Delta PLC MQTT module (AS-FFTP01) with Ignition, I have tested the connection using MQTT.fx - 1.7.1. I can subscribe the "Topics" from delta PLC. but I couldn't find the Delta MQTT 'Topics' on the Ignition - MQTT Engine - Edge Nodes.
I suspects two things:
- IG using 4.0.20 whereas Delta PLC MQTT module using the MQTT V3.1.1
- Ignition using Sparkplug concept but Delta blocks using Topics and Message concept, please let me know is there any problem with this.
I have attached screen shot of my PLC setting and Ignition for your reference. kindly give me your suggestions.
If a source device doesn't use Sparkplug B, then you must set up a custom namespace in Ignition. You also lose various features (like writeback) that are automatic with Sparkplug.
Hi @pturmel Thanks for your information. Now I can read the Tags on Ignition. Is there any other way to write the tag without Sparkplug B function.
There would need to be other topics for the reverse direction, and would have to be subscribed by the device, in some device-specific way. On the Ignition side, you have to script the publish to such a topic.