You are not logged in.
Pages: 1
Does anyone believe there is a need for a tap tool definition in Vericut? My concern has been that there isn't any feed/speed checking when running a tap tool. Since tapping feed needs to match a given spindle rpm it seems that this would be a relatively important thing to check for. Whether programming IPM or IPR the tap tool definition would have the lead defined so that checking could be performed. Any thoughts?
Thanks, Joel
Offline
I would find that to be a great enhancement.
It would also help identify a tapped hole. Unless I'm missing something, Now you have to use a drill/endmill type tool so how do you tell if a hole has been tapped or just drilled.
It would also catch wrong drill sizes.
Thanks, Clayton
Offline
A tap tool is needed. The Pitch would have to be passed with one of the SetDynamicVars settings.
Take it even farther, have an option to cut a thread. Threadmilling can do it now in Vericut. A user option since you may not want to convert threads when exporting a model.
Until then, we define a $RPM and $FEED variable that is set by S and F words.
Then in the G xx Tap cycle logic We have this code. At least it reports what TPI is being used.
MACRO "MessageMacro" {
AFTER_MOTION Yes OVERRIDE_VALUE 2 TEXT_OVERRIDE_VALUE "Tapping set for {#$RPM / #$FEED} TPI"}
Offline
Pages: 1