Internal error on command:"_QUAD_GANTRY_LEVEL"

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: BTT Octopus v1.1
Host / SBC: Pi 3B+
klippy.log

klippy (10).log (1.9 MB)

Describe your issue:

Hi all,

Recently updated all the things on my machine and now I can’t get it to run a print. I get the error mentioned in the title and am prompted to restart the firmware.

I am running a BTT Eddy probe with EddyNG. The odd thing is the machine will home using the same probe but throws an error when I send a QUAD_GANTRY_LEVEL.

To save some time parsing logs, I found this error that seems to be my issue but can’t make sense of it. Any assistance would be greatly appreciated.

Internal error on command:“_QUAD_GANTRY_LEVEL”
Traceback (most recent call last):
File “/home/pi/klipper/klippy/gcode.py”, line 223, in _process_commands
handler(gcmd)
File “/home/pi/klipper/klippy/gcode.py”, line 151, in
func = lambda params: origfunc(self._get_extended_params(params))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/home/pi/klipper/klippy/gcode.py”, line 151, in
func = lambda params: origfunc(self._get_extended_params(params))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/home/pi/klipper/klippy/extras/quad_gantry_level.py”, line 53, in cmd_QUAD_GANTRY_LEVEL
self.probe_helper.start_probe(gcmd)
File “/home/pi/klipper/klippy/extras/probe.py”, line 512, in start_probe
self.probe_offsets = probe.get_offsets(gcmd)
^^^^^^^^^^^^^^^^^^^^^^^
TypeError: ProbeEddy.get_offsets() takes 1 positional argument but 2 were given
Transition to shutdown state: Internal error on command:“_QUAD_GANTRY_LEVEL”

The klippy.log gives more essential information…
E.g.:+1:

...
Loaded MCU 'mcu' 105 commands (v0.11.0-110-gaca0c71a / gcc: (15:7-2018-q2-6) 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907] binutils: (2.31.1-11+rpi1+11) 2.31.1)
...
Loaded MCU 'eddy' 131 commands (v0.12.0-456-gfbd5b4921-dirty-20251025_134222-voron2 / gcc: (15:12.2.rel1-1) 12.2.1 20221205 binutils: (2.39-8+rpi1+18) 2.39)
...
Git version: 'v0.13.0-522-g4c89f7f82-dirty'
...

You are running 3 different versions of Klipper. You might update the old ones.

You may consider migration from Eddy NG.

Otherwise:

Reverting seems to be working. I’ll keep an eye for updates that are Cartographer compatible. Thanks!