I started to work on moving my lathe turret script from M101 to comp. It got me to thinking about what the comp code really is. I am used to the M101 shell script I wrote because it has a finite presence. If EMC hits an M101 code in the g-code file the M101 script starts, it does its thing and exits. It's born, lives and dies when I need it. On the other hand, the component gets loaded when EMC initializes and gets visited once every millisecond along with all the other things living in the servo thread. So, I am having a hard time understanding how to do such things as, while the turret is rotating, and I get a match on the tool position. I want to activate a stop turret command and wait 100 milliseconds for the turret to actually come to a stop. Well the component with the wait in it has been called a hundred times during that time. Am I limited to what I can do in nanosecond periods? Or, do I need to write the code to react to and maintain a status database and counters and complete tasks in small chunks? (Reminds me of one of my favorite movies, Memento)
Another question is, if I use iocontrol.0.tool-change to invoke my turret routine, do I need to go back and manually reset iocontrol.0.tool-change along with passing the completion status along to iocontrol.0.tool-changed? This should probably make itself evident when I get further along, but in the mean time I thought I'd ask. I think I hear someone in the distance saying "That's what Classic Ladder is for." Kirk Wallace ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
