aboutsummaryrefslogtreecommitdiffstats
path: root/docs/FAQ.md
diff options
context:
space:
mode:
authorKevin O'Connor <kevin@koconnor.net>2019-11-07 16:50:52 -0500
committerKevin O'Connor <kevin@koconnor.net>2019-11-07 16:50:52 -0500
commit3665e9fc53682ea3cddf49c24e10974c78f2d28c (patch)
tree677c7f8e70c00a5cf985de2ce84084d2d2a847b7 /docs/FAQ.md
parented610a6600dd982623ad79409f430a522910b202 (diff)
downloadkutter-3665e9fc53682ea3cddf49c24e10974c78f2d28c.tar.gz
kutter-3665e9fc53682ea3cddf49c24e10974c78f2d28c.tar.xz
kutter-3665e9fc53682ea3cddf49c24e10974c78f2d28c.zip
docs: Recommend safe_z_home over homing_override
Update BLTouch.md, FAQ.md, and sample-probe-as-z-endstop.cfg to recommend using a safe_z_home config section over a homing_override config section. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Diffstat (limited to 'docs/FAQ.md')
-rw-r--r--docs/FAQ.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/FAQ.md b/docs/FAQ.md
index 56490520..e3e3b163 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -211,9 +211,10 @@ the desired movement to the "custom g-code" section of your slicer.
If the printer requires some additional movement as part of the homing
process itself (or fundamentally does not have a homing process) then
-consider using a homing_override section in the config file. If you
-need to move a stepper for diagnostic or debugging purposes then
-consider adding a force_move section to the config file. See
+consider using a safe_z_home or homing_override section in the config
+file. If you need to move a stepper for diagnostic or debugging
+purposes then consider adding a force_move section to the config
+file. See
[example-extras.cfg](https://github.com/KevinOConnor/klipper/tree/master/config/example-extras.cfg)
for further details on these options.