EBB SB2209 USB + BTT Eddy Probe "pins.error: Unknown pin chip name 'probe'"

Basic Information:

Printer Model: Sovol SV06 Plus (frame, steppers, mainboard only)
MCU / Printerboard: EBB SB2209 USB + BTT Eddy Current Probe
Host / SBC: Pi 3B+
klippy.log (19.0 KB)

Describe your issue:

Hi everyone,

I’m setting up a Stealthburner on an SV06+ frame, with the following parts/components:

  • EBB SB2209 USB
  • BTT Eddy USB Probe
  • 3DO Nozzle Cam V2
  • Neopixel RGB LED lights
  • Rapido 2

Previously I had an NPN probe installed that worked without issue, however when I switched over to an Eddy probe now, I continually get the "unknown pin chip name: ‘probe’ " error.

I removed the original probe section, added a probe_eddy_current section (as outlined in the instructions) and then left my z end stops as is (probe:z_virtual_endstop).

Note: Since the EBB SB2209 has an E stepper driver on it, I am reusing the E stepper driver on the Sovol mainboard as a z1 stepper for auto gantry adjustment with independent z’s

After searching around online, it seems like most of the time this error is caused by an improper “probe:z_virtual_endstop” section in the stepper .cfg however I don’t think that’s my present issue. To me it seems related to either having dual independent z steppers, or the fact that the eddy probe is connected to the EBB, which is then connected to the host board (but I could be missing something)

If anyone saw the explanation for errors in my config it would be greatly appreciated. If I figure it out first, I’ll post the solution as well so others might benefit :slight_smile:

Thank you!

Hello @SirNut !

When you home the z-axes by a probe, you only have an endstop with the stepper_2, not with the other ones (Z1, Z2 etc) → lines 7 and 18

[stepper_z]
step_pin = PB6
dir_pin = !PB5
enable_pin = !PC3
rotation_distance = 4
microsteps = 32
endstop_pin = probe:z_virtual_endstop
position_min = -3
position_max = 259
homing_speed = 10

[stepper_z1]
step_pin = PB4
dir_pin = !PB3
enable_pin = !PC3
rotation_distance = 4
microsteps = 32
endstop_pin = probe:z_virtual_endstop

Hmm, if that’s the case do you know why I was able to home with an NPN sensor and this config?

I commented out my [probe] section in favor of the [probe_eddy_current btt_eddy] section, but the errors almost make it look like klipper is expecting [probe]. Possibly related - when I comment out the

klippy(7).log (128.5 KB)
Either way, commenting out the z1 endstop_pin does not seem to have changed the error

klippy(8).log (183.3 KB)
I tried changing the name from “probe” to “eddy” (name of the eddy mcu) which got rid of the error, but now shows a different error of the eddy config section being incorrect, but I pulled it straight from BTT

I appreciate your help btw Eddy :slight_smile: (very appropriate name given the circumstances lol)

Likely your Klipper version is too old.

I figured that since it was a fresh install it would have been up to date, but sure enough I just checked and was a few releases behind

Once I have updated everything I will update this question

Thanks!

I’m embarrassed to admit that solved the issue :upside_down_face:

Lesson learned: In the future, will always check for updates when running into issues

Thank you (and sorry for taking up your time I appreciate the input)

Here’s the log for successful boot up:
klippy(11).log (630.2 KB)

1 Like

Also, I believe this helped as well :slight_smile:

1 Like

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