SAVE A SOUL and help me make sense of this!
Some history (from FB group):
After a power outage, my printer began a job then stopped mid-print. I suspected the Raspberry Pi, so replaced it. Now I can’t get the software to flash the Octopus or toolheads.
With everything disconnected, I can flash the Octopus via USB power from the Pi, but since the Pi can’t power the toolboards too, the install fails because it can’t detect them.
When I power the Octopus from the PSU instead, the Pi no longer recognises it—so I can flash the Octopus on USB only, but not the toolheads; and with PSU power, not even the Octopus is seen.
Surely RatRig don’t have this pain in production, so why is it so difficult? Any advice would be hugely appreciated.
Later progress:
Still banging my head—so frustrating after it worked flawlessly for so long. I did get everything talking again: all boards updated, calibrations done once successfully. But now it won’t even home. It moves 10–20 mm, then Klipper throws a random error: Lost communication with MCU ‘toolboard_t0’, ‘t1’, or ‘MCU’.
No consistent logic. I can SET_CENTER_KINEMATIC_POSITION and move manually fine, but the moment I hit Home, it moves briefly then crashes.
Since then:
Now it loses connection with anything—MCU, T1, T2, and even the Beacon.
Tried:
New USB cable between Pi and Octopus → no change
Dedicated power supply for Pi → no change
Disabled performance mode → no change
Swapped back to old Pi → same errors, so likely not the Pi
I’m completely stuck at this point.
(RatOS v2.1.0 – v2.1.0-RC3-29-g6f87a747)
0 Replies