Problem solved and it’s all user error.
Probing just z requires the probe be placed differently than probing x, y, and z.
Over corner
On surface
At some point in my workflow I must have switched to just probing z and did not follow instructions and place the probe on the surface.
Lesson learned.
Thanks!
I am glad I read this article. I would have missed the probes position. Of course I have never used the probe height only the probe corner. I don’t think I will ever use the probe height setting now as I like to double side tape my probe in place during the probe and putting it on the surface rather than the corner for me would suck. I will stick probing the corner always.
Although, I do realize why they do that. If your start point is in the middle of the job you don’t want to go to the corner to probe so it would be natural to have the probe sitting on top of your job, hence the needed offset.
@Julien
I have been struggling with the Z height since day one with my machine. I have double and triple checked my procedure and still cant figure out why it is not giving a proper zero. It seems to be worse when I use the 60° cutter. It is almost as if it can’t calculate the change from the probe to the bit during the tool change. I probed with the BitZero V2 using the x, y, z option and once complete and verify the 0,0,0 dimensions of the probe and they are correct. Then when I start the job, it asks me to change the tool and I follow the prompts and then start the job. I now pause and stop the job immediately and verify Z0 and it can be off either up or down or correct as it has done a few times. I do this so I don’t lose more material as I have scrapped quite a few pieces. The confusing part is that the Z0 is good sometimes from the start. And if the Z0 is good, it stays correct through all the tool changes during the job.
A couple days ago, I ran a part and the Z was 15mm to high. Today I ran my first part and it was around 1.5mm high. The second part I ran today was 11mm low. I have even manually set the zero after stopping the job to place Z0 properly and that has worked until this last time. After I manually set the zero, and then went through the prompts to change the tool, it was 6mm too low and I scrapped out another piece of material. This time, I even set the Z0 with the 60° tool so the bit setter was registering the exact same tool that was used to set Z0 and it was low by 6mm.
X and Y have been basically perfect so this is just a Z issue.
Hopefully this wasn’t too jumbled and makes sense, but there is definitely something wrong. I hope it is just a simple oops on my part, but it is not looking that way so far.
Thank you for any guidance you can give me!!
Having a very similar issue, although mine always seems to be too deep. I have no idea what is causing it, but it sure is frustrating…
For both of you, @MetalwoodMFG and @TheWoodSamaritan .
Step-by-step write down each step you take after the machine’s initialization / homing routine. Write down the words from the screen prompts, too.
From you’re posts, we’re assuming that you both have the BitZero and BitSetter devices properly installed, but check this in your machine settings. If you don’t, nothing said here will make any sense.
Be sure to indicate the location of the BitZero including whether it is completely on top of the part or hanging over the edge of the part.
Indicate whether you use a bit for the XYZ procedure or whether you use a machined dowel and what size.
If you have the newer version 2 of BitZero, does it move during the operation?
Each step can then be evaluated in order, but remember the old saying, “Garbage in; garbage out”.
Please see the test file at:
Document step-by-step how you:
then post a post showing the results and we’ll do our best to work through this with you.
@WillAdams @CrookedWoodTex
Will,
Thank you for this calibration tutorial, but I want to point out one critical thing. The issue isn’t between bits during the running of a program, it’s only on the first bit used in the program that I am having the issue. Once the depth is set properly, the bit changes have been exactly the same depth. Sometimes it takes 3 tries to get it correct, but once it is correct, it stays correct throughout. I have made a handful of signs and the pocket cut out with a .25" endmill has the exact same depth as the letters that were cutout with a .125 bit and then a .0625 bit. (Which is what I wanted as the letters were cut to the same depth as the pocket)
This makes it very confusing as to where the problem is originating. I have manually set the Z0 using the first bit in the program and after the start job menu asks to change the tool, the actual zero was different as I described in my earlier post anywhere from positive 15mm to negative 11mm. (As you can read below, this has increased to a positive 25mm as of today)
Here is what I did step by step today. (I used your calibration file, but tweaked it a bit to show the depths. The top
A) Tried a slightly different method after probing X, Y and Z0 this time. I went to the Load new tool option before clicking on run job, but the bit was at Z0 on the computer screen and was 25mm above the part.
B) Re-loaded the bit sequence again without using the BitZero and it was still at 25mm. At least it repeated as I didn’t move anything.
C) Zeroed the .25 bit manually, clicked run again, clicked load new tool again and it was at the proper Z0 this time.
Is something here that shows that I am either doing it wrong or the machine is not cooperating.
Is there a way to start over and basically reboot this thing? Should I uninstall the software and restart the machine like it is the first time I ever used it?
Thank you for your help. Hopefully we can get this all back on track!!
I think you are getting into issues by letting the existing bit go to the bitsetter then changing it to a probe (Steps 2 & 3). You should either install the probe before the first run to the bit setter or after the existing tool has been measured, using the change tool button to install the probe then have it run to the bit setter again. I think the variability is the difference in stick out from your original tool to the probe.
Seems like you changed bits without going back to the Bitsetter.
You are both correct that I wasn’t running the probe to the bitsetter before probing the corner with the BitZero. I made the assumption that the probe calibrated itself for the z height without using the bitsetter. I will try out your advise later tonight or tomorrow morning and let you know how it went!!
I hope this solves the problem.
I am having the same issue and it is maddening. The instructions for the BitZero v2 are non existent, so are you suppose to use the probe vs a bit every time? Or can you use a bit like in v1.
I do not have the V2, but from what I gather using the probe pins(gauge pins) is the recommended procedure.
To use the BitZero with a probe you must have also have a BitSetter.
Otherwise, you cannot change the probe for a bit since it will result in a piece of metal with an unknown length sticking out of the collet. Which you’d then have to BitZero to measure.
If you are JUST doing Z probing, and not X&Y&Z probing, it probably doesn’t matter what is in the collet. A bit or probe will touch the bottom with equal accuracy.
The probe is supposed to be a perfect cylinder and therefore more accurate (than a bit) when its sides contact the inside of the BitZero V2 circle when doing X&Y&Z probing. The reasoning here is that the flutes of a bit cause gaps or flattened areas of the bit’s cross-section, meaning the bit’s current rotation in the collet can therefore affect its perceived width.
Well, that is correct only if you are executing gcode that is a combination of several toolpaths using different bits; such as end mill and vbit. Then the BitSetter is automating the bit length changes between toolpaths.
Well, that is correct only if you are executing gcode that is a combination of several toolpaths using different bits; such as end mill and vbit. Then the BitSetter is automating the bit length changes between toolpaths.
I don’t think so.
You can’t measure Z with a probe, and then change the probe to a bit, and then run the job.
Hi Jeff,
In the original message I wrote:
To use the BitZero with a probe you must have also have a BitSetter.
Otherwise, you cannot change the probe for a bit since it will result in a piece of metal with an unknown length sticking out of the collet. Which you’d then have to BitZero to measure.
@CrookedWoodTex suggested that this is only true when there are several toolpaths.
To which I responded:
You can’t measure Z with a probe, and then change the probe to a bit, and then run the job.
Here I was suggesting that the proposition is true all the time.
The operations described here are intended to be the only thing that is happening. That is, you cannot put a probe in, zero with that probe using the BitZero, then take out the the probe and put a bit in, and then hit “Start Job”.
edit: this is true with or without a bitsetter.
Apologies for reviving and old thread, but I’m having a similar issue and cannot figure out why this would be happening. I am cutting a very thin piece of stock, too thin to use the BitZero so I am setting X,Y, and Z manually. Once I start the Job Z is reset to too low and is plowing the bit into the stock.
Here are the steps that I am taking. Please note that I’m not changing bits at any time.
I never change the tool throughout this entire process. Any ideas on how this 3mm in Z height is lost?
Thanks,
Seth
Hey Seth,
Everything looks just fine, procedure-wise.
Have you set the correct Z-Axis for your machine and sent the configuration to the machine ?
Is the 1/16" endmill markedly shorter than the probing pin used?
Is the machine bottoming out and losing steps at the bottom of the travel?
This could be the issue. I recently upgraded to the HDZ and did update the machine configuration. I just checked it again however and you have to actually click the Load Defaults and Send Configuration buttons in order to see what settings were selected. The size of the machine did not change, so I did not click the Load Defaults button for the Travel Dimensions. Since I’m troubleshooting now I decide to click that button (thinking it would just reset to the same numbers) but instead I got a popup window showing the Z-plus instead of the HDZ. So maybe I needed to set HDZ under Travel Dimensions as well as Machine Type.
It would be very helpful if we could see what is set without having it hidden behind the button. The Load Defaults and Send Configuration Data buttons make it seem like they are going to perform just those functions when you click them, but instead you get popup windows with settings…
Now that I have HDZ picked in both locations I will do another test.
Thanks!
Seth
