-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MMU Shutdown after updating to 3.1 #617
Comments
Same error here.
Happy Hare 395db13 |
And after this, nothing works anymore.
|
Same error on the v3.1.0 tag. 4863e64 (tag: v3.1.0) |
This isn't a change in HH but something in the environment... Hmm. Did you upgrade OS / python? |
I am not sure exactly how I fixed it. Here is an account of what happened. After getting A day later, moonraker refuses to start, complaining about some syntax error. Which as far as I can tell was coming from klipper itself. For some reason, klipper was running in a python2 env, while moonraker was running under its own python3 env. How comes it worked the day prior far enough to start moonraker/mainsail, but not anymore? No idea. I even double checked the systemd units, and they did not look different. Clearly something changed that the reboot reloaded. I fully removed python2 from the whole machine as an extra precaution. And re-created a python3 env for klipper. Then I update Happy Hare to the latest main branch (some changes landed over night). And everything is now working fine. Interestingly, Happy Hare also stopped complaining about a lack of completed calibration. I still cannot explain how klipper managed to work under python2 one day and not the next. And why moonraker worked and then not anymore. But I must have had something loaded that a reboot cleared. |
100% sure this wan't a change in HH. Anyway, I've added a precaution to the code (and pushed an update). This will force an integer. FWIW the code is using: Final note: Python 2 is a dead language. I support it because Klipper does, but you really should upgrade to python 3. |
Thank you for the details @moggieuk. Back when I installed klipper with kiauth, it created a python2 venv. I used kiauth to handle the updates for me. Which apparently doesn't warn about python2 nor re-create a python3 env during updates. I am still on the ERCFv1. And Happy Hare is handling it very well so far. Thank you for the fantastic work. The original encoder is still working perfectly ;)
|
Hi, I have a problem after most recent update - 3.1
I'm gettin all sorts of errors
For example - during homing MMU I've got
Internal error on command:"MMU_HOME"
After restart I've got
Internal error on command:"__MMU_SENSOR_INSERT"
Internal error on command:"MMU_PRELOAD"
and looks like it traces to the same place.
Any ideas?
klippy (19).log
The text was updated successfully, but these errors were encountered: