Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.
Use your display name or email address to sign in:
I trimmed a basic surface parallel toolpath. Everything is get except it doesn't give me an entry move , just rapids straight to the surface. I'm using the keep tool down option and I understand that's why it's taking my entry away. Is there anyway to keep this ? Right now I'm just manually adding it in the gcode. It's now problem until I forget and rapid straight into the cut in ti.
It's happened in x6 . Before that I have no clue I got into programming in x6.
It only alarms when I activate the create arcs. All three planes cause an alarm.
The only hst paths I use are opti rough. Also happens on surface finish. Blend, parallel, ....
It's just when I filter the path. Using create arcs xy or xz yz
This happens mostly on the basic surface finish blend and parallel tool path. As well as optirough. I never use any other hst paths.
The only problem for me is trying to filter the code down. It's a hit or miss if it works. I can't find any common deal on how to resolve it
The machines have plenty of memory. I just hate waiting a half hour per 100,000 lines of code to load into the fadal. Also on opti rough if I don't create arcs in the filter tab the moves are all linearized.
So has anyone found a solid answer on how to not get helical move too short alarm on fadals yet. I've been having almost every tool path that's filtered alarm at the machine .
Well got the error againy today trying to filter a finish blend and a parallel tool path . I gave up and just left the program un filtered at fed it in the fadal by uaing DNC . Can't seem to find a pattern on what causes it.
SUM doesn't seem to catch this issue. I'll have to try the feed rate . I'm starting to think it may be that. Most of my parallel and blend paths are .02 step over at 120 ipm
this issue is really starting to drive me insane . No matter what I set the min arc length to, be it .001 or .1 , I continue to get these alarms at the fadal )we have 7 and it happens and all of them) that the helical move is too short. This seems to happen on 90% of the surface toolpaths I create.(parallel,blend optirough...) Only happens when I activate the filter.
my opti area path today did this. and afetr 10 trial and error of messing with parameters it was my helix entry was too small.
now im using a surface finish blend and I ran 70% of the program and now all of a sudden the fadl quit and said helical move to short.
How do I resolve this? Is it a post issue? fadal issue?
Ive changed the min arc length in my control def.
I'm new to indexable cutters and have never drawn a custom tool that I've actually posted out and ran.
I'm kinda lost on how I should draw this tool.
I'm using the first one on the list in the pic attached. Mfh 2000r- 10- 4t. With 4 inserts. Using the GM inserts .
This tool is being used for the TI part in my other post called " high speed roughing help"
eMastercam - your online source for all things Mastercam.
Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.