So far so good with klipper. I just sat down and learned a bunch.
I think I found what to do for the Z being at max at boot, Configuration reference - Klipper documentation so that way the bed doesn’t try to move out of the way (more positive).
1 Like
zhop is set at 10 mm in my system and that is the pre-home lower that makes noise when the bed is at the bottom. I don’t know how to have it only zhop when the system is rehoming from a known position.
Perhaps that would be the G28 homing override command…
when z is unknown then don’t z hop, but if z < 300 then zhop +10
because if at 0, the BLTouch probe won’t deploy fully. Not sure how to implement that in the printer.cfg, but I’ll get to it at some point.
I have a homing override on mine, and I still haven’t gotten it quite right.
I added the homing override when I installed the KlackEnder on my Ender 3 Pro
If you don’t specify any axes, then it always runs. So you then no longer have the ability to home an individual axis. This is the state I’m currently in.
if you specify:
axes: z
then it will only run when you home Z. The issue with that is that it will run with G28 Z0 as well as G28 by itself. Also, you can only have 1 homing override defined, so you can’t have one for Z and then another for X and another for Y to try to get around this.
It seems the expectation is that once you override homing, you always home everything.
I’ve been looking into it a little while I’m out of town, but I don’t have any way to test anything right now…
It looks like you might be able to do some parameter parsing, but I don’t know if the config language is smart enough to do what I want it to.
I know you can add custom parameters and check for them, but I’m not sure if it’s possible to write an override smart enough to pick the correct axes to home in a combinations.
you can do something like this…
[homing_override]
axes: z
set_position_z:0 # Make printer think Z axis is at zero, so we can force a move upwards away from build plate
gcode:
G90
G1 Z10 F3000 ; move up to prevent accidentally scratching build plate
{% if "x" not in (printer.toolhead.homed_axes | lower) %}
G28 X
{% endif %}
{% if "y" not in (printer.toolhead.homed_axes | lower) %}
G28 Y #Will only home XY if they are not currently homed
{% endif %}
G28 Z
And then it will only home X and Y if they are not already homed, but even that might be a little restrictive and not allow you to home X without cycling power or something if you accidentally manually moved it or something
There also may be some way using
{% if "X0" in params %}
G28 X0
{% endif %}
but there’s a lot of combinations, etc, and I don’t know the extent of what’s possible in there yet.
I’ll have to work on it when I get back in town if no one here has a solution already
1 Like
you would have to use the information about the system in a command similar to this
{% if "z" in (printer.toolhead.homed_axes) %}
and likely there is a way to get it’s current position as well
or something like that… still a Klipper noob.
1 Like
Okay, over thinking this one, turned off Z Hop on safe home.
XY homing fine, Setting Z stepper and probe positions…soooooo soo so close now.
2 Likes
Post your config when you get it figured out. I’m very curious to see how you get it worked out!!! Glad it’s going well and you’re learning a lot. I think you will really like it in the end. I know for me it’s so much easier than marlin lol
2 Likes
DUDE
2 Likes
WHAT???
1 Like
I’m having fun now.
1 Like
so enough with the fun. can you hurry up already, I want to try Vern (the mpcnc) on a piece of aluminum to go v4 → v5 … ? (not totally serious about the hurry) Ernest (v4) is cranking trucks again since I got more blue now:
the last truck attempt ran out at 55% (smart filament sensor saved the day… again) and the only other PLA I had wasn’t the right color - BUT IT WORKED!!
I keep getting text errors for filament setting macro on startup, but the thing works, so I’m leaving it for now along with that other one I always dismiss, but it doesn’t seem to matter yet.
The point to this message was that I have 3 klipper issues that are still unresolved:
- text error with variable setting when sfs triggers pause. yet it works and resumes
- another variable issue with a string value - I forget, but not a showstopper.
- the z belt grinding on startup. This is the one I really want to fix, but not at the cost of operation right now. Leave the motors on and it isn’t an issue.
1 Like
I think it is safe to say they are good to go. The only parts that change by size are the bed mounts, so make sure you set your build size before you export the DXF’s, I also included a stepper location sketch.
get rid of Z hop Mine don’t grind anymore. That happened twice and I stopped what I was doing to figure it out.
My config…lots of tuning to do. so this changes often.
ryancfg.zip (1.6 KB)
Oh…and I have a tungsten carbide nozzle coming. $40…harder than hardened steel and nearly the same conductivity as brass. West3D. Hope it gets here by the time I am ready to print.
3 Likes
Is that for the CF or the nylon or the PC?
CF, Also I have never changed a brass nozzle since I went to 0.5mm. Kinda wondering if I have worn any of mine out. So longevity and no fear of any material. I can experiment without killing a farm bot.
2 Likes
Okay, I tried to upload a gcode file, with only 3 small ones in the system. I am out of space. Uploads error out. I am doing a search by file size to try and find something suspicious.
Is there a trash can to empty or something?
I used winSCP searched the entire file system and sorted by size, nothing out of the ordinary.
Sorted by date, I expected thousands of files, there are a lot today but all tiny.
This sounds like you don’t have permission to save the file. I just had the same issue… There was an error in the printer.cfg file for the virtual SD location and it refused to upload.
I can’t even save a config change. (it does look correct, though).
I deleted a bunch of other files, and the free space does not increase.
REboot, power down wait, power up. Nothing
Well the new nozzle is here but I can not print.
I backed up my config, should I load up a new SD card?
1 Like