Alright I believe the problem is resolved… I switched from the TinyG post processor that is included with the Vetric Software to the one I found on the Synthetos forums that writes the gcode as G01 instead of G02/03. There is a few irregularities but I can tell that they were caused by chatter when ramping back down after a hold down tab. Thank you guys for all the help earlier today it means alot to me to be part of such a knowledgeable group of people. You’re AWESOME!
It’s rare that people use G02/03 anymore. Those were more for the days of small memory controllers, and now people prefer to do a ton of linear interpolation.
I’m use to doing it at work on our older Funuc based cnc’s and Haas Lathes… Old habits die hard 
Yeah, me too. A lot of modern online backtracers won’t even process them.
Looks great!
Looks like this could be a long job.
What feed rate and depth per pass/cut works for you
@cmcgrath5035 .250mm DOC 350mm/m feed rate 35mm/m plunge rate , that’s my starting point I make slight adjustments if I see some troublesome areas when cutting. I’m cutting pieces out of 6.35mm aluminium 6061-t651 for a 3D printer I’m building
@cmcgrath5035 Forgot to add 12000rpm spindle speed
@Alex_Krause Can you please post your file that has the G2/G3’s in it? Thanks - Alden
@Alden_Hart what’s the best way to get you that?
@Alex_Krause I’d suggest copy the Gcode to a Cloud Drive and post the URL.
While I have you attention, the part in the upper right picture looks uniform and I believe it is what you are calling “good”. But to me, it does not really look like the simulation model picture you posted 4/18. Am I missing something?
@cmcgrath5035 The simulation doesn’t take into account for the tool diameter is my guess. It is cutting with a 1/8" endmill
Awesome. Hopefully ARC support is fixed in TinyG soon.
Thanks. We have a version that is undergoing extensive testing.