M620.11 long retraction command info
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- api, documentation
Research direction
Start with the M620.11, M628, and M629 Change filament snippets in this issue, then compare them with slicer-setup.md in the linked mfm repository. Done means documenting which AMS and extruder motors each command affects, including the long-retract and undo-retract paths.
Written by the indexing model from the issue text.
Description
Bambu added a new AMS command of M620.11, M628, M629 with the long retraction before cut update and it is used in the Change filament gcode at the points below:
Long Retract
{if long_retractions_when_cut[previous_extruder]}
M620.11 S1 I[previous_extruder] E-{retraction_distances_when_cut[previous_extruder]} F{old_filament_e_feedrate}
{else}
M620.11 S0
{endif}
Long undo retract
{if long_retractions_when_cut[previous_extruder]}
M620.11 S1 I[previous_extruder] E{retraction_distances_when_cut[previous_extruder]} F{old_filament_e_feedrate}
M628 S1
G92 E0
G1 E{retraction_distances_when_cut[previous_extruder]} F[old_filament_e_feedrate]
M400
M629 S1
{else}
M620.11 S0
{endif}
I think that the M620.11 S1 moves both the AMS hub feeder motor and extruder motor backwards at the same time because there is not a matching G1 E-{retraction_distances_when_cut[previous_extruder]} for the retraction portion of the code. If the filament buffer is fully compressed, the extruder should not be able to long retract on it's own without AMS retraction. Likewise for the AMS retracting on it's own in the filament buffer is in the decompressed length during printing.
There is a M620.11 S0 and G1 with positive extrusion movement when undoing the retraction in the second block of gcode so it's even more confusing.
I make use of inserting new toolchanges in my post processing script and I have described my guesses on M620.11 on my repo as well (https://github.com/ansonl/mfm/blob/master/slicer-setup.md#set-filament-settings)
Do you have any better ideas on which motors that new G-codes activate in the AMS and extruder?
- Dominant language
- No language data
- Stars
- 682
- Forks
- 96
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Doridian/OpenBambuAPI
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Doridian/OpenBambuAPI#51 · 8 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Doridian/OpenBambuAPI#10 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
Doridian/OpenBambuAPI#72 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Doridian/OpenBambuAPI#59 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Doridian/OpenBambuAPI#56 · 1 comment ·
All issues in Doridian/OpenBambuAPI
Similar issues
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100