Klipper/Raspi wont boot with MCU plugged in

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: Octopus pro V1.0
Host / SBC Mainsail
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Hey all, I have a really challenging situation. I have setup a fresh install with bookworm, klipper and mainsail with klippian. I can get through the setup and get my config right, but after I power cycle the printer a few times it completely loses connection, the ping goes to 2003ms and I can no longer access the printer via the web UI or SSH. Does anyone have any insight? This only happens with my Klippian installation, my regular klipper install boots fine. Once it has booted without the MCU plugged in and then I plug it in, everything is fine and I can even do software reboots…
usb_disconnect_boot_log.txt (433.7 KB)

Does the printer maybe suck power from the Pi via USB when turned off?

Maybe this is already the answer?
I never tested Klippian because I can see no real benefit as the general setup of a printer typically is a one time task (their ADXL stuff is nice, but can be used stand alone)

OTOH it would seem strange that Klippian is causing this on hardware level, so :person_shrugging:

It is always difficult to identify root causes when the local installation differ significantly from the “standard”

Fair enough. I guess I’m just stuck on the fact that the klipper install shouldn’t really matter…

I have a dedicated 5v 3A power supply and the MCU has a separate power supply so I don’t think it’s a power issue…

How do you have the power supplies wired?

I’m particularly interested in how you manage your grounds.

I have the ground from the raspi and the output of the power supply tied to the ground of the main PSU. I reverted to bullseye instead of bookworm and it seemed to fix the issue however.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.