I just installed a klicky probe. After getting the settings and macros i needed to get it to function i've the move out of range error. Can any walk me through it? that way i know what to do in the future. I'll post my printer.cfg as well. i have all the klackender cfgs seperate. i can upload if need me. Thanks.
#Move out or range when trying to home//bed_mesh_calibrate
grim wing
polar shale
normally with a klicky setup you use z_offset: 0 for the probe section could that maybe be causing problems? I see yours is set to like -3. Also not familiar with klackender at all so not sure how it may differ from default klicky.
grim wing
normally with a klicky setup you use `z_offset: 0` for the probe section could t...
i'll set to 0 and see what it does. thanks.
still the same outcome. those numbers, 245, -8, 10 and 0. do those refer to XYZ? not sure about 0. Maybe E?
polar shale
oh yeah youre right. That would be xyz I conflated things in my head. Too much CAD on the wrong plane this week.
So lets get some more context. When exactly does this happen? After home but before mesh, after attaching probe, before homing?
Also, do you try to use the klicky probe as your Z endstop?
grim wing
at first i couldn't get through due to "unknown chip name 'probe'". so i deleted all klack cgs i had and uploaded them one by one to see which one is giving me that error. and it turned out to be SCREWS_TILT_CALCULATE whic made no sense because there was nothing in cfg stating "probe". but it went through. i was able to home, did z offset and min/max bed mesh with the offsets already saved. i was able to do all that but i couldn't execute BED_MESH_CALIBRATE or AUTO BED MESH because it would throw me the move out of range error. tried to play with the coordinates and now i can't even home.
i'm rather new to klipper but most of is self explanatory but it gets messy sometimes. i searched on reddit, git hub and they all had different outcomes.
polar shale
okay cool cool.
so First things first with that new information. I think you dropped a 0 off your X max point as its currently configured as only 24mm
polar shale
haha. So lets get that one fixed and then see where you most likely still break since you mentioned it broke before you started messing with things
grim wing
can't believe i missed that. probably after messing with all the endstop numbers
polar shale
most likely
grim wing
it's homing now. i'll see if it will do auto mesh.
is there specific macro to use? because on the klacker github, they had thier own macro which is practically the same.
new error for bed_mesh_calibrate
and 245 is too much. gonna baby step it to get the right movement to the end of the gantry
polar shale
so the one provided by klacker is just a re-make of the default one. So what it does is attatches the probe, then centers, then runs the base bed_mesh_calibrate macro and docks the probe. since klipper doesnt natively have a way to support detatchable probes
Does it fail before or after attaching the probe
grim wing
no. it does it's thing. picks up the probe, goes to the center and probes, drops it off and homes X.
polar shale
wait what? So it homes, grabs the probe, centers, probes the mesh, docks the probe, homes X, and then throws that most recent failure?
if so that could be a good thing because gives a good pointer to what could be next
grim wing
oh that part. sort of. when it homes, it does exactly what it's suppose to do. when i send the command for a bed mesh calibration, it picks up the probe, goes to the center and fails
polar shale
Ah okay that makes a lot more sense
and your probe is in front of the nozzle and a little to the right correct?
grim wing
it's behind it. i'll send a vid
polar shale
Oh behind it? That would be weird based on the config but could make sense with the error potentially.
grim wing
now it failed again during homing. strange
polar shale
hmmm what is it saying now?
I know its probably a similar error but this behaviour is being odd so want as much info as we can get
grim wing
same error move out of range. 245, -8, 10, 0
polar shale
okay. What did you change your max X to?
grim wing
240.5 because 245 was slamming
polar shale
hmm okay. So now that raises the quesiton where is it getting 245 from
grim wing
and 240 is just kissing the dock
polar shale
wait...you mean the probe's dock? Is the probe currently on the print head?
grim wing
no. it's stationed
polar shale
Okay
grim wing
i'll try to change the position min since they're in the negative. probably offsets it and doesnt actually get the 240
polar shale
hold on
So in this setup you have your Z endstop as the probe, which means to home Z it has to attach the probe. Right now I bet your klacky config file has the probe's dock position set to x=245, since you changed the X max to be 240.5 when it tries to grab the probe it is told to move outside its range which would be a problem
Could you share your klacky related cfg files?
grim wing
i can send you all the seperate cfgs for it. so you can skim through them and see what you find
lol
didnt read the last part
polar shale
Yeah. Specifically the ones from your machine though not their repo
that is exactly my plan
grim wing
according the kevinakasam these are compatible for the E3V2. that's why i got these cfgs
main file from his github
this one i have commented out since for some reason it throws "unkown chip name 'probe' error
brb, taking the dogs out for a bit
polar shale
cool Ill give a parooze
Okay first thing I see is that your probe in the variables file is the variable_docklocation_x is 241 which is larger than your 240.5 maximum X value. So either need to up your xMax or lower that value. But that is an asside and not the root of the problem
Heres what I am seeing step by step though to help you learn hopefully.
In klackender.cfg line 58 there is the definition of the [homing_override] which will be used when homing so we start looking there.
Here we see it runs a bit of homing gcode which is normal followed by a call of PROBE_OUT which isnt a default klipper macro so lets see what it is.
Line 111 is its definition
And it gets put into absolute positioning then runs a move to X245. Bingo we have our 245 breakage. This is repeated in PROBE_IN a few lines down.
What I fail to understand though is you have a variables file where you define the X position of the probe and then the probe in and out commands are hard coded to use a specific value rather than calling those variables.
Actually these files feel like they werent written together. is the klackender.cfg something that came from the same repo as the other klack-* files? Because based on the data held in them I kinda feel like they came from different sources.
Also if you would like to chat on voice about any of this to help teach im sure it could be arranged
grim wing
it's 2 different sources. the klackender.cfg came from Kevin himself. the other klack files came from another source that people on reddit say it helped them.
grim wing
so on probe out/in change to 240?
polar shale
well hold on
We have to make a decision. Do you want to use the klackender or klack-* setup. Because having both enabled is redundant, leaves room for interference breakage, and is just confusing
then we can go through fixing whichever one is relevant
grim wing
i can just comment them out on the printer.cfg and go with kevin's and see if that works
polar shale
the klack-* is closer to vanilla klicky but both have similar functions just defined differently
so commenting either one will still break just for different reasons
just dont want you running conflicting configs
so yeah you can comment out whichever one you dont want to use in the printer.cfg and we can start fixing values in the used one
grim wing
i'm the guy that does that. watch to many tutorials and i like what they put on their and i add to mine. ha. i was same way with jyers and mrisco firmwares. i was always screwing something up
polar shale
yep that makes sense. So just comment out klacky- and we will work on kevin's
Which yes the first fix is going to be to change those 245's to 240 since you said 240 kisses the dock. Though there is some other cleanup I would like to do as well
grim wing
yeah. i did before changing and it gave me the error. changed it to 240 and it homed
polar shale
perfect. I assume it still doesnt mesh?
actually if it still doesnt mesh ill be a little surprised
Because I bet your conflicting configs were causing problems
grim wing
gimme a minute. having magnet issues ha
grim wing
is F20000 too fast? throws the probe out of it's dock
polar shale
Yeah I would keep it around 6000
at least for now
lets get it functioning then you can play speed demon if you want once we know it works at slower speeds
grim wing
yeah, it wont mesh. range values -6.5, -12, 5, 0
my hotend keeps knocking down the probe.
polar shale
huh the nozzle shouldnt really be knocking into anything.
okay so lets work backwards a bit
its trying to go to y=-12 for some reason when meshing lets figure out why
grim wing
it's the probe carrier that's behind my toolhead. when i manually move it to the dock, it slides right in with no effort. it's a different story when it's doing it on its ow
own
polar shale
oh interesting. like its hitting it too agressively? or maybe over shooting it a bit
grim wing
no. it's traveling rather smooth but still fumbles it.
polar shale
hmm im not sure then. I didnt even know there was a klicky mod for the ender before this convo so not sure what might be causing that part
grim wing
Dropped it down to F4500. Seems to work
polar shale
ohh interesting setup
yeah your magnets might just be too weak for higher speeds
what command are you runnign to try the mesh
grim wing
on the macros panel, i have AUTO BED MESH
polar shale
cool
grim wing
but i can send BED_MESH_CALIBRATE and does the same
polar shale
I wouldnt use BED_MESH_CALIBRATE for right now
because that will actually probably break regardless of the out of range moves because it wont grab the probe
for our purposes use either AUTO_BED_MESH or G29
grim wing
i got G29 on the macros panel as well
polar shale
yep both that and auto_bed_mesh are the same thing effectively. They run the same code just multiple aliases
grim wing
gotcha. was wondering why those 2 are mentioned together and not the other one
polar shale
I have an answer but want to step through my thoughts first.
polar shale
gotcha. was wondering why those 2 are mentioned together and not the other one
the other one is the default klipper mesh
which gets called by those two but not until after grabbing the probe
So for example. This is all the Auto mesh is doing
[gcode_macro AUTO_BED_MESH]
gcode:
PROBE_OUT
BED_MESH_CALIBRATE
PROBE_IN
So based on the fact that we are able to home I assume this also picks up the probe without issue.
Which then means we need to investigate the BED_MESH_CALIBRATE section
So this has no definition in your configs because it is a default klipper command baked into the base package. Thats fine.
But we have to look at what it is being passed.
So we know from the error that the bad value is y=-12
so we have to find what could cause a -12 point in space to try to be called
Bed_MESH_CALIBRATE will make a grid based off of your bed_mesh section and then offset by your configured probe offset values.
However, this is where things start getting complicated because you have a bed_mesh in both printer and klackender, and then both have probe sections BUT the klackender one is called mcu_probe instead of probe
so if we take klackender for an example
Your bed mesh has a yMin of 30
and your mcu_probe has a y_offset of 21 indicating that the probe is 21mm behind the nozzle. So when the nozzle is at 0 the probe is at 21,
Or conversely if we want to probe the point y=30 then the nozzle needs to be 21 less than that or 9. Which we can see is not a problematic value
So then we take printer.cfg for the example. If I need to pause let me know
grim wing
i was literally just looking at both bed meshes and both have different values. so, i comment out the one in my printer.cfg. doesnt matter which it's being used.
polar shale
right. So the printer.cfg one was:
Mesh of yMin = 9
Offset of y -17
So any time the nozzle is at 0 the probe is at -17 or conversely if the probe needs to hit y=9 then the nozzle would be 17 above that or 26
grim wing
this is refreshing knowledge. just by this, i know what to look for kinda if i'm in a bind again.
polar shale
Exactly
So we know it isnt using both values from the same config. Which makes sense since the probe sections are named differently. However, if we take the mesh from printer.cfg and the probe from klack
Mesh min 9
Offset 21
Then for the probe to hit y 9 the nozzle would have to be at, you guessed it -12
so yeah commenting out the bed_mesh from the printer.cfg should fix the problem
The why behind it gets a bit funky because it has to do with how klipper loads its macros. It loads them top down. So it reads pritner.cfg which tells it to go load the klack config, that config defines a [bed_mesh], then it goes back to reading printer.cfg after that line and hits a new [bed_mesh] section overwriting what it previously had
I unfortunately cant tell you why its using mcu_probe instead of probe because my knowledge doesnt go deep enough to see what is causing that swap other than maybe its hitting the first probe type section and using it even though it isnt named 'probe'
If you have any questions about this whole endeavor please feel free to ask. I love when I can teach someone a solution rather than just give one time data
grim wing
oh mcu_probe? i changed that maybe like a few minutes before i sent the files here. it's back to just probe.
my bad
polar shale
AHHHHHH
okay.
so I would comment out the probe section in printer.cfg as well then
grim wing
yeah, someone one discord mentioned to someone else to add mcu before the probe and apparently it worked for him but not me
polar shale
ahh interesting
grim wing
the probe section came from klackender.cfg. i was told add it to the main cfg for some reason. that's why it's there
polar shale
Okay. In that case make it match what you have in klackender
because having 2 of the same section that differ is just a recipe for disaster
if its duplicated but matches then no harm no foul, if its duplicated and different then you get into messy situations
polar shale
yay!
polar shale
well.... did it crash on the far back line of probes? And did you make the probe sections match each other
grim wing
it was more like a silent crash. on the front side
polar shale
oh on the front? that I didnt expect
grim wing
Looked like it wanted to move some more
polar shale
ahh okay.
grim wing
luckily i saved the min/max bed mesh already. put everything default on the klackender.cfg to see what was triggering those errors. i think it's safe to put them back
polar shale
yep safe to put those back
grim wing
same with my x and y min endstops. they're like -10 and -8. i'll just put them at 0s
polar shale
well dont necessarily change those blindly to 0
check and see where they actually are because they may actually be endstops in the negative
grim wing
oh no. gonna do the whole thing again with the offsets
polar shale
yeah thats the thing to. If you change your position_endstop values youll have to redo almost all of your XY coordinates for like the probe dock and mesh values
because it will change where your max values are
grim wing
dammmmit
polar shale
yeah thats why those are one of the first things you configure haha
because they are the foundation for everything else
grim wing
i did all of that and then i started getting the errors. but at least i'm only looking at 1 klack cfg and not 5 of them.
polar shale
haha yeah
so when you did them before, you measured that x was -8 and y was -10 for your endstops?
If so then its fine to leave those values in
grim wing
no. dude from modbot said to put those since we're both have the micro swiss ha
polar shale
ahh gotcha. Yeah if those arent your measured values then you dont want them
but I think from here you have a good grasp on what you are doing. At least better than before lol
grim wing
yeah, i had my bl touch cgf profile before the klicky probe. it worked like a charm for the past 2 months since i got klipper. just this one is different since the probe is in the back and the probe to nozzle offset is stupid
polar shale
mmhm
haha
its a different beast indeed
but im glad we could get some root causes broken down and fixed
grim wing
yes. i appreciate your time for helping me. it's funny because i'm a volunteer on a different discord. i help other with their printers but can't help them with klipper. still learning the ropes.
polar shale
haha yeah klipper takes some adjusting. Well I am off to bed. If you have more questions feel free to ping me.
grim wing
thanks. but dont think i'll be doing that. but if i'm in another big one, i'll hit you up for sure.
grim wing
haha yeah klipper takes some adjusting. Well I am off to bed. If you have more q...
well, going back to the BL Touch. while doing the auto bed mesh, it crashed to the bed after like the 5th point from th 25 points and just started to just go down. then got internal error, looked in klippy log, something about my uart tmc2209 not responding. checked wiring to my z endstop, pins. all look good. did a "sanity" check for the probe. it stays open unless i pressed the sensor really hard and then it's triggered. at least i got a lesson our of this mission. ha
polar shale
ah yeah sounds like your switch is not actuating when it should. Thats unfortunate. But yeah like you said at least you got to learn from it!