Frequent Issue - MCU 'mcu' shutdown: Timer too close
This Issue (shown in pictures) happens pretty frequently.
Any idea why?
Logs attached.
9 Replies
Is that klipper.log from right after the issue? It doesn't have the MCU error in it
what is klipper running on and what other peripheral devices are connected besides the mcu?
This is what I have connected to my
Raspberry Pi 4 8GB RAM with
MicroSD Card 64gb V10 / U10:
- Klipperscreen.
- No webcam attached.
- Beacon rev h
- BTT Octopus V1.1 with attached:
* P1000 for the goliath hotend.
* BTT SFS 2.0.
* CPAP fan.
that doesnt seem like it should be too much for a pi4... can you get a console on the pi and see if any other processes are consuming cpu resources?
Console? What is this?
A terminal window.... Command line?
Anything that can give you a look at what processes are running and how much cpu is being used
Ahh okay
Actually the Beacon is attached to the Raspi Pi
I had this issue too. Problem is probably the SD card. Changed my card today and after that everything was ok again
Another thing could be to much resources used on the pi but with what you have listed i dont think thats the issue
I got the same issue. It started yesterday, just after I powered on the printer and disappeared after reset. Today happened again, also at power up 🤔
All components are up to date, and I am not doing anything really special (except maybe of running the Ebb36 on CAN)