Tapping Cycle is outputting wrong code, all operations are posting with tool break detection without the option to remove. Please help!

[cjelley91]

I recently started editing a post processor for a Mazak with A axis rotary table. Most of the changes I made seem to be ok,  however I am experiencing a few issues. 

First, the tapping with chip breaking cycle is outputting the code as follows:

(10-32 STI CUTTING TAP)
M1
G90
T18 M6
T28
S800 M3
G59
A0.
M8
G0 X2.3 Y-1.9
G43 Z1. H18
G0 Z0.1
G98 G95 G84 X2.3 Y-1.9 Z-0.9 R0.1 P0 Q0.2 F0.0312
G73 X2.3 Y-1.9 Z-0.9 R0.1 Q0.2 F25. K0.25 ***** (I NEED THIS LINE OF CODE REMOVED) *****
Y-0.9
Y0.9
Y1.9
X5.03
Y0.9
Y-0.9
Y-1.9
G80 G94
G0 Z1.
M9 *****(This Line and the line below are being added to every tool, I would like the option for tool break detection)*****
M350 *****(This is the M code for tool break detection) I'm not sure why every tool is automatically using this*****
M5
G53 Z0.
M152
M30

My modified post processor is attached below. Thank you.

[cjelley91]

I like how the post is outputting tool measurement after all cycles, however is there a way to disable this for certain tools within the software? Examples: shell/face mill, chamfer mills etc.?

When running multiple WCS my old post would post G0 Z5.0 to raise the machine to 5 inches above the work surface, now this new post is going to G53 Z0. I would also like this addressed.

I would also like the line at the end of the operation:

G53 Z0. (CHANGED TO G28 G91 Z0.)

THANK YOU!

[will_1]

Hi @cjelley91 ,

For the G73 issue you need a to add a break between your cases like this...

        break;

    case "chip-breaking":

For the G53 issue you can edit the writeRetract function to give you the output you are wanting.

Thanks,

Will

[cjelley91]

How would I modify this to move produce a G0 Z5.0 in between new work offsets? Is this what you're talking about?

writeRetract(Z);
zOutput.reset();

setWorkPlane(new Vector(0, 0, 0)); // reset working plane

[will_1]

Hi @cjelley91 ,

It makes sense to put it in the writeRetract function, but you don't have too. I would look at the newWorkOffset variable to decide when you output the G0 Z5.0.

I am always hesitant to hardcode values like you are wanting in cases where the touch off point is at the bottom of the stock or something like that.

Thanks,

Will