We are having issues creating the following toolpaths with Pro/E. Please note that this is currently possible in MasterCAM. The goal is to rough the following mill surface with a ball nose end mill in a helical type of motion - keeping a constant helical depth change all the way down:
Here is the mill surface:
When using Cut Line machining with a helical motion the toolpath looks like this. As you can see the helical motion between the spherical and conical part of the mill surface is not a constant plunging depth. This type of tool motion would be fine for finishing the surfaces but we are helical cutting into solid material:
I did create geometry that the tool follows to create the following sequence. This is possible but took a while to create a number of features to accomplish this:
We would like to ask PTC to enhance the Cut Line Helical milling output to provide a constant helical plunging motion down the entire mill surface. Has anyone else made a request from PTC to change this?
Best regards, Michael Braaten Synthes
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
I know we discussed this before and the solution was posted here, but I'd like to share some screenshots from Creo/Elements Pro M070 with Mike's problem solved: The picture above is no longer from another CAD/CAM system... 😉 Thanks PTC and customers who reported this issue... Best regards, Daniel
I have a 65mb ncl file. Vericut starts playback but a little ways into the verification at the beginning of a new tool vericut exits with no warning messages. I am running WF5 M070 on a dell T5500, 3.33 xeon, 6gb memory, Quadro FX 4800 using Nvidia driver 266.45, win 7 pro 64 bit.
Has anybody seen this before? Any suggestions on resolving?