Having a problem using the .063 grooving tool to machine the back radii on the three radii bumps. We get a warning and no toolpath stating flute is 0. He modeled the way it was shown on academy and I modeled it differently using revolve. We both get the same error. I tried using another grooving tool and even the full radius grooving tool and get the same warning. Has anybody else seen this problem? Am I overlooking the obvious?
Here is the warning image-
This is what we are trying to remove using a .063 square grooving tool.
1 Like
There was a fusion bug related to this awhile ago. Try creating a derived grooving operation from the grooving operation that is giving you issues. See if the error goes away.
If not, are you using the provided tool library? Can you give us a screenshot of the tool definition?
I can pull up my 93L and regen the toolpath to see if it’s a recently introduced bug.
1 Like
Just regenerated the toolpath and it still works fine. I have attached screen shots of my tool definition as well as the grooving config.
1 Like
Well, I got it to work, not liking how I did it. My tools was set exactly as your setup, and I did change my passes operations to go up and down instead of down only. It was strange, it would show tool path and show bytes, but when I regenerated all the operations, I would lose tool path again. So I turned off the remaining material option and I got code, it still shows a caution, but I do have code now.
2 Likes
Strange that it won’t do it with the previous operations. I wonder if there is a specific previous operation that’s confusing it.
Also what is the remaining warning?
The flute length is zero. ???
Hello!
I’ve been messing with my copy of the 93L trying to recreate this problem, but I haven’t had any issues with it. All of Steven’s screenshots match up with my file and I’ve tried switching tools, redoing the tool path and even programming it from the OP 2 side and dragging the path over and no matter what I get a good tool path.
If you go and share the file with us, I could take a look at it and see what’s up. Here’s how to do that just in case. http://academy.titansofcnc.com/series/fusion-360-fundamentals/share-your-fusion-360-file
The only two suggestions I can give at this moment is: Make sure fusion is up to date; there’s been a few updates in the last couple weeks so maybe one of those are messing with it. And two, if you make the tool path without using “rest machining” does it give you a working path?
The flute length error is really weird, I haven’t ever seen this before.
-Tyson
Thanks for taking a look at it. I ran it at home, on my teacher desktop and the student desktop. At home and my teacher desktop are set to automatically upgrade. Here is the public link https://a360.co/2wM5o3g
It is very strange, I tried messing with the pass you currently had and kept getting the flute error, but when I deleted your pass and made a new one I was able to make one without any fuss! Even used your tool you had. Have you been making a new path from scratch when you’ve been trying to fix this or just editing the old one?
Here’s the link back, https://a360.co/2rI5dAp if it still doesn’t work with my grooving pass added.
I will have my student try it again tomorrow, it is strange. he could never get a tool path, nor could I until we got SteveBuxton’s suggestions where I changed passes to up and down instead of down only. I would get a tool path, but it would disappear when you did a regenerate all. I then changed the rest material to off and was finally able to get code. I even changed the design model by removing the .020 filets (they were added as a feature) and added the filets into the sketch path. We tried multiple attempts, even used different tools (from cloud and from included library), tried a .078 wide grooving tool. Kept getting the zero flute error. I was stumped. Thanks everyone for the help, it showed my student the power of networking, he was amazed.
Okay, I hate when I cannot figure it out… I opened the file, it looked clean until I told it to regenerate again, then the error reappeared. 
. I am hoping it may have something to do with my version of AutoDesk. It does automatically upgrade, but being a student version, may be different than yours. 