Off center wrapping around X?

[jeff.brower]

We are driving a facemill around the outside of a cylinder on a vertical machine with a 4th axis rotary along X. We want to drive the tool 1.25" off center of Y rather than on center. Currently we are hand editing the Y axis move and it's working but not ideal. How do we make FC drive the tool centerline along the part at Y1.25?

Another issue coming up is a future cylinder shape part that will have several areas with larger diameters so we will want to drive the facemill along a contoured shape rather than just a straight cylinder. We will need to move the facemill into the valleys (along Y axis) then up in Z to the larger diameters while rotating Z and moving along X

Thanks,

Jeff

[zlancy244]

could add something like this into your post processor

<IF>[eq(<TOOL-NAME>,"3in Facemill")]<THEN>

[<Y-COORD> = <Y-COORD> + 1.5]

<ENDIF>

[jeff.brower]

Hadn't thought about a solution like that, thanks for the idea. We would prefer to figure out how to do it inside FC.

[marc-andre.jean]

Hi @jeff.brower,

There is a 3D feature that allow you to offset the Y axis in FeatureCAM. You must have a 3D shape of your part, and the finishing strategy named Four Axis Rotary will allow you to enroll the toolpath around any shapes of piece and follow it with your tool at a specific Y value.

This strategy will offer you three toolpath type (linear, cicular or Spiral) and the ability to offset your tool with a specific Y value.

To activate it, you must to be in a 4 axis project (defined in the stock proprieties). It's not necessary to have an Ultimate licence, only a Premium one since it,s not considered as a full 4 axis strategy.

Let me know if my solution could help you!

[jeff.brower]

Thank you, we need to try this to see if it works for our situation.

[Anonymous]

If something work in FCAM simulation and doesnt in real milling, postprocessor/machine limits is a reason, or both.

So you shouldn't tell that you prefer only fcam changes.

[marc-andre.jean]

Hi @Anonymous,

many posts processor have Y value forced to "0" when the wrapping is activated. The best would be to contact your local post team to verify if it's the case in your issue.