On Sunday 04 September 2016 11:52:42 Kirk Wallace wrote: > On 09/04/2016 03:47 AM, andy pugh wrote: > > On 4 September 2016 at 11:05, Gene Heskett <[email protected]> wrote: > >> I have wondered about those usages, and it occurs to me that these > >> usages of an alpha character should have their "scope" restricted > >> to the life of the canned cycle being executed, to disappear with > >> the stack cleanup as that particular canned cycle was exiting. The > >> fact that its even being discussed tells me it is non-volatile. > > > > No, the multi-spindle G76 needs a letter to tell it which spindle to > > synchronise to. > > Canned cycles tend to have sticky parameters so that one only needs to > invoke the G command to repeat the process with only adding the > parameters that change. > > Here is a canned cycle that drills a new hole just by adding an X and > Y to a new block. > > (Drilling) > T 3 M6 G43 H 3 > > S 4000 (RPM) > M8 (Coolant ON) > M3 (Spindle ON, Forward) > F 100.00 (Z Feed, inches/minute) > > G0 X 0.0000 Y 0.0000 (Hole 1 of 3) > G0 Z 0.3000 (Z Clear) > G90 G98 (Absolute Distance Mode, Canned return to Z or R) > G81 Z -4.0000 R 0.0000 (Canned Drill) > X 0.0000 Y 1.0000 (Hole 2) > X 0.0000 Y 2.0000 (Hole 3) > > G80 (Cancel canned cycle) > > G0 Z 0.3000 > > M9 (Coolant OFF) > M5 (Spindle OFF) > > G30 Z 0.3 (Go in Z only to preset G30 location) > G30 (Go to preset G30 location) > > M30 (End of Program) > > ~~~~~ I think what I ,meant to say is that a canned cycle should have its own private versions of all these option letters. So E could have one meaning for Andy's spindle thing, and another, different canned routine could have its own private E,I,L,H,K,J yadda.
I, in my poking at the sleeping dog, have only rarely used a #number variable high enough to stay out of the call stacks hair. Generally I use global declarations, so a call is a simple call with no argument passing to complicate the works, So someplace in the #200 to #4990 map numbered map we can use for our own uses, there ought to be room to declare a private, nv storage area for each of the "canned' cycles use, without impinging on a neighbor. The reason I ended it at 4990 is that I have one machine that I cobbled up a touchoff storage so I could home it, and return to the exact same position. This was at least a decade ago. So on that machine, my list of saved vars starts at #4990, not #5000. But I see thats now built into Linuxcnc. So if you build down from there (4999), my code will likely be the only code on the planet you break. Thats a shrug because I don't need it anymore. > On another issue, as far as I can tell, G76 only works along Z. I > thought that calling X, Y, or Z would locate the destination of the > line of action,but only Z works. ISTR finding that to be the case, waaaaay back up the calendar count. For that, we can use a G33. > A Y word errors out. An X can add an > X motion at the very end of the command. I did not retain this X move > in my version, but have the tool return to the starting point along > the tool clearance line. I can see no reason to do otherwise. To allow it is IMO, inviting a tool crash. And I don't need any more help as I get those just from my own typu's. ;) > ~~~~~ > In the wider world, G76 has a completely different function between > mills and lathes. Yes. 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> ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
