fraschetti
commented
3 years ago Hi @melyux
A bit of background: OctoPrint plugins operate inline with OctoPrint itself. This means when an event fires that a plugin is subscribed to (% complete, g-code processed, etc.), it's wildly important how long any given plugin (or combination of plugins) take to process that event. Priners typically keep a local buffer of commands and for hightly details prints (e.g. not long extrudes in a straight lines), the printer is likely constantly being fed new commands from OctoPrint. Because these plugins operate inline with the main OctoPrint processing thread, if one or more plugins are keeping OctoPrint busy, it may not have enough time to send commands to the printer and eventually the printer is left waiting what to do next. And of course if the printer is waiting and the nozzle is idle, even for a brief moment, it allows unwated filament to ooze out and blemishes to form.
So let's start by take a look at what, if anything, the Octoslack plugin is doing. Please follow the steps below to generate some debug logs if you're willing to kick off another print with the plugin going. The logs will likely give me an idea of what's going on but if you could summarize what you have enabled (what events are enabled, are you using the g-code event feature, etc), that may also help.
Enable DEBUG logging Reproduce the issue Send Octoprint.log Instructions to enable DEBUG logging for Octoslack
Enable DEBUG logging Ensure the following has been added to /home/pi/.octoprint/logging.yaml (or appropriate path for your OctoPrint installation) loggers: octoprint.plugins.Octoslack: level: DEBUG Restart OctoPrint sudo service octoprint restart For OctoPi releases, the log file will be located in: /home/pi/.octoprint/logs/octoprint.log
melyux
I was attempting a vase mode print for the first time and noticed some zits on my print, caused by the print head stuttering. Investigation showed that the stuttering wouldn’t happen when printing from SD card, or when printing in safe mode. I tried turning on my plugins by themselves and trying.
The result was... OctoSlack enabled just by itself was enough to cause stuttering in vase mode when printing from my Pi 3B+ OctoPrint. I could turn off OctoSlack and and enable all of the other plugins simultaneously (14 of them), and it would print perfectly. Meaning OctoSlack was solely responsible for the stuttering, which is probably slowness in how fast the Pi is sending the vase mode GCODEs.
Notes: OctoSlack is unconfigured because I hadn’t gotten around to it. So this is happening without any configuration. Vase mode requires sending lots of GCODE rapidly to the printer, so these issues really surface when doing vases.
Picture below: Left is with only OctoSlack enabled, all other plugin disabled Right is with 14 plugins enabled, OctoSlack disabled