klippy shutdown after MEASURE_COREXY_BELT_TENSION
Hey guys,
I just ran the MEASURE_COREXY_BELT_TENSION macro to check my belt tension, but after a few minutes klippy rebooted and the log showed this...
20:25:03
MCU 'mcu' shutdown: Move queue overflow
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
20:25:03
Testing frequency 133 Hz
20:25:02
Testing frequency 132 Hz
20:25:02
Testing frequency 131 Hz
I use a raspi 3a+ with an octopus 1.1.
Any idea what went wrong?
regards!
5 Replies
evolutionary-blush•16mo ago
tried it again, this time if failed again, but with a different error:
Previous MCU 'mcu' shutdown: Timer too close
This often indicates the host computer is overloaded. Check
for other processes consuming excessive CPU time, high swap
usage, disk errors, overheating, unstable voltage, or
similar system problems on the host computer.
When doing the command, switch to the machine tab and see what the CPU load is like. I suspect the 3a isn't powerful enough
evolutionary-blush•16mo ago
ok. will do that soon. The "Generate Shaper Graphs" macro is working.... no idea if that creates less cpu load?
you were right, cpu load is jumping between 10% and almost 100%. Is there another way to check if the belt tension is right?
and I have a raspi 3b+ somewhere.. would this help maybe?
Hey, please make sure you're using RatOS 2.0 32-bit
the 3a doesn't have enough memory for 64-bit
(this is in the docs)
evolutionary-blush•16mo ago
Oh. I haven’t updated to 2.0 yet. Good advice!!