When I end a 3D-print, the Z-axis is put as high as possible on my printer to prevent the nozzle hitting the printed object when moving the bed in X- and/or Y-position.
As a consequence, when a new print is started the print head/nozzle has to move down all the way again to its home position. For the X- and Y-movements, that goes quick. However, for the Z-movement that takes a while (approx. 15-20 seconds, not timed yet) and because of that long time before the print head/nozzle reaches its home position, OctoPrint is giving me a communication error, abandoning all settings (bed and nozzle heating are switched off) and also disconnects from my printer.
I have to reconnect the printer ASAP and also re-select my object to print ASAP to avoid cooling down too much both the bed as well as the nozzle.
Can this communication error be avoided? Is there some timeout that is set too short and that I can extend to overcome this issue?
- Raspberry Pi 3B+
- OctoPi image: 2019-09-26-octopi-buster-lite-0.17.0
- OctoPrint Version: 1.4.2
- Printer: Balco 3D TouchPrint (comparable with Wanhao Duplicator i3 Plus)
- Browser: Google Chrome
- Firmware: Standard FW delivered with the printer, no changes done
- Operating system: Windows 10 Home