OctoPrint 1.5.0 + GCodeLeveling Plugin Caused Extruder to Stop Working

Get Help
1

Just heads up that when I did the 1.5.0 upgrade yesterday, the extruder stopped working. Took me a while to figure it out. It turned out the GcodeLevelling plugin and 1.5.0 don't seem to get along well. You essentially lose all of your E commands in the Gcode along the pipeline and thus your printer extrudes nothing. The XYZ moves are fine as well as all other moves, just the extruder E moves get killed.

To resolve I simply disabled the GcodeLevlling plugin and presto, back to normal.

3 Likes
2

thanks for letting us now :+1:

unfortunately you aren't the first with that problem after the update.
I suggest you keep the plugin disabled until a new version is released

3

I've reported this to the author here:

It would probably be a good idea for anyone affected by this to help the author with analysing this issue by providing logs and such in this ticket.

I've also blacklisted the plugin on the repository for OctoPrint >= 1.5.0.

1 Like
4

Good Grief! I thought was an issue with my printer...Works perfectly fine from SD card - and now, THANKS to you tip, after disabling the Octolpase Plugin.
Sent as well, as requested the logs.octoprint.log (241.1 KB)

However, as Octolapse and the time lapse videos are part of my goal....kinda, looking for options alternative solutions....

5

Update for OctoLapse is available as of about 10 hours ago, you should get the update notification within 24 hours or you can force check for updates/reinstall it too.

6

I seem to be in same same boat, even after a couple years and doing full format and reloads of octoprint and machine firmwares, it seems to be persistent error/side effect that cant be fixed with software...
I am running an old creality "silent board".. I'm guessing octolapse will have to stay disabled until it get around to changing out that mainboard one day

7

A lot has changed in 2 years since this post, and my comment above indicates that there was an update to OctoLapse to resolve this issue released. Of course it's been a long time and I don't remember exactly what that was referring to, but I would guess you probably have a different issue than the one that was resolved here.