Is there a reason in the probing workflow, it probes, measures tool and then goes back to the probe?
Usually after a probe you are going to start a job. So it seems redundant to move back to the probe location, when the next thing you are going to do is start a program, which then measures the tool yet again. Why not just stay by the bitsetter location?
Maybe i missed something?
There are instances where one re-probes, so I believe it was done in support of that.
Love how much faster things are, but that one particular thing really doesn’t make sense to me. Everything else was an improvement minus that one workflow. Maybe that should be an option to configure?
I probably should go download the official release, i’m still technically running the beta, not sure if it really matters though.
If someone wanted to reprobe they could just rapid to current XY instead.
Moving back to XY after measuring means you just have to move back to the tool change location when you start the job.
It not a huge deal, just seems like a waste of time.