Advanced 5X question

[gcode]

I've uploaded a file the the X5 folder in the FTP site

filename = swarf.mcx-5

The first toolpath is a legacy 5X swarf taking multiple depth cuts

The second cut is my attempt to replicate it with an advance 5X toolpath.

It looks OK, but if you backplot and watch carefully you'll see its offest from the surface

by quite a bit.

Can anybody tell me what I need to do to make this toolpath work??

[Mic]

It's the combination of collision control and depth cuts.

 

If the tilt angle is just slightly off because of the collision control then your depth cuts will multiply this error on every new depth as they are offset axial.

 

If you use the normal stepover on the cut pattern side the tool will touch the surface in all levels.

[mayday]

I generally use morgh between to curves. add a curve to the top of the surface. Then use margins to get the depth cuts you want. Swarf seems very limited when the curves get a little complex, Plus you get much better tool axis control using limits.

[gcode]

I'll try that., but

I need ther reduced stepdown towards the bottom of the vane as the stock gets heavier there.

Maybe a legacy swarf is a better choice for this cut.

[Müřlıń®]

G did you figure out swarf yet?

 

I keep getting violation with tapered tools when using the new impeller blade finish.

 

Tried just a plain swarf but wow... there is allot of settings on that toolpath....havent got it to work yet.

[gcode]

I keep getting violation with tapered tools when using the new impeller blade finish.

 

try changing th SIde Tilt setting from 0 to 90 to 0 to (90- half your taper tool)

[mayday]

Also turn on side tilt collision when using a taper tool. that makes it look at the taper angle of the tool

[Müřlıń®]

Thanks guys will try those suggestions.

[idahobum]

Actually, check the cutter offset value on the backplot options screen. X5 automatically adds half the cutter diameter and it shows the tool off the surface you are trying to cut. Its just a visual issue, the actual nc code is correct, by setting the value back to 0 it should display correctly.