Fusion 360 and GRBL errors

[patofoto (Patricio Suarez)]

I use Fusion 360 for CAD and CAM. I have upgraded to GRBL 1.1 and latest version of CM4. I keep getting GRBL errors while milling. I can’t make sense of it. I have been sending the error codes I get to the Beta team but was wondering if anyone out there using Fusion 360 was experiencing the same thing. Anyone?. Today I keep getting a lot of G2 errors.

Any suggestions?

Just realized that I had posted before about the same problem and that it could be a G19 issue. Beta team has been informed. Anyone is going through the same?

[mikep]

Which post are you using? There are several GRBL posts for Fusion360. There’s some discussion over here:

Trouble with bCNC

I’ve run a number of jobs after using the carbide3d fusion360 post. Here are the up to date Autodesk posts - note that these are the same across several products, if it’s here, it works in fusion360. I don’t know if these are automatically updated when fusion updates. The grbl post was updated 18 days ago as of this post. http://cam.autodesk.com/posts/ There are a couple interesting ones in there, including two that output DXF instead of gcode. I have these other ones as well There’s this …

[patofoto (Patricio Suarez)]

@mikep I think I’m using the latest version of post for Carbide 3D. It states that it was updated 44 days ago.

[WillAdams (William Adams (Carbide 3D))]

Things to try:

• use metric
• test w/ some other app
• turn off ramping in

[patofoto (Patricio Suarez)]

-using metric
-another app?. Like UGCS?.
-have tried with ramping off and on

Thank you always for all your help

[WillAdams (William Adams (Carbide 3D))]

Yes, try Universal G-code Sender.

[patofoto (Patricio Suarez)]

Never have used UGCS to run a job. I’m guessing you use Generic GRBL post from Fusion 360, right?.

[WillAdams (William Adams (Carbide 3D))]

For a real test, same as w/ CM.

[patofoto (Patricio Suarez)]

I continued trying different strategies in Fusion 360 to see if I could figure out what was going on. Not too scientific but this is what I came up with. Studying the paths, I discovered that the GRBL errors came while the program was moving the head from one place to another. I looked closely at the path and saw a weird little curve.

This was related, I think, to the stay down distance in the linking tab. This were my settings when I was getting the error.

I changed them to this (trial and error):

and I got this:

No more GRBL errors. Don’t really know if this means something to someone. Just posting my findings in hopes of making things better for everyone. Will send this to the Beta team also.