117 Commits (01e4b0c067c23defa78a7c68bef872f132728875)

Author SHA1 Message Date
Scott Lahteine 9b9350e010 Fix jerky Z motion between probes
Suggested by #9375
7 years ago
Scott Lahteine 73e32925e4 References are better for array args 7 years ago
Scott Lahteine 728acf521c Followup to #8706 7 years ago
Scott Lahteine ae663a4198 PROBE_DOUBLE_TOUCH => MULTIPLE_PROBING 7 years ago
Scott Lahteine a67cf78c6b Clean up whitespace, spacing 7 years ago
LVD-AC 65f365333f [2.0.x] G33 probe error handling 7 years ago
Scott Lahteine 80ada58818 One fewer function call in probe_pt 7 years ago
Scott Lahteine c0000a0cdc Move servo code to modules/servo.* 7 years ago
Scott Lahteine 3bba7d60f3 No retroactive changes with M851 Z
If using babystep to adjust the Z probe offset, the axis will move and the mesh will be updated at the same time, causing a doubling of the Z offset over the rest of the print.

To correct for this, the current Z position would need to be modified in the opposite direction, canceling out the additional Z offset added to the mesh. This would be confusing to users, and moreover it would not be accurate without also taking the current Z fade level and current Z height into account.

It might make sense to change the mesh in the case where no babystepping is taking place, but this could be considered an undesirable side-effect of changing the `zprobe_zoffset`.

One way to remedy this would be to return to storing the mesh with `zprobe_zoffset` included, then subtracting `zprobe_zoffset` from the returned Z value. Thus, a babystep moving the Z axis up 1mm would subtract 1 from `zprobe_zoffset` while adding 1 to all mesh Z values.

Without including the `zprobe_zoffset` in the `z_values` there is no safe way to alter the mesh in conjunction with babystepping, although it's fine without it.
7 years ago
LVD-AC e334efb2a7 PROBE_MANUALLY etc. 7 years ago
Thomas Moore f34c3597dc Add delta_height variable in lieu of using home_offset 7 years ago
Scott Lahteine f8393a0908 Operate in Native Machine Space 7 years ago
Scott Lahteine 3e3911fb81 Use planner.leveling_active for all leveling systems 7 years ago
Scott Lahteine 9a930ebec2 Make leveling_is_active a macro 7 years ago
Scott Lahteine 965b0ab53e Spacing adjustments 7 years ago
Thomas Moore ddbd4b73e0 Move LPC1768 framework out of Marlin source folder 7 years ago
Scott Lahteine 551752eac7 Consolidate "bedlevel" code 7 years ago