Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Tapping - TPI value is ignored for taps only Pitch is currently supported
Curt_Welch
Member, csevp Posts: 42 ✭✭
in CAM Studio
I tested rigid tapping on the Haas quickly yesterday. It worked fine, but there is a dangerous bug/(broken feature) in the current beta system to watch out for.
You must enter the thread information when you define the tool, but even though the system allows you to enter threads in TPI (imperial) or Pitch (metric), the TPI value is ignored, and only the Pitch is currently used.
Before trusting the system and breaking a tap, I checked the g-code to determine what it was doing and saw this issue.
The system uses the thread pitch as defined in the tool, along with the RPM you enter, to calculate the feed. The Plunge value you can enter isn't used in the tapping cycle (which is fine).
However, the tool definition allows you to enter the thread data either in TPI (imperial standard) or Pitch (metric standard). However, the TPI value is ignored, and only the Pitch is currently implemented to control the tap cycle.
So even though you select the TPI option, which hides the pitch setting on the tool, and you enter 20 (for my 1/4-20 tap) the value of 1 is left hidden in the Pitch option, and the tap cycle produced is for 1 mm/thread vs 20 threads per inch.
So to make it work with my 1/4-20 tap, I had to convert from impertial threads to metric Pitch value (25.4/20 = 1.27) and enter that value as the pitch of the tap.
This is clearly just a work in progress with the software, as support for inches is implemented. But in this current half-implemented state, someone could break a tap not knowing the TPI value is being ignored.
However, as long as you don't trip over this half-implemented feature, I could tap holes just fine on my Haas! (once I realized the first tap I pulled out of the box wasn't the 1/4-20 trap I thought it was).
You must enter the thread information when you define the tool, but even though the system allows you to enter threads in TPI (imperial) or Pitch (metric), the TPI value is ignored, and only the Pitch is currently used.
Before trusting the system and breaking a tap, I checked the g-code to determine what it was doing and saw this issue.
The system uses the thread pitch as defined in the tool, along with the RPM you enter, to calculate the feed. The Plunge value you can enter isn't used in the tapping cycle (which is fine).
However, the tool definition allows you to enter the thread data either in TPI (imperial standard) or Pitch (metric standard). However, the TPI value is ignored, and only the Pitch is currently implemented to control the tap cycle.
So even though you select the TPI option, which hides the pitch setting on the tool, and you enter 20 (for my 1/4-20 tap) the value of 1 is left hidden in the Pitch option, and the tap cycle produced is for 1 mm/thread vs 20 threads per inch.
So to make it work with my 1/4-20 tap, I had to convert from impertial threads to metric Pitch value (25.4/20 = 1.27) and enter that value as the pitch of the tap.
This is clearly just a work in progress with the software, as support for inches is implemented. But in this current half-implemented state, someone could break a tap not knowing the TPI value is being ignored.
However, as long as you don't trip over this half-implemented feature, I could tap holes just fine on my Haas! (once I realized the first tap I pulled out of the box wasn't the 1/4-20 trap I thought it was).
0
Comments