Error in 2D chamfer toolpath

[Don.Cyr]

Trying to machine a chamfer around a profile but the toolpath will not generate with the following errors:

I don't see a ramp clearance height and the vertical leads-in is 0.

Any ideas?

I can work around it for now by doing a contour toolpath but would like to report a possible bug or at least get clarification on what the warning means.

Thank you.

I

[DarthBane55]

The 1st part of the warning is just a warning, that is not the reason for no toolpath generated.  It says that adding the ramp clearance height and the vertical radius is more than a specified value for feed height that you specified.  Meaning it will feed from higher than you specified in the feed height.  Just letting you know of that, but this is not preventing the toolpath.  

The "no passes to link" is what prevented it.  Gotta love that message...  it really provides no reason whatsoever as to why no toolpath was generated...  Sometimes it's easy, but sometimes, it is very frustrating.

Now in 2d chamfer, in the passes tab, there is a parameter for "chamfer clearance".  This is a value by which the tool will stay away from any walls that might be along the toolpath, so that your tool does not crash.  Without seeing your file, I don't know if you have any walls in the way...  but from experience, I know that sometimes this does not work and doesn't generate a toolpath.  Sometimes it's user induced, sometimes it's just a bug, or something that it sees that is not really there.  Then you right click on the path and choose "create derived operation" and choose 2d contour, and then you manage the clearance manually, meaning it can crash if you don't look at the result carefully, but this works always (and I believe this is what you did to solve your problem).

[engineguy]

@Don.Cyr 

Best to upload the file you are having problems with, I am not able to re-create your issue so it may be possible there is a problem with your Model.

Please upload a file that you have problems with, go to File > Export . Select f3d format and save to your PC somewhere and then attach it to your next reply.

Regards

Rob

[Don.Cyr · Accepted solution]

Thanks for the help, unfortunately, I can't post the part on here, with this particular customer, I can't even store these on Fusion cloud and have to save everything locally and work off-line... what a PITA.

I will work around it for now to get it running.

[seth.madore]

As @DarthBane55 suggested, the first warning is not the issue with failure to generate. 

Is it possible that your model already has the chamfer modeled on it? If so, you want to set your Chamfer value to zero and select the top section of the chamfer:

 

 

[euclidmandd]

I'd like to resurrect this post because the bug/error is still present 2 years later.  2D chamfer has no place to modify the ramp clearance height, yet it will still throw a warning and move the feed height up based on the ramp clearance height.  I realize it's not a show stopper, but it's annoying.  I don't like leaving warnings because it can make you numb to real issues and defeats the purpose of having them.  And ultimately it's preventing the toolpath from doing what it's supposed to.  Is there any "back-door" per se for seeing/changing operation parameters?  Or perhaps there's another way to set the default for a parameter since I can't do it through the operation dialog?

Unimportant side note:

While experimenting around, I also found some weird/undesirable behavior with ramping a chamfer with 2D contour.  The height the ramping begins at is based on the top height plus the ramp clearance.  I think that's fine for typical (non chamfering) operations, but it neglects the chamfer tip offset.  So even if the top height is set to "selected contour" and ramp height is set to 0, the tool ramps from the selected contour down by the chamfer tip offset.  In other words, I don't think there's any way to do less ramping than the tip offset. Honestly this isn't a problem for me since I never ramp with a chamfer, but I thought I'd point it out since it's probably not the behavior most people would expect.