Re: tool path / G code differences

Owen:

No, G code is not universal. Every controller understands it's own
specific dialect, and unfortunately, they're often similar enough
that the differences are non-obvious.

You can, however, rely on G0, G1, M0, and M2 between controls, as
these are essentially universal and all you really need for the
majority of practical operations - assuming a sophisticated enough
CAM program. Beyond that, things get quite interesting indeed.

TurboCNC doesn't support G40-42 just yet, by the way. Generate
your toolpaths with radius comp off in MasterCAM, or use a 0.0 radius.

Dave Kowalczyk
Everett WA
TurboCNC software --> http://www.dakeng.com/turbo.html

--- In CAD_CAM_EDM_DRO@y..., "Owen Lloyd" <sbw@c...> wrote:
> Wondering why it is that G code opened in one controller
software
> package [IE: TurboNC, Mach 5, Flashcut] does not give the same
results as
> when opened in another.
> More specifically ....... I generated G code for tool paths
created in
> Mastercam and opened the file in TurboCNC and all was good. Opened
the same
> Gcode file in Mach5 and get "radius too small to complete
operation" errors,
> opened it then in Cutviewer mill [I know this is not a controller
program]
> and it shows tool collisions every where. Flashcut claimed un
recognized
> commands.
> Is not Gcode universal?
> Respectfully,
> Owen Lloyd
> #111cmra
> #34wmrc
> "Enjoy Life, Race a Yamaha."
> www.sportbikewest.com