Regarding messing with the g-code interpreter, my vote is that g-code should describe axis position, feedrate; and spindle speed and direction, and little more. Everything else should be handled with CAM, including canned cycles and such. Less is more.
If one insists on "improving" g-code, I would start over with a language using keywords rather than letters. The need to to extract the most context from single symbols is a throwback from when teletypes ran at 300 Baud. Just my opinion based on very limited experience. -- Kirk Wallace http://www.wallacecompany.com/machine_shop/ http://www.wallacecompany.com/E45/index.html California, USA ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
