OctoSlack messing up prints (vase mode) #118
Comments
|
Hi @melyux A bit of background: So let's start by take a look at what, if anything, the Octoslack plugin is doing. Enable DEBUG logging Enable DEBUG logging |
|
Sure, I'll give it a try as soon as I can. Thanks for the background crash course. Interesting that plugins block in the main thread in priority of the printing. I guess it makes sense considering how things like OctoLapse work, but doesn't seem to make sense for things like OctoSlack. Is there an option for plugins to spin off in threads instead of blocking the printing thread? |
|
Great question - for Octoslack I've already moved as much as possible (image processing, sending messages to slack, etc.) but there is some work I still need to do in the main thread before I can fire up the thread. Most notably is grabbing various printer states (e.g. what's the % complete when the event fired) or evaluate a g-code event to potentially trigger events. The plugin has a ton of DEBUG logging so hopefully we'll be able to take a look to see if the plugin is doing any signifant work or otherwise getting hung up somewhere. |
|
Alright, got an octoprint.log. I tried it again and got the same results: no stuttering all the other plugins, but just Octoslack by itself leads to the nozzle stuttering in vase mode. Again, Octoslack is not configured at all, it's just freshly installed with no configuration whatsoever (i.e. it doesn't send any messages because I haven't set it up). Here's the log with debug for Octoslack on: |
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
The text was updated successfully, but these errors were encountered: