-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Integrate external purge estimates (eg Blobifier) to the filament consumption UI #7508
Integrate external purge estimates (eg Blobifier) to the filament consumption UI #7508
Conversation
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.
Looks good.
Thank you :)
Welcome :) |
sorry Offtopic: thank you |
Its from here: https://cults3d.com/en/3d-model/home/christmas-multicolor-knitted-containers-not-needed-supports There are also these ones that are free, from the same designer: https://cults3d.com/en/3d-model/home/santa-christmas-multicolor-knitted-container-not-needed-supports |
Description
With external purging solutions becoming more common, I’ve come across a limitation when assembling mine - it is impossible to estimate the amount of filament purged during slicing!
For example, when using Happy Hare together with the blobifier, it is not possible currently to estimate the volume of filament purged, because there are no G1 Ex commands issued by the slicer, but rather the purge volumes are calculated and executed by the printer/ happy hare and blobifier software and macros themselves.
This PR aims to address this limitation by tagging the purge commands as specially formatted comments and use that to calculate the projected flushed filament volume. This is particularly useful in combination with Spoolman as you can actually compare now the projected filament use vs your available filament in the spool man UI.
This should be fairly accurate as the flush/purge volume matrix is read by Happy Hare and is used by the blobifier to execute the purge. Also this approach allows the user to apply the same correction variable to the volumes (variable_purge_length_modifier), if other than 0.
This also allows the user to include the combined filament consumption between external purge (in the blobifier) and any prime tower that the user may have enabled (eg. to ensure the nozzle is primed before printing).
To set it up, set the below in your Change Filament g-code:
If your variable_purge_length_modifier is not 1.0, then you can adjust the calculated purge volume like so (eg. if the value is 0.6).
Make sure purge in the prime tower is disabled:

Tests
Tested with Bambu and Voron printers. As this is a comment in the Gcode and the code is only invoked when the external purge tag is present, there are no side effects.