Three times now my Sonic Pad has "forgotten" the WiFi connection, requiring me to reconnect to my WiFi again.
When this happens, I can no longer print normally. Each time I either upload a new print from my slicer (Orca or Prusa), it will not start the printing at 0%. It would load the print at some random %, like 2% or 17% etc. and then immediately move the print head to where it should be at that point in the print, and fail with the Extrusion halted due to low temperature errors.
This will happen even on older prints that have printed successfully multiple times.
This happens irrespective of where the print is initialised: From the Slicer, from Mailsail/Fluidd or from the Touch Screen, same behaviour.
Reverting to an older backup of Printer.cfg doesn't help.
Rebooting the Sonic Pad doesn't help.
Clearing the historic/failed prints doesn't help.
Deleting and re-uploading the gcode model doesn't help
Re-Slicing and renaming gcode and pushing to the printer doesn't help.
The only way I can resolve this issue is by doing a Factory Reset through the settings, at least I can choose to keep the Config and gcode files, and only reset the Logs. After doing this, it will print as normally again.
So something somewhere in the OS (maybe log related) is getting stuck causing the Pad to think any print has already started, and it should resume at some random point causing it to error out because the temperature isn't set and it tries to extrude.
Three times now my Sonic Pad has "forgotten" the WiFi connection, requiring me to reconnect to my WiFi again.
When this happens, I can no longer print normally. Each time I either upload a new print from my slicer (Orca or Prusa), it will not start the printing at 0%. It would load the print at some random %, like 2% or 17% etc. and then immediately move the print head to where it should be at that point in the print, and fail with the Extrusion halted due to low temperature errors.
The only way I can resolve this issue is by doing a Factory Reset through the settings, at least I can choose to keep the Config and gcode files, and only reset the Logs. After doing this, it will print as normally again.
So something somewhere in the OS (maybe log related) is getting stuck causing the Pad to think any print has already started, and it should resume at some random point causing it to error out because the temperature isn't set and it tries to extrude.