Non-critical MCU for beacon
Hello everybody, is it possible to set up the beacon probe as a non-critical mcu? I am having an issue with my beacon where it loses signal with klipper and kills my prints. I have tested multiple beacons probes and usb cables with no success which leads me to believe it is a power issue. I tried changing the powered USB hub as well as directly connecting the USB to the rpi but the issue persists. Being able to let the beacon not be critical after first layer would be really helpful. Thanks for any help you can offer 🙂
I unplugged the screen and the camera while running the beacon directly off the rpi power to see if there is any change, its currently printing but it normally stops a few hours in.
3 Replies
You obviously know this, but the beacon should NOT be losing connection. I don't know if there is a way to mark it as "unnecessary" but as it is doing z-probing I kinda doubt it.
multiple beacons, cables, and and ports are the smart things to try, iirc it should only be plugged directly to the rpi or good hub.
Maybe double check how you have the cables secured, that they're not wobbling out as the machine moves around?
I haven't heard of anyone having such consistent difficulties keeping their beacon connected before
right, I thought it was weird also. I have had it plugged into a separately powered hub for over a year without many issues the rare connection loss. I have made a little progress the probe normally has lost coms by now in the print. I only have what is required to print plugged into the pi right now seems to working fine.
I wonder what logs would show, like if the pi starts to get overloaded could it start to drop usb packets maybe? Completely blue-sky spitballing