June-28th-2018, 06:54 AM
Hi Flo,
the Node-RED fieldbus example is automatically loading a different firmware into the netX chip. This means starting two containers - one with LAN and one with PROFINET/Ethernet/IP - at the same time will never work. It is not predicable which container will succeed and in which order they are started. So this is a dead end.
Here is how I would do it: I would create my very own container. I would keep the LAN example like it is and would add from the fieldbus container github project the following source code lines from the dockerfile and would copy them into the netX LAN example and rebuild the new container.
#install node.js V8.x.x
url -sL https://deb.nodesource.com/setup_8.x | sudo -E bash - \
&& apt-get install -y nodejs \
#install Node-RED
&& npm install -g --unsafe-perm node-red \
This would just install node.js and node-red ... and no additional netX driver and fieldbus nodes that would cause a firmware reload into netX chip destroying your LAN interface.
As next I would modify the entrypoint.sh of the LAN example and would add a /usr/bin/node-red after the cifx0daemon has been loaded to let start node-red at each boot. Please do not forget to map port 1880 when starting the container.
the Node-RED fieldbus example is automatically loading a different firmware into the netX chip. This means starting two containers - one with LAN and one with PROFINET/Ethernet/IP - at the same time will never work. It is not predicable which container will succeed and in which order they are started. So this is a dead end.
Here is how I would do it: I would create my very own container. I would keep the LAN example like it is and would add from the fieldbus container github project the following source code lines from the dockerfile and would copy them into the netX LAN example and rebuild the new container.
#install node.js V8.x.x
url -sL https://deb.nodesource.com/setup_8.x | sudo -E bash - \
&& apt-get install -y nodejs \
#install Node-RED
&& npm install -g --unsafe-perm node-red \
This would just install node.js and node-red ... and no additional netX driver and fieldbus nodes that would cause a firmware reload into netX chip destroying your LAN interface.
As next I would modify the entrypoint.sh of the LAN example and would add a /usr/bin/node-red after the cifx0daemon has been loaded to let start node-red at each boot. Please do not forget to map port 1880 when starting the container.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
