Re: [CAD_CAM_EDM_DRO] Re: G-code user variables; convention?

Alan,

there are usualy several sets of parameters in the control but not all
of them can be set or changed by program macros (nor should they)
I've just been looking thru the parameters on one of the lathes at work
and came up with...

common variables
system parameters
optional parameters-long word
optional parameters-word
optional parameters-bit
machine system parameters
machine user parameters
barfeed user parameters (option)
process time estimate data
user parameters

usualy several pages/screens for each set of parameters
not to mention about 100 tool offsets and 128 pages of PLC data

naturaly you may want to trim the list down a bit ;-)

there are some good examples of how the variables and macros
are used at
http://www.cncci.com/tips/tips.htm
and
http://www.programmingunlimited.com/fTipsIntro.htm
and some macros for the Renshaw probes at
http://www.programmingunlimited.com/fProbing.htm

after looking thru some of them the idea of NAMED variables starts
to sound pretty good ,the macros can reach fairly deep into the
machine settings

Brian

On Friday 05 January 2001 13:23, you wrote:
> Brian,
>
> Thanks for the ideas. The '#' sign or 'V'. Both would be easy to do.
> And I just thought, someone posted that many of the #nn's were used to
> set machine parms. I guess I could use them to load stepper steps/rev,
> tpi, etc. also? Probably from a separate file, and probably
> automatically on program startup. Otherwise, I can do my usual plain
> text parameter file with simple expressions.
>
> The #defines are an interesting thought, pre-process the file.
>
> Alan KM6VV