Hey guys, built my LDO Voron 2.4 kit awhile back, recently converted to nitehawk and beacon RevH, was printing good until some capacitors blew on the nitehawk board and I got a replacement sent out, swapped the new board in last night and switch the serial to the new one, and I got a error message saying my mcu and nitehawk were on older klipper versions so I updated everything with kiauh by deleting klipper then reinstalling and on reboot it’s giving me the Unknown pin chip name “probe” and I’m not sure what is happening I’ve been through it 20 times.
#Unknown pin chip name “probe”
1 messages · Page 1 of 1 (latest)
Here is config https://pastebin.com/eXpNnhKc
Pastebin
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
Was required to delete it, per beacon instructions
you have a reference to probe in [stepper_z]:
endstop_pin: probe:z_virtual_endstop
have you installed beacon?
What I thought too, I ran the install script provided from beacon and it said it was already installed but maybe I’m on an older version?
The firmware or the install? Beacon install copies stuff to klipper directory. Rerun install.sh
I’ll look into updating beacon I think I’m on 1.1 and I think they have a 2.1 out now, the printer has been down for about a month
It will always say probe:
You need to update that too. Now I know you didn't reinstall
I will rerun the install sh again and see what happens
Hello everyone I have the same problem but I don't use beckon but clicky
Unknown pin chip name 'probe'
Klicky is still a conventional probe, and still needs a [probe] section in your config
Sgthrs? That's a weird one. Gonna need some context there
Did you maybe switch from 2209s to 5160s or something?
Make sure to update below for your relevant driver (2208 or 2209)
[tmc5160 stepper_x]
cs_pin: PC4
spi_software_mosi_pin = PA7
spi_software_miso_pin = PA6
spi_software_sclk_pin = PA5
interpolate: True
diag1_pin: ^!PG6 # use the same pin that was previously the endstop_pin!
driver_SGT: -64 # -64 is most sensitive value, 63 is least sensitive
run_current: 2.00
#hold_current: 0.2
sense_resistor: 0.075
#stealthchop_threshold: 999999
So there's obviously still a reference to sgthrs someplace...