MQTT experts

PLC

Member
Join Date
Sep 2002
Location
NC
Posts
311
Any MQTT experts here?
I’m trying to learn and test an s71200 client with a MQTT broker/server.

Can anyone suggest a simple broker/server I can use on a pc ? (That you have used)

Just something simple to send any data back and forth
 
Yes, it's very simple to use.


I would recommend watching a Youtube video or Googling a tutorial on how a broker works
 
I'm the Scada administrator for Pioneer Oil and we have several remote (very remote) locations that all of the data to and from these locations use the MQTT protocol.

We use Ignition Scada, Cirrus Link, Maple Systems, to handle all our MQTT needs.

Our remote locations are connected back to our Scada Server with our own "Private Cellular Network".

I can say if your looking at MQTT, I would recommend using the "Sparkplug B 3.1.1" protocol.

This is my 2 cents worth.
 
Last edited:
I tired MQTT last year with S7-1200 and could not make it work. Going by the memory of a man who doesn't like remembering I think it had something to do with authentication. I was able to connect to a local broker but I could not connect to an online one. I believe S7-1200 does not support secure communication and having to open a port that was blocked by my ISP. Can't seem to find my notes.
 
I tired MQTT last year with S7-1200 and could not make it work. Going by the memory of a man who doesn't like remembering I think it had something to do with authentication. I was able to connect to a local broker but I could not connect to an online one. I believe S7-1200 does not support secure communication and having to open a port that was blocked by my ISP. Can't seem to find my notes.


Latest FW for 1200 (v4.4, requires v16) allows for secure communication.
 
Fantastic, now we're talking.


Thanks mk42.




Edit: I just realized secure communication was available also with 4.3 which is the version I was working with. I will have to dig in more to find out what issues I had; I'm quite sure it had to do with connecting to remote server.
 
Last edited:
Edit: I just realized secure communication was available also with 4.3 which is the version I was working with. I will have to dig in more to find out what issues I had; I'm quite sure it had to do with connecting to remote server.

I guess I was one off, whichever. I think DNS showed up in the 1200 somewhere along the way as well. New FW def does add OPC UA to the 1200, which is nice.

I've heard that dealing with certificates is terrible, especially when you start mixing in cloud providers. We (controls engineers) don't know the terminology, and the directions basically say "here's how it works without security. To be secure, add certificates" without covering the steps required.
 
Last edited:
Jeev
Wow. Now that’s very interesting.
I’m digging more and more with MQTT and I haven’t seen that before
Great info
 

Similar Topics

Hi Guys, I am facing problem in connecting “Siemens PLC” with MQTT-broker. 1. In node-red, MQTT-node status remains connecting. 2. In...
Replies
2
Views
117
My task is to connect a MQTT broker on IP range 192.168 towards my OT network with the L33ER PLC on 10.10. IP range. Need communication both...
Replies
0
Views
424
Hello, Have anyone here use Ignition to connect to a Remote IO using MQTT, then use ControlLogix or CompactLogix to connect to Ignition using...
Replies
1
Views
409
Working on a project using MQTT and an Automation Direct Click Plus. Have the bidirectional communication pretty much figured out. One of the...
Replies
1
Views
1,429
In the setup of MQTT on the AD Click PLC, it looks like an IP address needs to be entered. Is there a way to specify a public broker by name...
Replies
1
Views
1,330
Back
Top Bottom