Skip to content
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

Big Blob of filament after M600 #12654

Open
2 tasks done
thedizze opened this issue Apr 26, 2024 · 7 comments
Open
2 tasks done

Big Blob of filament after M600 #12654

thedizze opened this issue Apr 26, 2024 · 7 comments

Comments

@thedizze
Copy link

thedizze commented Apr 26, 2024

body1
1714307987737
Marlin M600
body1
Body1.zip

Description of the bug

After performing a filament change with M600 a big blob of filament was dropped on the first move over the printed part
Issue in previous version with same setting was not present or it dropped just little pipmle of filament

Project file & How to reproduce

.

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.7.4

Operating system

windows 10

Printer model

Twotrees sapphire sp5

@carlosjln
Copy link

This same thing has happened to me every time I do a filament change, I have to use the tweezers to pull the filament until the nozzle starts to move.

The pause action should ideally happen in the middle of an infill path so that any potential blobs are hidden inside the print.

@rtyr
Copy link
Collaborator

rtyr commented Apr 27, 2024

M600 behavior is handled by the firmware not the slicer. We can check your your project file if you provide it.

@carlosjln
Copy link

@rtyr thanks for the confirmation 🤔 I was suspecting that could also be the case, because it behaves similar when I tell it to pause through the screen.

@Tupson444
Copy link

I think this might be related to relative/absolute E moves. If it is set different in the slicer and the firmware, the printer might extrude or retract a lot when executing M600, due to wrong E position (if absolute coordinates were e.g. 80mm, instead of a move of -1mm, it would do +79mm, or something like that).

@thedizze
Copy link
Author

M600 behavior is handled by the firmware not the slicer. We can check your your project file if you provide it.

Hello i've added a zip with gcode an 3mf file and screenshot of my marlin m600 settings

seems that the issue appears when I do reverse prints and I "trick" the printer like if It's a dual extruder. If I do a normal color change at layer everything is fine.

Can you help me in understand and solve the problem ? thank you

@thedizze
Copy link
Author

retraction
what is this setting (set on 10 by default on both virtual extruders) can be influent?

@rtyr
Copy link
Collaborator

rtyr commented Apr 30, 2024

Yes, this should be set to 0 in your case.

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

No branches or pull requests

4 participants