Nozzle scrubber and purge not working

[Snechovski]

Hello everyone, so I recently put a klicky on my voron 2.4 and added the purge bucket and scrub brush. My klicky works good and the printer works good except the purge and scrub don't work. I'm using fluidd and I've added all config files like it says to do. If I press the clean nozzle in fluidd it works it just don't work when I go to print something. Also when I go to print a file the machine homes all axis does the klicky on the gantry parks the klicky and homes the xyz two more times in a row and goes right to printing it does nothing with the purge and scrub. So the question is why isn't purge and scrub working with the print and why does it home xyz so much? Thanks for your help. 

[SteveThatcher]

I am working on my own build and will be using the purge bucket setup. I will be interested to hear how the problem gets resolved.

[Snechovski]

good luck with your build its a lot of fun and rewarding!

[SteveThatcher]

38 minutes ago, Snechovski said:

good luck with your build its a lot of fun and rewarding!

hopefully it won't involve luck... LOL

[Snechovski]

[GarthSnyder]

@Snechovski, did you add nozzle-scrubbing commands to your startup G-code?

[Snechovski]

Do you mean this one,

[include /home/pi/klipper_config/nozzle_scrub.cfg] 

If so I tried it everywhere in macros in print start everywhere the instructions say and still nothing. 

[GarthSnyder]

That's not the start G-code, those are just the macros to to implement CLEAN_NOZZLE et al. You still have to run CLEAN_NOZZLE from somewhere.

[claudermilk]

You have to call CLEAN_NOZZLE in your PRINT_START macro.

[Snechovski]

hi and thanks for the post thats what im having trouble figuring out

[claudermilk]

Just put in a call to the macro and it will work.

Right now I have it home if needed, warm up, do z_tilt_adjust, then clean the nozzle, Klicky calibrate_z, then print.

 

 

[Snechovski]

do you have a example of yours i can look at?

[claudermilk]

Sure. It's still very much WIP, but it works.

[gcode_macro PRINT_START]
gcode:
    # Parameters
    {% set bedtemp = params.BED|default(60)|int %}
    {% set hotendtemp = params.HOTEND|default(215)|int %}
    {% set chambertemp = params.CHAMBER|default(0)|int %}

    _CG28                    ; only home if not already done
    G90                      ; set to absolute
    G0 X125 Y240 Z30 F3600
    M117 Warming up...
    STATUS_HEATING
    CASELIGHT_WARMING
    M190 S{bedtemp}                                                                  ; set & wait for bed temp
    #TEMPERATURE_WAIT SENSOR="temperature_sensor chamber_temp" MINIMUM={chambertemp}  ; wait for chamber temp
    M109 S{hotendtemp}       ; set & wait for hotend temp
    ATTACH_PROBE_LOCK        ; Attach the probe and force it to stay
    Z_TILT_ADJUST
    # Do bed mesh here?
    #M117 Cleaning...
    CLEAN_NOZZLE 
    #G1 E-1.0 F3600           ; retract so no drool
    CALIBRATE_Z              ; instead of another z home, get actual z offset from probe
    DOCK_PROBE_UNLOCK        ; dock the probe and unlock
    M117
    G1 E6.0 F3600            ; extrude 6mm to account for clean_nozzle retraction
    #do purge line here
    STATUS_PRINTING
    CASELIGHT_PRINTING

 

[Snechovski]

now do you have this in your printer.cfg or are you making a call for it 

[claudermilk]

Which? PRINT_START or NOZZLE_SCRUB?

I'm already breaking things out and taking advantage of the include command. So PRINT_START currently live in a macros.cfg file and NOZZLE_SCRUB lives in nozzle_scrub.cfg. In printer.cfg, I have these two lines which makes it as if they were all in one file:

[include macros.cfg]               # for custom macro definitions
[include nozzle_scrub.cfg]         # Nozzle Scrub & Purge Bucket

 

[Snechovski]

yeah thats what i meant ill work on this for a bit thanks a bunch

[Snechovski]

i think im finaly getting it, i got it to scrub and purge but ive used a little of everyones config files so now i have to tune but at least you helped me figure out what i wasnt doing thank you again claudermilk.

[Snechovski]

one more question, so when i add the call lines does it matter what ones i do first like, [include ./nozzle_scrub.cfg] first then [include ./print_start.cfg] second or the other way around. what im asking is will it call in the order i put it?

[Snechovski]

got er figured out thanks a bunch..

[Demosth]

2 hours ago, Snechovski said:

got er figured out thanks a bunch..

What was your issue resolution -  to provide insight for anyone else who might have the same question!

[Snechovski]

Basically I went off of what claudermilk showed me and I went to github.com and just took some config files and made them into my own that's about it. Other than claudermilk showing me some kind of direction all the other replies we're basically what I already knew. 

[claudermilk]

23 hours ago, Snechovski said:

one more question, so when i add the call lines does it matter what ones i do first like, [include ./nozzle_scrub.cfg] first then [include ./print_start.cfg] second or the other way around. what im asking is will it call in the order i put it?

Just as a quick answer to this for others' future reference, it doesn't matter what order the includes are in. The effect is that all the separate files are handled by Klipper as if they are all one giant, monolithic file. Order of macros appearing in the files doesn't matter than I have seen.

[Snechovski]

thanks again claudermilk !

[Nysios3000]

Hey guys, my i just installt the scrubber, but the nozzle is 20mm to high. so it does not scrub the nozzle. But in the macro i can't find a Z-high for the scrubbing?

Can i just add a z-High or did i missed a part ?

 

Thanks

[claudermilk]

I've heavily reworked mine now, but IIRC you need to update the variable_brush_top value at about line 53.