aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorJordan Woyak <jordan.woyak@gmail.com>2021-02-11 13:52:46 -0600
committerGitHub <noreply@github.com>2021-02-11 14:52:46 -0500
commit4b32067565ac40055580b9bfd83eb5dec562e19b (patch)
tree902755279267c591d92a818e2e3a597fb4ab7cca /docs
parent03b62ca04f7de4f332b71791298617e92c94a5cc (diff)
downloadkutter-4b32067565ac40055580b9bfd83eb5dec562e19b.tar.gz
kutter-4b32067565ac40055580b9bfd83eb5dec562e19b.tar.xz
kutter-4b32067565ac40055580b9bfd83eb5dec562e19b.zip
docs: Fix typo in Sensorless_Homing.md (#3916)
Signed-off-by: Jordan Woyak <jordan.woyak@gmail.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/Sensorless_Homing.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Sensorless_Homing.md b/docs/Sensorless_Homing.md
index 949866a3..140baede 100644
--- a/docs/Sensorless_Homing.md
+++ b/docs/Sensorless_Homing.md
@@ -36,7 +36,7 @@ driver_SGT: # tuning value for sensorless homing
The above snippet configures a TMC2130 for the stepper on the X axis. Make sure to fill in the missing values based on your configuration.
-The `driver_SGT` value describes the threshhold when the driver reports a stall. Values have to be in between -64 (most sensitive) and 64 (least sensitive). On some TMCs like the TMC2209 this value doesn't exist in this form as the hehavior is different to the TMC2130. In the case of the TMC2209 the threshold is defined by the `driver_SGTHRS` value in the config and go from 0 (least sensitive) to 255 (most sensitive). Have a look at the datasheet of your specific TMC to avoid mistakes.
+The `driver_SGT` value describes the threshhold when the driver reports a stall. Values have to be in between -64 (most sensitive) and 64 (least sensitive). On some TMCs like the TMC2209 this value doesn't exist in this form as the behavior is different to the TMC2130. In the case of the TMC2209 the threshold is defined by the `driver_SGTHRS` value in the config and go from 0 (least sensitive) to 255 (most sensitive). Have a look at the datasheet of your specific TMC to avoid mistakes.
If you have a CoreXY machine, you can configure one stepper driver for X and the other for Y homing as you would on a cartesian printer. Be aware that Klipper needs both `DIAG1` pins connected to the MCU. It is not sufficient to use only one signal from one of the stepper drivers (as it is possible on e.g. Marlin).