July-27th-2022, 05:26 PM
Well Devendra,
devices of type netFIELD are handling process data such as fieldbus data totally differently than netIOT devices years before. I agree that a manually installed Node-RED can be used too on the devices of course, but in general with netFIELD devices data is transported across a central MQTT message broker and then distributed from there "to the world" .
This in turn has also the advantage that once data is known in the central MQTT message broker that it can be transmitted to multiple clients at a time or even better to Node-RED also which supports a MQTT client node by default. This gives the netFIELD devices more flexibility than we ever had with our "old" netIOT devices that rely on Node-RED only.
For a correct setup you need to onboard your device to a netFIELD Cloud account first. From there you deploy the container "mosquitto" as central MQTT message broker to your device from the list of available containers. Did you get managed this?
Thx
Armin
devices of type netFIELD are handling process data such as fieldbus data totally differently than netIOT devices years before. I agree that a manually installed Node-RED can be used too on the devices of course, but in general with netFIELD devices data is transported across a central MQTT message broker and then distributed from there "to the world" .
This in turn has also the advantage that once data is known in the central MQTT message broker that it can be transmitted to multiple clients at a time or even better to Node-RED also which supports a MQTT client node by default. This gives the netFIELD devices more flexibility than we ever had with our "old" netIOT devices that rely on Node-RED only.
For a correct setup you need to onboard your device to a netFIELD Cloud account first. From there you deploy the container "mosquitto" as central MQTT message broker to your device from the list of available containers. Did you get managed this?
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
