a4cd0336bd
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> |
||
|---|---|---|
| .. | ||
| chelper | ||
| extras | ||
| kinematics | ||
| clocksync.py | ||
| configfile.py | ||
| console.py | ||
| gcode.py | ||
| klippy.py | ||
| mathutil.py | ||
| mcu.py | ||
| msgproto.py | ||
| parsedump.py | ||
| pins.py | ||
| queuelogger.py | ||
| reactor.py | ||
| serialhdl.py | ||
| stepper.py | ||
| toolhead.py | ||
| util.py | ||
| webhooks.py | ||