When printing with Octopi it will fail for essentially any print longer than 5 hours.
I have an Anycubic Chiron running stock 1.3 firmware. Every print I have tried to run over night has failed. I wake up to the printer being stationary, still heated, and will an serial port error.
"Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves."
I have ensured that the printer cable is good. It has a ferrite choke. I dont run the cord along any steppers or the power supply and this just keeps happening.
It is to the point where I just print from the SD card whenever I have a large print, which is kind of demoralizing with all the effort I spent to setup Octoprint.
I am running OctoPrint 1.4.0 running on OctoPi 0.17.0, the server connects to the printer no problem. I am using a Rasberry Pi 4b from a Cano kit, so I know the power supply is solid. I do not have a camera connected to the Pi and have no other services running on it.
I have tried replacing the USB cable and running in safe mode, it makes no difference
I have attached 2 logs. The first (octoprint(1)) occurred when monitoring the print while running from the SD.
The second happened when printing from Octoprint directly.
octoprint (1).log (846.5 KB) octoprint.log (733.1 KB)
2020-06-05 04:34:15,339 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2020-06-05 04:47:35,474 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-06-05 05:02:35,475 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-06-05 05:17:35,477 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-06-05 05:32:35,479 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-06-05 05:47:35,480 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-06-05 05:51:13,957 - octoprint.server.util.flask - INFO - Passively logging in user _api from ::ffff:192.168.0.106
2020-06-05 05:51:13,958 - octoprint.access.users - INFO - Cleaning up user session 27044B727CD84B4FA2B3FE72F156758D for user _api
2020-06-05 05:51:13,958 - octoprint.access.users - INFO - Logged out user: _api
2020-06-05 05:51:13,960 - octoprint.access.users - INFO - Logged in user: _api
2020-06-05 06:02:35,482 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-06-05 06:17:35,484 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-06-05 06:32:35,486 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-06-05 06:47:35,487 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-06-05 06:49:06,948 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-06-05 06:49:36,983 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-06-05 06:50:07,008 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-06-05 06:50:37,036 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-06-05 06:51:07,078 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-06-05 06:51:37,098 - octoprint.util.comm - INFO - No response from printer after 6 consecutive communication timeouts, considering it dead.
2020-06-05 06:51:37,123 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
This seems to be the relevant part of octoprint.log. Without serial.log one can't see what's really happening.