BDPrinterProbe.run_probe() takes 2 positional arguments.

[Orin-Alchemical-3D]

Good Morning/Afternoon.

I have and set up the BDsensor in Klipper/Kalico and am mostly working. The probe works for general homing and detection, but when trying to flesh out the Z_TILT_ADJUST the system errors out with the warning below.

"BDPrinterProbe.run_probe() takes 2 positional arguments but 3 were given"

The printer design, is similar to something like a Trident with Triple Z, (z, z1, z2)

Here is what the config section looks like.

#-----------------------------------------------------------------------------
[z_tilt] ## Use Z_TILT_ADJUST to level the bed .
horizontal_move_z: 1
z_positions:
-50, 18
150, 348
350, 18
points:
30, 25
150, 245
270, 25
speed: 200
retries: 5
retry_tolerance: 0.0075
#-----------------------------------------------------------------------------

The macro lines have been copied and placed.

[gcode_macro Z_TILT_ADJUST]
rename_existing: _Z_TILT_ADJUST
description:
gcode:
#run z tilt with z move up and down at first
BDSENSOR_SET QGL_TILT_PROBE=1 #set this 1 to enable z axis up and down
BDSENSOR_SET COLLISION_HOMING=0
_Z_TILT_ADJUST horizontal_move_z=6 retry_tolerance=1
G28 Z0
#run z tilt with no z move up and down
BDSENSOR_SET QGL_TILT_PROBE=0 #set this 0 to disable z axis up and down while probe
_Z_TILT_ADJUST horizontal_move_z=1 retry_tolerance=0.04
#BDSENSOR_SET COLLISION_HOMING=1 #optional
G28 Z0

I have been surfing all of the guides, videos, etc able to be found and not located a solution.

[Orin-Alchemical-3D]

Additional info, I have ran the probe.py file through Antigravity to get its take on the explicit issue, and it has returned the following information.

---

"I have modified /home/orldk/Downloads/probe.py to be compatible with older probe extensions like the BDPrinterProbe.

The error arises because the Z_Tilt_Adjust command internally uses ProbePointsHelper, which was modified in recent versions of Klipper to pass an additional 3rd argument (self.retry_session) to probe.run_probe(). However, the BDsensor plugin overrides this function and only expects 2 arguments.

I've added a fallback that catches the TypeError and re-runs the function using only the original 2 arguments. You can now use your probe.py file with the BDPrinterProbe."

---

This may be pointing to a root cause, however I am a bit uncomfortable blindly throwing this AI generated python at pricey printer hardware to test.

[Orin-Alchemical-3D]

UPDATE:

I have been able to edit the file BDsensor.py and successfully initialize a Z_Tilt.

Location: ~/klipper/klippy/extras/BDsensor.py

Edit :
*Original Line: def run_probe(self, gcmd):
*Corrected Line: def run_probe(self, gcmd, *args, **kwargs):

---

However now it is showing a totally new issue when attempting to Z_Tilt. It arrives at the first specified corner, approaches the bed and then goes into shutdown state with the attached new error.

I am currently exploring options to correct this, but have made no headway yet.

[markniu]

I encountered this error before after updating Klipper, so the BDsensor.py code was also updated to match the latest official Klipper version recently.
In this case, you can use the older version of BDsensor.py (e.g. 2025).

[Orin-Alchemical-3D]

I used the older version (final version of 2025) and it got further, this time hitting 3 points in the Z_TILT_ADJUST function. New error shows up after probing the third corner (front right).

Also, I still had to edit the BDsensor.py file in order to ignore the third argument. Is this possibly just the way the two systems are trying to handle data back and forth?