-
Notifications
You must be signed in to change notification settings - Fork 83
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
moonraker connection issues #49
Comments
@dans98 this is really weird, but i had the same issue recently, i'll dig into it and see what's up |
I would say that python2 is probably the reason? |
oh yeah - dangerklipper drops support for python2 |
hmm, let me see if i can get to 3 without having to completely rebuild the pi from scratch. |
@dans98 what you could do is use kiauh to uninstall klipper, then use kiauh to install it with python3 |
@bwnance I tried thats but it didn't work. I tried completely clean slate install last night but ran into what i assume is the debian usb bug. I'm going to try a clean state setup again today and then run the following commands.
Seems it's the recommended way to deal with the debian issue on the klipper discord. |
@dans98 ok, thank you! we'll definitely take a look at why this is going on - we'd like the barrier of entry for danger klipper to be minimal 😅 |
@bwnance i think switching to python 3 will fix the above initial issue. I think I'm running into the debian usb bug now, because after i flash the mcu it doesn't show up anymore. I think i got lucky in the past, as i started with mainsailOs like 20 months ago and everything just worked! |
oh, ok! let me know if I can help with anything! |
@dans98 did you sort it out? anything I can help you with? |
Sorry I had family in town for a few days so I haven't had a chance to respond. It took a few tires, but it seems none of the 'fixes' work with my duet 2. What worked was going back to mainsailOS version 0.7.1 (the last buster build), and then just upgrading everything. That got me to python 3.7.3, and the latest releases of klipper, mainsail, and moonraker. when my family leaves tomorrow i'm hoping to get converted over to danger klipper. I'll post an update! |
I got everything up and working last night. Switching to DangerKlipper was cake when I finally got mainline klipper working properly! |
I'm try to switch to danger klipper from klipper, so i can do some testing and do a pr for the pid calibration improvements. I used kiauh to switch over to my fork of danger clipper master, but im getting an error thats looks to be encoding or json decoding related.
klipper: v0.0.0-5104-g2c0d70bb-inferred
mainsail: v2.7.1
moonraker: v0.8.0-138-gfe120952
from the klipper log
from the moonraker log
logs:
klippy.log
moonraker.log
i went into the WebRequest init and added a little logging.
the logged info.
I'm not sure why this is happening, as i thought unicode was considered to be a string. if i revert to klipper everything works fine.
The text was updated successfully, but these errors were encountered: