11 Commits (2c8d12d3ec229c658ab22f4d231f1fd9f8381dee)

Author SHA1 Message Date
Scott Lahteine 0feeef2604 Update copyright in headers 6 years ago
Scott Lahteine d556dc1865
Fix and improve EEPROM storage (#12054)
* Clean up Temperature PID
* Improve EEPROM read/write/validate
* Group `SINGLENOZZLE` saved settings
* Group planner saved settings
* Group filament change saved settings
* Group skew saved settings
* Group `FWRETRACT` saved settings
6 years ago
Scott Lahteine cee34f7290
Followup for BABYSTEP_HOTEND_Z_OFFSET (#11916) 6 years ago
InsanityAutomation 1104054d73 2.0 IDEX Independent z offset and other fixes (#11862)
* Add Formbot Raptor board

Co-Authored-By: InsanityAutomation <insanityautomation@users.noreply.github.com>

* Add a second Z probe Z offset

Co-Authored-By: InsanityAutomation <insanityautomation@users.noreply.github.com>

* Modify method to utilize live adjustment of hotend z offset

Should probably move config option to babystepping and rename as it may now apply to all multiextruder systems

* Move config item and catchup other code to current method
6 years ago
Scott Lahteine 4793c34c53 Fix M290 boolval bug
Fix #8577
7 years ago
Scott Lahteine d18d40e1d6 M290 report on change, P0 to leave Probe Z Offset alone 7 years ago
Scott Lahteine be00e421a7 Patch up M290, M851 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
Scott Lahteine 50f09cc029 Miscellaneous cleanup 7 years ago
Scott Lahteine c938273bd5 Coding standard patch of M290 7 years ago
Scott Lahteine bd78ca0ee3 Add M290 Babystepping 7 years ago