Hopefully someone out there can shed some light on this - in a nutshell I’m trying to setup the following:
AB PLC –> Node-Red –> MQTT –> Ignition
We currently use ignition edge to poll AB devices and publish data via MQTT, so I’m attempting to come up with an ultra-lightweight edge device to poll the PLC, then publish the data in sparkplug B to my MQTT server for ignition to pick it up.
The plan is to run node-red on an advantech ADAM for a handful of tags with low power draw for those fringe edge cases where a full blow ignition edge is overkill and I want to save data on metered connections.
Using ignition edge the data shows up in our IO server on the following path:
Edge Nodes –> Facility group –> Facility Name –> Tag Group –> Tags
Works great, everything is happy.
Using node-red it shows up on the following path:
Edge Nodes –> Facility group –> Facility Name –> Device –> Tag Group –> Tags
That additional Device entry in the path is killing me, using the mqtt sparkplug device node there is no way I’ve been able to find to NOT get that node to inject the device field.
When try the other nodes, mqtt sparkplug out getting it to perform an NBIRTH and get store and forward working, and all the stuff that the mqtt sparkplug device node just does out of the box is a nightmare.
Has anyone managed to get node-red polling local PLC’s and publishing proper sparkplug B into ignition without the device node just putting that extra step in the path? am I using the wrong nodes?
Been going in circles for weeks and I’ve not found a way to make this work.
