Tutorial, step by step, for Auto Tool Measurement
25 Jul 2016 15:44 #77994
by kylotron
Tutorial, step by step, for Auto Tool Measurement was created by kylotron
I LinuxCNC, i have my small CNC and i have a number of tools.
Now i have the need to realize the machining with different tools and i homemade 2 sensors connected to the input PROBE-IN, one mobile, the 1.33 mm thick, and a fixed, positioned at X741 Y102 coordinates.
I can manually reset the workpiece or the tool relative to the fixed sensor.
But how can i automate the tool zero with respect to the workpiece?
Bernardo
P.S.: sorry for my English, it is generated using google translator.
Now i have the need to realize the machining with different tools and i homemade 2 sensors connected to the input PROBE-IN, one mobile, the 1.33 mm thick, and a fixed, positioned at X741 Y102 coordinates.
I can manually reset the workpiece or the tool relative to the fixed sensor.
But how can i automate the tool zero with respect to the workpiece?
Bernardo
P.S.: sorry for my English, it is generated using google translator.
Please Log in or Create an account to join the conversation.
25 Jul 2016 17:25 - 25 Jul 2016 17:27 #78003
by andypugh
Replied by andypugh on topic Tutorial, step by step, for Auto Tool Measurement
If you start LinuxCNC and look in the sample configs:
sim/axis/remap/manual-toolchange-with-tool-length-switch
You will find a simulated config that does what you want.
You should just need to copy the nc_subroutines and python folders from that configuration to your configuration and then add the relevant section to your INI file:
(edit} And connect your tool-length switch to motion.probe-input
sim/axis/remap/manual-toolchange-with-tool-length-switch
You will find a simulated config that does what you want.
You should just need to copy the nc_subroutines and python folders from that configuration to your configuration and then add the relevant section to your INI file:
[RS274NGC]
...
SUBROUTINE_PATH = nc_subroutines:../../nc_files/remap_lib/common_nc_subs
...
ON_ABORT_COMMAND=O <on_abort> call
#
# ------ remapping toolchange - related codes ----------------------
#
# see python/remap.py for the prolog and epilog handlers
# see nc_files/remap-subroutines for the NGC procedures
#
# the prepare_min.ngc and change_min.ngc are templates - fill in as needed
REMAP=M6 modalgroup=6 prolog=change_prolog ngc=manual_change epilog=change_epilog
(edit} And connect your tool-length switch to motion.probe-input
Last edit: 25 Jul 2016 17:27 by andypugh.
Please Log in or Create an account to join the conversation.
29 Dec 2018 19:27 #123112
by Karri
Replied by Karri on topic Tutorial, step by step, for Auto Tool Measurement
Hey
Does anyone have idea why my machine doesn't care of the "Current Z length",
I'm able to use this example config to measure the tool height, but the machine goes as deep as g-code says, without any matter how long the tool is.
I make first tool measurement with "reference tool" button pressed and second tool measurement unpressed, but second tool goes too deep, like it would be as long as reference tool.
Does anyone have idea why my machine doesn't care of the "Current Z length",
I'm able to use this example config to measure the tool height, but the machine goes as deep as g-code says, without any matter how long the tool is.
I make first tool measurement with "reference tool" button pressed and second tool measurement unpressed, but second tool goes too deep, like it would be as long as reference tool.
Please Log in or Create an account to join the conversation.
30 Dec 2018 10:25 #123139
by andypugh
Replied by andypugh on topic Tutorial, step by step, for Auto Tool Measurement
Does the G-code contain a G43 to apply tool geometry corrections?
Please Log in or Create an account to join the conversation.
30 Dec 2018 16:22 #123162
by Karri
Replied by Karri on topic Tutorial, step by step, for Auto Tool Measurement
Thx for fast reply.
There is g43 in code, but i found out that if there is allready g43 in the "Active g-codes:" -window, the new G43 turns it to G49 and doesn't allow to turn it on again. G43 comes back in active after re-entering "t4 m6" to MDI and going through the lenght measurement.
If i manually enter to MDI new z position it works, but if i enter g43 z100 then it turns g49 mode, and goes to "absolute" value.
There is g43 in code, but i found out that if there is allready g43 in the "Active g-codes:" -window, the new G43 turns it to G49 and doesn't allow to turn it on again. G43 comes back in active after re-entering "t4 m6" to MDI and going through the lenght measurement.
If i manually enter to MDI new z position it works, but if i enter g43 z100 then it turns g49 mode, and goes to "absolute" value.
Please Log in or Create an account to join the conversation.
30 Dec 2018 16:53 - 30 Dec 2018 16:54 #123164
by Leon82
Replied by Leon82 on topic Tutorial, step by step, for Auto Tool Measurement
Use g49g53z0 to return before the tool change.
Or g49
G91g28z0
You should cancel the offset before Channing tools.
Or g49
G91g28z0
You should cancel the offset before Channing tools.
Last edit: 30 Dec 2018 16:54 by Leon82.
Please Log in or Create an account to join the conversation.
30 Dec 2018 17:01 #123165
by Leon82
Replied by Leon82 on topic Tutorial, step by step, for Auto Tool Measurement
I haven't used the tool offset yet on mine because I'm waiting for my r8-er32 holders to come but on some controls like even the fanuc a g54 value affects the tool height input.
Where is g54 value?is it the amount you are off
Where is g54 value?is it the amount you are off
Please Log in or Create an account to join the conversation.
30 Dec 2018 17:18 #123167
by Karri
Replied by Karri on topic Tutorial, step by step, for Auto Tool Measurement
Hi
I think that the measurent function is ok, because its the same which comes with the Linuxcnc and the tool lenght what it shows are correct.
It just change the G43 mode to G49, if the code is containing another G43 when it is allready on.
I think that the measurent function is ok, because its the same which comes with the Linuxcnc and the tool lenght what it shows are correct.
It just change the G43 mode to G49, if the code is containing another G43 when it is allready on.
Please Log in or Create an account to join the conversation.
30 Dec 2018 21:13 - 30 Dec 2018 21:14 #123171
by Karri
Replied by Karri on topic Tutorial, step by step, for Auto Tool Measurement
Ok, i got it working - well atleast for my current needs
Thx for Leon82, i put G49 to manual_change.ngc subroutine.
But the problem was still that every new G43 cancelled previous G43 - So i edited the Autodesk inventor Cam postscript according to this
forums.autodesk.com/t5/fusion-360-comput...om-post/td-p/7168904 and it removed all g43 from codes, because that subroutine will turn those G43 on everytime it runs.
and now it goes through 5 tool change and measurement between.
Thx for all of your help
Thx for Leon82, i put G49 to manual_change.ngc subroutine.
But the problem was still that every new G43 cancelled previous G43 - So i edited the Autodesk inventor Cam postscript according to this
forums.autodesk.com/t5/fusion-360-comput...om-post/td-p/7168904 and it removed all g43 from codes, because that subroutine will turn those G43 on everytime it runs.
and now it goes through 5 tool change and measurement between.
Thx for all of your help
Last edit: 30 Dec 2018 21:14 by Karri. Reason: typos
Please Log in or Create an account to join the conversation.
22 Jan 2022 11:58 #232761
by Karri
Replied by Karri on topic Tutorial, step by step, for Auto Tool Measurement
Hey
Could you edit your answer that:
-you allso need to update python paths to ini file, and probe location etc ...
BR. some clever one who just spent 10h fighthing with the system and then looked down of the example ini file
Could you edit your answer that:
-you allso need to update python paths to ini file, and probe location etc ...
BR. some clever one who just spent 10h fighthing with the system and then looked down of the example ini file
The following user(s) said Thank You: johnbump
Please Log in or Create an account to join the conversation.
Time to create page: 0.081 seconds