BTT Octopus Z Endstop not working after Klipper Update

General Discussion
1

Hello together,

im running a custom printer via Klipper on Android.
BTT Octopus 1.1
Klicky Probe as Z endstop
sesoreless homing for XY with TMC2209 drivers.
fluidd - v1.29.1
fluidd-config - v1.2.0-0-gce48c585
klipper - v0.12.0-143-g01c7befa
moonraker - v0.8.0-325-g99b97afc
klippy (3).log (129.9 KB)

After a longer break of arround 3 months, i recently plugged in my printer. After a print i realized that there are updates for everything and i installed these. Now my Z endstop is´nt working anymore. It´s allways triggered. I get the error: “!! Error evaluating ‘gcode_macro _SetProbeState:gcode’: gcode.CommandError: Probe attach failed!” Due to the fact that at the print before there where no issues,
i assume that it have to do with the updates. On the print befor the updates, Homing, quadgantry level etc. worked fine like ever. I checked all wiring, the switch and the magnets and everything in intact and correctly plugged in.
Can someone help me please?

Kind regards JOSh

2

Have you checked that your 3rd party macros run with the new Klipper version?

3

the only macro i use is the klicky probe and that is up to date as well. if i in fluidd at “tune” test the endstops, it does´nt matter which pin i use, nothing than sensorless homing works. i even tried to assign a normal switch to an other pin and this does´nt trigger as well. :frowning:

4

With almost 1500 lines of config, the Klicky macros are the only 3rd party macros?

5

you´re right but from line 251 to 1258 is only klicky specific. calibrating, attach, deploy, quadgantry level an so on. after that its only sensoreless homing and the printer config.

6

As indicated by @EddyMI3D:
Your klicky mcros is misbehaving. Could be:

  • due to the macro using deprecated functions
  • hardware issues, preventing the correct functionality

Check the proper functioning of the trigger / probe and update to the latest version of the macro

7

Ok, i try to get rid of the klicky macro in the first place to ensure that it has´nt to do with this, because the latest version is installed. Again, i checked the wiring, switch etc. which works and prior to the updates everything was fine as well.
But for now i have to go to work.
I´ll update tomorrow and let you know what happens.

JOSh

8

Hello together,

i´m sorry for beeing late. After i yesterday accidently crashed my whole system by updating the core system data, i´m now back on running. At least i did a backup before.

Now on to the solution:
@Sineos was right. It had to do with the cable from the probe. I measured everything before writing the post and all seems to work fine. I could simulate the probe by using a bridged cabe and it worked. I measured again and you know what, the cable behind the magnets of the klicky probe was broken. Probably because of the pressure from measuring at the magnets, i somehow get contact and when the probe attaches, the cable became loose.
The biggest problem i think is, that this issue came right after the klipper update.

I´m feeling bad about beeing the next one who askes dumb questions because of it´s own fault. I´m sorry for that and apreciate the help provided.

Kind regards

JOSh

9

No bad feelings.
Remote diagnosis is always difficult and we can only relate our experience and knowledge about Klipper or 3D printing in general.

Then it depends on your willingness to follow our advice and do a proper diagnosis. You did and successfully solved the issue. :+1:

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.