Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

5 axis trajectory - weird...

marker4x4

New member
Hello, hello, how's everyone.





I came across this oddball situation, where I can't make the cutter to retract to the clear surface between two consecutive cuts. Please see the picture and attached sample fileset.
 
It appears to be a bug when using number_cuts.


Work Around:


Rather than using the automatic number_cuts, Set the number_cuts back to 1. Copy and past the Automatic Cut, Auto Plunge, Follow Cut, and Retract.


Set the axis_shift parameter to -.0625 for the first Automatic Cut.


Turn this issue into PTC.
 
dbrainsky said:
It appears to be a bug when using number_cuts.


Work Around:


Rather than using the automatic number_cuts, Set the number_cuts back to 1. Copy and past the Automatic Cut, Auto Plunge, Follow Cut, and Retract.


Set the axis_shift parameter to -.0625 for the first Automatic Cut.


Turn this issue into PTC.





Wow, I found (another) bug
smiley32.gif
smiley32.gif
smiley32.gif
smiley32.gif
!!!


I feel special
smiley2.gif
. Thanks for the input, that's exactly what I ended up doing.
 
Mark,


Yes there is a bug in WF4 related to the retract planes when using NUMBER_CUTS. The work around is to set NUMBER_CUTS back to one, and copy/paste Automatic Cuts in Customize box, change the AXIS_SHIFT for each cut. I hit this same bug a couple months ago and turned it into PTC with no results. Maybe if you send yours in, they will have enough info to fix the bug.


Kent
 
Kent Hanson said:
Mark,


Yes there is a bug in WF4 related to the retract planes when using NUMBER_CUTS. The work around is to set NUMBER_CUTS back to one, and copy/paste Automatic Cuts in Customize box, change the AXIS_SHIFT for each cut. I hit this same bug a couple months ago and turned it into PTC with no results. Maybe if you send yours in, they will have enough info to fix the bug.


Kent





Has that been fixed in the WF5? Anyone tried?
 

Sponsor

Back
Top