RPi v0.92.2 not properly recovering/reconnecting after hard firmware halt/reset
Hello!
Recently updated 2 out of 5 of my hub Pi's to 0.92.2, but had one throw a thermal runaway due to a fan issue (All machines are running Marlin 1.1.9). In previous versions, the firmware would automatically recover and reset the machine, but I noticed that the machine was halted.
I hard-reset the controller, and when it came back on, the hub did not automatically try to reconnect. It was still "green/active" in the interface, but the bed temperature was zeroed out and no data was being passed. I had to deactivate/reactivate printer for it to successfully reconnect.
Is this a new bug, intentional behavior change, or something wonky with my own setups? Normally i'd say it was this one hub, but I forced one into a firmware-halting error on a different installation/board, and it did the same thing.
Comments
The problem is if the serial driver is hanging somehow a reset on printer side is not enough. It does not reset the serial driver chip on printer. Unplugging usb and depowering printer would do that and then it should automatically recover.
This is something happening outside of servers control. At least if the above procedure helps. Would also mean that the printer serial converter did go to error state. Did you update by using the buster image so that you have a new kernel?
I think I might have changed error handling. In marlin.xml firmware description you have
which puts it in halted state. In earlier versions it would deactivate printer so you would have needed to activate. This could lead to disturbing loops without user being able to see the messages in console or with automatic activation even an automatic error loop. It also confused users that the printer was suddenly not active. You should also have gotten a message about the halt i the messages list in gui.
Will see why emergency stop does not help here. Always thought it also restarts connection.