MCU Timing Error
Consistently getting a timer too close error, about 45 seconds into prints- Tried two different pi's, with and without camera attached. V3.1 running 2.1, issue started 2 updates ago.
Solution:Jump to solution
Right then it's possible it's just filesystem corruption. 2 options:
1. Assume it's just filesystem corruption and reflash ratos to current card, then start shutting down the pi properly (you can do that from the menu in the top right in mainsail)
2. Assume it's a dying sd card, get a new one and flash ratos to that and start shutting down the pi properly....
7 Replies
Seems like dying sd card
Plenty of free memory and minimal system load
It's possible it's just filesystem corruption. Do you have a habit of just flipping the switch on your printer without properly shutting down the pi?
It's an old card for sure.
Pi has seperate power but yes I've definitely hit the power on the pi supply without shutting it down
Solution
Right then it's possible it's just filesystem corruption. 2 options:
1. Assume it's just filesystem corruption and reflash ratos to current card, then start shutting down the pi properly (you can do that from the menu in the top right in mainsail)
2. Assume it's a dying sd card, get a new one and flash ratos to that and start shutting down the pi properly.
So, chicken or the egg situation here, but the restarts have been due to the pi just turning off its web interface during long prints. It'd print fine, but interface wouldn't come back til it rebooted
I guess we'll see if the card fixes that
but the restarts have been due to the pi just turning off its web interface during long printsUnfortunately i've never been able to reproduce this, i have pi's that have been running non-stop for months with no disconnections 🤷♂️ . If you can get me a syslog from when this happens i can try and take a look.
Same- I can't intentionally duplicate it, even reprinting the same file
Grabbed a new card, flashed a new copy and copied the configs over. Just printed a full print no issues