Re: gcode comments
Posted by
Alan Marconett KM6VV
on 2001-01-25 19:09:30 UTC
Thanks Ballendo!
Yes, I like the '/' slash. Should be easy to do. And might as well do
the ';' semi, as it would work for the stock defines. Could M01
"Temporary Stop" used to allow a manual tool change? What starts it
again?
Alan KM6VV
ballendo@... wrote:
Yes, I like the '/' slash. Should be easy to do. And might as well do
the ';' semi, as it would work for the stock defines. Could M01
"Temporary Stop" used to allow a manual tool change? What starts it
again?
Alan KM6VV
ballendo@... wrote:
>
> Alan,
>
> The ";" used to be the standard way to end a block of gcode. This was
> before pc-based controls. Nowadays, the CR,LF combination is the
> standard. (Carriage Return,Line Feed) But it may be worthwhile to
> allow the semicolon, for backwards compatibility. As I mentioned, the
> semicolon is still the standard for HPGL files.
>
> The "/" character is called "optional block delete". Or "optional
> block skip". Or "block skip". Or "slash code".
> Most older controls REQUIRED this "slash code" when used, to be the
> first character on the line/block. Some new controls allow its' use
> within a block, which can be VERY useful! (more later)
>
> The way it works is:
>
> When the control parser reads a "/" character, it skips the remainder
> of the line/block, IF the "Block Delete" switch (which is on the
> control panel) is SET. If the panel switch is not set, the "/" has no
> effect.
>
> This is like the M01 "optional stop".
>
> (it's later)
>
> One useful way to use block skip is to drill, or not drill, in
> related but disimilar parts. You just put a slash in front of
> the "extra" holes. If the switch is set, these lines will be skipped
> and the holes won't be drilled.
>
> Another useful way to use slash codes/block delete is to change
> feeds/speeds when making the same part from different materials. You
> just use the F word and S word as usual, BUT you put two
> different 'instances' on each line where you want to change feed or
> speed. For example:
>
> G01 x5 y3 F15 S500 / F75 S2500
>
> Now most controls which support mid-line/block "/" will set F to 75
> and S to 2500, if the switch is OFF(since the parser usually replaces
> until the last parameter is read). If the switch is on, these codes
> are not read and the F15 and S500 will be used.
>
> pretty cool, huh!
>
> You can use a variation of this technique to "add-in" roughing passes
> when machining castings, based on operator evaluation...
>
> Hope this helps.
>
> Ballendo
>
> P.S. I tried to get Tom to implement this in EMC, but last I checked,
> he hadn't...
>
> >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.
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