CAD CAM EDM DRO - Yahoo Group Archive

Re: gcode comments

on 2001-01-25 10:55:29 UTC
Ballendo,

So is the ';' not advisable? I want to implement the "stock size"
also. I have also read (NIST ?) that '/' can be used to "comment out" a
line. Is this in general acceptance? I like the '()' comments, easy to
parse. Although I'm inclined to put in "//" or "/* ... */" comments!
;>)

Jon E. brought up G92, which is something I had been looking for. His
description (thank you Jon) also reminded to put in code for limit and
home switches (not that I've got any switches mounted yet). Seems the
G92 also saves (to file) the offset of the "new coordinate" to the home,
so that it can be re-established (hope I got that right). What I want
to know, is/are there specific command(s) to "go home" and zero the X/Y
axis?

Alan KM6VV

ballendo@... wrote:
>
> Smoke,
>
> The standard gcode character for identifying comments is the "(" .
> Some controls will require a closing parenthesis also, but most just
> stop reading the line/block when they encounter a "(" left
> parenthesis.
>
> Some controls (usually HPGL related) use a semicolon ";" as the 'end
> of line/block' character. Some will assume a linefeed also, others
> will require an implicit linefeed (the 'enter' key).
>
> BTW, non-standard characters are used for these two functions in many
> programs. One can often tell what language the controller programmer
> used to create the code since "'" (used in BASIC) and "*/" (used in C)
> are found used to define comments in several cnc controller
> programs...
>
> Hope this helps.
>
> Ballendo
>
> P.S. These types of characters are sometimes referred to as
> "delimiters". Which means they are the character used to determine
> when one thing ends (its' limit) and possibly another begins...
>
> >I did find that you can (one you learn how) save some time by setting
> >up your tools and stock size in advance right in your text program.
> >you have to precede them with a semi-colon and (in my case if I want
> >to run the program on the schools machine) surround the whole
> >statement with a set of parentheses ().
> >Smoke
>

Discussion Thread

Alan Marconett KM6VV 2001-01-25 10:55:29 UTC Re: gcode comments Jon Elson 2001-01-25 15:29:59 UTC Re: [CAD_CAM_EDM_DRO] Re: gcode comments ballendo@y... 2001-01-25 18:18:52 UTC Re: gcode comments Alan Marconett KM6VV 2001-01-25 19:09:30 UTC Re: gcode comments ballendo@y... 2001-01-25 21:20:23 UTC Re: gcode comments Ray 2001-01-26 18:35:37 UTC Re: gcode comments Alan Marconett KM6VV 2001-01-26 19:11:12 UTC Re: gcode comments ballendo@y... 2001-01-27 19:03:41 UTC Re: gcode comments Matt Shaver 2001-01-27 22:04:29 UTC Re: [CAD_CAM_EDM_DRO] Re: gcode comments Brian Pitt 2001-01-27 22:46:33 UTC Re: [CAD_CAM_EDM_DRO] Re: gcode comments Raymond Henry 2001-01-28 20:08:41 UTC Re: Re: gcode comments ballendo@y... 2001-01-29 16:02:45 UTC Re: gcode comments ballendo@y... 2001-01-29 16:25:38 UTC re:Re: gcode comments ballendo@y... 2001-01-29 19:37:12 UTC re:Re: Re: gcode comments Brian Pitt 2001-01-30 02:22:54 UTC Re: [CAD_CAM_EDM_DRO] re:Re: gcode comments ballendo@y... 2001-01-30 21:14:58 UTC re:re:Re: gcode comments Smoke 2001-01-30 21:32:45 UTC Re: [CAD_CAM_EDM_DRO] re:re:Re: gcode comments Brian Pitt 2001-01-30 23:48:17 UTC Re: [CAD_CAM_EDM_DRO] re:re:Re: gcode comments ballendo@y... 2001-01-31 03:20:13 UTC re:re:Re: gcode comments ballendo@y... 2001-01-31 03:50:09 UTC re:re:Re: gcode comments