bed crashed priming tower into print head after filament change | ArmoredTurtle 3D | Page 1

quaint tree Apr 18, 2026, 5:01 PM

#

I cannot for the life of me figure out where the setting is that is making my bed run back up into my print head. This is on a Mercury One.1

frank willowBOT Apr 18, 2026, 5:01 PM

#

<@&1304550334839918672>

torpid crow Apr 18, 2026, 5:31 PM

#

During what operation?

quaint tree Apr 18, 2026, 5:32 PM

#

it happens between the two nozel brush passes

#

I have all the z moves in _afc_brush_vars set to -1

#

torpid crow Apr 18, 2026, 5:37 PM

#

What about z for poop or for park?

#

Also maybe easier to just have you run debug so we can see your settings

frank willowBOT Apr 18, 2026, 5:37 PM

#

@quaint tree, please run this debugging script when not printing and post the resulting link in chat.

Troubleshooting - Armored Turtle Documentation

Armored Turtle Project Documentation

quaint tree Apr 18, 2026, 5:39 PM

#

#

https://termbin.com/rvl3

torpid crow Apr 18, 2026, 7:37 PM

#

Ok, I'm just going through everything and I'll just make observations as I go

#

For one thing, your kick Z has to be set to something > 0, or it defaults to 0.5

#

This is a Z above the bed for kick

#

the sequence it does it cut -> park -> unload -> load -> poop -> wipe -> kick -> wipe -> continue

#

so if you say it is something weird between two wipe passes, it could be the kick

#

also z_after_kick should be a bigger number. After it finishes the kick, it goes to this height

#

and this doesn't have a check, it'll go to -1 in your case, so this could be your problem

quaint tree Apr 18, 2026, 7:41 PM

#

even if my bed moves z and the poop tray never changes relitve to the gantry?

torpid crow Apr 18, 2026, 7:42 PM

#

Even if what? If you have kick enabled (which you do) it will try to do the kick routine as you've programmed it to do

quaint tree Apr 18, 2026, 7:43 PM

#

so my bed moves z but my poop tray and brush are mounted to the printer frame. the z relationship between print head and tray never change

torpid crow Apr 18, 2026, 7:44 PM

#

If you have kick enabled, it will always move Z

#

If you need kick to work a different way you need to customize the macro

#

The kick_start_loc also moves z to the location in there, you've also got that at -1

quaint tree Apr 18, 2026, 7:46 PM

#

I thought -1 was a overide or dont move place marker

#

it is in the brush section

torpid crow Apr 18, 2026, 7:46 PM

#

In some places it is, but doesn't look like kick. I suggest you just read the macro

quaint tree Apr 18, 2026, 7:47 PM

#

" # Position of the center of the brush (Set z to -1 if you dont want a z move)"

torpid crow Apr 18, 2026, 7:48 PM

#

  G1 Z{kick_start_z} F{z_travel_speed}
...
  {% if kick_z > 0 %}
    G1 Z{kick_z} F{z_travel_speed}
  {% else %}
    RESPOND TYPE=command MSG='AFC-KICK: kick_z value to low. Please adjust in AFC_Macro_Vars.cfg. Defaulting to 0.5mm z-height'
    G1 Z0.5 F{z_travel_speed}
  {% endif %}
...
  G1 Z{z_after_kick} F{z_travel_speed}

quaint tree Apr 18, 2026, 7:48 PM

#

torpid crow In some places it is, but doesn't look like kick. I suggest you just read the ma...

so the one thing I will add is, before I had a issue with the host memory card, I didnt have this problem but ever since I got the printer back on line, it now crashes into the print inbetween nozzle brushings

torpid crow Apr 18, 2026, 7:48 PM

#

These are your z moves in the kick macro

#

Did you have kick enabled before?

quaint tree Apr 18, 2026, 7:48 PM

#

yes

torpid crow Apr 18, 2026, 7:48 PM

#

Or did you customize the macro?

quaint tree Apr 18, 2026, 7:48 PM

#

no

torpid crow Apr 18, 2026, 7:48 PM

#

I don't know what to tell you

quaint tree Apr 18, 2026, 7:49 PM

#

thats fair

torpid crow Apr 18, 2026, 7:49 PM

#

This is the way the macro is written, just gotta work with it. Maybe you can try to disable it to make sure we're on the right track

quaint tree Apr 18, 2026, 7:49 PM

#

all the settings you sited, were as you suggest, this morning. I changed them today trying to solve the issue

#

ok\

#

thats a good idea, disable kick to verify it is were the problem lies

#

that is intgeresting since the bed doesnt move until the nozzle is being cleaned

torpid crow Apr 18, 2026, 7:53 PM

#

let me read through the wipe routines real quick

quaint tree Apr 18, 2026, 7:53 PM

#

it also says this in the macro vars: "variable_z_purge_move : False # Set to False to not move in Z during poop"

torpid crow Apr 18, 2026, 7:53 PM

#

z_move = -1 is right here

quaint tree Apr 18, 2026, 7:53 PM

#

I changed it back

torpid crow Apr 18, 2026, 7:54 PM

#

z_purge_move is for poop

#

# Move in Z after brush to avoid bed if brush is at Z0 (Set z to -1 if you dont want a z move)
variable_z_move                   : -1

