Stringing

[shrubstabla]

If this is a feature request describe it here

___REPLACE_THIS__FEATURE_REQUEST_DESCRIPTION_GOES_HERE

Version of Octolapse

Octolapse Version: ___REPLACE_THIS__OCTOLAPSE_VERSION_GOES_HERE

Version of OctoPrint

OctoPrint Version: ___REPLACE_THIS__OCTOPRINT_VERSION_GOES_HERE

When you ran into the problem, did you have diagnostic logging enabled?

Diagnostic Logging was Enabled: ___REPLACE_THIS__YES_OR_NO

What were you doing when the problem occurred

1. ___REPLACE_THIS__STEP_ONE_GOES_HERE
2. ___REPLACE_THIS__STEP_TWO_GOES_HERE
3. __REPLACE_THIS__STEP...

What should have happened?

___REPLACE_THIS__PUT_YOUR_DESCRIPTION_HERE

What happened instead?

___REPLACE_THIS__PUT_YOUR_DESCRIPTION_HERE

Operating System running OctoPrint and Octolapse

OS Name: ___REPLACE_THIS__OS_NAME_GOES_HERE Os Version: ___REPLACE_THIS__OS_VERSION_GOES_HERE

Printer model & used firmware incl. version

Printer Model: ___REPLACE_THIS__PRINTER_MODEL_GOES_HERE Printer Firmware Version: ___REPLACE_THIS__PRINTER_FIRMWARE_VERSION_GOES_HERE

Browser and version of browser, operating system running browser

Browser: ___REPLACE_THIS__BROWSER_VERSION_GOES_HERE Browser OS: ___REPLACE_THIS__BROWSER_OS_GOES_HERE

Link to the gcode file you were printing when the problem occurred

Link to Gcode File: ___REPLACE_THIS__GCODE_FILE_LINK_GOES_HERE

Link to settings.json

Link to settings.json with all passwords removed: ___REPLACE_THIS__SETTINGS_JSON_LINK_GOES_HERE

Link to plugin_octolapse.log

Link to plugin_octolapse.log: LINK_GOES_HERE

Link to octoprint.log

Link to octoprint.log: ___REPLACE_THIS__LINK_GOES_HERE

Link to contents of Javascript console in the browser

Link to javascript console output: ___REPLACE_THIS__LINK_GOES_HERE

Screenshots and/or videos of the problem:

Screenshot/Video Links: ___REPLACE_THIS__LINKs_GO_HERE

Please consider becoming a patron

If you like this project, please support my work by becoming a patron, and consider adding a 'star' to the repository. It takes a lot of time and effort to maintain the project and respond to issues. The cost of test prints, software, cameras, printer parts, etc. can quickly add up, so every bit helps.

You can find various videos and tutorials by subscribing to my Youtube channel. You can also follow me on Twitter.

I’m recently new to 3D printing, and I installed Octoprint in Jan this year. About a month ago I set up OctoLapse, which has been consistently running on every print I made. I began noting stringing and spent a long time striving to improve my print quality but I just couldn’t do it. Then, yesterday, I got to the bottom it. It was OctoLapse. Each time the printhead moved away so the snapshot could be taken, a whisper of filament built up, the accumulation of which has ruined several intricate and time consuming models. I have included a photo of a whale’s head with a track of filament build up that has ruined the print. I have since disabled OctoLapse and all stringing test output is significantly improved. What I also noticed was that the movement of the printhead that caused this stringing was not accompanied by retractions, which I think should have been inserted when OctoLapse inserted amendments to the Gcode,

I understand you do not warranty OctoLapse, making the point that it is used at my risk. I reluctantly accept that, but I thought it’s important to pass on this information.