#Can not update MCU 'mcu' config as it is shutdown

18 messages · Page 1 of 1 (latest)

ancient urchin
#

After every reboot of my Pi, i got this message. I can hit "firmware restart" an everything works fine, but that's not the way to go. Is there a way to delay to put in the config, so the mcu can start and Mainsail is waiting?

ancient urchin
#

after a "firmware restart" everything is here. but after a pi reboot, i got the error from above

ancient urchin
#

No one got a clue?

junior trench
#

Is that your v0?

#

What board it might be that the PI powers the board via usb

ancient urchin
#

It's my V2. The Board is the spider V1.1 and i'm powering it over the breakoutpins vom the Spider

junior trench
#

what does breakout pins mean?

#

from the messages I can see that your mcu is in shutdown that normally indicates an klipper eroor

#

Was that like that from the beginning g or is that something new?

#

Also that question would be better ask in the Voron discord maybe in request help question. There would be much more support people specialized to Voron than here!

ancient urchin
ancient urchin
ancient urchin
junior trench
#

Open a help ticket there

hollow halo
ancient urchin
hollow halo
# ancient urchin nothing, sorry

From my side, I could see that everything worked fine as long as [mcu rpi] was not declared in the printer.cfg

Knowing that I use [mcu rpi] only for the ADXL345, so I created a macro file "macros_adxl345.cfg" integrating the Klipper ADXL345 configuration, and a [include macros_adxl345.cfg] in printer.cfg

After calibrated input_shaper with the ADXL345, I comment out #[include macros_adxl345.cfg] in the printer.cfg to disable the ADXL345 configuration which includes [mcu rpi], and everything is back to normal.