Skip to content

Latest commit

 

History

History
179 lines (149 loc) · 12.5 KB

sequential_purge.md

File metadata and controls

179 lines (149 loc) · 12.5 KB
Raw

STILL TESTING DO NOT USE

Sequential Purging

This incredible macro ensures that you won't have to fret about forgetting to remove your purge line from your bed. While the macro itself doesn't remove the purge line automatically, it does provide a buffer, minimizing the chance of error by always accommodating the previous purge line from the previous print.

Join

Modes

Continuous

In continuous mode the purge line gets drawn every print in an order and when the purge_sections_amount is full it will start back at the first purge section.

Limited

In limited mode a purge line gets drawn every print and you dont have to worry about accidentally leaving the purge lines on the bed because the print will not start once the purge_sections_amount is full.

Installation

  1. Use ssh to open your printer's terminal, eg Putty

     cd
 
 git clone https://github.com/Department-of-Design/Kevins-Awesome-Macros.git

 ln -s ~/Kevins-Awesome-Macros/config printer_data/config/KAM

 cp ~/Kevins-Awesome-Macros/config/KAM-settings.cfg ~/printer_data/config/KAM-settings.cfg

  2. Open your moonraker.conf file and add this configuration:

    [update_manager Kevins-Awesome-Macros]
type: git_repo
channel: dev
path: ~/Kevins-Awesome-Macros
origin: https://github.com/Department-of-Design/Kevins-Awesome-Macros.git
managed_services: klipper
primary_branch: main

  3. Add this to your printer.cfg.

    [include KAM-settings.cfg]

  4. Restart your firmware by sending FIRMARE_RESTART.

  5. Send the macro _INITIALIZE_PURGE in your printers console to initialize the purge counting. This fortunately only has to be done once so you can forget about it afterwards.

  6. Open KAM-settings.cfg. Next go to the Sequential Purging section.

    [gcode_macro _KAM-settings]
description: Settings for KAM macros

#     _____                             _   _       _   _____                 _             
#    / ____|                           | | (_)     | | |  __ \               (_)            
#   | (___   ___  __ _ _   _  ___ _ __ | |_ _  __ _| | | |__) |   _ _ __ __ _ _ _ __   __ _ 
#    \___ \ / _ \/ _` | | | |/ _ \ '_ \| __| |/ _` | | |  ___/ | | | '__/ _` | | '_ \ / _` |
#    ____) |  __/ (_| | |_| |  __/ | | | |_| | (_| | | | |   | |_| | | | (_| | | | | | (_| |
#   |_____/ \___|\__, |\__,_|\___|_| |_|\__|_|\__,_|_| |_|    \__,_|_|  \__, |_|_| |_|\__, |
#                   | |                                                  __/ |         __/ |
#                   |_|                                                 |___/         |___/ 

# Continuous: where the purge line gets drawn every print in an order and when the purge_sections_amount is full it will start back at the first purge section.
# Limited: draws a purge line every print and you dont have to worry about accidentally leaving the purgelines on the bed because the print will not start once the purge_sections_amount is full.
# !! for the Limited mode you need CHECK_PURGES somewhere before the SEQUENTIAL_PURGE command in your PRINT_START macro. Preferably before your printer heats up so you don't waste the heating time. 
# !! when the purge section is full you can use RESET_PURGES to clear the system and start at the first purge section on your next print.

# set this to True if you want continuous, and to false if you want limited
# default is True
variable_continuous: True

# this is only...

Here you can configure the settings for the macro. The most important setting is variable_continuous. With this you can select what mode you want to use. For continuous you have to set variable_continuous to True.

After making any changes in the config you will need to restart the firmware by using FIRMWARE_RESTART

Configuration

