Re: [CAD_CAM_EDM_DRO] tool path / G code differences

Hi Owen:

Mach1 checks the radius computation in G41,G42 code to ensure your not
gouging your stock. This is a rather annoying action (for some, necessary
for others)which can be turned off on the logic page. EMC checks these
values to a very tight tolerance, (settable in the code) and I suspect that
Turbo doesn't check them at all. (probably a good thing). I think
Gouge/Concavity checking should be a warning instead of a failure and will
be changing things to that level.

Next weeks version of Mach1 (release 1.0 Finally) will also correct the
checking of these values in the tool path display ( a current bug).
G-Code is a "standard" with many flavours. I think your seeing some of
the differences in those flavours. Some controllers have all the codes
implemented, some don't. This might explain the "command not found". This is
why so many post processors exist. They take care of the specific
differences in controllers.

The differences exist for many reasons. As a programmer, I try to resist
the urge to add commands, but even I have added many. M41 for example in
Mach1 opens a file for point cloud storage during digitizing, M42 closes
that file. You won't find those commands in any other processor but I had to
put them somewhere. (this is probably the most common excuse) Personally, I
try to only add M commands as they won't affect most people who don't use
them. When programmers change or add G-Commands, it can cause these types of
problems.

Unfortunately, many machine use the same G code for different things, this
is where the problems become accute because they defy expectations.

I hope this explaination helps,
Art
www.artofcnc.ca