Printer Model:Custom
MCU / Printerboard: Octopus Pro
Host / SBC: Mainsail / Pi 3b+
klippy.log
klippy.zip (1.4 MB)
Every time i boot/power cycle my printer, i have to re-install shake&tune and TMC_autotune via “$ wget -O - https://raw.githubusercontent.com/Frix-x/klippain-shaketune/main/install.sh | bash”
What needs fixing to ensure that I do not need to re-install these packages every time?
…
With or without the SBC (whatever it is)?
Args: ['/home/pi/klipper/klippy/klippy.py', '/home/pi/printer_data/config/printer.cfg', '-l', '/home/pi/printer_data/logs/klippy.log', '-I', '/home/pi/printer_data/comms/klippy.serial', '-a', '/home/pi/printer_data/comms/klippy.sock']
Git version: 'v0.13.0-403-gb4c7cf4a3-dirty'
Untracked files: klippy/extras/autotune_tmc.py, klippy/extras/gcode_shell_command.py, klippy/extras/motor_constants.py
Branch: master
Remote: origin
Tracked URL: https://github.com/Klipper3d/klipper.git
CPU: 4 core ARMv7 Processor rev 4 (v7l)
Device: Raspberry Pi 3 Model B Plus Rev 1.3
Linux: Linux version 6.1.21-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1642 SMP Mon Apr 3 17:20:52 BST 2023
Python: '3.9.2 (default, Mar 20 2025, 22:21:41) \n[GCC 10.2.1 20210110]'
The only logical explanation is if there are some weird SD card/system issues.
Or your system is configured in a way that it resets its state after the power cycle.
(and so any config changes will be reset too, after the power cycle).
I guess, simplest test that you can do is to
$ echo lol > ~/test_file
$ sudo reboot
$ cat ~/test_file
lol
If it persists, then something more complicated is happening.
Hope that helps.
Sorry my mistake, I am using a Pi 3b+.
So, do you also power cycle the Pi3+ ?
yes, the main board and pi running from the same source. So they get cycled together
Then issues are preprogrammed.
When you power cycle the Pi the moment it does a write to the SD card, the data on that SD card can be corrupted.
I am using a BIGTREETECH SKSM, which should allow the pi to shutdown safely if the power is removed.
However if the SD is becoming corrupted, it the only fix to wipe it and re-flash klipper?
No. You cannot simply remove power to the Raspberry Pi (or basically any system with an operating system) and expect it to start up again properly.
What happens if you execute sudo shutdown now from SSH or click on “Shutdown” in the web console:
“Shutdown” from the web interface, then power off (after five seconds), then power on, results in the same error.
I just looked at your klippy.log. You have a poop ton of macros and you’ve added additional python files to your installation.
I’m surprised that nobody here previously has pointed out that you have a “dirty” Klipper installation which is something that we normally don’t provide help with.
Have you gone back to the people supporting the autotune software and asked for help there?
Sorry, we are really only equipped to help with stock Klipper. Any modifications make or problems with the modifications are outside our area of expertise.
