Printer Model: Custom Trident Build
MCU / Printerboard: Octopus Pro V1.1 Raspberry Pi 4 klippy.log
Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
…
Upgraded Klipper recently. Since restarting, I get the error as in topic. Printer worked fine before upgrade, and I have not updated my printer.cfg file.
I have a beacon installed with this set as the z_probe virtual endstop. klippy.log (17.6 KB)
Ok, odd.
I have Beacon update manger added to Moonraker. Beacon was showing as updated, along with all other component.
I ssh’d into the Pi, tried to pull the latest files from Git (already up to date) and reran the install.sh script in the Beacon folder.
It now works.
Thanks for prodding me in the correct direction. Possibly, Moonraker needs some instruction to rerun the install script when updating Beacon (or anything else)
It is the same for the BD sensor as it is not integrated in mainline yet.
A personal advice: install command shell via KIAUH and write a little script and macro to rerun the install script from within Mainsail.
If I’m not wrong it did the trick for me and is quite handy.