I am confused again.
Maybe someone has figured this out already.
I'm talking bigfix 2.0.x 64876f7
For Configs there is;
//#define HOMING_BACKOFF_POST_MM { 2, 2, 2 } // (mm) Backoff from endstops after homing
//#define Z_AFTER_HOMING 10 // (mm) Height to move to after homing Z
//#define Z_AFTER_PROBING 5
When I do a Z home with Z_AFTER_HOMING undefined, Z_AFTER_PROBING = 15 and HOMING_BACKOFF_POST_MM { 0, 0, 20 }
the G28 Z result is Z home, then move to 20 then to 15 It moves to 15 because Z_AFTER_HOMING is undefined. If Z_AFTER_HOMING = 10, the G28 Z result is Z home, then move to 20 then to 15 even though Z_AFTER_HOMING = 10. There seems to be a little redundancy here helping me be confused.
Why does both Z_AFTER_HOMING and HOMING_BACKOFF_POST_MM { 2, 2, 2 } exist?
AND why does Z_AFTER_PROBING override Z_AFTER_HOMING if it is bigger.
Has this been over thought or is there logic behind it?
with backoff = 20, homing = 30, probing = 15; after probing it goes to 15. After homing it goes to 30. Backoff appear to be unused at least for Z. My backoff for X, Y = 0, 0.
It seems like Z_AFTER_HOMING has no purpose.
