On Wednesday 06 August 2014 07:40:25 Rick Lair did opine And Gene did reply: > Good Morning Guys, > > Dewey, > > I see this patch, I am working on testing it now, thanks > > Andy, > > The guys tried running a program last night, and as soon as it gets to > the tool call in the program, the gcode for the program disappears and > the subroutine pops up in the window, and the gremlin backplot jumps > from the picture of the part and goes back to the 0,0 point of the > display, > > We are using gmoccapy if that makes a difference? > > Any thoughts, > > Thanks
I am using axis, too lazy to switch, and I don't generally fix whats not broken. But I am seeing something similar, not in the backplot, but in the axis code display window at the bottom. Anytime a tool change is approaching, the code disappears, and the tool table appears. Always with the same tool highlighted regardless of the upcoming tool number being requested. And, IIRC, the tool table display remains until the following o<tedautoz> call, which dynamically sets the TLO, has been completed. But, I am not at all sure it is the LCNC tool table being displayed, I believe its the expected tool table from headers of the pcb2gcode generated files! Which is nice since the insert tool requester does NOT spec the size of the drill its looking for, but the text window does show the pcb2gcode expected tool diameter in the M6T2 line. No clue how that is done but it does appear to work correctly. Where people like me, without a tool changer, or as Stuart once said, a 2 armed tool changer, can lose track, having the popup display the diameter of the tool being requested in the popups larger font would be quite a usable bit of help for aging eyes. A 2.6.x hint perhaps? But I actually think the instant behavior is useful. In the long run, one more column in the tool table, that contained a code number that describes the tool, where 0=drill, 1=flat faced mill, 2=round nosed mill, etc, etc, would seem to be useful. 0-9 for milling tools, 10-29 for lathe tools. Wish list... ;-) > Rick Lair > Superior Roll & Turning LLC. > PH: 734-279-1831 > www.superiorroll.com > > -----Original Message----- > From: andy pugh [mailto:[email protected]] > Sent: Tuesday, August 05, 2014 12:46 PM > To: EMC developers > Subject: Re: [Emc-developers] Tool Table and Wear offset Table > > On 5 August 2014 17:36, Rick Lair <[email protected]> wrote: > > Apparently I spoke too soon, but I swear it was working properly > > yesterday, > > > when I did the update. > > > > The original toolchange.ngc file you wrote works fine, what we > > modified it too doesn't. For some reason it is not reading/using the > > tool data in the > > T1 > > > locations in the tool table. > > Yes, this is the problem I pointed out. > You need to G43 the tool offset data, then G43.2 the wear modifier. > Your changes removed the G43 #<tool> and only left a G43 #<wear> > > (actually, it doesn't matter what order you do them in, but G43 > #<tool> and G43.2 #<wear> feels more logical.) Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
