Troubleshooting Klipper and reviewing logs

General Discussion
1

Basic Information:

Printer Model: Trident 300
MCU / Printerboard: BigTreeTech Octopus
Host / SBC: raspberry pi 3b
klippy.log.zip (796.6 KB)
KlipperScreen.log

Describe your issue:

…
Hi
I am getting the following error in the mainsail conesol. I can’t figure out what it means.
Conesole output error

SDCARD_RESET_FILE cannot be run from the sdcard

Exceeded maximum retries [5/5] klipper

And when I look in KlipperScreen log, it says that the following things do not exist. But I have checked and they exist.
And it also shows that there may be a future start error, regarding the module.

KlipperScreen.log warnings 
Moonraker warnings:
[update_manager]:
 Failed to load extension klipper_tmc_autotune:
 Invalid path for option `path` in section [update_manager klipper_tmc_autotune]:
 Path `/home/pi/klipper_tmc_autotune` does not exist
[update_manager]:
 Failed to load extension klipper_auto_speed:
 Invalid path for option `path` in section [update_manager klipper_auto_speed]:
 Path `/home/pi/klipper_auto_speed` does not exist
Unparsed config option 'origin:
 https:
//github.com/andrewmcgr/klipper_tmc_autotune.git' detected in section [update_manager klipper_tmc_autotune].  This may be an option no longer available or could be the result of a module that failed to load.  In the future this will result in a startup error.
Unparsed config option 'managed_services:
 klipper' detected in section [update_manager klipper_tmc_autotune].  This may be an option no longer available or could be the result of a module that failed to load.  In the future this will result in a startup error.
Unparsed config option 'primary_branch:
 main' detected in section [update_manager klipper_tmc_autotune].  This may be an option no longer available or could be the result of a module that failed to load.  In the future this will result in a startup error.
Unparsed config option 'install_script:
 install.sh' detected in section [update_manager klipper_tmc_autotune].  This may be an option no longer available or could be the result of a module that failed to load.  In the future this will result in a startup error.
Unparsed config option 'origin:
 https:
//github.com/anonoei/klipper_auto_speed.git' detected in section [update_manager klipper_auto_speed].  This may be an option no longer available or could be the result of a module that failed to load.  In the future this will result in a startup error.
Unparsed config option 'primary_branch:
 main' detected in section [update_manager klipper_auto_speed].  This may be an option no longer available or could be the result of a module that failed to load.  In the future this will result in a startup error.
Unparsed config option 'install_script:
 install.sh' detected in section [update_manager klipper_auto_speed].  This may be an option no longer available or could be the result of a module that failed to load.  In the future this will result in a startup error.
Unparsed config option 'managed_services:
 klipper' detected in section [update_manager klipper_auto_speed].  This may be an option no longer available or could be the result of a module that failed to load.  In the future this will result in a startup error.

Is it just a Klipper bug, or should I do something about it?

I ask because sometimes it won’t start a print and I have to restart the system to get it to start again.

I can find the following when I search in klippy.log

 cat klippy.log | grep -i "dirty"                        
Git version: 'v0.12.0-358-gc88ee84be-dirty'
Git version: 'v0.12.0-358-gc88ee84be-dirty'
Git version: 'v0.12.0-358-gc88ee84be-dirty'

I’m new to this, and I’ve been told not to update Klipper unless I first check if the update is stable, as it can potentially break Klipper.

Will updating Klipper solve the problem, or do I need to reinstall Klipper completely, as mentioned in the Troubleshooting guide?

I’d prefer to wait a few days before updating, so I have time to fix any issues if something goes wrong.

2

Interesting. So you rampage through Klipper with macros and third-party modifications, hoping it gets easier?

Anyway:

[virtual_sdcard]
path = ~/printer_data/gcodes
on_error_gcode = CANCEL_PRINT

[gcode_macro CANCEL_PRINT]
description = Cancel the actual running print
rename_existing = BASE_CANCEL_PRINT
gcode = 
	SET_IDLE_TIMEOUT TIMEOUT={printer.configfile.settings.idle_timeout.timeout}
	CLEAR_PAUSE
	SDCARD_RESET_FILE
	PRINT_END
	BASE_CANCEL_PRINT

Calling CANCEL_PRINT from [virtual_sdcard] and then calling SDCARD_RESET_FILE in CANCEL_PRINT is not working, as far as I know.

The rest of your errors come from incorrectly installed third-party modules.

1 Like
3

I’m not sure I understand what you mean.

Maybe I haven’t been specific enough. I bought the printer used, and everything was already installed when I got it. Now I’m trying to familiarize myself with it. I haven’t installed anything on it myself.

Is it possible that you can point me in the direction of where I should change the above:

I have the following, at the bottom of my Pause_resume_cancel.cfg

[gcode_macro CANCEL_PRINT]
rename_existing: BASE_CANCEL_PRINT
gcode:
    SET_IDLE_TIMEOUT TIMEOUT={printer.configfile.settings.idle_timeout.timeout} ; set timeout back to configured value
    CLEAR_PAUSE
    SDCARD_RESET_FILE
    PRINT_END
    BASE_CANCEL_PRINT

Pause_resume_cancel.cfg (4.4 KB)

~/printer_data/gcodes

And this folder is empty, but I assume that’s the intention?

Are you referring to modules like Mainsail, Cartographer, KlipperScreen, etc., that might not have been installed correctly?

The person I bought the printer from either used KIAUH or downloaded and installed the files manually from source.

Can you point me in the direction of how to troubleshoot these modules?

Thanks, and sorry. If I know how to troubleshoot this, I can work through and try to fix the issues.

4

TBH, the installation looks a bit messy and has unsupported third-party modules installed (which we do not support). At least one of these modules is either unnecessary or potentially detrimental (GitHub - andrewmcgr/klipper_tmc_autotune: TMC stepper driver autotuning Klipper python extra).

Additionally, there are some additional scripts being called, and it is unclear what they do or their quality.

I would recommend starting clean and setting up the printer yourself. This way, you know exactly what is on it. You can use a new SD card and keep the old one as a backup.

For a step-by-step approach, see:

1 Like
5

Okay, thanks. That sounds like a good plan. I might as well upgrade my Raspberry Pi 3 to a Pi 4, since I’ll need access to the controller board anyway.

Just one last question: I like to keep my system fairly clean, so I’m considering installing Raspberry Pi OS Lite (64-bit), Debian version 12 (Bookworm).

Is that okay to use? I’m asking because it’s lightweight, and most of the work will be done via SSH or Mainsail.

The last time I used Debian, it was Debian 10, which had WiFi issues that needed to be fixed manually. I’d like to avoid that this time.

6

This is a good choice and my go-to distribution as well. I’m not aware of any major bugs in this version, although I’m not a good candidate to judge Wi-Fi, as my printers are all wired up.

1 Like
7

Ok, thanks.
It’s going to be nice to install everything myself.

8

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