2D Contour - Finishing Passes Use Roughing Feedrate

[BbellYS6XC]

In the attached file, I have a 2D contour path for machining across the grain in hardwood. The goal is to have two roughing passes, each at multiple depths, and two finishing passes at full depth. The finishing passes should be at a slower feedrate (100ipm). 

When I simulate the toolpath, it seems to do what I want except that the finishing passes are done at the same feedrate as the roughing passes.

What am I doing wrong?

Edit - I removed the multiple depths and roughing passes and get the same result: even though the Finish Feedrate is set to 120ipm, it still uses the tool default of 536ipm for the finishing passes. So apparently it just ignores the Finish Feedrate.

I can obviously just separate it into two toolpaths, a roughing toolpath and a finishing toolpath, but I'd like to know if I'm misunderstanding what the different settings are for. Thanks

[engineguy · Accepted solution]

@BbellYS6XC 

Seems like some weird "bug" at your end, I tried various changes same as you but could not get it to work, so whatever it is I am missing it as well 😞

So, on a wild guess I created a new 2D Contour with the same settings and that works, tried changes to that and it still works, see image below of simulation showing the Finishing feedrate at the 120in/min, very strange, what build are you on? I am on 2.0.15023, file attached 🙂

Try doing a new Contour and see if that works 🙂

[BbellYS6XC]

Isn't that bizarre.

Like you suggested, I created a new 2D Contour toolpath with all the same settings. Now it does the second of the two finishing passes at the slower feedrate, but the first one is still at the higher feedrate. So apparently it distinguishes between the "real" finishing pass and all the "faux" finishing passes that come before. 

Thanks for your help.

[oleg.tikhomirov]

Hi @BbellYS6XC

Thanks for feedback. 

1) Not using finishing feedrate for your original example is a bug. I'll create a ticket and post it here.

2) Finishing feedrate aplies only to final finishing path. You can see it in tool tip so it works as designed. But I see your point so I'll create improvment request and post number here.

[oleg.tikhomirov]

CAM-41670 and CAM-41671

[brianEF265]

I may be seeing the same issue - simulate runs at the same federate despite the roughing and finishing passes having different rates. Have the above tickets been resolved? (If it's possible for me to check myself, could you post a link to how it's done? I couldn't figure it how to get to the issue tracker with google).

[a.laasW8M6T]

Hi

Fusion simulation will not show different feedrates, they are all represented at the same speed(even rapids).

Edit:

While the movement on the screen doesn't differentiate you can still see what the feedrate is for the current move in the info tab

As for the Tickets, they are for Internal Autodesk use only and cannot be accessed by the public

You can also check in the toolpath data: