Open Menace-Dennis opened 4 years ago
FormerLurker
commented
4 years ago I will look into this. Octolapse will already do what you are asking if there is only a single travel move in the case that the triggering command is a travel (G0/G1 with no E parameter), but it is not currently capable of storing multiple travel commands (lift/travel/delift, for example). Anyway, neat idea, and I'll leave this open.
FormerLurker
commented
4 years ago Whoops, didn't mean to close :)
Menace-Dennis
commented
4 years ago Cheers! I was just watching my 3D printer and realised, depending on the filament, the oozing from that long z-hop can cause "zits" so I think it would definitely help. My post-processing script for Cura has definitely helped the issue, it would just be nice if it was inbuilt into Octoprint, especially now as you're doing pre-printing analysis of the Gcode. Anyway, thanks for all your work with Octolapse, it's a great plugin.
If this is a feature request describe it here
Currently, when z-hop is enabled, Cura will lift the head and move to the starting x and y location of the next layer before the layer change. Octolapse in addition then takes the nozzle to the snapshot location, takes the snapshot and returns to that position. Seeing as you now perform pre-processing, I was wondering if you could provide an option for when z hop is enabled that the pre-next layer travel moves will be ignored and then will go to the starting point afterwards. I.e. the nozzle lifts from the end of the last layer goes to the snapshot location, takes the snapshot and then goes to the starting point location. This would reduce oozing and improve print quality by reducing the time the nozzle is lifted. Currently I have the stabilisation on disabled and run a post-processing script on Cura to do this for me. But, I'd like to be able to change the stabilisation pattern. It involves tracking the final location and z height before the end of the layer and putting this after the trigger to make sure it returns to this location, the movements from ";MESH:NONMESH" to ";TIME_ELAPSED:" are then removed. You then have GCode like below which works with the Disabled stabilisation:
For when already lifted:
G1 F300 Z6.2 ;MESH:NONMESH ;TIME_ELAPSED:2719.947034 ;TIMELAPSE BEGIN G0 F300 Z6.2 ;Making sure height is correct ; Already Retracted: True ; Already Lifted: True G0 F9000.0 X140.0 Y140.0 ;Park print head @OCTOLAPSE TAKE-SNAPSHOT ;Octolapse Trigger G0 F9000.0 X111.435 Y99.349 ;Move to the next point ;TIMELAPSE END ;LAYER:53 G0 X111.435 Y99.349 Z6.3
For when not already lifted:
G0 F9000 X106.126 Y129.481 ;MESH:NONMESH ;TIME_ELAPSED:3757.061674 ;TIMELAPSE BEGIN G0 F300 Z8.4 ;Making sure height is correct ; Already Retracted: False G0 F1800.0 E1052.38779 ;Retract Filament ; Already Lifted: False G0 F300.0 Z9.2 ;Z hop G0 F9000.0 X140.0 Y140.0 ;Park print head @OCTOLAPSE TAKE-SNAPSHOT ;Octolapse Trigger G0 F9000.0 X116.48 Y131.922 ;Move to the next point G0 F300.0 Z8.4 ;Undo Z hop G0 F1800.0 E1057.38779 ;Undo Retract Filament ;TIMELAPSE END ;LAYER:82
Version of Octolapse
Octolapse Version: 0.4.0
Version of OctoPrint
OctoPrint Version: 1.4.0
When you ran into the problem, did you have diagnostic logging enabled?
Diagnostic Logging was Enabled: _REPLACE_THISYES_OR_NO
What were you doing when the problem occurred
What should have happened?
_REPLACE_THISPUT_YOUR_DESCRIPTION_HERE
What happened instead?
_REPLACE_THISPUT_YOUR_DESCRIPTION_HERE
Operating System running OctoPrint and Octolapse
OS Name: _REPLACE_THISOS_NAME_GOES_HERE Os Version: _REPLACE_THISOS_VERSION_GOES_HERE
Printer model & used firmware incl. version
Printer Model: _REPLACE_THISPRINTER_MODEL_GOES_HERE Printer Firmware Version: _REPLACE_THISPRINTER_FIRMWARE_VERSION_GOES_HERE
Browser and version of browser, operating system running browser
Browser: _REPLACE_THISBROWSER_VERSION_GOES_HERE Browser OS: _REPLACE_THISBROWSER_OS_GOES_HERE
Link to the gcode file you were printing when the problem occurred
Link to Gcode File: _REPLACE_THISGCODE_FILE_LINK_GOES_HERE
Link to settings.json
Link to settings.json with all passwords removed: _REPLACE_THISSETTINGS_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_THISLINK_GOES_HERE
Link to contents of Javascript console in the browser
Link to javascript console output: _REPLACE_THISLINK_GOES_HERE
Screenshots and/or videos of the problem:
Screenshot/Video Links: _REPLACE_THISLINKs_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.