I started programming NC machine using calculator paper and pencil, then typed it all out to tape on a flexowriter or simply used mdi ti input what I wanted the machine to do. There was no sense in punching a tape since it was a one time job. Punching tape was just one more step where an error could be introduced with a simple typo. I used CNC machines the same as you would use a manual machine. I view Gcode as electronic machine levers and handles where instead of running a manual machine by turning the handle I tell the machine where to position with a simple x-position y-position. The Gcode that every now and then somebody wants to replace with some other language is as simple as it gets. any language or scripting language is much more complicated than Gcode and I really don't care to learn another language!
It should be very simple to use your favorite language to issue NML or HAL commands or queries without messing with the Gcode interpreter. If that's how you wnat to control your machine fine, do it. Just don't think for a minute that I should agree and start learning some scripting language! I know Gcode forward and backward, inside an out, and have absolutely no desire or reason to change to anything else. So if you know or have a favorite scripting language I suggest that you learn how to send EMC the appropriate NML and/or HAL commands and leave Gcode alone!!! BTW it's been a long time since I've used any punched tape but I was also able to read directly from the tape and interpret those hole patterns. There is no simpler way to command a machine tool. Dale Hugh Currin wrote: > I've been casually following the scripting language thread. I don't fully > understand the purpose, and have little experience, but with my limited > knowledge I agree with Stuart. > > I would suggest EMC should strive to be the best machine controller possible. > Currently this means, to me, it interprets "standard" G-code and moves axes > according to these G-code commands. I start to become uncomfortable when the > direction is to accept other commands and/or make extensions to "standard" > G-code. > > I also think G-code is similar to assembly language. Ideally one should use a > solid modeler to develop the part. Transfer this to a CAM package, probably > using IGES. Develop the set-ups, tool paths, tooling, speeds/feeds, etc. in > the CAM package. Export G-code from the CAM package using a post processor > specific to the CNC machine and controller to be used. I also think that post > processor should be very solid so you don't "have to" work in G-code. (It's > nice to know G-code while standing at the machine, but to change code there > can easily cause problems). > > For example such niceties as cutting splines should be in the realm of the > CAM > package until there are "standard" G-code commands for splines. Converting > them to lines or circular arcs makes for very long G-code programs but who > cares, we now have access to giga-bytes of hard disk storage. EMC accepting > non-standard G-code commands for splines is not helpful, no CAM package could > generate these non-standard codes. > > Maybe a simple processor is in order. A program which converts a scripting > language into G-code? > > Or maybe I'm missing the point. If so I apologize for taking up bandwidth. > > Thanks. > > On Sunday August 19 2007 8:55 pm, Stuart Stevenson wrote: > >> I don't understand the point needing/wanting to use a scripting >>language instead of G code. The part I don't understand is the >>'instead' of. Symbolic control, usually called G CODE, can coexist >>with other symbolic machine control protocols. Other symbolic >>expressions can be used. >> >>...... >> I see the G code (or any other symbolic) language as assembly >>programming. The machine control/machine tool is the processor. The >>output is the part you hold in your hand. A post processor is a >>compiler. Catia, NCL Mastercam... is Python, C, TCL.... >> You can use any language you want to generate positions and >>commands. You then will need to post process it into a machine >>tool/control specific format. > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
