What is the problem?
I've been using OctoPi with no issues for years now and after upgrading from 1.4.0 to 1.4.2 my printer is timing out. No other changes. On a Rpi 3B+. Seems to always happen in pre-setup where the printer is calibrating and warming up. I literally printed 1 dozen things last week on 1.4.0 with the same setup and had no issues. I had added the OctoPod plugin for fun but have been troubleshooting with that disabled just to remove that variable from the equation.
2020-08-08 20:53:13,194 - Recv: ok
2020-08-08 20:53:13,203 - Send: N51 M204 S30081
2020-08-08 20:53:13,210 - Recv: ok
2020-08-08 20:53:13,217 - Send: N52 G2937
2020-08-08 20:54:03,316 - No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long
running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2020-08-08 20:54:03,409 - Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer sti
ll connected and alive?)"
What did you already try to solve it?
Rebooted numerous times and updated the serial connection from 30->40secs after applying that was posted to fix the setting saving issue.
Additional information about your setup
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
Lulzbot Mini printer
chrome Version 84.0.4147.105 (Official Build) (64-bit)
MacOs Mojave 10.14.6 (18G6020)
Cura lulzbot edition 3.6.8
Filesystem Size Used Avail Use% Mounted on
/dev/root 7.1G 1.9G 4.9G 28% /
devtmpfs 433M 0 433M 0% /dev
tmpfs 438M 0 438M 0% /dev/shm
tmpfs 438M 5.9M 432M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 438M 0 438M 0% /sys/fs/cgroup
/dev/mmcblk0p1 253M 53M 200M 21% /boot
tmpfs 88M 0 88M 0% /run/user/1000