Re: g-code routines

["Lawrence Glaister" <lg-at-jfm.bc.ca>]

Hi Ray and the group...
I like the idea of a popup application for generating generic gcode
routines/snippets. The emc interface seems to be well defined (see editor
code). There is no reason that a popup with a few entry fields for
parameters
either entered or read from current machine positions, could not coded in an
easily expandable way.
=======================================================
Lawrence Glaister VE7IT             email: lg-at-jfm.bc.ca
1462 Madrona Drive                  http://jfm.bc.ca
Nanoose Bay BC Canada
V9P 9C9
=======================================================
----- Original Message -----
From: Ray <rehenry-at-up.net>
To: Multiple recipients of list <emc-at-nist.gov>
Sent: Saturday, November 18, 2000 8:41 AM
Subject: g-code routines


>
>
> Hi
>
> I want to develop a Tcl/Tk interface that executes programs like Jon
> Elson's g-code writing routines and pops them up from somewhere in the EMC
> HMI's.   I would think that it could also become a stand alone system.
This
> project is not intended to replace the effort to develop CAD/CAM or
> conversational programming (CPLD) but should provide a modest and
> reasonably quick step in the direction of assisted writing of g-code
> programs.
>
> This is where I am on this project.
>
> 1 - g-code produced would be RS274NGC compatible to allow for hard coding
> within the routines.
>
> 2 - Terry said that it would not be difficult to modify jon's existing c
> code to work with an interface. (whatever interface is)
>
> 3 - Jon suggested that we write a common set of specifications so that
> others could write compatible routines.
>
> 4 - Common code and the derrivitives of Jon's routines would be gpl
> copyright.  Specs, help, and documentation would be gpld.
>
> 5 - We would make a place for all of it in the sourceforge repository and
> provide for compiling, if needed, and setup in the EMC install procedures.
>
> 6 - The Tcl/Tk interface would;
> a.  auto menu so that new routines can be accessed
> b.  query the executable for labels and variables
> c.  look for associated graphic files
> d.  produce a main entry screen from this information.
> e.  submit data to the executable
> f.  receive g-code from the executable
> g.  permit viewing of code produced
> h.  permit editing of variables and resubmit
> i.  save RS274NGC code to file or pass to other programs.
>
> I'd like to get a working first draft of this system ASAP.
>
> Comments?  Help? Project name? Snippets of specifications? Directory
> structure?  Appearance?
>
> Let's keep the comments on list until all that want to comment have had a
> chance.  I suggest that we snip and create new sub topics to keep posts
> shorter.  If it generates enough interest, I'll post summaries and create
> a place on linuxcnc.org.
>
> Thanks for your attention to this long post.  Thanks in advance for your
> response.
> --
>
> Ray
>
>
>