Re: G-code user variables; convention?

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


Jon Elson wrote:

>
> Matt Shaver wrote:
>
> > Alan Marconett KM6VV wrote:
> >
> > > I have been thinking of adding variables. NIST
> > > uses #nnn for a variable name. Not very intuitive (no disrespect
> > > intended as I admire the efforts of NIST; but variable NAMES are a lot
> > > easier to work with). CNCpro has variables, might be same/similar.
> > > What's the standard (ha)? I'm inclined to "do my own", you know how us
> > > programmer types are. ;>)
> >
> > Most commercial controls have three or four digit numbered variables
> > (usually called parameters in the documentation). They're used for all
> > kinds of purposes including configuring the behavior of the control and
> > displaying the state of internal logic terms. I figure that's where NIST
> > got the idea to use numbered, rather than named, variables.
>
> Right! How will you keep named variables from being confused with
> the command words, that use many of the alphabetic characters?
>
> Jon