Re: Expanding Gcode in Auggie
Posted: Tue Dec 25, 2018 2:12 am
Terry:
The way it works is that Auggie KNOWS some commands as being core commands, G0,G1,G2,G3,G4 and
many others, but any command not hardwired in generates a script call. For example if you try to do a
G72, it will call G72() as a script call. Which means if the user has a "global G72() { }" script in their
library, that script will be called. Its the same with M codes, Flood mist and such all are scripted in
the library as those M codes are recognized, but an M192 would then look for a script called
M192() and if not found, its simply ignored. Auggie basically recognizes motion and some
state cannons and little else. What it doesnt recognize it looks to the library to explain.
While Auggie actually does have threading and probing code in it, Ive never added interface
capability to do so. From Mach3 I know only 1 in a thousand use probing in CNC, and fewer than
that use threading. As M3 and M4 are still on the market and use a number of interfaces, it doesnt
seem to make sense to add them to Auggie. Auggie can be run by the same person who runs M3
or M4 after all as the pokeys works on all three programs.
You have to keep in mind that Auggie took one year to write, was written specifically to give me
a 6th order motion queue, laser power control during motion and C script in the code capability that I think CNC had to head towards. Mach3 had 10 years of development, Mach4 is in about its 10th year of
development. Ive of the opinion that eventually the things Auggie does will become possible in
more mainstream programs that have the time and staff to develop them to a professional
level, as a free program Auggie hopefully sets the stage as a tech display of how it could
be done. I use it every week for laser work and would be lost without it, but my cnc router
still runs on Mach3, on a version from 10 years ago. So even I wont swap my router to Auggie,
but I wouldnt soil my laser with mach3 either. :)
Art
The way it works is that Auggie KNOWS some commands as being core commands, G0,G1,G2,G3,G4 and
many others, but any command not hardwired in generates a script call. For example if you try to do a
G72, it will call G72() as a script call. Which means if the user has a "global G72() { }" script in their
library, that script will be called. Its the same with M codes, Flood mist and such all are scripted in
the library as those M codes are recognized, but an M192 would then look for a script called
M192() and if not found, its simply ignored. Auggie basically recognizes motion and some
state cannons and little else. What it doesnt recognize it looks to the library to explain.
While Auggie actually does have threading and probing code in it, Ive never added interface
capability to do so. From Mach3 I know only 1 in a thousand use probing in CNC, and fewer than
that use threading. As M3 and M4 are still on the market and use a number of interfaces, it doesnt
seem to make sense to add them to Auggie. Auggie can be run by the same person who runs M3
or M4 after all as the pokeys works on all three programs.
You have to keep in mind that Auggie took one year to write, was written specifically to give me
a 6th order motion queue, laser power control during motion and C script in the code capability that I think CNC had to head towards. Mach3 had 10 years of development, Mach4 is in about its 10th year of
development. Ive of the opinion that eventually the things Auggie does will become possible in
more mainstream programs that have the time and staff to develop them to a professional
level, as a free program Auggie hopefully sets the stage as a tech display of how it could
be done. I use it every week for laser work and would be lost without it, but my cnc router
still runs on Mach3, on a version from 10 years ago. So even I wont swap my router to Auggie,
but I wouldnt soil my laser with mach3 either. :)
Art