[mactec54]

Hi Reg, glad to help. Not that it matters much, but I'm pretty sure a G0 cancels any Fixed Cycle like G80 does. Meaning technically you wouldn't need the G80's. I just left them in there for good measure.

G00, G01, G02 and G03 all belong to the movement group of codes and will turn off any active canned cycles, not recommended though.

It is not good practice to turn off your canned cycles using movement codes.

Always make it clear that canned cycles have been turned off by using the G80 cancel command once you have finished running your canned cycles, another reason it should always be in the Program Header (Safety Line) also.

[the_gentlegiant]

....Always make it clear that canned cycles have been turned off by using the G80 cancel command once you have finished running your canned cycles, another reason it should always be in the Program Header (Safety Line) also.

Already standard practice here.

Every tool I've ever called starts out like this: (Obviously changes to start location/H/T/S and sometimes G54 needed)

T2M6 (A TOOL OF SOME KIND)
G17G20G40G49G54G80G90G98

G0X0.5Y-0.5
G43Z0.1H2S7500M3T3
M8

[mactec54]

Already standard practice here.

Every tool I've ever called starts out like this: (Obviously changes to start location/H/T/S and sometimes G54 needed)

T2M6 (A TOOL OF SOME KIND)
G17G20G40G49G54G80G90G98

G0X0.5Y-0.5
G43Z0.1H2S7500M3T3
M8

The Safety Line is not effective when you are running through a program, a G80 must be used, or it can reuse the active Canned cycle after a move to another position.

The Safety Line is in effect only at the start of a Program and cancels all previous calls that may not have been canceled.

[the_gentlegiant]

The Safety Line is not effective when you are running through a program, a G80 must be used, or it can reuse the active Canned cycle after a move to another position.

The Safety Line is in effect only at the start of a Program and cancels all previous calls that may not have been canceled.

Guess I wasn't understood earlier.

I always use G80 to end Fixed Cycles. My Safety Line only only adds to the certainty of the machine's condition at the start of a new tool. No matter what happened before it.
It may also have been missed that the programming example I gave in post #11 is how every tool starts in a program, not how every program starts. (Except for the fact that eventually, every program starts with a tool loading to the spindle.) It's super redundant, but I also use it as a tool start header, because it's easy to spot when scrolling through a program. I program semi manually, meaning no post processor is spitting out my code sight unseen, so quickly finding tool startups is important to me. The two distinct looking lines with the space right after really helps.

Earlier I only mentioned how G0 will cancel a Fixed Cycle as simply stating a matter of fact. Not that I was advocating for it in general use.