SBC: Emergency Macro on "Lost connection to Linux"
-
As reported yesterday, I had a spurious disconnect of my Raspberry Pi from the printer which caused the machine to stop the printer dead in the water until everything was rebooted. The printer didn't receive any commands successfully after that.
I think it would be useful to have a disconnect Macro that runs on the "Lost connection to Linux" event that moves the print head to a safe parking position. That way, potential issues with the heater not turning off and machines which have effectors that need to engage a brake to avoid sinking into the part / the bed to fall down, could do a hail-mary move.
-
As part of the planned work for v3.4 I'll bring the Linux interface code in RRF in line with the stepper driver code in one of the next releases, I hope that will resolve the spurious disconnect you had, too.
It is possible that v3.4 will bring support for the SD card in the Duet even when in SBC mode, which would then allow RRF to call a macro file when the connection to the SBC is interrupted. But be aware it will take some more time before this is addressed.
When the SBC disconnects, RRF already shuts down all the heaters and discards potentially blocking requests.
-
@chrishamm said in SBC: Emergency Macro on "Lost connection to Linux":
When the SBC disconnects, RRF already shuts down all the heaters and discards potentially blocking requests.
As you can see in in my recent experience, at least in some cases the Duet board thinks that it can't shutdown heaters on tool boards and prints scary messages.
It's better to print the message despite successfully shutting down the heater than the other way round, but it still leaves me with worry.
That said, I am looking forward to 3.4! I will nonetheless look into switching to standalone mode for a couple long running prints ....
-
It is indeed quite strange that both CAN and SPI stopped working at the same time. I'll discuss this internally in hope to find a solution soon. Also note that I do not recommend using RRF 3.3-b1 with DSF 3.2. If everything goes well, we'll do a coordinated pre-release for 3.3-b2 tomorrow, though.
-
@chrishamm said in SBC: Emergency Macro on "Lost connection to Linux":
Also note that I do not recommend using RRF 3.3-b1 with DSF 3.2.
In the future, if possible, this should be pointed out in the beta release notes either here in the forum, and/or on the github page. When I asked about the availabilty of 3.3b1 for SBC via apt, I was told to do the update manually ...
-
@oliof In the future we'll do coordinated (pre-)releases again - 3.3-b1 was an outlier, sorry for the confusion there. In general it's best to keep the SBC up-to-date by using apt only, else I cannot guarantee that the combination of DSF and RRF will work as anticipated.
