Work with probe
When I get a new tool that I am putting in a dedicated holder I use a GCode file that measures the tool using the tool setter and writes the length to the tool table.
John
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
You will have to remove the extra .txt extension from two file to get back to the original file names. I had to add that to make the forum system happy.
Attachments:
Please Log in or Create an account to join the conversation.
What I actually did was to steal G59.3 to store Z0 when the nose of the spindle is on the tool setter. Then when I measure a tool I use the difference between G59.3 Z0 with the G59.3 tool setter trip point. That tells me how long the tool sticks out of the spindle. That number is record as the tool length in the tool table. When I touch off on the stock i record that value in parameter #4001 to #4008 corresponding to G54 - G59.2. With that data the tool offset can be calculated during the tool change.I don't know for sure, but I wonder if he sets the 3d probe as a tool number and sets a Z offset for it. That offset would be set at the table surface (the same surface the tool setter is referenced from) then your 3dprobe is relative to the toolsetter.
Please Log in or Create an account to join the conversation.
I like that you can still use a 3d probe to probe the top surface (different from Gmoccapy style).
Mixing probed and unprobed tools is excellent.
How do you preset repeatable tools? maybe you already said.
I was set on pruducing the gmoccapy/versa style in a python remap for linuxcnc but maybe I'll look at this more first.
Please Log in or Create an account to join the conversation.
Thank you for the files!Here are my files. I store the probe length in parameter #5162 in the linuxcnc.var file.
You will have to remove the extra .txt extension from two file to get back to the original file names. I had to add that to make the forum system happy.
Unfortunately linuxcnc.var.txt does not load, maybe you can add the files as a zip?
Please Log in or Create an account to join the conversation.
[PROBE]
LENGTH = 4.027841 <- Adjust this value as needed for your probe.
The only thing to see in the linuxcnc.var file is this. You need to add the 4001 to 4008 lines to your file while LinuxCNC is not running. Just use 0.000000 when adding them. This is where the Z touch-off will be stored for each coordinate system G54 to G59.2. Adding these to the file makes the values persistent.
4001 -9.902594
4002 -10.541490
4003 -9.413268
4004 0.000000
4005 0.000000
4006 0.000000
4007 0.000000
4008 0.000000
5161 8.526600
5162 3.196200
5163 0.000000
Please Log in or Create an account to join the conversation.
How do you preset repeatable tools?
I have a G-Code file that I run when I want to measure a tool and record the value in the tool table. I also use a G-Code file to measure the tool setter. I use inches so those I have tested but I also have files for metric but those have not been tested.''
Wow, The editor and quoting doesn't work very well anymore.
Attachments:
Please Log in or Create an account to join the conversation.
Thanks mate that is the kick in the bum I needed.
cmorley post=229356 userid=482
I don't know for sure, but I wonder if he sets the 3d probe as a tool number and sets a Z offset for it. That offset would be set at the table surface (the same surface the tool setter is referenced from) then your 3dprobe is relative to the toolsetter.
Please Log in or Create an account to join the conversation.
But the Cmorley's way seems the safest in my opinion. If I understand it correctly it will give me relative Z difference between actual cutter and 3d probe. I will definitely give this a go both probes are spring loaded so what can go wrong
I had to move the machine today so it is all disconnected, but when it is all back together I will be researching more.
Please Log in or Create an account to join the conversation.