Good evening friends,
Quick one to say I got an answer to my message to https://gtc-tools.com
about their broken registration form and should soon get a login to access
data to share with LinuxCNC and FreeCAD communities 🙂
TY
J
___
Emc-developers maili
Hi
Hey Jose, could you please tell us a bit more about this code?
BTW, installed HSMAdvisor this night and discovered it had some kind of
tool db feature included... Will make a small report about it.
Have a nice sunday my friends
TY
J
___
Emc-develo
On Thu, 7 Jul 2022 at 18:25, Jose Luis wrote:
And this is using the tool database schema?
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912
On 21/6/22 23:18, Jose Luis wrote:
On 18/6/22 1:47, andy pugh wrote:
On Fri, 17 Jun 2022 at 17:07, Jose Luis
wrote:
Still need to figure the parts from linuxcnc like where i can get or
put
the data.
Dewey added an interface. I'll be honest and say that it isn't how I
would have done it.
I've been in machine tool applications engineering for almost 2 decades.
Sometimes you just don't question the dumb, you just find the parameter to
fix what they want.
Safety wear would be nice, but if the machine is installed and calibrated
properly, those tool setters should either be dead nuts
Le ven. 1 juil. 2022 à 20:42, Feral Engineer a
écrit :
> I deal with customers wanting machines to leave the wear comp in after
> touching off a new tool. I don't understand why.
>
If not zeroing, the only thing I could want is a parameter to optionaly set
a positive security offset to be added
I deal with customers wanting machines to leave the wear comp in after
touching off a new tool. I don't understand why.
Phil T.
The Feral Engineer
Check out my LinuxCNC tutorials, machine builds and other antics at
www.youtube.com/c/theferalengineer
Help support my channel efforts and coffee add
Le jeu. 30 juin 2022 à 18:28, Feral Engineer a
écrit :
> On our machines, when you touch your tools off on the
> tool setter, the wear offset for that tool zeroes out automatically. It's
> just beneficial to have, especially on a lathe.
>
Actually, until this week when I killed a part with that
d wear offsets works
for sure.. but it a hack and doesn't allow proper standard support in screens.
I certainly don't suggest we eliminate g43.2 functionality though.
From: andy pugh
Sent: June 29, 2022 10:13 PM
To: EMC developers
Subject: Re: [Emc-devel
different offsets,
> not
> > > tool number.
> > > t11 = tool pocket 1 offset 1
> > > t12 = tool pocket 1 offset 2
> > >
> > > There is also
> > > T111 = tool 1 offset 1 wear offsets 1
> > >
> > > To pick a particular
On Fri, 24 Jun 2022 at 02:46, Chris Morley wrote:
>
> Different edges of the same tool is done by having different offsets, not
> tool number.
It certainly _can_ be done that way, but I see no reason to preclude
doing it a different way.
And (as delivered) LinuxCNC does not handle T11 to mean a
T111 = tool 1 offset 1 wear offsets 1
> >
> > To pick a particular tool for a pocket in Gcode is not standard on a
> lathe.
> > I'm quoting Okuma, I believe Fanuc is similar but I'm sure there are
> > exceptions of course.
> >
> > Anyways the probl
knowing what offset/wear offset is
> currently set is still the same.
>
> Chris
> ____
> From: andy pugh
> Sent: June 23, 2022 7:29 PM
> To: EMC developers
> Subject: Re: [Emc-developers] tool database in python
>
> On Thu, 23 Jun 2022 at 06:4
: Re: [Emc-developers] tool database in python
On Thu, 23 Jun 2022 at 06:42, Chris Morley wrote:
> for instance, you can use multiple tool offsets (one at a time) on a single
> tool position.
Indeed, which is why a database needs to allow several tools to be
simultaneously in the same p
On Thu, 23 Jun 2022 at 06:42, Chris Morley wrote:
> for instance, you can use multiple tool offsets (one at a time) on a single
> tool position.
Indeed, which is why a database needs to allow several tools to be
simultaneously in the same pocket.
(To store different edges of the same tool as di
M
To: EMC developers
Subject: Re: [Emc-developers] tool database in python
On Wed, 22 Jun 2022 at 04:15, Feral Engineer wrote:
> I would like to see a wear comp along with cutter radius/diameter, while
> we're on that subject.
That's do-able with LinuxCNC is it is, though it
On Wed, 22 Jun 2022 at 04:15, Feral Engineer wrote:
> I would like to see a wear comp along with cutter radius/diameter, while
> we're on that subject.
That's do-able with LinuxCNC is it is, though it's slightly clunky.
Basically G43.2 allows you to add as many other H-number offsets as you wan
Could probably do this (tool-by-name) with params: #facetool = 3
Would be friendlier if you could enter that in the tooldata base
From: Feral Engineer
Sent: June 22, 2022 3:13 AM
To: EMC developers
Subject: Re: [Emc-developers] tool database in python
Those
Le mer. 22 juin 2022 à 00:32, andy pugh a écrit :
> On Tue, 21 Jun 2022 at 20:57, Jérémie Tarot wrote:
>
>
> The T-number can be the pocket number if you want to run your query
> that way. But it's a very bad choice for a random toolchanger.
>
Good point! 🤔...
But then it is a CAM thing too bec
Those masso wanks still don't have tool radius comp
I would like to see a wear comp along with cutter radius/diameter, while
we're on that subject. Also, as Jeremie mentioned, Siemens controls allow
you to call up a tool by number: T6 M6 or by name: T="My Tool". Similar
functionality would also be
Simple Tool Changer on mill,
The pocket number IS the tool number loaded into the spindle.
An M06/M6 command then puts the spindle tool in the correct pot and the
machine waits for the next tool pot number to be positioned to allow the
spindle to be loaded.
Machines with a tool change rack or a ca
On Tue, 21 Jun 2022 at 20:57, Jérémie Tarot wrote:
> > So, the tool _number_ as associated with the G-code T-command is very
> > deliberately _not_ a key but a "property."
> I think that number is really a pocket_id in a tool_magazine to which is
> associated a tool_id, which in turn has a tool_
On 18/6/22 1:47, andy pugh wrote:
On Fri, 17 Jun 2022 at 17:07, Jose Luis wrote:
Still need to figure the parts from linuxcnc like where i can get or put
the data.
Dewey added an interface. I'll be honest and say that it isn't how I
would have done it. But I didn't do it so
https://linu
Le lun. 20 juin 2022 à 10:26, andy pugh a écrit :
> On Sun, 19 Jun 2022 at 08:35, Håvard F. Aasen via Emc-developers
> wrote:
>
>
> You have to bear in mind how the tools are called up from the G-code.
>
> M6 T6
>
> There is only a single integer passed to whatever selects the tool.
>
Anyone wh
On 6/21/22 15:25, Jérémie Tarot wrote:
Le lun. 20 juin 2022 à 07:39, Rod Webster a
écrit :
Once you have a unique primary key, there is no need to enforce uniqueness
on other fields. But in many cases it is a good idea.
Agreed
I would not make this
user definable as you are talking about
Le lun. 20 juin 2022 à 07:39, Rod Webster a
écrit :
> Once you have a unique primary key, there is no need to enforce uniqueness
> on other fields. But in many cases it is a good idea.
Agreed
I would not make this
> user definable as you are talking about the database structure which should
>
On 20.06.2022 10:23, andy pugh wrote:
> On Sun, 19 Jun 2022 at 08:35, Håvard F. Aasen via Emc-developers
> wrote:
>
>> As this is described, it seems to me that toolID really is a description,
>> and T_number could be used as the primary key, like so
>> toolID INTEGER PRIMARY KEY
On Sun, 19 Jun 2022 at 08:35, Håvard F. Aasen via Emc-developers
wrote:
> As this is described, it seems to me that toolID really is a description,
> and T_number could be used as the primary key, like so
> toolID INTEGER PRIMARY KEY, -- alias T_number
> description T
Once you have a unique primary key, there is no need to enforce uniqueness
on other fields. But in many cases it is a good idea. I would not make this
user definable as you are talking about the database structure which should
not need revising (other than to add fields if required)
Rod Webster
*13
Le dim. 19 juin 2022 à 09:35, Håvard F. Aasen via Emc-developers <
emc-developers@lists.sourceforge.net> a écrit :
> On 18.06.2022 01:47, andy pugh wrote:
> > On Fri, 17 Jun 2022 at 17:07, Jose Luis
> wrote:
> >
> >> Still need to figure the parts from linuxcnc like where i can get or put
> >> th
Every SQL data table should have a auto incrementing Id in the primary key
something like this in MySQL
ToolID int NOT NULL AUTO_INCREMENT,
You might also have a user editable Tool Number
but this separates indexes used to create relationships with other tables
from Human intervention.
Anytime I i
On 18.06.2022 01:47, andy pugh wrote:
> On Fri, 17 Jun 2022 at 17:07, Jose Luis wrote:
>
>> Still need to figure the parts from linuxcnc like where i can get or put
>> the data.
>
> Dewey added an interface. I'll be honest and say that it isn't how I
> would have done it. But I didn't do it so..
Le sam. 18 juin 2022 à 01:50, andy pugh a écrit :
> On Fri, 17 Jun 2022 at 17:07, Jose Luis wrote:
>
> > Still need to figure the parts from linuxcnc like where i can get or put
> > the data.
>
> Dewey added an interface.
Nice
I'll be honest and say that it isn't how I
> would have done it. B
On Fri, 17 Jun 2022 at 17:07, Jose Luis wrote:
> Still need to figure the parts from linuxcnc like where i can get or put
> the data.
Dewey added an interface. I'll be honest and say that it isn't how I
would have done it. But I didn't do it so
https://linuxcnc.org/docs/devel/html/tooldatab
Hello, turboss here
Did a draft of Andy Pugh page on the wiki in python with sqlachemy.
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?ToolDatabase
Relation between tables still not 100% done.
Still need to figure the parts from linuxcnc like where i can get or put
the data.
Thanks.
lin
35 matches
Mail list logo
