Printing With Octoprint causing Stuttering and Blobs

What is the problem?
When printing with Octoprint I get stuttering an a lot of Surface Blobs
What did you already try to solve it?

Installed New Octopi 017 on new SD card Sandisk Ultra 16 GB. Connected by ethernet to pi 3B+. Turned off wifi and bluetooth. Printed Identical gcode file direct from Printer main board and good quality clean print
Printer Ender 3 Pro. SKR Mini E3 Board
Log shows loads of time outs

Please can you advise what to try next
Ta

Logs (octoprint.logt serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)

2020-04-25 17:17:58,619 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Connecting"
2020-04-25 17:17:58,644 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-04-25 17:17:58,651 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-04-25 17:17:58,657 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Operational"
2020-04-25 17:17:58,673 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-04-25 17:17:58,681 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin bugfix-2.0.x (GitHub)"
2020-04-25 17:17:58,691 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2020-04-25 17:18:01,985 - octoprint.filemanager.analysis - INFO - Analysis of entry local:CCR10_RC3_-x2-PETG.gcode finished, needed 48.15s
2020-04-25 17:18:27,549 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: CCR10_RC3_-x2-PETG.gcode, owner: cmd, user: cmd
2020-04-25 17:18:27,579 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2020-04-25 17:18:27,592 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: CCR10_RC3_-x2-PETG.gcode, owner: cmd, user: cmd
2020-04-25 17:18:27,602 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-04-25 17:18:27,610 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2020-04-25 17:18:29,637 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2020-04-25 17:24:05,998 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2020-04-25 17:26:34,790 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:26:38,790 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:26:42,789 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:27:02,798 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:27:06,791 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:27:26,794 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:27:32,794 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:27:36,795 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:27:56,803 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:28:00,811 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:28:18,804 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:28:24,817 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:28:28,817 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:28:38,810 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:28:44,821 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-04-25 17:28:54,811 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)

This is a common problem with both delta-style printers and those with 8-bit controller boards. You might take the edit-your-Marlin advice as seen here or visit the Anti-Stutter plugin thread.

forgot to add
nfiguration.h

#define BAUDRATE 250000
Configuration_adv.h

#if ENABLED(SDSUPPORT)
#define BLOCK_BUFFER_SIZE 64 // SD,LCD,Buttons take more memory, block buffer needs to be smaller
#else
#define BLOCK_BUFFER_SIZE 64 // maximize block buffer
#endif

#define MAX_CMD_SIZE 96
#define BUFSIZE 32

#define DEFAULT_MINSEGMENTTIME 50000

Also SKR Mini E3 is 32 bit I believe

Try the same file running OctoPrint in Safe Mode. If it doesn't do it, then list the plugins you have installed here.

ok will do later thanks

On the plug ins it is a fresh install so only the std installed plugins - no third party

Will look at the Arc Welder later and maybe do some comparisons Thanks

I tried safe mode and no improvement there are no plugins although I have just added arc welder but at present it is disabled. I did see on one of the threads recommend by @OutsourcedGuru that there are some questions about the TFT 35 screen I have. Do you think this might be the issue I quite like the screen but could try the old screen?

The problem isn't limited to delta-style or 8bit only. I have a cartesian printer (Anycubic i3 Mega) with a 32bit mainboard and I am suffering from this error for two years now.

2 Likes

What plugins do you have installed?

1 Like

I have the exact same issue when printing with octoprint, but not from the SD card. I'm using a BTT SKR 1.4 T. I spent several days trying to fix this issue from the marlin/board side but in the end running in safe mode made all the blobs go away. I'm now trying to find the faulty plugin(s).

I've heard of two specific plugins, DisplayLayerProgress and TPLinkSmartplug, that can cause this. I know there have been changes to both my plugin and the other one to try and resolve this, but I personally haven't heard any reports back from users that were experiencing it.

1 Like

Of course those are the 2 plugins I use :expressionless: Thank you for pointing this, this should reduce the number of my tests

For issues related to my plugin I would love to get some feedback with the latest release.

Which one of your plugins: tplink?

Yes, that's the one that had reports of causing stuttering/blobs, but I have yet to be able to reproduce the issue personally. If it is happening with the latest version I would definitely like to know as I've done some extensive processing changes on the back-end in one of the newer versions that should have helped if the issue existed within my plugin at all. Like I said, I don't remember ever getting any feedback on the posted issue.

So I just printed my test model after enabling back your plugin and all was fine. I'll now test DisplayLayerprogress.

Update: I can confirm that in my case DisplayLayerProgress is the one creating the blobs.