From 8eceb9d40ad4206b70a7a563eade228b807bd417 Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Fri, 19 Mar 2021 08:35:21 -0400 Subject: [PATCH] mcu: Update hints for "Timer too close" and "No next step" errors In practice, these errors are usually due to problems on the host computer instead of problems with communication. Signed-off-by: Kevin O'Connor --- klippy/mcu.py | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/klippy/mcu.py b/klippy/mcu.py index ec2cce7a..849f8deb 100644 --- a/klippy/mcu.py +++ b/klippy/mcu.py @@ -824,7 +824,12 @@ class MCU: return False, '%s: %s' % (self._name, stats) Common_MCU_errors = { - ("Timer too close", "No next step", "Missed scheduling of next "): """ + ("Timer too close", "No next step"): """ +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.""", + ("Missed scheduling of next ",): """ This is generally indicative of an intermittent communication failure between micro-controller and host.""", ("ADC out of range",): """