Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OctoSlack causing layer shifts #126

Open
GaryBoone opened this issue Oct 5, 2021 · 0 comments
Open

OctoSlack causing layer shifts #126

GaryBoone opened this issue Oct 5, 2021 · 0 comments

Comments

@GaryBoone
Copy link

I've been suffering from layer shifts in my prints. After checking belt tensions and checking for other mechanical issues, I suspected plugins might be the cause. I did a search by enabling/disabling plugins and narrowed the primary suspect to OctoSlack. Here's the data:

Plugin Run1 Run2 Run3 Run4 Run5 Run6 Run7 Run8 Run10 Run11
DryRun Plugin (1.2.0) enable disable disable disable enable enable enable enable disable disable
Firmware Updater (1.12.0) enable disable disable disable enable enable enable enable disable disable
Octoslack (2.2.0) enable enable enable disable disable disable disable enable enable enable
Preheat Button (0.8.0) enable disable disable disable enable enable enable enable disable disable
PrintTimeGenius Plugin (2.2.8) disable disable disable disable enable enable enable enable disable disable
Prusa ETA override Plugin (0.1.1) disable disable disable disable enable enable enable enable disable disable
Resource Monitor (0.3.5) disable disable disable disable enable enable enable enable disable disable
Slicer Thumbnails (1.0.0) enable enable disable disable enable enable enable enable disable disable
Tab Order (0.5.12) enable enable disable disable enable enable enable enable disable disable
TemperatureFailsafe (0.2.3) enable enable disable disable enable enable enable enable disable disable
LAYER SHIFT OCCURRED yes yes yes no no no no no no yes
>25hrs ~19hrs ~17hrs >25hrs

The data appears to implicate OctoSlack, but of course it's not conclusive. It could just be a rare problem and I'm often running with OctoSlack enabled.

I have enabled logging for OctoSlack, but it appears that logging only covers maybe 3 hours. So I'm not sure if the logging I have covers the most recent layer shift. Also the log is long and contains private info like names and tokens. So let's narrow down what we're looking for in the logs and I'll scrub a relevant portion to post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant