canned cycles was EMC interpreter was Re: BoBCad Question

Art,

This may help you understand canned cycles:

On the old NC (no computer, therefore no C) control was by tape with
punched holes. The tape was run through a reader for each run/part.
Operator/programmers soon found that they were repeatedly using the
same set of instructions (when boring a hole, for example). They made
sections of tape containing these commonly used cycles, and spliced
the short sections of tape into the program as needed. Since the tape
was paper, these short pieces of tape were kept in cans to prevent
moisture from ruining them. So, "canned" cycles. The first OOP
(object oriented programming) :-)

Later, programs to be run many times were put onto plastic tape, for
durability, but this was expensive, and paper tape machines were
still seen in the late 70's.

So, the answer is that a canned cycle is a set of instructions which
can be called at any time, and has certain properties and parameters
(similar to a programming object). There ARE "standard" canned cycles
for drilling/boring/ etc. , but mfrs can create ANY canned cycle they
feel will be helpful to their customers.

The "standard" canned cycles are from G80 to G89. Many controll mfrs.
use the G70's for add-on canned cycles... (pocket milling, for
example)

Hope this helps.

Ballendo

--- In CAD_CAM_EDM_DRO@y..., "Fred Smith" <imserv@v...> wrote:
> >Do
> > I understand correctly, that a Canned Cycle is a subroutine by
> another name,
> > or is a canned cycle limited in its application?
> > Art F
>
>
> A canned cycle is NOT a subroutine. A subroutine involves
> redirecting the serial execution of a CNC program, they are
nestable, and can have multiple repetitions.
>
> A canned cycle is a valid word address, the same as G01, G02, G00,
> etc. It is executed in sequential order the same as any other G-
code.
>
>
> Best Regards,
>
> Fred Smith
> IMService