Open whitis opened 2 years ago
One problem seems to be that when you think you ran off the end of the spool you don't update the amount of filament used/remaining so you keep running out on every print rather than getting past the point of running out.
FilamentManager 1.9.1 on Octoprint 1.7.3 seems to be responsible for multiple inappropriate pauses in consquitive prints. Prints are interrupted by message "M0 command blocked" (there were no M0 commands in Gcode file) and Insufficient Filament. Had to hit resume. Print cooled down so layer adhesion will be poor. On most recent prints I was told there was insufficient filament to print and started anyway (there was a lot left on spool). On the first two I was not. It still interrupted the print. Further, filament manager doesn't give you the option to leave your prints alone when you reach the "end" of the spool.
First print broke in half in use - where FilamentManager stopped it. The current print has an 1/8" gap between layers in one corner caused by the unauthorized stop.
And the blocked M0 commands are still executed, they are just executed by OctoPrint instead of the printer.