#mcu 'mcu': Unable to connect

3 messages · Page 1 of 1 (latest)

ivory lion
#

I purchased a back-up board as a safeguard. I had to manually install the firmware on my back-up board because it wasn't being detected during the configuration process. I would like to know why one board would be detected and not another? I would gladly pay RatRig to test these boards before sending them out. Also, I'm receiving the following error message on my back-up board:

Klipper reports: ERROR

mcu 'mcu': Unable to connect
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer

prisma plinthBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

gusty stirrup
#

This is a community run discord, if you want to talk to ratrig you should email them directly.

As for why, without the debug.zip (that we ask for in rule #2 #1233461645167169576 message) there is no way to know anything more than what you have told us (which isn't much).