Hi there,
What is the correct way to store the actual dimensions/parameters that a G32 probes? I am seeing quite high deviations (>2mm), repeated running will bring that down to <0.02. It would be very good if some of those values could be pre loaded so that it only needs to run once.
My general approach is that the slicer profile/gcode should contain all the knowledge, so 'run command X a few times before you do Y' does not cut it for me. So far I have a G28 followed by a G32 in the start gcode (Cura), but it appears to be losing steps at the extremely fast move of the G32.
I've read some stuff about 4 point vs 6 or 7point calibration which should result in some actual measured variables for 'tower height' and arm radius etc, but I can't find it in the 'commissioning' part of the docs, or here on the forum. Any help, tips or pointers will be appreciated.
