I am working on a Linuxcnc retrofit on a 2 axis waterjet. They use abrasive along with the waterjet to cut steel and aluminum on this machine.
If they are cutting out a large sheet of material, the nozzle will wear and the jet will become a larger diameter during the course of the job. They would like to be able to adjust the jet size (think tool diameter) on the fly or at least do it as the machine is paused, or stopped, and then do a run from line to resume. The tool table seems to be in a state of flux right now so I am looking for advice on how to best do this. In the message string below (lathe application) the G43 and G43.2 is discussed in the context of a lathe. Would the same work for tool diameter? With a G41/G42 and a G41.1 and G42.1? It looks like G41.1 and G42.2 deal with the tool diameter directly whereas G43.2 incrementally adjusts an existing tool? Does it matter which tool table I use to do any of this? I have 2.6.3 installed right now on the machine but I have the 2.7___ master LinuxCNC master installed on a different PC so I can test with either software. Any advice is appreciated. Thanks, Dave On 8/6/2014 11:16 AM, Gene Heskett wrote: > 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 --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
