-
-
Notifications
You must be signed in to change notification settings - Fork 887
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
Fix wipe tower issues with SEMM and ramming turned off #6934
Fix wipe tower issues with SEMM and ramming turned off #6934
Conversation
Hey @igiannakas |
@SoftFever Sure thing - see attached video here: Project link: https://drive.google.com/file/d/14oXy9z96a3jdIdgVSk3iqld1MTCkvys4/view?usp=sharing its on layer 115 Edit: with correct project link |
I got it now. |
No worries and thank you for helping out with this 🙏🏻🙏🏻 |
This reverts commit 9fc465c.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thank you
…th wipe tower extrusions. (#6980) … # Description This update, along with #6934, resolves the remaining issues with the wipe tower. The GCode class will no longer maintain its own Z height information (m_nominal_z). Instead, it will utilize the Z height from GCodeWriter's m_pos. This approach is less error-prone. This PR also fixes #6755. It also enforce "Enable Filament ramming" option @igiannakas It should fix the wipe tower crashing issue # Screenshots/Recordings/Graphs <!-- > Please attach relevant screenshots to showcase the UI changes. > Please attach images that can help explain the changes. --> ## Tests <!-- > Please describe the tests that you have conducted to verify the changes made in this PR. -->
* Fix wipe tower issues with SEMM and ramming turned off * Purge tower last layer collision potential fix (for SEMM) * Revert "Purge tower last layer collision potential fix (for SEMM)" This reverts commit 9fc465c.
Description
Fixes issues discussed here: #6894
EDIT: Reverted changes for Z issues when next layer starts over the wipe tower. Keeping the below commentary for reference only.
@SoftFever Would appreciate a review for the nozzle crash on the last wipe tower layer issue please. This was added here 13ddb38 but with the model below I get a nozzle crash on the top layer as the nozzle is forced one layer down. For some reason this:
Returns the previous layer Z when on the final wipe tower layer, so it pushes the nozzle down to the wipe tower.
Maybe that is expected as on the last layer of the wipe tower the nozzle finishes the layer, does the tool change and then immediately moves to the next layer while still over the wipe tower. See below:
Last layer where a toolchange is needed is printed - the grey line is the last print
The first move of the next layer is the purge tower (the fix is applied to the below screenshot so there is no z going to the prev layer):
So technically Z hasn't changed over the model, so the gcode gen function doesnt know of this new height. So when setting it to current Z we are actually setting it to the previous Z from the model...
Just a theory on this as I am really not sure. In any case, this PR appears to have resolved it for SEMM by removing the specific code segment that causes this Z move on the wipe tower.
I have not tested this with a multi toolhead profile so please do before merging anything in :)