#

that's good, the brush has this logic:

{% if z_move >= 0 %}
      {% if verbose > 1 %}
        RESPOND TYPE=command MSG='AFC_Brush: Finish z_move.'
      {% endif %}
      G91
      G1 Z{z_move} F{z_travel_speed}
      G90
    {% endif %}

#

so if you're -1 it won't move, which is what you want for a gantry brush

quaint tree Apr 18, 2026, 7:55 PM

#

right, that is where I got the missguided idea to add -1 to the poop vars

torpid crow Apr 18, 2026, 7:55 PM

#

We haven't talked about poop yet

#

but -1 isn't handled in kick

#

variable_brush_loc                : -22,17,-1  # Position of the center of the brush (Set z to -1 if you dont want a z move)

this is right

quaint tree Apr 18, 2026, 7:56 PM

#

oh right, i got crossed up with kick

#

sorry

torpid crow Apr 18, 2026, 7:56 PM

#

nw, there's a lot to keep track of, and I just wanna make sure we're on the same page

quaint tree Apr 18, 2026, 7:56 PM

#

I totally understand

#

I was crossed up for a second

torpid crow Apr 18, 2026, 7:57 PM

#

ok z in poop is controlled by the z_purge_move, which you have False

quaint tree Apr 18, 2026, 7:58 PM

#

and that should mean it does not move the "Z" correct?

torpid crow Apr 18, 2026, 7:58 PM

#

Except for one part...

#

Oh nvm

#

Yeah, so if that's False there should be no z movement in poop at all

#

Is that what you want, and consistent with your observations?

quaint tree Apr 18, 2026, 7:59 PM

#

ok so poop is prob not the issue

torpid crow Apr 18, 2026, 7:59 PM

#

I don't think it is

#

so yeah, set the -1's in brush, and disable kick, see where you stand

quaint tree Apr 18, 2026, 8:00 PM

#

I do not want any z movement durring cut/clean/poop/ wipe besides an anitial z hop before moving from the print

torpid crow Apr 18, 2026, 8:01 PM

#

Oh I guess I should check park then too

quaint tree Apr 18, 2026, 8:01 PM

#

none of those actions need movement from the bed to work and any movement down, could resault in a crash

torpid crow Apr 18, 2026, 8:02 PM

#

the park logic:

  {% if park_z > 0 and park_z < z_safe %}
  G1 Z{park_z} F{z_travel_speed}
  {% endif %}

#

so 0 for park is right

quaint tree Apr 18, 2026, 8:03 PM

#

ok good

torpid crow Apr 18, 2026, 8:03 PM

#

Your z_hop here:

#--=================================================================================-
#------- Pause/Resume ---------------------------------------------------------------
#--=================================================================================-
z_hop: 5                        # Height to move up before and after a tool change completes

is the initial one

quaint tree Apr 18, 2026, 8:03 PM

#

perfect

#

I just hope I can find what is introducing this unwanted z movement.

torpid crow Apr 18, 2026, 8:04 PM

#

Well, let's find out. Right now it seems to be the most obvious cause

#

Everything else on the surface at least seems ok

quaint tree Apr 18, 2026, 8:04 PM

#

when it happens, no mater how many layers the print is currently at, it always bring the nozzle down to almost touching the bed

#

Thank you for your time. I will disable kick and see what I get

torpid crow Apr 18, 2026, 8:06 PM

#

post back, if thisn't it we'll keep looking. what you want to do will be possible one way or another

#

I think we'll have to customize kick though, I just don't see how it could work as written

quaint tree Apr 18, 2026, 8:07 PM

#

Your awsome. Ill let you know

#

im good at hardware but not so much with software

torpid crow Apr 18, 2026, 8:08 PM

#

You happen to have a backup of your old installation configs?

quaint tree Apr 18, 2026, 8:10 PM

#

I was missing some, hence all of my issues now. It happened last year and I got so frustrated, I didn't come back to it until this week. This was once my favorite machine

torpid crow Apr 18, 2026, 8:10 PM

#

if you have config/macros/Kick.cfg from your old installation, post it here

quaint tree Apr 18, 2026, 8:11 PM

#

I have to assume I dont have the final version because the ones I have on this machine, are the only ones I found

#

Trust me, I have saves of it this config now

torpid crow Apr 18, 2026, 8:12 PM

#

ok, just wondering

quaint tree Apr 18, 2026, 8:12 PM

#

I really wish I did. it had all kinds of things I had honed to perfection

#

I'm still running Kicky but I want to convert to eddy. Im not gonna crack that egg until this is sorted

torpid crow Apr 18, 2026, 8:15 PM

#

good call. When you do maybe you'll find a beacon or carto inside!

quaint tree Apr 18, 2026, 9:23 PM

#

nice dad joke

quaint tree Apr 19, 2026, 12:24 AM

#

It looks like your right. The kick macro was the issue. I must me wrong that I was using it before.

torpid crow Apr 19, 2026, 2:07 AM

#

quaint tree It looks like your right. The kick macro was the issue. I must me wrong that I w...

I dunno what your poop situation is like then, do you need kick or no?

#bed crashed priming tower into print head after filament change