[glovebox20]

Hey All.

Just wondering if anyone else is haveing problems with their tap feedrates when importing tools.

When I import my tools from a tool table, the Feed rate for the taps is way off. After a lot of diging, I found the post was using 'tool_drill_lead' * 'spin' for the tap feed rate caluation.

What is 'tool_drill_lead' on a tap and why is it being used for the feed rate caluation? I using the Standard gMilling_Haas_3x post witch we recived when installing the software.

[txcncman]

Lead equals the distance the thread advances in one revolution. A 1/4" - 20 thread advances 1" on 20 revolutions, so to get the amount of advancing for one revolution, you would divide 1" by 20 revolutions (1" / 20 = 0.050"=lead). If you spin this tap 1000 times per minute (RPM), to get the feed rate needed, you would multiply the lead (0.050") times the "spin" (1000) which would be 0.050" X 1000 = 50 IPM (Inches Per Minute).

[glovebox20]

I guess that makes sense.

But why is the "tool_drill_lead" different than the "feed_teeth" value?

[glovebox20]

I attached a file showing the error.

[glovebox20]

I posted some screen shots of my tool set up and the Tap feed rate not matching the operation Data Feed Rate. Running Inventorcam 2012

[txcncman]

Feed per teeth is for milling. Period.

Why your software is outputting the feed rate incorrectly, I have no idea. Maybe you need to contact support for your software.

You know the correct answer now. You can input it manually before running the program.

[glovebox20]

Feed per teeth is for milling. Period.

Why your software is outputting the feed rate incorrectly, I have no idea. Maybe you need to contact support for your software.

You know the correct answer now. You can input it manually before running the program.

If I wanted to wirte G-codes by hand, I wouldn't use cam!!!

I have contacted Solidcam support and they did admit that there tool tables need work, and they are 'currently working' on the problem. I feel that they are waiting until the next version release to fix it, and in the meantime, I'm breaking Taps!

I just can't belive I'm the only one with this problem. Nice software otherwise, but I will not tolerate improper feed rates with my cam software. Taps are no exception.

[txcncman]

If I wanted to wirte G-codes by hand, I wouldn't use cam!!!

I have contacted Solidcam support and they did admit that there tool tables need work, and they are 'currently working' on the problem. I feel that they are waiting until the next version release to fix it, and in the meantime, I'm breaking Taps!

I just can't belive I'm the only one with this problem. Nice software otherwise, but I will not tolerate improper feed rates with my cam software. Taps are no exception.

Sorry. "Want to" and "have to" are sometimes different things.

[glovebox20]

Sorry. "Want to" and "have to" are sometimes different things.

Thanks for clearing that up for me, but It still dosn't make me feel any better when there is a tap stuck in my part. I guess I'll have to learn to slow down and double check everything.

[simonsayshello]

Hi Glovebox20,
I have the same problem except mine will post a feed rate of 196.456 if I don't catch it it turns my Haas into a punch press I had solidcam on the phone and got no real answer they told me to change the number of flutes on the tap and I thought what does flutes have to do with feed and pitch and then save the tap as a Tab file in the tool library so I did I made new Taps library as a Tab file and I can use a tap in one program and it will work fine but in the next program it doesn't work so I have to check all my tap code.

[glovebox20]

Hi Glovebox20,
I have the same problem except mine will post a feed rate of 196.456 if I don't catch it it turns my Haas into a punch press I had solidcam on the phone and got no real answer they told me to change the number of flutes on the tap and I thought what does flutes have to do with feed and pitch and then save the tap as a Tab file in the tool library so I did I made new Taps library as a Tab file and I can use a tap in one program and it will work fine but in the next program it doesn't work so I have to check all my tap code.

I got the same respond as well from Solidcam about the # of flutes. If you need help modfiying your post so the displayed Feedrate in your opertion Data is what Solidcam will post, I can help you out with that.