Machine Initialization…nothing new here except not probing
Zeroing process…new steps to probe bit after zeroing regardless of whether that was with a BitZero or manual. Process is the same after zeroing is complete.
Job start process…difference here is that after probing bit length CM compares it against the stored bit length for validation and acts accordingly if things are out of sync.
Mid job zeroing process…difference here is that a new Z’ is persisted along with WZ being updated as per tool length delta.
A happy path workflow where the user does what he is supposed to. Followed by one where he does not. CM is able to detect that he has not and prevents the job from being ran until the situation is corrected. This is not something the current workflow can detect and would allow the user to shoot themselves in the foot.
NOTE: All this is predicated on there being a method to store a Z’, either in a previously unused grbl setting or in a file in CM.