Unknown pin chip name 'probe' after updating Klipper

General Discussion
1

Basic Information:

Printer Model: Panda Cube
MCU / Printerboard: SKR 1.4 and Arduino Nano
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
klippy(5).log (128.6 KB)

Describe your issue:

Yesterday I updated klipper via the normal update manager. Since then I get this error: "Klipper reports: ERROR

Unknown pin chip name ‘probe’

Once the underlying issue is corrected, use the “RESTART”
command to reload the config and restart the host software.
Printer is halted"
Everything worked perfectly fine for months now and I didn’t changed any of my “.cfg” (as far as I’m concerned). All other Issues related to this problem occured due to someone setting up their printer incorrectly, not after an update.
…

1 Like
2 
[stepper_z]
step_pin = EXP2_6
dir_pin = !EXP2_5
enable_pin = !EXP2_7
microsteps = 32
rotation_distance = 8
endstop_pin = probe:z_virtual_endstop
homing_retract_dist = 0
position_max = 235
position_min = -40

[tmc2208 stepper_z]
uart_pin = EXP1_6
run_current = 0.450
stealthchop_threshold = 999999

[stepper_z1]
step_pin = P0.22
dir_pin = !P2.11
enable_pin = !P0.21
microsteps = 32
rotation_distance = 8
endstop_pin = probe:z_virtual_endstop

[tmc2209 stepper_z1]
uart_pin = P1.8
run_current = 0.450
stealthchop_threshold = 999999

[stepper_z2]
step_pin = EXP2_3
dir_pin = !EXP2_4
enable_pin = !EXP1_8
microsteps = 32
rotation_distance = 8
endstop_pin = probe:z_virtual_endstop

For more than one Z-axes:

You have at least one endstop.

or

You can have an endstop for each axes.

or

You can have only one virtual_endstop.

3

klippy(7).log (13.2 KB)

Still same issue.

6

You installed beacon but it seems you did not follow the relevant instructions, in particular Quick Start - BEACON DOCUMENTATION

1 Like
7

How did you come to this conclusion? This config worked fine for weeks wirhout any changes and I used the instructions.

8

According to your log:

Git version: 'v0.12.0-93-g43a9685c'
Branch: master
Remote: origin
Tracked URL: https://github.com/Klipper3d/klipper.git

→ Pristine Klipper repository. If any non official module would have been installed, then the Klipper would mark its repository as dirty.

[beacon]
serial = /dev/serial/by-id/usb-Beacon_Beacon_RevD_8AF223494E5737374D202020FF07192B-if00
x_offset = 0
y_offset = -21.5
mesh_main_direction = x
mesh_runs = 2

→ Beacon as a probe.

So, I do not really care what worked on your side or not, I just go by the information in the log.

9

Okay so Klipper is working alright, but what could be the problem then? What made you think I didn’t set up the Beacon properly? Was there anything abnormal? Thanks so far

10

It’s working again. I don’t know why. Haha but I’m not complaining. I just wrote it whitout “probe:” and then again with “probe:” and suddenly its working again.

1 Like
11

immagine
Same issue, restart Klipper service from that menu.

12

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