Re: G-code user variables; convention?

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

Brian Pitt wrote:

>
> Alan,
>
> for a roll your own interpreter the #NamedVariables would be fine ,but
> the programs would not be portable to a diffrent machine,not very
> many are anyway of course ;-)
> they would make programs more readable
> you could also keep the usual numbered variables and add a
> NAME field to the variable table ie.
>
> #0100 [ALIAS #MyVariable]; (sets the name field)
> #MyVariable = 2.54;
>
> or even
>
> #define #0100 #MyVariable
>
> and pass the program thru a preprocesor step before running it
> (could also check for out of range numbers,bad calls,etc)
>
> Brian
> Ps Okuma and one or two others use 'V' for variables as well
> most mills I've seen to use the'#' sign
>
> On Thursday 04 January 2001 23:20, you wrote:
> > Jon,
> >
> > If variables are preceded with a #, then #MyVariable could be
> > distinguished from a 'M', for example. Shouldn't be that hard. Is this
> > useful? reasonable? Otherwise, a "separator" (white space), or the
> > start of a numeric field could be used, and "words" would have to be
> > "whole" (Avar7 would NOT be recognized as 'A'). Other ideas?
> >
> > CNCpro uses V0 - V100 e.g., "V59=2.34", although I really didn't want to
> > copy him!
> >
> > Alan KM6VV