Skip to content

Conversation

@RanieriFerreira
Copy link

Problem

I've been using the M600 command on my K1C for a few days, but most of the time, the filament gets stuck during the UNLOAD FILAMENT process, as shown in the image below:

filament-stuck

After researching, I found an open discussion where other users reported the same issue:
GitHub Discussion #678

Solution

To fix this, I replaced the fourteen separate extruder commands with a single extrude and retract command. This simplifies the unloading process and improves reliability.

@alvarogalia
Copy link

Is there a way to call the native GCODE_MACRO? There is a reason for all the retractions and extrusions made when changing filament, and that is because of the ramming curve that prevents filament blob

@RanieriFerreira
Copy link
Author

Which native GCODE_MACRO are you referring to?

The issue occurs when the GCODE_MACRO UNLOAD_FILAMENT is triggered by the M600 command:

The same GCODE_MACRO can also be triggered from the M600 menu option:

RESPOND TYPE=command MSG="action:prompt_button UNLOAD FILAMENT|_UNLOAD_FILAMENT|secondary"

If there's a specific reason for using fourteen separate extruder commands, I'm not aware of it. However, it didn’t work for me or another K1C user. On the other hand, the two simple extruder commands I proposed worked in every test I conducted.

Could you test this on your machine or another model to confirm?

@alvarogalia
Copy link

Seems like the native macro is called QUIT_MATERIAL in gcode_macro.cfg and it is updated by firmware once in a while.
The reason for make that much movements is because the printer has to mold the filament in a specific way that it can get removed and inserted again automatically without having to unlock the extruder, I think that this is to be able to use CFS

I've been using M600 since a while and never had this problem on 7 machines (V3 and K1)

This is the shape the end takes when using QUIT_MATERIAL, it has uniform width and left no residue that can make a clog
IMG_7221

@nof0xgvn
Copy link

nof0xgvn commented Feb 27, 2025

Unload itself works for my K1C, even changed the guppyscreen unload gcode to the M600 one because the ramming is nice i think.
just noticed that if you forget to actually change the filament quickly, it will warm up again and clog the extruder.
So maybe unload with ram and then turn off/down the temps instead of holding it?
Or even turn down the temps before (not sure if ramming is still possible like that), so it's somewhat cooler when the filament just sits there.
Maybe just letting the extruder fan run might help.

Edit:
I also lovered my extruder run current to 0.45 which (which makes it run cooler)
image

@joaquin021
Copy link

joaquin021 commented Apr 21, 2025

Seems like the native macro is called QUIT_MATERIAL in gcode_macro.cfg and it is updated by firmware once in a while. The reason for make that much movements is because the printer has to mold the filament in a specific way that it can get removed and inserted again automatically without having to unlock the extruder, I think that this is to be able to use CFS

I've been using M600 since a while and never had this problem on 7 machines (V3 and K1)

This is the shape the end takes when using QUIT_MATERIAL, it has uniform width and left no residue that can make a clog IMG_7221

I agree with you, the best would be to make a call to the native macro QUIT_MATERIAL which works perfectly and does not create clogs.

The problem of the _UNLOAD_FILAMENT created in the M600.cfg is the G1 E10 F300 (line 32) command.
If it is replaced by G1 E100 F300 as in the native macro, it does not generate clogs.
But I think the intent of this macro is to do the same as the native to create the tip, but extruding less filament before retracting it.
Putting a G1 E50 F300 I think also works, and you may be able to reduce it if you don't want to extrude as much. But by doing just that E10 extrusion, it generates a clog most of the time.

@keetsta
Copy link

keetsta commented Jun 2, 2025

bump, i had the same problem while using an M600, this made me think that i just broke my extruder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants