Mqtt egine ignition edge groov epic

Ignition
1

Hi,

what could be failing?

2020-11-27_20h05_15
2020-11-27_20h05_151280×984 50.5 KB

2
  1. There is no MQTT broker running on ‘localhost’. (At a guess - EPIC does not have one out of the box).
  2. Do you have an MQTT broker running on 192.168.55.30?

In other words, its failing because both of those IP addresses do not have an MQTT broker running on them?

3

Hi Beno,

I feel the delay in answering, I can barely connect.

  1. The address 192.168.55.30 belongs to Epic.
  2. Does the Ignition Edge from Epic have any broker?

this is more like a play test, knowing what can or cannot be done with the team.

that is, from the ignition installed on my Windows computer, the Mqtt Engine module appears with the connected status and I can connect to the Epic and see its variables.

I try to do the same with the Ignition Edge of the Epic, to read by Mqtt the variables of the Epic itself, but this does not have the status of connected.

I know I can do it by Opc Ua, but Mqtt Sparkplug simplifies a lot, but it is more a test, to see the possibilities of the Epic.

4

I think it would be worth your time to spend a few minutes reading on the Inductive Automation and Cirrus Link websites and perhaps view a few of their videos.
Keep in mind that there are three MQTT modules.
(Broadly speaking here)
Engine for subscribing.
Transmission for publishing.
Distributor is the broker.
You can install any of these modules on the EPIC, but should you?
If you are just playing around then, sure, run a broker on EPIC to see that it works, but at the end of the day take a step back and think about the system architecture you want to build, support and maintain.

5

you’re right, thank you.