aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKevin O'Connor <kevin@koconnor.net>2021-06-12 14:13:53 -0400
committerKevin O'Connor <kevin@koconnor.net>2021-06-12 14:16:23 -0400
commita0c27571dd0ff841a1464a7df05a8cdd7a2d135d (patch)
treed911b8e32d4b8ba38ab448d65c031b7af19f1f21
parent07004a889d9664eefd65613d79c663d3ca705c20 (diff)
downloadkutter-a0c27571dd0ff841a1464a7df05a8cdd7a2d135d.tar.gz
kutter-a0c27571dd0ff841a1464a7df05a8cdd7a2d135d.tar.xz
kutter-a0c27571dd0ff841a1464a7df05a8cdd7a2d135d.zip
docs: Note previous firmware state issue with TMC2209/TMC2209 in TMC_Drivers.md
If a high UART frequency is used to communicate with TMC2208/TMC2209 drivers then it may not be possible for Klipper to communicate with the drivers until they are reset. Note this in the troubleshooting document. Reported by @matthewlloyd. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
-rw-r--r--docs/TMC_Drivers.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/TMC_Drivers.md b/docs/TMC_Drivers.md
index fee1e75a..fd082bde 100644
--- a/docs/TMC_Drivers.md
+++ b/docs/TMC_Drivers.md
@@ -381,6 +381,12 @@ Make sure that the motor power is enabled, as the stepper motor driver
generally needs motor power before it can communicate with the
micro-controller.
+If this error occurs after flashing Klipper for the first time, then
+the stepper driver may have been previously programmed in a state that
+is not compatible with Klipper. To reset the state, remove all power
+from the printer for several seconds (physically unplug both USB and
+power plugs).
+
Otherwise, this error is typically the result of incorrect UART pin
wiring or an incorrect Klipper configuration of the UART pin settings.