Run times from set-up sheet

[nickz]

Did a search and have not found any topics regarding my problem....

When running my set-up sheet, the run-time for my tapping is huge. This is because we are running "Rigid Tapping, (synchronized)" and the G-code macro for this requires FPR, "feed per revolution". This is causing the run-time on the set-up sheet to become unrealistic. Is there some where I can fix this? Post? Config? etc.

Thanks

[CycleTimeCharles]

You should setup your post so that it outputs the pitch from the Tap parameters not from the feed rate dialog. That way you and the setup sheet see the actual feed rate and the post outputs the pitch.

The variable to output in the post is n_tap_thds

[nickz]

The G-code output is correct, its only the run-time that is being processed as if it is FPM (feed per minute) instead of FPR. The pitch is coming out as the feedrate in the G-code correct.

ie. M10 x 1.5 thread,

Fanuc control, metric.

G842 X0. Y0. Z-30. R2.5 F1.5

G95 is in the G842 macro and is the only time we use FPR, all other operations are FPM.

[CycleTimeCharles]

I was not trying to change the output of your code, just that the feedrate variable needs to be the actual feedrate for the setup sheet to work properly. This will require the post to use the TPI variable and not the feedrate value. It also makes programming easier, you pick the tap and you do not need to fill in the feed.

[nickz]

Yes you are correct, sir.

Ok, I am using a Fanuc post and the variable "n_tap_thds" is not in this post. Is this a "system variable" (lack of better description) that I can include into the post or other file? I am using the HTML set-up sheet and I do not completely understand how this system works.

[This message has been edited by nickz (edited 07-27-2001).]

[CycleTimeCharles]

Yes it is a "system variable"

Check out MPMASTER.PST from this web site and see how "n_tap_thds" is used.