I recently purchased the Enterprise IIoT Gateway which I plan to connect to our MQTT que in Azure, locally the gateway will connect to sensors via Ethernet/IP and a PLC via OPC UA.
Is this possible to run multiple protocals on the Gateway and are there any guides to what protocals are supported with documentation to how to configure them?
Hi @richardosborne Sure, the Enterprise IIoT Gateway runs Node-RED as a service. You can use Node-RED to send NCD sensor data over MQTT or OPC-UA. We have some guides on our website, which I’ve shared for your reference:
MQTT:
Note: This is an article using AWS, but we explain how to configure the MQTT node parameters.
OPC-UA:
MQTT nodes are included in the Node-RED core and are supported by the Node-RED team, while OPC-UA nodes are third-party libraries.
Please take a look at this and feel free to let us know if you have any questions.
Thanks,
Eduardo M.
Would it be possible to use an internal mosquitto service on the gateway to listen to messages being sent from another node-red enabled plc?
My goal is to integrate with some existing hardware via hardware into ETH1.
Do you have any recommendations?
Hi @danempiric Yes, you can run an MQTT broker directly on the Gateway. We recommend using the node-red-contrib-aedes library, which allows you to host a broker within Node-RED without the need for an external service like Mosquitto.
Once configured, you can publish to or subscribe from topics using external clients connected to the broker via the ETH1 port (or any other available interface).
Note: I’ve only tested it locally, but it might work.
Thanks.
thanks, when i’m trying to add the pallete I’m getting these errors that the node red is not the latest, is it OK to update the node-red with NCD’s hardware/pallete? They are backwards compatible?
Yes, you can update by following this guide:
Hi, i have loaded the aedes onto the gateway but am still unable to write anything to the gateway from my plc to the gateway. I am able to write information from my MAC but nothing is going through from the plc.
I feel like there is a setting I’m missing
plc ip address is 192.168.12.48
the mqtt in on the gateway
aedes node
mqtt out on the plc
gateway ip address
Hi @danempiric let me perform some local test with similar setup.
Just to confirm, are you connecting your PLC to the Gateway using Eth1 port? if not, be sure you are using this Eth1.
actually i was able to figure it out. I’m such an idiot, I didn’t have the ethernet ports setup on the same subnet so they weren’t able to see each other. The biggest issue I saw was that the ETH1 port on the gateway was on the same subnet as the ETH0 port. This was causing conflicts in the network reading the PLC. So I changed the subnet on eth1 on the gateway to match the PLC and bingo it started working.
Great! We performed a test and it worked as well. We will publish a basic guide on our website.
Thank you.
