After a year I tried using the bitzero. I’m still a little unclear as to the big deal of it.
Anyhow, I hook it up, everything works great, so I go to probe, it probes, everything’s fine, THEN when I check the measurements, it is exactly .5 lower than the board it was sitting on for the measurement. This is too stupid not to be something i’m missing.
bit touching the poart should be zero Z it shows 0.508
No, it does not. It knows where the tip of the tool is relative to machine Z-axis zero, but without a measurement of the tool, it does not know the offset.
The bitzero determines the Z stock zero based on the tip of the bit, once the stock Zero is determined it has to measure the bit/spindle combo to determine where the Z axis is at compared to the Z zero of you stock to ensure it knows how far to actually lower the Z axis to reach the desired DOC you programed in for the tool path parameters. The bit/spindle combo height is different each time you change the bit relative to the spoil board/stock, therefore it measures it to make sure it drive to the correct setting.
Think of it this way: The first tool measurement is a reference for further tools.
When you change tools thereafter, it compares the Z position of the tooltip touching the bitsetter to the previous Z position (tool offset), then applies the difference as an offset to the Z height of your part to get the new tool in the same position.
If you’re only using one tool, or resetting the Z zero for each tool, then the tool measurement is redundant.
I personally liked the old way. Measure the first tool on initialize for the reference. Set zero. Measure any new tool (On a program toolchange, or a manual toolchange).
Is it the case that this would only matter for subsequent bit changes? For example, if a user used the BitZero for endmill #1, going to the BitSetter right afterwards to measure endmill #1 should not matter. But, if a cut requires an endmill change, then the BitSetter would be important to measure the offset for endmill #2?