Setting Description Input Default
variable_continuous Setting for setting the mode you want to use. True (Continuous)
False (Limited)		 True
variable_stop_print_on_warning This is only needed on limited mode. This will stop the print if the purge section is full, if this is set to false it will echo a message to console instead of aborting the print.
This will also automatically reset the purges and continue printing. Use at your own risk.		 True
False		 False
variable_warning_time Time user has to remove purges 0 to 3600 30
variable_x_purge_offset The distance the purge line is away from the bed in X on both sides. This will only (haven't tested this on any other printers) work on configurations where the 0,0 point is on the left bottom corner of the bed. 0 to 100 10
variable_y_purge_offset The distance the purge line is away from the bed in Y. This will only (haven't tested this on any other printers) work on configurations where the 0,0 point is on the left bottom corner of the bed. 0 to 100 3
variable_purge_sections_amount The amount of purge sections in the line. 0 to 20 5
variable_purge_height The distance from the bed for the purge line. Any number above 0 0.4
variable_flow_rate Flow rate for the purge line, many put this as their hotend flow limit. Any number above 0 12
variable_purge_amount Amount of filament purged. Any number above 0 80
variable_tip_distance The distance between the tip of the filament and the nozzle before purging, should be similar to the final retract amount specified in PRINT_END. Any number above 0 10
variable_purge_line_end_overlap Specifies the overlap of the purge line with the next purge line in percentage. Percentage from 0 to 100 50
min_temp_extrude temperature where filament can be extruder, will error below this temp. Temperature in Celcius 180

Macros in config

This package contain's 3 macros: SEQUENTIAL_PURGE, CHECK_PURGES and RESET_PURGES.

For continuous mode you only need SEQUENTIAL_PURGE. With the limited mode you need all 3 the macros.

Here's how your PRINT_START would look for both of them.

Continuous

Home printer
Heat printer
(more print start stuff)
SEQUENTIAL_PURGE

In the continuous mode you can just replace your purge with the SEQUENTIAL_PURGE command.

Limited

CHECK_PURGES
Home printer
Heat printer
(more print start stuff)
SEQUENTIAL_PURGE

For the limited mode it's a little different, here you check if the purge section is full before the print start's so you don't heat the printer up to find out there's still purges.

Usage (only when using limited mode)

When your purge section is full and you try to start a print, you'll notice you can't. This is because your printer knows the purge section is full and you'll have to remove all the purge lines and use the RESET_PURGES command to let the printer know you've removed all purges. Now you can start a print again and be happily ever after.

Technical info

Here is a flowchart on how the macro performs.

flowchart TD
    A[SEQUENTIAL_PURGE] --> 
    B[Get settings] --> 
    C[Calculate]--> 
    D[Divide the full purge section in multiple \n sections with the given purge_sections_amount] -->
    E[Calculate the section_index, which \nrepresents which section the current purge falls\n into based on the purge_index and the \nnumber of purge_sections_amount]--> 
    F[Get the first coordinate of the purge line]--> 
    G[Get the last coordinate of the purge line]--> 
    H[Continuous or Limited?]
    H --> |Continuous|I[Make Purgeline in given section] --> A
    H --> |Limited|J[Make Purgeline in given section] --> K[End macro. Aka start print]
Loading

Uninstalling

That's unfortunate, is the macro not working for you? If you're having trouble you can eihter send me direct message on Discord @ danni_design or ping me in the KevinAkaSam's sandbox server.

If you really wish to uninstall this macro you can do so by running these commands in your SSH terminal of choice:

cd
rm -rf Kevins-Awesome-Macros
rm printer_data/config/KAM-settings.cfg
rm printer_data/config/KAM

And remove the following from your printer.cfg

[include KAM-settings.cfg]

Troubleshooting

I'm getting an error about save_variables!

This happens because the macro already includes the `save_variable` section. To fix this remove the section in a place that is not sequential_purge.cfg.
I'm getting the error `Error evaluating 'gcode_macro sequential_purge :gcode': jinja2.exceptions.UndefinedError:'dict object' has no attribute 'purge_index'`

This error is caused by running an older version of Klipper, to resolve this either update your system or run RESET_PURGES.

Credits

Huge thanks to Kyleisah for the amazing work on KAMP and for the inspiration for this macro.