aboutsummaryrefslogtreecommitdiffstats
path: root/docs/Sensorless_Homing.md
diff options
context:
space:
mode:
authorKevin O'Connor <kevin@koconnor.net>2020-11-16 18:47:32 -0500
committerKevin O'Connor <kevin@koconnor.net>2020-11-18 20:10:21 -0500
commit15b5dbaf8ffac8e3889b2cc0ba7a61bce1e9fb6f (patch)
treefbb9fb7be4266684eb67f0b7d36379b523f8a240 /docs/Sensorless_Homing.md
parent9fd8f7761e424807c9f69165430e562bb2ab0390 (diff)
downloadkutter-15b5dbaf8ffac8e3889b2cc0ba7a61bce1e9fb6f.tar.gz
kutter-15b5dbaf8ffac8e3889b2cc0ba7a61bce1e9fb6f.tar.xz
kutter-15b5dbaf8ffac8e3889b2cc0ba7a61bce1e9fb6f.zip
docs: Move config reference information to new Config_Reference.md
Move all the config reference information from files in the config/ directory to a new Config_Reference.md document. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Diffstat (limited to 'docs/Sensorless_Homing.md')
-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 d8f95fdb..949866a3 100644
--- a/docs/Sensorless_Homing.md
+++ b/docs/Sensorless_Homing.md
@@ -61,7 +61,7 @@ The name of the virtual end stop pin is derived from the name of the TMC2130 sec
The TMC2130 and TMC5160 have both a `diag0_pin` and `diag1_pin` in most known hardware the `diag1_pin` is appropriate. In order for klipper to correctly configure the driver for sensorless homing, the correct configuration property name `diag0_pin` or `diag1_pin` must be used. Which is used is determined by which driver pin is connected to the MCU pin.
-ATTENTION: This guide only mentions the mandatory parameters and the ones needed to set up sensorless homing. There are many other options to configure on a TMC2130, make sure to take a look at `config/example-extras.cfg` for all the available options.
+ATTENTION: This guide only mentions the mandatory parameters and the ones needed to set up sensorless homing. There are many other options to configure on a TMC2130, make sure to take a look at [config reference](Config_Reference.md#tmc2130) for all the available options.
## Testing of SPI/UART communication
Now that the stepper driver is configured, let's make sure that Klipper can communicate with the TMC2130 by sending the following extended G-Code command to the printer: