aboutsummaryrefslogtreecommitdiffstats
path: root/docs/BLTouch.md
diff options
context:
space:
mode:
authorKevin O'Connor <kevin@koconnor.net>2021-07-27 13:29:36 -0400
committerKevin O'Connor <kevin@koconnor.net>2021-07-27 13:29:36 -0400
commit37efd1b8f19eadafb45d1d52148d5e21e3fef204 (patch)
treebc3c3851a2e317168bac20bc5d3e6df0ff24694d /docs/BLTouch.md
parentafca515e2c2db240b4d354a0ae665479894ef89b (diff)
downloadkutter-37efd1b8f19eadafb45d1d52148d5e21e3fef204.tar.gz
kutter-37efd1b8f19eadafb45d1d52148d5e21e3fef204.tar.xz
kutter-37efd1b8f19eadafb45d1d52148d5e21e3fef204.zip
docs: Use hash marks for header lines
Consistently use leading hash marks (#) to note section headers. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Diffstat (limited to 'docs/BLTouch.md')
-rw-r--r--docs/BLTouch.md24
1 files changed, 8 insertions, 16 deletions
diff --git a/docs/BLTouch.md b/docs/BLTouch.md
index 6fad76c5..e763fbef 100644
--- a/docs/BLTouch.md
+++ b/docs/BLTouch.md
@@ -1,7 +1,6 @@
# BL-Touch
-Connecting BL-Touch
--------------------
+## Connecting BL-Touch
A **warning** before you start: Avoid touching the BL-Touch pin with
your bare fingers, since it is quite sensitive to finger grease. And
@@ -39,8 +38,7 @@ It's important that the z_hop movement in safe_z_home is high enough
that the probe doesn't hit anything even if the probe pin happens to
be in its lowest state.
-Initial tests
--------------
+## Initial tests
Before moving on, verify that the BL-Touch is mounted at the correct
height, the pin should be roughly 2 mm above the nozzle when retracted
@@ -83,8 +81,7 @@ doesn't stop when you touch the pin.
If that was successful, do another `G28` (or `PROBE`) but this time
let it touch the bed as it should.
-BL-Touch gone bad
------------------
+## BL-Touch gone bad
Once the BL-Touch is in inconsistent state, it starts blinking red.
You can force it to leave that state by issuing:
@@ -106,8 +103,7 @@ right position so it is able to lower and raise the pin and the red
light turns on and of. Use the `reset`, `pin_up` and `pin_down`
commands to achieve this.
-BL-Touch "clones"
------------------
+## BL-Touch "clones"
Many BL-Touch "clone" devices work correctly with Klipper using the
default configuration. However, some "clone" devices may require
@@ -144,8 +140,7 @@ the second query reports "probe: TRIGGERED" then it indicates that
`pin_up_reports_not_triggered` should be set to False in the Klipper
config file.
-BL-Touch v3
------------
+## BL-Touch v3
Some BL-Touch v3.0 and BL-Touch 3.1 devices may require configuring
`probe_with_touch_mode` in the printer config file.
@@ -172,8 +167,7 @@ probe. If configuring this value on a "clone" or older BL-Touch
device, be sure to test the probe accuracy before and after setting
this value (use the `PROBE_ACCURACY` command to test).
-Multi-probing without stowing
------------------------------
+## Multi-probing without stowing
By default, Klipper will deploy the probe at the start of each probe
attempt and then stow the probe afterwards. This repetitive deploying
@@ -203,8 +197,7 @@ to True. On these devices it is a good idea to test the probe accuracy
before and after setting `probe_with_touch_mode` (use the
`PROBE_ACCURACY` command to test).
-Calibrating the BL-Touch offsets
---------------------------------
+## Calibrating the BL-Touch offsets
Follow the directions in the [Probe Calibrate](Probe_Calibrate.md)
guide to set the x_offset, y_offset, and z_offset config parameters.
@@ -218,8 +211,7 @@ far above the nozzle as possible to avoid it touching printed parts.
If an adjustment is made to the probe position, then rerun the probe
calibration steps.
-BL-Touch output mode
---------------------
+## BL-Touch output mode
* A BL-Touch V3.0 supports setting a 5V or OPEN-DRAIN output mode,
a BL-Touch V3.1 supports this too, but can also store this in its