Trying out the male portion of an inlay this evening. GRBL generated in Fusion360. The run got to 12.8% then quit and generated this error. Any thoughts?
snowflake inlay m 8.nc (137.1 KB)
This error keeps coming up. Apparently it’s caused by Grbl and Fusion 360 not agreeing about how arcs are calculated — keeping Fusion 360 from generating them is one solution (there are some post-processors which do this).
One can check if it will happen by running a file through Grbl in check mode — I believe there’s a utility for this, or an option in Grbl for it — here:
As a service to GUIs, Grbl has a “check G-code” mode, enabled by the $C system command. GUIs can stream a G-code program to Grbl, where it will parse it, error-check it, and report ok’s and errors:'s without powering on anything or moving. So GUIs can pre-check the programs before streaming them for real
I’ve suggested that there should at least be an option in comm / control programs to do an MD5 hash on gcode files, check to see if a file has been run before and if it hasn’t, submit it in simulation mode before actually running. If you think this is a good idea please submit it to the author(s) of your program, or implement it yourself.
I get this ALL the time…
Changes that (all help me) with my Fusion360 files:
- Open the tolerance
- Min Rad to 0.02 (In Fusion F360 AND the Postprocessor)
- Eliminate Helical moves
- Break the file into smaller files sizes to pin point the error.
- Change the method 2D adaptive to Pocket or something that works
- Try to eliminate small 3D moves
Sometimes it only take one of these, and sometimes it takes all 6. I know the fustration!
7 Likes
Great stuff from both of you, greatly appreciated. Will check this out. Thanks!
Worked like a charm Rich. Ended up changing the min rad and eliminating helical movement. Job ran a little differently than it was, as expected, but outcome was the same. Thanks again for both of your timely responses!
2 Likes