Skip to content

Commit

Permalink
Update tip_forming_and_purging.md
Browse files Browse the repository at this point in the history
  • Loading branch information
moggieuk authored Mar 3, 2024
1 parent 114b944 commit 990702f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion doc/tip_forming_and_purging.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@ Just don't forget to persist the final result in `mmu_parameters.cfg` when the p

## ![#f03c15](/doc/f03c15.png) ![#c5f015](/doc/c5f015.png) ![#1589F0](/doc/1589F0.png) No Wipe Tower Option

The wipe tower is a great solution for handling the purge necessary when changing tools (Prusa Slicer also has an experiemental "purge to infil" to minimize waste) but it has the downside of taking up a large portion of the build plate. To avoid this an add-on purging system can be used during the toolchange allowing the wipe tower to be disabled! A great example of such a system is [Blobifier](https://github.com/Dendrowen/Blobifier/blob/main/Config/blobifier.cfg). In fact the additional macro to drive Blobifier is supplied in the Happy Hare "config/mmu/addons/" directory. It can be added to Happy Hare with a single line addition in `mmu_macros_vars.cfg`.
The wipe tower is a great solution for handling the purge necessary when changing tools (Prusa Slicer also has an experiemental "purge to infil" to minimize waste) but it has the downside of taking up a large portion of the build plate. To avoid this an add-on purging system can be used during the toolchange allowing the wipe tower to be disabled! A great example of such a system is [Blobifier](https://github.com/Dendrowen/Blobifier/blob/main/Config/blobifier.cfg) by Sjon Huisman. In fact the additional macro to drive Blobifier is supplied in the Happy Hare "config/mmu/addons/" directory. It can be added to Happy Hare with a single line addition in `mmu_macros_vars.cfg`.

Setting up a purge system is beyond the scope of this page but such a system will require purging volumes discussed above. These purge volumes can be automatically [pre-processed](/doc/gcode_preprocessing.md) from the g-code and stored by Happy Hare for the duration of the print. This information is made available to your macros through printer variables, e.g. `printer.mmu.slicer_tool_map`. The other way to setup purge volumes is via the `MMU_SLICER_TOOL_MAP` command. All three of these commands would estabish the simple 9-tool matrix shown in the illustration above from Prusa Slicer. Read more about this command [here](/doc/slicer_setup.md) and [here](/doc/command_reference.md)
```yml
Expand Down

0 comments on commit 990702f

Please sign in to comment.