3diy
/
klipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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>
This commit is contained in:
Kevin O'Connor 2021-03-19 08:35:21 -04:00
parent 6c9404ac0c
commit 8eceb9d40a
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
klippy/mcu.py
View File

@ -824,7 +824,12 @@ class MCU:
return False, '%s: %s' % (self._name, stats) return False, '%s: %s' % (self._name, stats)
Common_MCU_errors = { 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 This is generally indicative of an intermittent
communication failure between micro-controller and host.""", communication failure between micro-controller and host.""",
("ADC out of range",): """ ("ADC out of range",): """