Hi Chip,
Thanks for looking at it...
I have been using CutViewerMill and CutViewerTurn to proof my G-code since I purchased the software bundle from Robert at MeshCAM a few years ago. Mach3 and the CutViewers were part of the bundle. Both versions of CutViewer have been dependable for proofing and editing G-code with my other methods of generating G-code (DeskCNC, and a few lathe code generators). So, I never got in the habit of proofing code in Mach3.
I loaded the G-code in Mach3 2.01 and found the two empty tool calls (T&H). The arcs are displayed closer to what they should be, but still not correct. If you zoom in, you will see they are not a smooth transition from entity to entity in the area I call the "foot". They are slightly larger radii than they should be. I haven't calculated the I' & J's to see what they should be... haven't wrapped my brain around that one yet... been dependent on CAM to work those out.
I'm wondering now why CutViewer and Mach3 are interpreting the code so differently? Just to check, I loaded the code in NCPlot and got the same results as CutViewer. Who's on first?
Need to get back to my eBay stuff... will look closer at the code later and see if I can figure out what's out of place.
Thanks again, Paul