option wear tool lathe
16 Jan 2015 00:43 - 16 Jan 2015 00:44 #55037
by jlviloria
option wear tool lathe was created by jlviloria
regards,
I'm looking for information to see how I can adapt my lathe to work with tool wear.
I installed the "fanuc_tool_change_style" patch but have problems crashes.
I do not care so much that I touch tool change of an machining center (t01 m6 g43 h1).
I really need is after the end of the machining cycle is able to repass the cut playing with a value add or subtract the compensation of the tool. without changing a value in the program.
compensation = 100 mm
wear = 0.05 mm
any suggestions for how to do this?
thanks,
Jorge Viloria
I'm looking for information to see how I can adapt my lathe to work with tool wear.
I installed the "fanuc_tool_change_style" patch but have problems crashes.
I do not care so much that I touch tool change of an machining center (t01 m6 g43 h1).
I really need is after the end of the machining cycle is able to repass the cut playing with a value add or subtract the compensation of the tool. without changing a value in the program.
compensation = 100 mm
wear = 0.05 mm
any suggestions for how to do this?
thanks,
Jorge Viloria
Last edit: 16 Jan 2015 00:44 by jlviloria.
The following user(s) said Thank You: joekline9
Please Log in or Create an account to join the conversation.
16 Jan 2015 03:02 #55040
by andypugh
Instead of that have a look at the sim/axis/lathe-fanucy sample config in the stock 2.6 (or higher) distribution.
That uses the base LinuxCNC version, unpatched, but using the G43.1 additive offset idea.
(and if _that_ crashes then I need to know about it)
Replied by andypugh on topic option wear tool lathe
I installed the "fanuc_tool_change_style" patch but have problems crashes.
Instead of that have a look at the sim/axis/lathe-fanucy sample config in the stock 2.6 (or higher) distribution.
That uses the base LinuxCNC version, unpatched, but using the G43.1 additive offset idea.
(and if _that_ crashes then I need to know about it)
Please Log in or Create an account to join the conversation.
16 Jan 2015 04:59 - 16 Jan 2015 05:03 #55045
by jlviloria
Replied by jlviloria on topic option wear tool lathe
Andy,
The problem with fanuc_tool_change_style is that the tool table locks, indicating that there is the tool number.
Chris Morley, was working to repair, but still hangs improved and I could not find a pattern or probable cause, goes at any time.
www.linuxcnc.org/index.php/english/forum...ffset-patch?start=70
I understand G43.1 according to assign a different compensation for example (T01 M6 G43.1 H10) takes the value of the tool 10 as their compensation.
I want to have is that you can add or subtract a small value (wear) the compensation. to correct any errors in the compensation or to give an accurate measure.
fanuc for, is managed lathe. T0101 being second 01 "G43 H01".
but we have two tables tools, geometry and wear.
the wear does is add or subtract the value assigned to the compensation table geometry diametrically value.
I have thought so, that when a tool is called, LinuxCNC read the two tables and subtract or add agree to sign the compensation. but really like doing is what my head explodes. not programming.
thanks,
The problem with fanuc_tool_change_style is that the tool table locks, indicating that there is the tool number.
Chris Morley, was working to repair, but still hangs improved and I could not find a pattern or probable cause, goes at any time.
www.linuxcnc.org/index.php/english/forum...ffset-patch?start=70
I understand G43.1 according to assign a different compensation for example (T01 M6 G43.1 H10) takes the value of the tool 10 as their compensation.
I want to have is that you can add or subtract a small value (wear) the compensation. to correct any errors in the compensation or to give an accurate measure.
fanuc for, is managed lathe. T0101 being second 01 "G43 H01".
but we have two tables tools, geometry and wear.
the wear does is add or subtract the value assigned to the compensation table geometry diametrically value.
I have thought so, that when a tool is called, LinuxCNC read the two tables and subtract or add agree to sign the compensation. but really like doing is what my head explodes. not programming.
thanks,
Last edit: 16 Jan 2015 05:03 by jlviloria.
The following user(s) said Thank You: joekline9
Please Log in or Create an account to join the conversation.
16 Jan 2015 05:14 #55046
by andypugh
Look at the sample config I pointed at. It works on stock LinuxCNC, no need for the patch.
(In fact, revert to the stock installation because the patch + the remap in that sample config is likely to work badly together)
Replied by andypugh on topic option wear tool lathe
The problem with fanuc_tool_change_style is that the tool table locks,,
Look at the sample config I pointed at. It works on stock LinuxCNC, no need for the patch.
(In fact, revert to the stock installation because the patch + the remap in that sample config is likely to work badly together)
Please Log in or Create an account to join the conversation.
16 Jan 2015 08:06 #55063
by JR1050
Replied by JR1050 on topic option wear tool lathe
I think what you mean is , how does ones modify to tool table with an additional field for tool wear. Fanucs, starting with the 10 series I think, had an a field for the tool offset and an additional field to was added or subtracted to the actual tool offset to size a part. I at one time changed the labeling of the tool table from w and u to x wear and z wear, but that value would have to be added or subtracted in the python code, which I hadn't figured out yet. It would seem to me adding some code to axis .py to tell it
" add the value of x offset field of a given tool to the same tools offset value". I feel your pain, adjusting offsets on a lathe is a pain. You could set each tool with G92 from your indexing position and use the offsets as wear offsets. I used to do that on 5t controls.
" add the value of x offset field of a given tool to the same tools offset value". I feel your pain, adjusting offsets on a lathe is a pain. You could set each tool with G92 from your indexing position and use the offsets as wear offsets. I used to do that on 5t controls.
Please Log in or Create an account to join the conversation.
16 Jan 2015 22:43 - 16 Jan 2015 22:44 #55082
by jlviloria
Replied by jlviloria on topic option wear tool lathe
JR1050, correct, there must be a way to compensate for wear of the tool,
LinuxCNC I think this thought only milling, although the option that gives me
Andy, I have not been able to test as I generates the following error.
the stdglue file does not appear in the directory
thanks
LinuxCNC I think this thought only milling, although the option that gives me
Andy, I have not been able to test as I generates the following error.
the stdglue file does not appear in the directory
Debug file information:
initialize: module '/home/roland/linuxcnc/configs/sim.axis/lathe-fanucy/toplevel.py' init failed:
Traceback (most recent call last):
File "/home/roland/linuxcnc/configs/sim.axis/lathe-fanucy/toplevel.py", line 19, in <module>
import remap
File "./remap.py", line 19, in <module>
from stdglue import *
ImportError: No module named stdglue
Interp ctor: cant instantiate Python plugin
initialize: module '/home/roland/linuxcnc/configs/sim.axis/lathe-fanucy/toplevel.py' init failed:
Traceback (most recent call last):
File "/home/roland/linuxcnc/configs/sim.axis/lathe-fanucy/toplevel.py", line 19, in <module>
import remap
File "./remap.py", line 19, in <module>
from stdglue import *
ImportError: No module named stdglue
Python plugin configure() failed, status = -11
Python plugin required for prolog=, but not available: 71:REMAP = T prolog=get_T_number ngc=toolchange
A configuration error is preventing LinuxCNC from starting.
More information may be available when running from a terminal.
6244
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal componentsthanks
Last edit: 16 Jan 2015 22:44 by jlviloria.
Please Log in or Create an account to join the conversation.
16 Jan 2015 23:17 #55084
by andypugh
That's annoying.
The file _probably_ exists somewhere, I am not at a LinuxCNC machine at the moment so can't look for it. Nor am I likely to be anywhere near one until after the 27th.
If someone else could look at this? I guess it is something to do with how files get moved around during the copy into the user configs area.
Replied by andypugh on topic option wear tool lathe
Andy, I have not been able to test as I generates the following error.
the stdglue file does not appear in the directory
That's annoying.
The file _probably_ exists somewhere, I am not at a LinuxCNC machine at the moment so can't look for it. Nor am I likely to be anywhere near one until after the 27th.
If someone else could look at this? I guess it is something to do with how files get moved around during the copy into the user configs area.
Please Log in or Create an account to join the conversation.
16 Jan 2015 23:26 - 17 Jan 2015 00:03 #55088
by dgarrett
Fixed for deb builds with commit: 1964b7b 2014-07-27
it is in master (and 2.7)
git.linuxcnc.org/gitweb?p=linuxcnc.git;a...0c386b41171bce46878e
Replied by dgarrett on topic option wear tool lathe
Andy, I have not been able to test as I generates the following error.
the stdglue file does not appear in the directory
Fixed for deb builds with commit: 1964b7b 2014-07-27
it is in master (and 2.7)
git.linuxcnc.org/gitweb?p=linuxcnc.git;a...0c386b41171bce46878e
Last edit: 17 Jan 2015 00:03 by dgarrett. Reason: add link
Please Log in or Create an account to join the conversation.
17 Jan 2015 02:14 #55101
by jlviloria
Replied by jlviloria on topic option wear tool lathe
Dgarret, thanks for replying, install the master version, 2.8.0. pre-1, and hands me the same error, I'm running on Debian live version, which is published on the website,
./autogen.sh
./configure --prefix=/usr
make
sudo make install
may be happening, that file stdglue that it serves, because I open other settings SIM and I open well.
thanks,
Jorge Viloria
./autogen.sh
./configure --prefix=/usr
make
sudo make install
may be happening, that file stdglue that it serves, because I open other settings SIM and I open well.
thanks,
Jorge Viloria
Please Log in or Create an account to join the conversation.
17 Jan 2015 03:27 #55104
by dgarrett
Installing, especially to /usr is NOT recommended for run-in-place (RIP)
and may create conflicts and other problems with a co-installed deb package.
(Note also that src/Makefile does NOT provide an uninstall option so
it can create a mess that is hard to unwind)
Instructions for a RIP build (do NOT require make install):Note when using a RIP build, the lathe-fanucy files will not be
copied to your home directory (this does happen when using
a deb build and the configuration selector)
Alternatively (and much easier unless /usr is messed up), you can
just install a deb from the buildbot: buildbot.linuxcnc.org
The buildbot text has not been updated for 2.7 but you can
direcly browse to find a deb package starting at:
buildbot.linuxcnc.org/dists/
For example, for wheezy, 2.7, realtime(rt), the most recent deb today is
from commit 18a933a:
When a deb install is successful, all paths will exist in standard
places and the user is not required to manage the enviroment.
Deb packages can also be easily removed or upgraded without
creating conflicts.
Replied by dgarrett on topic option wear tool lathe
??? Why did you use:./autogen.sh
./configure --prefix=/usr
make
sudo make install
??? Why did you do:--prefix=/usr
make install
Installing, especially to /usr is NOT recommended for run-in-place (RIP)
and may create conflicts and other problems with a co-installed deb package.
(Note also that src/Makefile does NOT provide an uninstall option so
it can create a mess that is hard to unwind)
Instructions for a RIP build (do NOT require make install):
$ cd your_git_root/src
$ ./autogen.sh
$ ./configure # for uspace use --with-realtime=uspace
$ make
$ sudo make setuid
# then set environment (for any shell you want for rip stuff)
$ . ../scripts/rip-environment
$ which linuxcnc # --> make sure it is correct, e.g., your_git_root/linuxcnc
# now go to the sim directory:
$ cd ../configs/sim/axis/lathe-fanucy
$ linuxcnc lathe-fanucy.inicopied to your home directory (this does happen when using
a deb build and the configuration selector)
Alternatively (and much easier unless /usr is messed up), you can
just install a deb from the buildbot: buildbot.linuxcnc.org
The buildbot text has not been updated for 2.7 but you can
direcly browse to find a deb package starting at:
buildbot.linuxcnc.org/dists/
For example, for wheezy, 2.7, realtime(rt), the most recent deb today is
from commit 18a933a:
$ wget http://buildbot.linuxcnc.org/dists/wheezy/2.7-rt/binary-i386/linuxcnc_2.7.0~pre2.275.g18a933a_i386.deb
$ sudo dpkg -i linuxcnc_2.7.0~pre2.275.g18a933a_i386.deb
$ which linuxcnc # --> make sure it is /usr/bin/linuxcnc
$ linuxcnc # start the config selector and go to sim/configs/axis/lathe-fanucy
# the config selector will copy the configuration to ~/linuxcnc/configs/When a deb install is successful, all paths will exist in standard
places and the user is not required to manage the enviroment.
Deb packages can also be easily removed or upgraded without
creating conflicts.
Please Log in or Create an account to join the conversation.
Time to create page: 0.121 seconds