I have this working (tool list gcode properties) in principle.
It's a small change in glcanon.py:
def change_tool(self, arg):
self.first_move = True
try:
self.tool_list.append(arg)
except Exception as e:
print(e)
Then requires an screen that looks for gcode properties to look for the tool
list.
is anyone else working on this? If not I will try to get to it this week end.
Chris
________________________________
From: Small Shop Concepts <lcvet...@gmail.com>
Sent: January 14, 2023 12:32 AM
To: EMC developers <emc-developers@lists.sourceforge.net>
Subject: Re: [Emc-developers] Show used tools for loaded NC program?
If i do not have a tool in my carousel i get an error stating the tool not
in the carousel and the program wont start. It runs through and checks i am
guessing at cycle start. I used to have an issue where if i called a tool
twice with a different tool between it would error because it was not
accounting for returning the tool to the carousel.
I do like the idea of having the tool list read at program load and
displayed somewhere on the gui for those who do not have cam that prints
the tool list in the gcode file.
On Fri, Jan 13, 2023, 4:59 PM Nicklas SB Karlsson <n...@nksb.eu> wrote:
> Looking into file generated by post processor I used it does not print
> a list of tools used.
>
> It is easy to miss one and then program in best case quit then row to
> insert tool is reached, not a big problem but still annoying. In best
> case it would also check if tool is in tool table, this check should
> work if each tool get a unique number.
>
> Nicklas Karlsson
>
>
> fre 2023-01-13 klockan 16:39 -0500 skrev Small Shop Concepts:
> > That can be accomplished in the post processor of most cam softwares,
> > it
> > writes the tool lost at the top of the gcode file.
> >
> > On Fri, Jan 13, 2023, 4:32 PM Nicklas SB Karlsson <n...@nksb.eu> wrote:
> >
> > > Anyone else think it would be useful with possibility to show which
> > > tools a loaded NC file use?
> > >
> > > Then pressing a button list with tools needed is shown. So far I
> > > have
> > > manually read the g-code file to determine which tools must be
> > > prepared.
> > >
> > >
> > > Nicklas Karlsson
> > >
> > >
> > >
> > > _______________________________________________
> > > Emc-developers mailing list
> > > Emc-developers@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/emc-developers
> > >
> >
> > _______________________________________________
> > Emc-developers mailing list
> > Emc-developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-developers
>
>
>
>
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
