Lathe Parametric Programming

[britovsekmatic128]

Hello,

i am wondering is there a way to make the CAM for lathes almost automatic?

For example, i would like that the outside roughing toolpath always goes 5mm over the half of the total lenght that i set in the CAD workspace, essentially having a parameter to always offset the half+5mm in the toolpath strategies.

The same for inner roughing and finishing but always going to the BoreDepth value.

So when i change the values in CAD the CAM will update with these values, is it possible and will result in a stable programming procces or if it is even worth it and will i have troubles down the line trying to troubleshoot what went wrong/isn't working?

2nd question: Is there a way to bring in 3d cad models of holders/tools into the tool library?

3rd question: Why are the graphics in my lathe workspace simulation so funky?😬 (Milling works/looks fine)

Many thanks!!!

[ltomuta]

1. You cannot access CAD parameters in CAM.
2. You cannot import tool models. There is however a script floating around the interwebs that can read a 3D model and generate the holder geometry out of it.

[ltomuta]

Here's the link to the script mentioned above. https://www.nyccnc.com/solid-model-to-tool-holder/

[britovsekmatic128]

I know you can't  access CAD parameters in CAM directly, but since F360 is model aware i think it could posible to set the offset depth(Geometry tab) according a parameter.

[ltomuta]

As long as the model information exposed to you through an operation's CAM parameters is enough for your needs you can, of course, use it. Here's a half+5mm example

[britovsekmatic128]

For me it really isn't working. I get the paramaters working but i don't get the desired result and after clicking ok to see the toolpath and going back to editing it i get Failed to evaluate expression in the offset window.

[ltomuta]

Yes, you are right. It only works once and only if the start offset is 0.
The problem is that such expression is recursive, it uses backHeight_value to calculate the backHeight_offset but once the offset changes then backHeight_value changes as well

[ltomuta]

So here's an offset expression that does not depend on backHeight_value: 

(abs(surfaceZLow)-abs(surfaceZHigh))/2-5