Interesting, I’ve not run into that particular error before.
Yes, it’s usable as a virtual endstop. My machine with the virtual endstop is out of commission at the moment or I’d copy paste the config.
Try defining the pin in a “[probe]” section and leaving all the other options in the “[dockable_probe]” section, or however many Klipper requires.
It’s probably something stupid I’m missing since I’m new to Klipper.
I tried what you said, but not it’s looking for the other config options for probe like ‘z_offset’. If I add the z offset to probe, then it gives me an error that says ‘dockable_probe’ is not a valid config section. I’ve included my config file. I appreciate your help
printer.cfg (9.4 KB)
Apologies, I seem to have led you astray. Got my machine back online and the config is how you had it initially with “probe:…”. Can you put it back and upload the Klipper log? That will have the config and error messages.
I think this is the config you are asking for, the same one I posted previously. Would you be willing to share your config?
klippy-6.log (2.2 MB)
Hmm, are you using the dockable_probe.py from the GitHub linked in the OP? Where is it from? You’ve got a mix of dockable_probe config options from this and another module.
I don’t know where they came from, I thought it was included in Klipper as it’s a newish install and I don’t remember adding any extra modules. Do I need to do a fresh Klipper install to resolve this?
Ah, no, it’s not part of Klipper yet. Perhaps you’re using a fork. What is the provenance of this machine and Klipper install? ‘git remote -v’ run in the Klipper directory will shed a little light on things.
I installed Klipper using the Mainsail image so I don’t believe that it’s a fork.
pi@VZBot330:~/klipper $ git remote -v
origin https://github.com/Klipper3d/klipper.git (fetch)
origin https://github.com/Klipper3d/klipper.git (push)
Yeah that’s the main repo. Hmm. Is the image MainsailOS? What does your Moonraker config look like? That can have an updater that pulls in 3rd party repos. If you upload the dockable_probe.py file that would tell us what version/make it is.
Yes, the image was Mainsail OS.
mainsail.cfg (15.3 KB)
I can’t find the dockable_probe.py. Is it possible I never installed it? If so, how would I go about installing?
Well, I feel stupid, I didn’t have it installed. Now that I have it installed, I keep getting a failed to attach error. All of my positions are correct and I can step through everything using the individual commands and the query responses are correct, not sure what I’m missing.
Console step by step with query after every step:
11:26 AM
Probe Status: DOCKED
11:26 AM
QUERY_DOCKABLE_PROBE
11:26 AM
MOVE_TO_APPROACH_PROBE
11:25 AM
Probe Status: ATTACHED
11:25 AM
QUERY_DOCKABLE_PROBE
11:25 AM
MOVE_TO_DOCK_PROBE
11:25 AM
Probe Status: ATTACHED
11:25 AM
QUERY_DOCKABLE_PROBE
11:25 AM
MOVE_TO_DETACH_PROBE
11:25 AM
Probe Status: ATTACHED
11:25 AM
QUERY_DOCKABLE_PROBE
11:25 AM
MOVE_TO_DOCK_PROBE
11:25 AM
Probe Status: DOCKED
11:25 AM
QUERY_DOCKABLE_PROBE
11:24 AM
MOVE_TO_APPROACH_PROBE
Config:
[dockable_probe]
pin: EBBCan: PB9
x_offset: -24
y_offset: 35
z_offset: 13
samples: 3
sample_retract_dist: 2.0
approach_position: 355, 25
dock_position: 355, 87
detach_position: 300, 87
check_open_attach: true
attach_speed: 40
detach_speed: 40
travel_speed: 100
dock_retries: 3
The attach and detach processes have 3 gcodes each. The codes you ran are part of it but they’re incomplete and at the end it moves to detach but says it’s attached and then moves to attach and says detached. That’s not expected.
Read through the movement gcodes and also take a look at the position examples. Something is misconfigured but I can’t tell what without being in front of the printer. My guess is a coordinates or movement ordering problem.
It was a movement ordering issue. I have a Euclid style probe, so I reordered the movement commands in the dockable_probe.py and it attaches, homes z, and detaches successfully. My next issue is that I get a fault when I try to run the z-tilt command. “Internal error on command:“Z_TILT_ADJUST””. Is it an issue with the way I edited the file?
dockable_probe.py.txt (26.0 KB)
klippy-10.log (163.7 KB)
printer-2.cfg (9.3 KB)
"/home/pi/klipper/klippy/extras/probe.py", line 123, in _probe
epos = self.mcu_probe.probing_move(pos, speed)
AttributeError: 'DockableProbe' object has no attribute 'probing_move'
You’ve run into an issue with an incompatibility with recent Klipper changes. See the latest comments on the GitHub PR.
That’s unfortunate, so close! I really appreciate all of your help figuring out all of the “me” issues and all of the work you’ve put into this feature. I’ve learned a ton and hopefully I can continue to learn and contribute in the future.
I desperatly need your help…
Updated Klipper on my Annex K3 with dockable Probe:
seems a problem with the dockable_probe.py , see the log
any thoughts?
thanks
klippy-9.log (186.4 KB)
You’re in luck, the issue is you’re using a new version of Klipper that is incompatible with the version of the dockable_probe module. Get the latest dockable_probe module and the problem will go away.
I’m already using the latest version I think
last modify was 2 years ago … I’m looking in the wrong place ?
has this been ever addressed?
btw i’ve ah Voron v2
i’ve been running into the klipper issue after the probe changes to klipper from 10.jun24
Internal error during connect: init() takes exactly 2 arguments (3 given)
and found @cloakedcode fix to it…
the issue is that i still used the original annex probe from mental and now i run into the issue that my config still had dock_fixed_z: True and allow_delayed_detach: false these two again failed then…
after disabling these two settings, klipper would start but now on QGL is failing:
Internal error on command:“MOVE_TO_APPROACH_PROBE”
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
this is the log snipped what happens in klippy log… sadly i’m nowhere near ah dev. to understand whats happening … 
Internal error on commandMOVE_TO_AP.txt (57.1 KB)
