Octoprint Timeout

Hi there,
I keep getting a communication timeout on Octoprint. I'm hoping that someone can help me out or at least point me in the right direction. Here is what I know.

  • When I generate gcode from Cura, send it to Octoprint, and print, everything works fine.
  • When I generate gcode from Fusion 360, upload it to the Octoprint SD card, and print, everything works fine.
  • When I generate gcode from Fusion 360, press the upload to Octoprint button, and print, I keep getting an error.

I have attached the log file with the error to this thread. Hopefully someone has seen this before. Thanks in advance for your help.

octoprint.log (130.2 KB)

Hello @jonvh!

First, please shutdown OctoPrint properly. Do not just pull the plug. You will corrupt the filesystem on the SD card sooner or later.

You may also reinstall the Slack plugin.

Do you mean the SD card in the Pi or in the printer?

Could you please a bit more specific what error you get?
Have you compared the gcode files: uploaded to the SD card and that one in this

And if you need help, choose the subforum Get Help, not General.

Thanks for the tips. I appreciate it. I'll be sure to shutdown Octopi properly.

When I am referring to the SD card, I am referring to wherever this button puts them:

The error that I get is:

2020-11-11 17:12:50,995 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-11-11 17:12:53,001 - octoprint.util.comm - INFO - No response from printer after 6 consecutive communication timeouts, considering it dead.
2020-11-11 17:12:53,101 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
2020-11-11 17:12:53,131 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2020-11-11 17:12:53,732 - octoprint.plugins.tracking - INFO - Sent tracking event commerror_timeout, payload: {'commerror_text': 'Too many consecutive timeouts, printer still connected and alive?'}

I have reviewed the gcode files from the two. But they look like the matrix to me. I can tell that they are different, but not in any sort of meaningful way because I'm not quite sure what I should be looking for that might cause the error.

I asked, because I assume that the F360 to OctoPrint uploader scrambles something, so that printing is denied.

The Upload button stores the file on the OctoPrint SD card.
The Upload to SD stores the file on the printers SD card. This can take a long time.

Concerning the pulled plug: I found some sections in your log like this:

2020-11-11 01:44:19,685 - octoprint.plugins.tracking - INFO - Sent tracking event print_done, payload: {'origin': 'local', 'file': '99d4eb9d8b3917945e9f5bbbc979f65bc4ee2486', 'elapsed': 2323}
2020-11-11 01:34:43,820 - octoprint.startup - INFO - ******************************************************************************
2020-11-11 01:34:43,823 - octoprint.startup - INFO - Starting OctoPrint 1.4.2
2020-11-11 01:34:43,829 - octoprint.startup - INFO - ******************************************************************************

The startup time stamp if before the last timestamp.
A regular shutdown should look like this:

2020-11-05 11:38:43,040 - octoprint.server - INFO - Calling on_shutdown on plugins
2020-11-05 11:38:43,338 - octoprint.events - INFO - Processing shutdown event, this will be our last event
2020-11-05 11:38:43,343 - octoprint.events - INFO - Event loop shut down
2020-11-05 11:38:43,530 - octoprint.plugins.tracking - INFO - Sent tracking event shutdown, payload: {}
2020-11-05 11:38:43,797 - octoprint.server - INFO - Goodbye!
2020-11-05 11:38:56,878 - octoprint.startup - INFO - ******************************************************************************
2020-11-05 11:38:56,879 - octoprint.startup - INFO - Starting OctoPrint 1.4.2
2020-11-05 11:38:56,882 - octoprint.startup - INFO - ******************************************************************************

Thanks for looking into this, and you are correct about the shutdown. Up until I read your post yesterday I just shut the power off for the Octoprint server, so the log would reflect that. I will shut it down from the software from now on, thank you for pointing that out.

There is no F360 to OctoPrint uploader. That was going to be the next step if I was able to successfully print. My current process is that I post-process from F360 to my laptop. Then upload it from there (manually) using the OctoPrint interface.

So you store it on the hard drive and then you move it over to OctoPrint.

Could you please share a sample gcode file? Or at least the first 200 lines or so. Maybe there is something in the F360 gcode that makes OctoPrint feel bad.