PrinterProbe error after commit #d4bae4d

Basic Information:

Printer Model: Voron V2
MCU / Printerboard: Octopus
klippy.log (1.9 MB)

I got an "Internal error during connect: ‘PrinterProbe’ object has no attribute “sample_count” after the last update. Followed by several other errors related to the Printer Probe if I manually fix this one. Basically, auto z config cannot access the probe anymore. I suppose this is an unwanted side effect of commit (d4bae4d)
Any recommendations on how to proceed?

What probe are your using? If a beacon then that team knows about it and is working on a fix.

If you need a working printer now then you’ll need to roll back your klipper to commit 49c0ad6.

You are using an unofficial Klipper modification ( that is causing issues because the underlying official code-base changed.

Klipper does not carter for unofficial modifications since there is no official plugin system and the APIs and methods are not guaranteed to stay stable.
If you want to continue using this modification, the original author would have to adapt.

A post was merged into an existing topic: No

3 posts were split to a new topic: No

My problem was solved by the author of So this thread can be closed.

1 Like