Chamfer tip offset cannot be negative...... It isnt

Chamfer tip offset cannot be negative...... It isnt

Ryan_Fab
Advocate Advocate
770 Views
5 Replies
Message 1 of 6

Chamfer tip offset cannot be negative...... It isnt

Ryan_Fab
Advocate
Advocate

Hi Everyone,

 

An error that Ive been seeing lately is when chamfering. Im getting an invalid value. It says tip offset cannot be negative, but Im not asking it to be. I can get around it by just removing the 'mm' from the end of the number and it turns to black and computes.

 

Should I be posting this in bugs?

 

 

Ryan_Fab_0-1642067125112.png

 

0 Likes
771 Views
5 Replies
Replies (5)
Message 2 of 6

seth.madore
Community Manager
Community Manager

No, you've come to the right place for that issue. Could you share your file so we can see what may be causing this?

File > Export > Save to local folder, return to thread and attach the .f3d file in your reply


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 3 of 6

Ryan_Fab
Advocate
Advocate

Cheers Seth, 

 

file attached as requested

0 Likes
Message 4 of 6

seth.madore
Community Manager
Community Manager

And what happens if you just regenerate the toolpath without changing the "mm"?

I opened up your file and do see the red "!" in the Browser, but when I open up the toolpath, nothing is in error. Clicking OK just calculates the toolpath without an issue.


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 5 of 6

Ryan_Fab
Advocate
Advocate

The 1.5mm field remains red and causes the same error. The only thing that fixes it for me is to input it again minus the mm.

 

If at any point i regenerate the whole setup or even the one process it brings back the error.

0 Likes
Message 6 of 6

zach.allaun
Advocate
Advocate

I've been meaning to post about this but haven't had the time. I'm having the exact same issue as Ryan on, I believe, every instance of 2D Chamfer. While it will regenerate the toolpath despite the error, if you edit the toolpath, you cannot click "OK" until you've deleted the unit. It will then temporarily show no error, but the moment you edit again (or save the file and open it again later), the error will appear again.

 

This is one of those things that doesn't *technically* limit me in any way, but I firmly believe that spurious/incorrect warnings/errors really need to be addressed ASAP. These sorts of things train users to ignore warnings, causing them to miss valid warnings or errors when they come up.

 

Since I've found time to reply, I'm also going to piggyback on this and suggest that Fusion should have a better solution for warnings/errors in general. Fusion is a large, actively developed system that's trying to develop sane defaults that are correct for the majority of users, but this means a lot of spurious warnings. An example and my personal pet peeve: finish feedrate is higher than cutting feedrate (finish feedrate occasionally should be higher than the cutting feedrate to account for chip thinning). The problem is that there's no way for me to say, "Hey, Fusion, I'm cool with this situation, please don't warn me about this." Instead, my Setup now has a warning indicator that will forevermore mask warnings I may actually care about.

 

A solution to dismiss warnings (and possibly even "errors", such as the one that spawned this thread) would be really helpful in maintaining files/setups that occasionally "break the rules" without inuring users to warnings as a whole.