aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorredstone99 <redstone@gmail.com>2022-11-22 18:55:43 -0500
committerGitHub <noreply@github.com>2022-11-22 18:55:43 -0500
commit14eec15267d395d0f72109838bf67c4080f30d4e (patch)
tree8d0d70517a7ca8c9bfea1aa7027acb9f5c60a21a /docs
parentc51f169c06921152a2e9c386016660d0bb09f767 (diff)
downloadkutter-14eec15267d395d0f72109838bf67c4080f30d4e.tar.gz
kutter-14eec15267d395d0f72109838bf67c4080f30d4e.tar.xz
kutter-14eec15267d395d0f72109838bf67c4080f30d4e.zip
safe_z_home: Fix final z hop to use relative z coordinates (#5879)
After a G28 z-axis homing, there is a final z hop. It was hoping to height z_hop as an absolute z height rather than relative. If the z-axis home leaves the head at a z height higher than z_hop, e.g. because you were using a probe to do z homing, this meant that it was z hopping in the negative z direction, which could result in crashing the toolhead. Signed-off-by: Joshua Redstone <redstone@gmail.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/Config_Changes.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/Config_Changes.md b/docs/Config_Changes.md
index bbf81fe1..ada67ad0 100644
--- a/docs/Config_Changes.md
+++ b/docs/Config_Changes.md
@@ -8,6 +8,12 @@ All dates in this document are approximate.
## Changes
+20221114: Previously, with safe_z_home, it was possible that the
+z_hop after the g28 homing would go in the negative z direction.
+Now, a z_hop is performed after g28 only if it results in a positive
+hop, mirroring the behavior of the z_hop the occurs before
+the g28 homing.
+
20220616: It was previously possible to flash an rp2040 in bootloader
mode by running `make flash FLASH_DEVICE=first`. The equivalent
command is now `make flash FLASH_DEVICE=2e8a:0003`.