[HuFlungDung]

I suppose there is not enough user base here to get a decent poll result, but I would still like to know if the cycle "initial plane" and "retract plane" is perfect as set up.

I can see the need for a couple of different options, depending on what your controller expects. The options I am referring to are simply this: should these two planes be absolute values or incremental? Should the values be operated on mathematically or just "left alone" so to speak.

I do have sort of a system to make the resultant output come out right.

Here is what I have figured so far. Here is what I have set up in my deep hole peck cycle:

/Z{CD} Z{_PECK} /Z{_RETURNSTOP} /R{CP} /T{_DWELL} G83
/Z{_P8}

Here is how I might want a sample of code to look, where the initial plane is equal to the Rapid plane:

T4 ( 3/32 DRILL)
F12.5
S70 M3
T400
M8
/X2.6734 /Y-13.1875 /Z1. (Rapid plane absolute)
(if initial plane <> rapid plane then a value appears here)
/Z-1.2 Z-0.4 /Z-0.01 /R0.2 /T0. G83
/Z0.2 (this is the move to the initial plane, absolute in value, the cycle begins to execute at Z0.2)
/X3.1855
/X3.6976

In the above sequence the tool rapids from Z1 to Z.2, then rapids from Z.2 by the incremental distance indicated by the /R value, which brings the tool tip right to Z0. Then the drill drills an incremental Z-1.2, with a peck distance of -.4.

A chipbreak move is indicated by the /Z-0.01, which I created the variable {_RETURNSTOP} to hold. This is fine.

If the initial plane is equal to the Rapid plane, then no nc output results between the initial Rapid height and the calling of the cycle. This is okay by me.

Whatever I put into the Retract plane field is apparently subtracted from the initial plane to equal the net retract height that is output. This seems weird to me. I'd just as soon be able to type in what I want it to be in absolute, and have that exact same figure come out in my code.

For my controller, the R value is an incremental distance, that the tool will traverse (at rapid) at the start of every hole in the cycle. The end of every single cycle results in a retraction back up to where the tool started the cycle at.

Suppose Rapid height is 1", initial plane is .2" absolute and retract plane is .2" absolute. In order to make the right code, I have to enter values in the initial and retract fields that give a subtrahend of 0.2 . Thus, I would put in .2 in the initial field and 0 in the retract field. This results in nc output of .2 for the value /R{CP}. note the retract plane value of 0 is meaningless so far as where I intend to begin the tool at, which would have to be at a value of R.2

Because some kind of subtraction also seems to be performed on the initial plane variable {CP}, I cannot use it either, so instead I created this new parameter /Z{_P8}.

This is not whining. I am just wondering if there needs to be more of a "setup" to the nature of these Initial plane and Retract plane variables, depending on what various controllers require.

Perhaps it is all in the method I am thinking in, but it seems to me that the rest of the toolpath wizards operate on the principle that the various tool planes are absolute Z values, but when we get into the cycles, then all of a sudden, they switch to relative values.

I am sorry if I am not making this perfectly clear. But, you would know by now perhaps if you had any difficulty making the right input when you fill in the fields in the cycle wizard, using your own machine's cycles.

Just to test your own cycle setup, does what you have also work if you want to drill a hole at a lower level, like Z-1. down to Z-2., but maintaining your retract height at Z.2 between holes?

Maybe they should add the words "relative or incremental distance" to the Initial and Rapid planes in the cycles?

Opinions? Discussion?