On 6/29/22 17:06, andy pugh wrote:
On Sat, 25 Jun 2022 at 13:00, gene heskett wrote:
The tool table is essentially empty on this xyzb mill, but if I had an entry
that adequately describes a .0625" (1.58 mm) ball nose 4 flute mill, with
a .250" LOC, (6.36 mm) including the fact that its a BN, w
On Sat, 25 Jun 2022 at 13:00, gene heskett wrote:
> The tool table is essentially empty on this xyzb mill, but if I had an entry
> that adequately describes a .0625" (1.58 mm) ball nose 4 flute mill, with
> a .250" LOC, (6.36 mm) including the fact that its a BN, what would the
> table entry look
Greetings all;
The tool table is essentially empty on this xyzb mill, but if I had an entry
that adequately describes a .0625" (1.58 mm) ball nose 4 flute mill, with
a .250" LOC, (6.36 mm) including the fact that its a BN, what would the
table entry look like for G21 metric mode?
Background:
I h
On Sun, 3 Jan 2021 at 10:47, Jérémie Tarot wrote:
>
> Have a look at work done lately on tool table improvements in QtPyVCP, you
> may find what you need about custom fields
Can you explain what is happening there? I haven't been keeping up.
But I would say that tool table improvements probabl
Greetings;
This code to carve the clearances for the lid stay hinge when its
installed on a 1.5" wide strip of Mahogany that must so wide so it can
hang out on the inside edge, with a 11/32 wide groove 1/4" deep to
retain the top end of the cedar plank lining, is a 3 stage & 3 tool
routine, an
Greetings;
This is a repeat, because the original was sent at 20:32 my time
yesterday, and at 02:22 my time this morning, nearly 6 hours elapsed
time, the message has not come back. I am on several other lists that
sourceforge hosts and none of them are apparently of any priority to
sourcefor
Greetings;
3rd send, 03:21 AM & still no return from sourceforge. Gr.
Seriously, we need a mail list server that works.
However, to simplicate the issue, I just now found John Thorntons truely
excellent description under the wiki entry starting with "Tool Touch
Off", which extends to 2 w
On Sat, 6 Jun 2015 07:11:35 -0700
"jrmitchellj ." wrote:
> Sorry, that is MD I command.
> You should see the tool number at the bottom of the axis screen.
>
> If there is no tool number listed there, you dont you don't get the
> "tool table" option in the touch off screen.
Ok, I think I underst
Sorry, that is MD I command.
You should see the tool number at the bottom of the axis screen.
If there is no tool number listed there, you dont you don't get the "tool
table" option in the touch off screen.
On Jun 6, 2015 7:07 AM, "jrmitchellj ." wrote:
> You have to installed a tool in the mach
You have to installed a tool in the machine using the "T#M6" in mid so LCNC
knows what tool it has to work on.
Ray
On Jun 6, 2015 7:02 AM, "andy pugh" wrote:
> On 6 June 2015 at 14:12, Matt Shaver wrote:
> > It's been a long time since I worked with this... What has to be
> > declared in the .i
On 6 June 2015 at 14:12, Matt Shaver wrote:
> It's been a long time since I worked with this... What has to be
> declared in the .ini or .hal files to inform Axis that there should be
> a "Tool Table" option in the touch off dialog?
It is either a "T" at the end of the coordinate system list, or
It's been a long time since I worked with this... What has to be
declared in the .ini or .hal files to inform Axis that there should be
a "Tool Table" option in the touch off dialog?
Thanks,
Matt
--
__
On 5/28/2015 6:26 AM, Marius Liebenberg wrote:
> I dont know how to touch off into T. I always put the tool to the job
> and set Z=0. My understanding is that the tool table must take care of
> the rest. So once I have loaded all the tools in the table and touch
> them off to the reference of the
>On 28 May 2015 at 13:26, Marius Liebenberg
>wrote:
>
>> Should I use any other than Tx M6 with G43 already active in the
>>setup
>> code?
>
>Yes. G43 is not modal. You need to G43 after every tool change.
Ah that might be the problem.
>
>(Actually, it is possible to configure for "sticky"
On 28 May 2015 at 13:26, Marius Liebenberg wrote:
> Should I use any other than Tx M6 with G43 already active in the setup
> code?
Yes. G43 is not modal. You need to G43 after every tool change.
(Actually, it is possible to configure for "sticky" G43, but I think
that was an experimental additi
>On 28 May 2015 at 11:08, Marius Liebenberg
>wrote:
>> what happens
>> if I have to change tool 1 and the offsets for the new tool changes.
>> Does the rest of the tools in the table adjust automatically or must
>>I
>> redo all the tools in the table gain?
>
>If you change Tool 1 then you c
On 5/28/2015 8:04 AM, andy pugh wrote:
> On 28 May 2015 at 12:46, Rick Lair wrote:
>> We only reference the G54-59 coordinate systems on the Mill side, on the
>> lathe side, we solely use G92. I believe it is because we are only
>> working in one "plane" and are only referencing one part, the G
On 28 May 2015 at 12:46, Rick Lair wrote:
> We only reference the G54-59 coordinate systems on the Mill side, on the
> lathe side, we solely use G92. I believe it is because we are only
> working in one "plane" and are only referencing one part, the G54-59
> allows you to run say 5 parts in 5 dif
On 5/28/2015 7:34 AM, andy pugh wrote:
> On 28 May 2015 at 12:25, Rick Lair wrote:
>
>> then take a skim cut on the OD of the part, measure that OD,
>> then enter that value into the tool table, in diameter.
> I assume you mean "X" and not "D" in the tool table here?
Yes, I forgot about the "D"
On 28 May 2015 at 12:25, Rick Lair wrote:
> then take a skim cut on the OD of the part, measure that OD,
> then enter that value into the tool table, in diameter.
I assume you mean "X" and not "D" in the tool table here?
> Then on the next part, we will MDI back to T0101, manually jog and touch
gt; -- Original Message --
> From: "Chris Morley"
> To: "EMC"
> Sent: 2015-05-27 19:16:05
> Subject: Re: [Emc-users] Tool Table blues
>
>> There is a difference between touching off to set tool offsets and
>> touching off to set the origin (part z
t;
> -- Original Message --
> From: "Chris Morley"
> To: "EMC"
> Sent: 2015-05-27 19:16:05
> Subject: Re: [Emc-users] Tool Table blues
>
>> There is a difference between touching off to set tool offsets and
>> touching off to set the origin (part
On 28 May 2015 at 11:08, Marius Liebenberg wrote:
> what happens
> if I have to change tool 1 and the offsets for the new tool changes.
> Does the rest of the tools in the table adjust automatically or must I
> redo all the tools in the table gain?
If you change Tool 1 then you could touch-off th
is Morley"
>To: "EMC"
>Sent: 2015-05-27 19:16:05
>Subject: Re: [Emc-users] Tool Table blues
>
>>
>>There is a difference between touching off to set tool offsets and
>>touching off to set the origin (part zero). Sounds like u were
>>t
y message -
>From: "sam sokolik"
>To: "Enhanced Machine Controller (EMC)"
>
>Subject: [Emc-users] Tool Table blues
>Date: Wed, May 27, 2015 9:18 AM
>
>
>I found these directions very informative..
>
>http://linuxcnc.org/docs/2.6/html/lathe/lathe-user.h
hine Controller (EMC)"
Subject: [Emc-users] Tool Table blues
Date: Wed, May 27, 2015 9:18 AM
I found these directions very informative..
http://linuxcnc.org/docs/2.6/html/lathe/lathe-user.html#_tool_touch_off
sam
On 5/27/2015 11:03 AM, andy pugh wrote:
> On 22 May 2015 at 17:20, M
I found these directions very informative..
http://linuxcnc.org/docs/2.6/html/lathe/lathe-user.html#_tool_touch_off
sam
On 5/27/2015 11:03 AM, andy pugh wrote:
> On 22 May 2015 at 17:20, Marius Liebenberg wrote:
>> Then I put tool 1 in the post and do a reference cut.
>> I touchoff X to the cut
On 22 May 2015 at 17:20, Marius Liebenberg wrote:
> Then I put tool 1 in the post and do a reference cut.
> I touchoff X to the cut size
> I touchoff Z to the chuck face.
> Save the tool table and reload
> Then I do a tool change with the button in Gmoccapy and put the next
> tool in and repeat th
Hi Ed
Had no replies but yours so far.
-- Original Message --
From: "Ed"
To: emc-users@lists.sourceforge.net
Sent: 2015-05-26 23:49:48
Subject: Re: [Emc-users] Tool Table blues
>
>Did anyone explain this properly? If not I can give it a go.
>
>Ed.
>
>
&
Did anyone explain this properly? If not I can give it a go.
Ed.
On 05/22/2015 11:20 AM, Marius Liebenberg wrote:
> So finally I can no longer ignore the tool table functions of LCNC and I
> have never had the prevaledge to understand them well.
>
> Please assist me in getting my head a
So finally I can no longer ignore the tool table functions of LCNC and I
have never had the prevaledge to understand them well.
Please assist me in getting my head around this.
What I have on my lathe is this.
My limit switches are close to the chuck for the Z axis and fully
retracted for the X
On 8/1/2012 2:32 PM, jeremy youngs wrote:
> thanks for posting that kent I dont yet know how to post bugs but thats on
> my list of things to learn I to wish i had an atc also
>
>
Jeremy (and Andy):
Dewey Garrett has already responded on the emc-developers list (that's
where the bug tracker anno
thanks for posting that kent I dont yet know how to post bugs but thats on
my list of things to learn I to wish i had an atc also
On Wed, Aug 1, 2012 at 2:17 PM, Kent A. Reed wrote:
> On 7/29/2012 5:46 PM, Kent A. Reed wrote:
> > On 7/29/2012 4:53 PM, andy pugh wrote:
> >> On 29 July 2012 21:43,
On 7/29/2012 5:46 PM, Kent A. Reed wrote:
> On 7/29/2012 4:53 PM, andy pugh wrote:
>> On 29 July 2012 21:43, jeremy youngs wrote:
>>> thanx andy i wiil try that im a little confused "2 trailing new
>>> lines"? I
>>> think you are sying remove tool 5 then reload?
>> No, I am saying that the file e
On 7/29/2012 4:53 PM, andy pugh wrote:
> On 29 July 2012 21:43, jeremy youngs wrote:
>> thanx andy i wiil try that im a little confused "2 trailing new lines"? I
>> think you are sying remove tool 5 then reload?
> No, I am saying that the file ends with two blank lines, and that
> seems to be caus
thanx for clarification I will see if i can spot that myself, It does seem
that if they are blank that they cant possibly be an argument or a
statement huh? oh well the important thing is you helped i learned and
in an hour or so ill have a part thanx again
On Sun, Jul 29, 2012 at 4:53 PM, and
got it andy thanx, i didnt realize there was a tool menu in axis and when i
reloaded that it worked. Sometimes I feel like a dumb oaf so i have to
extend thanx
--
Live Security Virtual Conference
Exclusive live event will c
On 29 July 2012 21:43, jeremy youngs wrote:
> thanx andy i wiil try that im a little confused "2 trailing new lines"? I
> think you are sying remove tool 5 then reload?
No, I am saying that the file ends with two blank lines, and that
seems to be causing a problem. I don't know why, as it shouldn
thanx andy i wiil try that im a little confused "2 trailing new lines"? I
think you are sying remove tool 5 then reload? trying not to be thick
headed here so pls forgive im trying to aclimate to this tool and work
offset, some day when i get smarter i want to tackle this as ive seen some
discussio
On 29 July 2012 12:55, jeremy youngs wrote:
> heres the tool table. I tried g10 l1 and it had the same error, i wrote
> tool 5 in and saved the file . I dont understand why it sees all the other
> tools?
I tried your tool.tbl in a sim, and get the same result.
By removing the two trailing newlin
heres the tool table. I tried g10 l1 and it had the same error, i wrote
tool 5 in and saved the file . I dont understand why it sees all the other
tools? thanx fellas
tool.tbl
Description: Binary data
--
Live Security Vir
On 29 July 2012 00:54, jeremy youngs wrote:
> N232 M01
> N234 T5 M6
> N236 G0 G90 G54 X.7213 Y-1.068 S5704 M3
> N238 G43 H5 Z.25
> N240 Z.1
> N242 G1 Z-.0167 F6.16
>
> tool #5 not in tool library error ???/ I put this tool in the library
Have you reloaded the tool table?
tool.tbl is a short fil
N232 M01
N234 T5 M6
N236 G0 G90 G54 X.7213 Y-1.068 S5704 M3
N238 G43 H5 Z.25
N240 Z.1
N242 G1 Z-.0167 F6.16
tool #5 not in tool library error ???/ I put this tool in the library ,
tried g10l1 and it tells me the same every time. it will not mdi a t5m6 for
the same reason? im at a loss and any hel
Even though EMC2 does not directly use all of the information available in
a tool crib list a complete description of the cutter is valuable to the
machinist running the machine. I have seen as many as four 1/2 inch
diameter X 1.25 4 flute end mills used in one program. The only difference
is the c
On 15 December 2011 21:00, Dan Field wrote:
> So now I wonder why there is even a Tool Crib in EMC?
It has a number of uses. The main one is tool-length compensation. You
can change tool and the tip of the tool is still at the XYZ that the
screen says it is at. (or the XZ in the case of a lathe)
questions
> >in a forum.
> >
> > Good luck
> > jim
> > -----Original Message-
> > From: Dan Field [mailto:danfi...@roadrunner.com]
> > Sent: Thursday, December 15, 2011 3:01 PM
> > To: Enhanced Machine Controller (EMC)
> > Subject: Re: [
nswered than just
> asking questions in a forum.
>
> Good luck
> jim
> -Original Message-
> From: Dan Field [mailto:danfi...@roadrunner.com]
> Sent: Thursday, December 15, 2011 3:01 PM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users] tool table definiti
.@roadrunner.com]
Sent: Thursday, December 15, 2011 3:01 PM
To: Enhanced Machine Controller (EMC)
Subject: Re: [Emc-users] tool table definitions
On 12/15/2011 6:27 AM, andy pugh wrote:
> On 15 December 2011 14:06, wrote:
>
>> For example how to define a 1/8" ball nose mill
> If y
On 12/15/2011 6:27 AM, andy pugh wrote:
> On 15 December 2011 14:06, wrote:
>
>> For example how to define a 1/8" ball nose mill
> If you want to automatically compensate for the ball-radius then I am
> afraid that you can't. EMC2 doesn't know enough about the material
> shape to compensate for ba
On 15 December 2011 14:06, wrote:
> For example how to define a 1/8" ball nose mill
If you want to automatically compensate for the ball-radius then I am
afraid that you can't. EMC2 doesn't know enough about the material
shape to compensate for ball-nose (or V) cutters. All EMC2 knows about
is
A little help with tool table definitions please
Having read 'http://www.linuxcnc.org/docs/2.4/html/gcode_tool_compensation.html'
I am still to thick to get it
For example how to define a 1/8" ball nose mill
Richard
--
10
On 9 September 2010 15:52, John Kasunich wrote:
> A dowel pin works great for this - very precise, and you can simply
> push it against the side of the tool, then raise the tool (or lower
> the knee) slowly until the pin rolls under.
I think I have just found a use for the shank of the 6mm carbi
On Wed, 08 Sep 2010 22:22 -0700, "Speaker To-Dirt"
wrote:
>
> For what it's worth. I stumbled across this by accident. At a tool
> change take your tool to an area where there's still a surface z0.000.
> End the move with z1.000. Remove the tool, and insert the new tool.
> Now use a clamp arm
Your knee is your tool offset table.
On Thu, Sep 9, 2010 at 12:22 AM, Speaker To-Dirt
wrote:
>
> For what it's worth. I stumbled across this by accident. At a tool
> change take your tool to an area where there's still a surface z0.000. End
> the move with z1.000. Remove the tool, and inser
For what it's worth. I stumbled across this by accident. At a tool
change take your tool to an area where there's still a surface z0.000. End the
move with z1.000. Remove the tool, and insert the new tool. Now use a clamp arm
from your clamp kit that is 1" on a side. Raise or lower the k
For tool measurements off the taper of the holder, for cat 40 and cat 50 at
least it should be easy to even purchase blocks to use on the surface plate
with a height gage. Every place I worked at had some, so I never had to
source out.
If this is available for your tool holders it provides nice con
On 8 September 2010 15:25, Igor Chudov wrote:
> (then start program that again asks for T2.)
Maybe practice on polystyrene foam...
--
atp
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programmi
looks good
On Wed, Sep 8, 2010 at 9:25 AM, Igor Chudov wrote:
> Got it.
>
> Do in MDI:
>
> M6 T2 G43
> (then set height using a sliding gage block)
> (then set Z=zero)
> (then start program that again asks for T2.)
>
> - Igor
>
>
>
> On Wed, Sep 8, 2010 at 9:20 AM, Stuart Stevenson
> wrote:
> >
Got it.
Do in MDI:
M6 T2 G43
(then set height using a sliding gage block)
(then set Z=zero)
(then start program that again asks for T2.)
- Igor
On Wed, Sep 8, 2010 at 9:20 AM, Stuart Stevenson wrote:
> the g43 is the important part
> you need to turn on the tool length offset for the tool in
the g43 is the important part
you need to turn on the tool length offset for the tool in the spindle and
then the tool will be able to set the work piece coordinate zero
On Wed, Sep 8, 2010 at 8:26 AM, Andy Pugh wrote:
> On 8 September 2010 14:20, Igor Chudov wrote:
> >
> > Should I select my
On 8 September 2010 14:20, Igor Chudov wrote:
>
> Should I select my first tool in MDI
> (say M6T2),
Don't forget the G43...
--
atp
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming ski
Stuart, thanks. Great explanation. I already set up a little tool table.
One more question, is, once I set up the tool table, how to set the
initial offset so that the first tool chosen in the program, would be
properly adjusted for height. Should I select my first tool in MDI
(say M6T2), and then
Igor,
The whole point of tool length offsets is to run the program as if all
tools are the same length. Early NC machines had the tool length
incorporated in the program and the operator had to match each tool length
to the programmed tool length for each tool. There were elaborate tool
holders t
On 7 September 2010 16:50, Igor Chudov wrote:
> So say I touch off with one tool from tool table, then switch tool to
> my desired cutting tool, and the cutting tool would automagically be
> adjusted vertically to compensate for difference in offsets between
> the cutting tool and the tool I used
What I am doing now is setting up a tool table using GUI.
I first homed the mill. Then I would load one tool after another: for
each of them, I would find the Z coordinate so that they barely clear
a gage block. Then, I enter the minus of that as Z attribute of the
tool.
I will try with a piece o
Igor Chudov wrote:
> Ed, thanks.
>
> What do you use to locate Z edge of a part?
>
> You cannot use a ball end electronic edge finder, right?
>
My hideous technique is to lower the tool close to the part, then feel
under the
cutting edge with a .005" thick piece of paper. When the paper starts
Igor Chudov wrote:
> On Tue, Sep 7, 2010 at 10:27 AM, Stuart Stevenson wrote:
>
>> you can use the measured tool length as the number in the tool table
>> you will need to set your z zero to use the measured tool length
>>
>
> Stuart, do you mean that I have to set my zero by "touch off"?
Igor Chudov wrote:
> Ed, thanks.
>
> What do you use to locate Z edge of a part?
>
> You cannot use a ball end electronic edge finder, right?
>
> - Igor
I do use the zero tool. Usually I use a carbide end mill as a feeler. As
mentioned earlier, bring tool zero down to just above the work piece
Ed, thanks.
What do you use to locate Z edge of a part?
You cannot use a ball end electronic edge finder, right?
- Igor
On Tue, Sep 7, 2010 at 11:56 AM, Ed wrote:
> Igor Chudov wrote:
>> Guys,
>>
>> First off, thanks to all for porting EMC to 10.04, it is fantastic.
>>
>> Just a question. I
Igor Chudov wrote:
> Guys,
>
> First off, thanks to all for porting EMC to 10.04, it is fantastic.
>
> Just a question. I use quick change toolholders based on NMTB-30.
>
> I am trying to get a tool table started. And I wonder if I can simply
> measure the total length of the tool, in toolholder
Igor Chudov wrote:
> Guys,
>
> First off, thanks to all for porting EMC to 10.04, it is fantastic.
>
> Just a question. I use quick change toolholders based on NMTB-30.
>
> I am trying to get a tool table started. And I wonder if I can simply
> measure the total length of the tool, in toolholder, w
On Tue, Sep 7, 2010 at 10:27 AM, Stuart Stevenson wrote:
> you can use the measured tool length as the number in the tool table
> you will need to set your z zero to use the measured tool length
Stuart, do you mean that I have to set my zero by "touch off"?
So say I touch off with one tool from
On Tue, Sep 07, 2010 at 10:17:01AM -0500, Igor Chudov wrote:
>
> Just a question. I use quick change toolholders based on NMTB-30.
>
> I am trying to get a tool table started. And I wonder if I can simply
> measure the total length of the tool, in toolholder, with a caliper,
> and then subtract s
you can use the measured tool length as the number in the tool table
you will need to set your z zero to use the measured tool length
On Tue, Sep 7, 2010 at 10:17 AM, Igor Chudov wrote:
> Guys,
>
> First off, thanks to all for porting EMC to 10.04, it is fantastic.
>
> Just a question. I use qui
Guys,
First off, thanks to all for porting EMC to 10.04, it is fantastic.
Just a question. I use quick change toolholders based on NMTB-30.
I am trying to get a tool table started. And I wonder if I can simply
measure the total length of the tool, in toolholder, with a caliper,
and then subtract
> Meanwhile, I wonder if we could just enlarge it by a
> factor of 10 or 100 and forget about it for a while.
A binary order of magnitude would keep me happy for a long
time and a decimal order of magnitude would suffice forever.
I could put more smarts into my Eagle hole extractor, but
those d
On Sat, May 29, 2010 at 8:55 PM, Chris Radek wrote:
snip
> Maybe doubling yours would keep you happy for a while. I am not sure
> what all would be involved in removing these limitations, and I don't
> know of anyone working on it currently. It would be nice if the
> tool table could be arbit
On Sat, May 29, 2010 at 05:44:24PM -0400, Ed Nisley wrote:
> In Axis 2.4.0, is it true that the tool table can have only
> 48-ish entries?
I thought it was 56ish, but yes it's something like that.
> The problem is that Eagle's part libraries have a
> bewildering variety of hole diameters, which
In Axis 2.4.0, is it true that the tool table can have only
48-ish entries?
I'm drilling circuit boards from Eagle layouts, using a
script that extracts all the holes, sorts them by drill
diameter, then visits each set in nearest-neighbor order.
The problem is that Eagle's part libraries have
Am 06.01.2010 um 16:16 schrieb Michael Haberler:
>
> Am 06.01.2010 um 06:21 schrieb Erik Christiansen:
>
>> On Tue, Jan 05, 2010 at 10:18:59PM -0600, Chris Radek wrote:
>>>
>>> Here is what the new tool table format looks like:
>>>
>>> http://git.linuxcnc.org/gitweb?p=emc2.git;a=blob;f=configs/si
Good day gurus,
Just FWIW, I'd like to share my view as a newbie hobby machinist using
EMC regarding the tool table.
> I'm proposing a much more moderate goal: to encode the current EMC
> tool table such that it can be reused by other programs, and with some
> self-description
On Wed, 2010-01-06 at 16:21 +1100, Erik Christiansen wrote:
> On Tue, Jan 05, 2010 at 10:18:59PM -0600, Chris Radek wrote:
> >
> > Here is what the new tool table format looks like:
> >
> > http://git.linuxcnc.org/gitweb?p=emc2.git;a=blob;f=configs/sim/sim.tbl;hb=tlo_all_axes
>
> Now that looks
Am 06.01.2010 um 06:21 schrieb Erik Christiansen:
> On Tue, Jan 05, 2010 at 10:18:59PM -0600, Chris Radek wrote:
>>
>> Here is what the new tool table format looks like:
>>
>> http://git.linuxcnc.org/gitweb?p=emc2.git;a=blob;f=configs/sim/sim.tbl;hb=tlo_all_axes
>
> Now that looks very business-l
2010/1/6 Alex Joni :
> Having the field name (letter) followed by a number is a lot more flexible
> and easier to read (and you can always sort the lines as you like).
You can also, include tool wear (to an extent) if G-code expressions
are allowed.
I am thinking:
D 10.00 ; 10mm end mill
D [10.
> True, but you can use a * or | or / or \ or some unused character. In
> Excel
> you can define the separator.
> The gist is that the the software is set up to handle 16 fields or
> arguments.
Now why would you want to do that?
' ' (space) is just as good separator as any, you can still import i
e Controller (EMC)
> Subject: Re: [Emc-users] tool table
>
> 2010/1/6 Roland Jollivet :
> >
> > Just poking in here, but why not use comma delineators.
> ...
> > One can still use a prefferred editor or spreadsheet
>
> Comma delimited data can cause problems
True, but you can use a * or | or / or \ or some unused character. In Excel
you can define the separator.
The gist is that the the software is set up to handle 16 fields or
arguments. Fields will be defined as time goes on, but the user might want
to use the last few for own descriptions or for man
2010/1/6 Roland Jollivet :
>
> Just poking in here, but why not use comma delineators.
...
> One can still use a prefferred editor or spreadsheet
Comma delimited data can cause problems for spreadsheets with
localisation where the decimal separator is a comma. Probably not an
issue internally to E
Just poking in here, but why not use comma delineators. Then you can by
default have, say, 16 parameters per tool, most unused for now, but allows
expansion of parameters at any stage. So each line would look something
like;
1, T1, P1, D0.125000, Z+0.511000 , , , , , , , , , , , , ;1/8 end mil
On Tue, Jan 05, 2010 at 10:18:59PM -0600, Chris Radek wrote:
>
> Here is what the new tool table format looks like:
>
> http://git.linuxcnc.org/gitweb?p=emc2.git;a=blob;f=configs/sim/sim.tbl;hb=tlo_all_axes
Now that looks very business-like.
> You can see tool number, pocket, diameter, Z offset
On Wed, Jan 06, 2010 at 02:59:13PM +1100, Erik Christiansen wrote:
> If we don't watch out, there is a risk that the only way to read or edit
> our configuration files would be some GUI monstrosity! (Hopefully, I
> exaggerate horribly. :-)
I sure sympathize with this worry. XML is very hostile
On Tue, Jan 05, 2010 at 01:00:39PM -0500, Stephen Wille Padnos wrote:
> So yes, making changes so that extra information could be added as
> necessary would be great.
Within the existing plain text format, that would be nifty indeed.
> Making a format that humans can't read or write without soft
One other thing that would be nice in the tool table would be to specify the
units of measurement. Then if a tool was metric or inch there would be no need
for manual unit conversion before entering the value.
John Figie
FBICS has a tool catalog with many features. The data is stored in a STEP
Part 21 file.
IMO, it would be worthwhile to examine the features Tom envisioned even if
Part 21 won't be used.
I think there is at least some discussion of the catalog in the FBICS docs
on Tom Kramer's NIST page. I could d
Michael Haberler wrote:
> Alex,
>
> I glossed over your references and am shocked, it's just a single
> *table* ;-)
>
> I'm proposing a much more moderate goal: to encode the current EMC
> tool table such that it can be reused by other programs, and with some
> self-description features (field nam
Alex,
I glossed over your references and am shocked, it's just a single
*table* ;-)
I'm proposing a much more moderate goal: to encode the current EMC
tool table such that it can be reused by other programs, and with some
self-description features (field names, types, version number, machi
>
> Since I assumed shareable tool information is an industry-wide problem
> I had been googling around on the issue but didnt find a obvious
> candidate for such a format, although a saw a manufacturer who makes
> tool geometry information available in XML. Maybe there is such a
> format, I just
Hi Greg,
Am 03.01.2010 um 06:38 schrieb Greg Bentzinger:
>
> So now for a brighter topic - any chance the new tool table format
> might include geometry + wear? I had heard mention some changes were
> planned.
The tool table definitely is a data structure which has the "let's add
this and t
2009/10/27 Frank Tkalcevic :
> Thanks. Do I need to use G43 on each tool change line, or can this be set
> once to tell EMC to always use the tool table offsets?
Every time. You get used to it.
--
atp
--
Come build wi
> > However, after homing (with no tool loaded) and issuing an
> M6T1, the
> > x/z coordinates haven't been adjusted for the the tool offsets. Is
> > there something else I need to do?
>
> Yes. G43.
>
> M6 T1 G43 will work, or you can use an H-word to load offsets
> from a different tool tab
1 - 100 of 116 matches
Mail list logo
