V-Core 3 - Octopus 1.1 and RPi connection issue - 'mcu': Unable to connect

After first bed mesh probing with Beacon H the printer stopped responding. Klipper returns the error: "mcu 'mcu': Unable to connect". Reinstallation from scratch (new images for the Pi and the board)didn't help. It seems RPi works fine, but it still cannot connect to the board. Tried flashing with RPi and PC via DFU, none of them worked. Under USB devices the unknown one shows, similar to yours, but I don't see DFU connection. Can I check something else or is the bard fired?
No description
No description
No description
7 Replies
cgrr
cgrrβ€’3mo ago
When I get that message it usually means loose connection at the beacon. I reseat the connector. reboot and then it is fine.
MZ
MZβ€’3mo ago
Reconnected at the beacon - no change. Hi @blacksmithforlife πŸ‡ΊπŸ‡Έ here's the description of the issue.
MZ
MZβ€’3mo ago
Interestingly, RatOS configurator tool/wizard was able to flash the board or at least that's what it showed πŸ€”
No description
No description
MZ
MZβ€’3mo ago
It works again with a new board.
E-TF[102] Riker
E-TF[102] Rikerβ€’4w ago
Hey, i just suffered a catastrophic failure of my printer where the umbilical got melted and shorted the cables inside. I also now have this issue. Have the exact same steps as you and still doesnt work. Ive ordered a new board to see what happens but i am wondering if you ever got your old one working again
MZ
MZβ€’4w ago
Hey, no. I've noticed that there are more LEDs lit up on the new one, so definitely, the old one was cooked in more than one place. πŸ˜… @E-TF[102] Riker good luck with the new board!
E-TF[102] Riker
E-TF[102] Rikerβ€’4w ago
Thank you! πŸ™