I'm using Node-Red to connect a laptop to a Mitsubishi Alpha-2 microcontroller via an usb-serial cable.
The communication doesn't start immediately when I fire up my laptop.
Initially I suspected a permissions issue in Linux, but I'm no longer sure that this is the problem.
Powercycling the Alpha-2 does not work.
Rebooting the laptop does not work.
However, when I restart the Node-RED process ( node-red-restart ), the communication is magically restored. I suspected the first node-red process might have had a different owner but that is not the case, I checked.
This sounds very like a problem a week or two back. Have you configured node red to autostart on boot? If so then if you disable autostart sudo systemctl disable nodered
and reboot, then start nodered is it ok? If so then node-red is starting too quickly and the serial port doesn't function for some so far unknown reason. Have a look at this post which tells you how nodered can be delayed on boot, which fixed the problem in this case Serial woes.. buffer issue?
@dceejay I don't know whether you want to consider this. This is the second Pi recently that seems to have a problem with the serial port on boot, fixed by delaying the node-red start. I haven't got any hardware to try it myself.
Oh yes, sorry I got confused.
Obviously not a Pi related issue. The previous instance was one where the device was continually sending data, so it isn't that either, as yours polls.
