Rest Machining stopped working on this part.

[CuttingEdgeManufacturing]

Still doing some testing to isolate issue, but basically at an earlier point the rest machining was working just fine from what i recall.

Setup 2:

Basically tool 18(2.0" FM) clears almost all the material from the part, then i come in where i can with T12 and T7 (.5" and .25" respectively) to do some more clean up. and then T15 (.5" relieved) comes in to clean up the rest before we start ballmilling. however. all 4 of these tools are removing all material as if rest machining is not present. i have regenerated toolpaths, i have removed operations and did them again. nothing is fixing the problem.

any silly thing i did that causes this? or is this an ongoing issue?

[CuttingEdgeManufacturing]

Almost immediately after this post i found that changing (continue rest machining) in the stock tab of setup2 to false, the operations are using rest machining properly now. i believe i should be able to continue using rest stock in this instance.. so that makes this a bug i think?

[mattdlr89]

@CuttingEdgeManufacturing I'm seeing the same as you. The rest material is failing to generate when you have the "continue rest machining" checked. If you don't use that then it seems to work fine but appears to be a bug to me. @seth.madore do you agree?

[mattdlr89]

@CuttingEdgeManufacturing I think it is the empty toolpath in Setup1 causing the issue. If you delete that then rest works for me. Also seems like a bug as an empty toolpath shouldn't break everything else. 

[CuttingEdgeManufacturing]

Oops. forgot I had that in there. Yea that shouldn't break rest machining. at least its not likely a very common issue. 

[seth.madore]

---

@mattdlr89 wrote:

@CuttingEdgeManufacturing I'm seeing the same as you. The rest material is failing to generate when you have the "continue rest machining" checked. If you don't use that then it seems to work fine but appears to be a bug to me. @seth.madore do you agree?

---

Thanks for tagging me. This does look like a bug, I'll investigate this morning