Basic Information:
Printer Model: RatRig Vcore 3.1
MCU / Printerboard: Octopus pro + EBB42
Host / SBC rpi4
klippy.log
klippy.log (143.9 KB)
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
Describe your issue:
After updating Klipper, I get this error…
Unknown pin chip name ‘probe’
The truth is, the update process was NOT as simple as other times… I’ll tell you how it went, in case it’s related:
-
As I’ve done many times, I checked the FLUIDD updates section and saw that I had some pending updates, including KLIPPER.
-
I used the FLUIDD update, and the first thing that changed was that it wouldn’t let me update because I had to send a command through the console. I don’t remember what it was, but something like DMESG…
-
I connected via telnet to rpi and sent that command, the one the FLUIDD update manager told me to.
-
Afterwards, I tried updating from FLUIDD, and everything was updated except KLIPPER.
-
I connected via telnet again, this time trying KIAUH, and with this I was able to update.
-
I rebooted and I get the aforementioned error “Unknown pin chip name ‘probe’”
I looked at the log, but I can’t understand it. It’s VERY long, so I’m attaching it.
Is there any way to “clean” the Klippy.log so it takes up less space?
I should mention, in case it helps, that the zprobe I’m using is a Beacon3D, which was working correctly before the update.
The configuration section, although it will be in the log, is copied here.
What could it be?
*NOTE: Before uploading the Klippy.log, I emptied it and restarted the printer. I did this because the log will take up a LOT of space.
