i am trying to run node-red on my wago pfc200-8204 which is assigned by a DHCP server. i am trying to run command to start node-red however it creates the container to start it, for momentarily and then exits immediately. Is this can happen due to firmware as i just changed firmware recently for factory resetting. Here is more detail about my error.
root@PFC200-41E863:~ docker start 30bffb3b7ff0
30bffb3b7ff0
root@PFC200-41E863:~ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
30bffb3b7ff0 nodered/node-red “npm --no-update-not…” 3 minutes ago Up 2 seconds (health: starting) 0.0.0.0:1880->1880/tcp wago-node-red
root@PFC200-41E863:~ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
30bffb3b7ff0 nodered/node-red “npm --no-update-not…” 3 minutes ago Exited (135) 6 seconds ago wago-node-red
root@PFC200-41E863:~ timed out waiting for input: auto-logout
Connection to 192.168.1.20 closed.
Hello thanks for the help. i actually think that if you install older firmware on wago (3.0.59 (12) I believe), we cannot run latest versions of the node-red somehow. i installed version 8 of the node-red, which is quite old and it ran alright on the web browser.
This is the error i am facing if i try to run newer image of the node-red instead of rpi-v8 version image.
Not sure how to avoid this or what is causing it.
The 750-8202 has less memory than the newer 750-8212. Because of this, starting with FW19 requires a different firmware. These can be downloaded & installed with e!COCKPIT directly if the PFC is FW12 or higher (see image below). If your PFC is running FW8, you will need to update with an SD card. Here is FW17 link, which you can unzip and image.
Version 3.0 works well on Generation 2 PFC controllers. The 8204 is a generation 1 and was replaced with a higher performing, expanded storage version with no price increase a few years ago for this reason. The 750-8214 runs NR version 3.0 very nicely. I would suggest upgrading the controller to allow for this functionality.
