diff options
| author | Dmitry Butyugin <dmbutyugin@google.com> | 2023-09-30 02:46:42 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-09-29 13:46:42 -0400 |
| commit | a4cd0336bdd9df78c1b2a1296a481e84efc2b821 (patch) | |
| tree | cc2b4a3a02eca0ff19ae2e2973e7976d663b8abe /docs | |
| parent | 21b784297916ac31b0e83161976effea048b53cb (diff) | |
| download | kutter-a4cd0336bdd9df78c1b2a1296a481e84efc2b821.tar.gz kutter-a4cd0336bdd9df78c1b2a1296a481e84efc2b821.tar.xz kutter-a4cd0336bdd9df78c1b2a1296a481e84efc2b821.zip | |
idex_modes: Fixed the case when carriages home in the same direction (#6310)
Previous version of the code assumed that dual carriages home away
from each other, which is not true on some machines, which have the
second dual carriage homing on the first carriage. The new code
correctly identifies the relative order of the carriages now.
This fixes discrepancies between the documentation and the actual
implementation of the carriages kinematic ranges calculation.
Notes about dual_carriage homing and proximity checks changes
Fixed clearing of homing state after homing in certain modes
In case of multi-MCU homing it is possible that the carriage position
will end up outside of the allowed motion range due to latencies in data
transmission between MCUs. Selecting certain modes after homing could
result in home state clearing instead of blocking the motion of the
active carriage. This commit fixes this undesired behavior.
Signed-off-by: Dmitry Butyugin <dmbutyugin@google.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/Config_Changes.md | 9 | ||||
| -rw-r--r-- | docs/Config_Reference.md | 8 |
2 files changed, 17 insertions, 0 deletions
diff --git a/docs/Config_Changes.md b/docs/Config_Changes.md index 063af8ac..6d83238d 100644 --- a/docs/Config_Changes.md +++ b/docs/Config_Changes.md @@ -8,6 +8,15 @@ All dates in this document are approximate. ## Changes +20230826: If `safe_distance` is set or calculated to be 0 in `[dual_carriage]`, +the carriages proximity checks will be disabled as per documentation. A user +may wish to configure `safe_distance` explicitly to prevent accidental crashes +of the carriages with each other. Additionally, the homing order of the primary +and the dual carriage is changed in some configurations (certain configurations +when both carriages home in the same direction, see +[[dual_carriage] configuration reference](./Config_Reference.md#dual_carriage) +for more details). + 20230810: The flash-sdcard.sh script now supports both variants of the Bigtreetech SKR-3, STM32H743 and STM32H723. For this, the original tag of btt-skr-3 now has changed to be either btt-skr-3-h743 or btt-skr-3-h723. diff --git a/docs/Config_Reference.md b/docs/Config_Reference.md index 25e7cc46..24139183 100644 --- a/docs/Config_Reference.md +++ b/docs/Config_Reference.md @@ -2065,6 +2065,14 @@ in this section (CARRIAGE=0 will return activation to the primary carriage). Dual carriage support is typically combined with extra extruders - the SET_DUAL_CARRIAGE command is often called at the same time as the ACTIVATE_EXTRUDER command. Be sure to park the carriages during deactivation. +Note that during G28 homing, typically the primary carriage is homed first +followed by the carriage defined in the `[dual_carriage]` config section. +However, the `[dual_carriage]` carriage will be homed first if both carriages +home in a positive direction and the [dual_carriage] carriage has a +`position_endstop` greater than the primary carriage, or if both carriages home +in a negative direction and the `[dual_carriage]` carriage has a +`position_endstop` less than the primary carriage. + Additionally, one could use "SET_DUAL_CARRIAGE CARRIAGE=1 MODE=COPY" or "SET_DUAL_CARRIAGE CARRIAGE=1 MODE=MIRROR" commands to activate either copying or mirroring mode of the dual carriage, in which case it will follow the |