diff options
| author | Kevin O'Connor <kevin@koconnor.net> | 2021-03-19 08:35:21 -0400 |
|---|---|---|
| committer | Kevin O'Connor <kevin@koconnor.net> | 2021-03-19 08:35:21 -0400 |
| commit | 8eceb9d40ad4206b70a7a563eade228b807bd417 (patch) | |
| tree | 06d2c355ca16e2682bbbdf1b610941e281073341 /klippy | |
| parent | 6c9404ac0c3925ccaa03f1a2046fe00499758495 (diff) | |
| download | kutter-8eceb9d40ad4206b70a7a563eade228b807bd417.tar.gz kutter-8eceb9d40ad4206b70a7a563eade228b807bd417.tar.xz kutter-8eceb9d40ad4206b70a7a563eade228b807bd417.zip | |
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 <kevin@koconnor.net>
Diffstat (limited to 'klippy')
| -rw-r--r-- | klippy/mcu.py | 7 |
1 files changed, 6 insertions, 1 deletions
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",): """ |