> The M-codes from M101-M199 are "custom M-codes". When the interpreter > encounters one, it looks for a file named the same as the code, for > example M101, and executes it. That file should be in the nc_files dir > specified in your ini file. So you could make M101 be a bash script, > python, perl, compiled code - whatever you want. > > If you can write a script to send the right command to the power strip > to power off the vac table and such, then you can make that an M code. > Similarly for email - you could have a script that sends an email. A > couple of caveats though - the scripts get two parameters, an integer > and a float (I think), and they can't return a success/failure code to > EMC - it's just assumed that the command has completed "successfully" > when control is returned to EMC.
That's very interesting, and will certainly come handy. Yet there is one other reason I'd prefer my approach - I don't have to alter my gcode-file for that. I read about axis-remote - I hadn't had a chance yet to see that in action, but maybe I can implement my desired functionality using that - by polling the state of axis remotely. Please don't take my insistence as ignorance! I'm certainly impressed by the options you guys made me aware of, and customizing our setup using them sure will happen - e.g. notifying the operator about a tool change needed via an acoustic signal or some such. Thanks, Diez ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
