Step 2 is redundant and was C3D’s solution to addressing issues where individuals where swapping out tooling after the initial measurement taken by the bitsetter after the machine initialization and prior to setting Z-zero. The result was invalid offsets being calculated and users where either air cutting or have the bit plunge into their stock/table, etc…
Many have mentioned that they didn’t like this however at the same time understand why it was added but it does seem to have met the intent since I rarely see posts (or at least way less then before) of users mentioning that their machine keeps air cutting or plunging into their material/table.
The initialization process and the starting a job are redundant but necessary. Even though it is aggregating it helps keep you from making mistakes. When I started in the old days there was no BitZero or BitSetter so when I got those accessories I had to learn a new work flow. After several years of using both I have gotten used to it.
The one thing that really bugs me is the message about do you want to zero when first starting up. I wish I could uncheck getting that message. It is just an extra step that I have to acknowledge but I guess it also keeps you from making a mistake.
I use the center a lot for jobs so when the initialization asks for a tool I generally put in a vee bit to help center the job accurately. The last job bit is still in the bit and is seldom a vee bit. The last X Y and Z zero are persistent over power cycles. However that is dependent on the homing cycle. The inductive switches are pretty accurate but you can be a few thousands off each power cycle. I always use the rapid positions to double check the X and Y positions before starting the same job after a break. I also use the bottom of material a lot and I always check the Z +6MM just in case. The beauty of using the bottom of the material is I seldom have to set Z zero and the side benefit is my spoilboard does not get eaten up.
If you run the same job over and over then turn off your BitSetter and power cycle. I have noticed that if you turn off the BitSetter and do not power cycle and initialize the jog cuts an air job. I think it has to do with the internal coordinates set up during initialization and are over ridden by the setting of X Y and Z zeros. What ever the reason it cuts an air job. You still get prompted for the tool every time you start a job but again that is for success of your job.