canvas: put the purge-end retract back before returning to the print - #319
Open
kyleinoregon wants to merge 1 commit into
Open
canvas: put the purge-end retract back before returning to the print#319kyleinoregon wants to merge 1 commit into
kyleinoregon wants to merge 1 commit into
Conversation
KICK retracts retract_amount after the tray purge so the wipe does not ooze. Nothing ever un-retracts it: AFC restores the print position as soon as the tool change ends, Orca slices with relative extrusion and only un-retracts the retract it did itself, so every colour starts retract_amount short. With the default 2 mm that is about 15 mm of thin line at the start of each colour region through a 0.8 nozzle, and more with smaller lines. It shows up as a crescent-shaped gap at the start of each perimeter after a change. Un-retract at the end of the wipe, while still over the wiper, and take one more swipe to shed the bead that makes. The travel back to the print then happens in the same state as any other travel in the print. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every colour on a CANVAS print starts short by
retract_amountof filament, and this is why.KICKretractsretract_amount(2 mm by default) after the tray purge so the wipe does not ooze, and nothing ever un-retracts it. AFC restores the saved print position as soon as the tool change ends, so the head is already back on the part when the slicer's G-code resumes. Orca slices with relative extrusion, so it only un-retracts the retract it did itself; it has no idea about the macro's. The firstretract_amountof extrusion after a change just refills the melt zone.With the default 2 mm through a 0.8 nozzle at 0.4 mm layers that is roughly 15 mm of thin line at the start of every colour region (about 60 mm with 0.4 mm lines and 0.2 mm layers). Against a light it shows as a crescent-shaped gap at the start of each perimeter after a change, and as light through the part at the colour boundaries.
The change is three lines in
KICK: after the last wipe, while still over the wiper, un-retract the same amount and take one more swipe to shed the small bead that makes. The travel back to the print then happens in the same state as any other travel in the print, with only the slicer's own retract in effect, and the first perimeter after a change starts at full flow.macros.cfghas its ownKICKfor the non-CANVAS path; it is left alone because a purge line follows it before printing starts.Tested
Centauri Carbon with CANVAS, COSMOS 26.08.0, four wood PLA lanes, 0.8 nozzle, a 4-colour concentric-ring coin with 25 changes per print. Before: a crescent gap along the outer ring's inner boundary and a gap around the centre disc on every print, visible against a light. After: both gone on the first print with the change, no other settings touched. Also verified in the sliced file that Orca's tool-change "extra length on restart" cannot substitute for this: Orca 2.4.2 drops it, and even if it did not, the un-retract would land on the part after AFC's own return move.