2D Contour - Transition moves perform with Cutting Feedrate

[tayfun]

Hello everyone,

Today I realized a possible bug on 2D Contour strategy. Maybe it's not.

I have made a CAM program on 24 May 2017. At this date, everything was like it supposed to be. But today I re-generate all toolpaths and I saw that transition moves performing with Cutting Feedrate which is very slow. If I don't re-generate them, it still acts like it supposed to be. (transition moves with lead-in lead-out feedrate.)

Transition paths show with green lines like Lead-in and out paths. But Fusion 360 considers "Cutting feedrate" as feedrate right after lead-out path unlike the date 24 May 2017.

Please check the simulation videos and keep your eyes on my mouse cursor. 

[Laurens-3DTechDraw]

As a tip for the next time making a video might be a lot easier with Screencast which you can find here: https://knowledge.autodesk.com/community/screencast

You don't have to but it might be easier.

What you see here is a little tricky to get right and I know the developers aren't totally sure on how they want to work this out.

That move should at least be in lead-out feedrate, but possibly we need to use stay-down linking feedrate. (Not implemented in all Operations but maybe it should)

What speed did it use before the regeneration?

[tayfun]

Thank you for the tip. I'll use it next time.

Before regeneration, it was same with lead-out feedrate which is 7000mm/min.And movement is Lead-Out. Please check the image. It's before regeneration.

Right now, as you can see it is 600mm/min. It causes to a lot longer cycle time.

[tayfun]

As a temporary solution, I closed "keep tool down" option under "Linking" tab. It more/less reduced cycle time to same like 24 May 2017. But Z axis always move to "Retract Plane" with G0 movement as predicted. I think this is unwanted situation which causes unnecessary Z axis up&down movements and it is obvious there has been some algorithm changes since May.

I hope developers is going to put a textbox/checkbox/radio button under the keep tool down option to adjust transition feedrate instead derive it from cutting feedrate.

[Laurens-3DTechDraw · Accepted solution]

---

@Anonymous wrote:

I hope developers is going to put a textbox/checkbox/radio button under the keep tool down option to adjust transition feedrate instead derive it from cutting feedrate.

---

Yes! We need that.

[andypugh]

I am not sure about the "Solved" tag on this. 

It seems that 2D Adaptive still has non-engagement cuts at the rapid rate, but I would consider 2D pocket to be unusable at the moment when (for my current part) 90% of the time the cutter is not touching the work but is still moving at the feed rate. (Using rapid retract doesn't really cut it for me with my knee-mill)

[Laurens-3DTechDraw]

I think the solved marking is due to the fact the question got answered.

Not that the problem got solved.

For that we will tag @cj.abraham to see if this has a ticket in the system still, and if there are any updates on it.

[bmxjeff]

Any updates on this? I didn't see an Autodesker comment @al.whatmough.  

[cj.abraham]

Added CAM-9094 to allow use of non-engagement feedrate when using keep tool down.

[bmxjeff]

Thanks! @cj.abraham

[Steinwerks]

---

@cj.abraham wrote:

Added CAM-9094 to allow use of non-engagement feedrate when using keep tool down.

---

Oooh this would be really welcome! Thanks @cj.abraham!

[Eric_E]

Good idea, I hope the developers are motivated to do this soon. If not, could we at least get the transition move at the lead out feed rate as it used to be.

[Anonymous]

Has this ever been fixed? (It has been some time)

I am using version 7.0.0.17442 and it is still 'transitioning' at the cutting feedrate!

I am working on a part here which has 18,000"(457,200mm) of transitioning....

[bmxjeff]

@cj.abraham Any news : )

[Anonymous]

I would love for this to be addressed.  80% of my programming is 2D contour and for 3 years I've been using a custom script to modify the nc code as a workaround.  I've spent hours trying to work it out in my post processor but was never able to come up with a solution.

[seth.madore]

@bmxjeff this doesn't look like it's gone anywhere, sadly. Opening up the case again and asking if there is any chance for improvement.

[Anonymous]

Any update? (on CAM-9094)

[thekondrat]

Hello @seth.madore 

Do you have any news about  CAM-9094 ticket?