Hi Chris, This could be a good place to start a religious war. On the other hand I think some of the choices are fairly obvious, or will be until someone points out a glaring omission. ;-)
I'm kinda with Ray in that I don't see a necessity to use up a whole string of M codes (think > 16 gears). :-( One either goes with a lookup table or other mechanism ... to determine the appropriate gear; or the programmer chooses explicitly. Most of the time you are trying to deliver maximum power to the spindle and that determines the right gear. A lot of this looks like a tool change; you must be at a slow spindle rpm to change gear so the sequence is pretty well fixed. Rarely should one need to radically change speed with the same tool although that can happen with a finishing pass. A gear change like a tool change probably requires the tool to be out of the workpiece. Maybe just G53G0Z0(spindle up) rather than tool change position. However most of the time this will happen in sequence with a tool change. The same concepts apply to a lathe but the axes and moves change a bit. S xxxx(new spindle speed) M5 (or the M5 can be implied) Mxx (where xx specifies gear change), xx (gear) or autoselect (M3 should be implied after the gear change). Carry it across a M2/M30 ... probably not. Let the start of the next program set it. This is where lookup begins to seem reasonable. It is always easier to edit and compose. Have at it. I just donned my nomex so I'm safe. ;-) Dave On Apr 14, 2008, at 6:22 PM, Chris Radek wrote: > On Mon, Apr 14, 2008 at 05:44:53PM -0700, [EMAIL PROTECTED] wrote: >> >> Sounds like you are facing many of the issues we encounter with >> larger retrofits. Certainly your choice of M words to associate with >> various gears is one such set but I caution that these things are not >> standardized in any meaningful way among control vendors. > > I keep seeing this come up - seems like we should do something. > > Making some M codes that manipulate some HAL bits is not too hard. As > Ray says, picking the M codes and figuring out how they should work is > the hard part. > > For instance should they be a group so only one can be on at a time? > What turns them off? Does M2/M30/% reset them? My machine has 2 > gears, Sam's has 16; maybe the next guy's has 64? What happens if > you command a gear change while the spindle is running full speed? In > what order are the M codes run if one of our new ones shares a line > with other M codes? I bet there are other questions I haven't > thought of right away. > > It would be great if you guys who have experience on a variety of > machines could come up with a design that has the possibility of being > flexible enough to run most gearboxes. The wiki would be a great > place for this collaboration. > > I see M codes 10-29, 31-47, 70-99 are currently unused. There are > some others but those are the big blocks. > > Chris > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save > $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http:// > java.sun.com/javaone > _______________________________________________ > Emc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-users ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
