Joined
·
26 Posts
I have a Probotix Asteroid with the ATLas tool length sensor installed and ever since I have set it up I've had a problem with the z-axis resetting itself right after it touches off the sensor and wants to drive the bit right into the table. Let me explain what I do in order so you all can get a better picture.
This is what I do after I set up my material and clamp it in place.
Step 1. I open the file in Linux CNC
Step 2. I set my x and y-axis origins
Step 3. I set the z-axis using my z puck touch off plate
Step 4. I initiate the program and hit continue on the prompt to load my tool (since I have already loaded my tool and touched off with it)
At this point the tool heads over to the ATLas sensor to touch off and as soon as its done doing so, it rapids over a few inches or so. At this point the z-axis resets (for some reason) and the machine attempts to drive the bit straight down into the table. I always have my finger on the 'P' key to pause the program and then I'll cancel the run.
The only way I know how to fix this is to run this first failed attempt and then to reload the the file, touch off the z-axis again with the puck and rerun the program. It usually runs right the second time.
My question is this. Has anyone else ran into this issue? And if so, what have you done to fix it so it runs right the first time every time?
I forgot to add that I do have the correct postprocessor installed straight from the wiki and that I use Aspire to export my g-code.
Thanks in advance for any responses
This is what I do after I set up my material and clamp it in place.
Step 1. I open the file in Linux CNC
Step 2. I set my x and y-axis origins
Step 3. I set the z-axis using my z puck touch off plate
Step 4. I initiate the program and hit continue on the prompt to load my tool (since I have already loaded my tool and touched off with it)
At this point the tool heads over to the ATLas sensor to touch off and as soon as its done doing so, it rapids over a few inches or so. At this point the z-axis resets (for some reason) and the machine attempts to drive the bit straight down into the table. I always have my finger on the 'P' key to pause the program and then I'll cancel the run.
The only way I know how to fix this is to run this first failed attempt and then to reload the the file, touch off the z-axis again with the puck and rerun the program. It usually runs right the second time.
My question is this. Has anyone else ran into this issue? And if so, what have you done to fix it so it runs right the first time every time?
I forgot to add that I do have the correct postprocessor installed straight from the wiki and that I use Aspire to export my g-code.
Thanks in advance for any responses