search

andrewmcgr / klipper_tmc_autotune

TMC stepper driver autotuning Klipper python extra
GNU General Public License v3.0
554 stars 119 forks source link

Internal error during connect: cannot import name signature #174

Open h3rm opened 1 month ago

h3rm commented 1 month ago

Describe the bug Internal error during connect: cannot import name signature error message. If i comment out all autotune rows in the printer.cfg the printer can suddenly connect again

To Reproduce Steps to reproduce the behavior: after todays full update i get the error: https://imgur.com/cBKVtbn

Expected behavior normal start

Screenshots https://imgur.com/cBKVtbn

Logfile moonraker.log klippy.log

Dragi2k commented 1 month ago

i have the same issue

Dragi2k commented 1 month ago

5hagbard23 found the solution, and Posted it in discord. Python is too old and should be Updated : sudo systemctl stop klipper; rm -rf ~/klippy-env; python3 -m venv ~/klippy-env; ~/klippy-env/bin/pip install -r ~/klipper/scripts/klippy-requirements.txt; sudo systemctl start klipper works on my side

h3rm commented 1 month ago

5hagbard23 found the solution, and Posted it in discord. Python is too old and should be Updated : sudo systemctl stop klipper; rm -rf ~/klippy-env; python3 -m venv ~/klippy-env; ~/klippy-env/bin/pip install -r ~/klipper/scripts/klippy-requirements.txt; sudo systemctl start klipper works on my side

maybe use with care. i bricked my klipper config (https://github.com/Guilouz/Klipper-Flsun-Speeder-Pad/wiki) totally with this ( i think cause of rm -rf ~/klippy-env but i don't know)

update: reinstall of klipper + moonraker via KIAUH worked. now the autotune plugin seem to work too.. weired

vndk36 commented 1 month ago

I had the same issue and the klippy logs where not super clear. I tried the commands on the command line. It worked well on my side without bricking the klipper config. Your case may vary. Thx @Dragi2k