MCU or T0 or T1 running at the wrong Mhz
I've gotten a shutdown and error every time I try to print. Not sure what is going on. I haven't changed anything since I completed a print with no problem, last night.
33 Replies
this isn't an error
However it's odd indeed
Post a debug.zip (download from the configurator sidebar)
It comes after a shutdown. So I assumed it was part of it
Could be power related, do you get a warning about pi undervoltage too?
No, I've got a 5v 75w PSU, so 5v power isn't an issue
24v power manybe? That's what the mcu and both toolheads run on
They support a pretty large voltage range and the onboard dc/dc converter accepts like 3-36V or some such, so unlike that's the issue. I was thinking the 5V rail may had been collapsing and affecting the 3.3V rail but that doesn't seem to be the case then.
Something's up with your USB setup
Hmm...The MCU, T0, and T1 are all connected to the waveshare
How do you have everything plugged in? Can you show me on a drawing?
What about the beacon
beacon is on there too
Ok good, what's connected to the pi? And i'm assuming the waveshare is plugged into a 3.0 port, right?
(blue plug instead of black)
Yes, it is. The pi has VAOC and my other hub is connected to the 2nd 2.0 port
The only thing that I've done differently from my last good print to now is I prioritized klipper and added affinity settings to the processors.
Your other hub?
Yea, its got the USB for klipper screen and cameras
Can you show me how you did that?
Have you tried disconnecting that hub?
sudo su -
mkdir /etc/systemd/system/klipper.service.d
cat << EOF > /etc/systemd/system/klipper.service.d/override.conf
CPUSchedulingPolicy=rr
CPUSchedulingPriority=50
IOSchedulingClass=realtime
IOSchedulingPriority=0
EOF
systemctl daemon-reload
systemctl restart klipper.service
Gist
CPU Affinity for Klipper and Friends
CPU Affinity for Klipper and Friends. GitHub Gist: instantly share code, notes, and snippets.
I can, give me a few minutes
Try this image instead: https://github.com/Rat-OS/RatOS/actions/runs/11301673501 that isolates cpu3 and pins klipper to it
GitHub
Performance: isolate cpu 3 and pin klipper to it · Rat-OS/RatOS@50a...
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - Performance: isolate cpu 3 and pin klipper to it · Rat-OS/RatOS@50ab37e
Or delete /etc/systemd/system/klipper.service.d and do this: https://github.com/Rat-OS/RatOS/commit/50ab37eef4e41ffdb8c59256efc21e1bf111ac20
then reboot
Ok, I'll start with the USB hub and go from there
however i wouldn't suspect this to fuck over the usb devices, they're disconnecting randomly
yep sounds like a good plan
I'm gonna be pissed if it's the hub. It was like $100! It's designed as a server usb expander. Runs on 24v
holy shit
IOSchedulingClass=realtimeThis won't work btw, it's not supported by the kernel
To be fair, I had it sitting on the shelf from an old project, so I didn't pay that just for this. But I had some issues with USB hubs on one of my vorons, so I figured it would be a safe bet.
Ok, I'll go off of what you posted and get rid of it
Yeah hubs can be problematic. Separate power and MTT, and you're usually good to go, i would expect a $100 server usb expander to have both of those (and you already said it runs on 24v).
https://www.amazon.com/gp/product/B00C3GFRUM/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 this is it
7 Port USB 3.2 Gen 1 Hub w/Surge Protection & Screw-Locking Ports
Industrial Grade | +7~24V DC Input | Surge Protection | Surface Mountable | DIN Rail | 5 Gbps | Screw Lock Protect Your Equipment: The 7-port USB 3.2 Gen 1 features 350 Watts of surge protection to keep your connected peripherals safe from harm. Super Fast Speeds: This USB hub is 3.2 Gen 1 compli...
yep that uses 2 GL3520's, MTT hubs controllers.
So it should be good, right?
Maybe I'll try a different USB connecting it. I just pulled one out of my stash because the OE has screw downs
I would assume so yes
well, I changed out the USB cable to the hub and did a power off reboot of the pi. I'm almost an hour into a print, with no issues. Maybe it was the cable giving me all those weird USB errors in the kernal log. Hopefully this is the end of my issues. I'll look at the kernal log after it's finished and see whats happening
😮
🤷♂️
hope it's fixed!
I am still getting the wrong Mhz warning, but no more lost comms, so I'm going to close this.