On Sun, 2 Sep 2012 16:45:26 +0100, Andy Pugh wrote: > On 2 Sep 2012, at 16:37, EBo <[email protected]> wrote: > >> So, not only do we need to identify what areas >> of the workspace is in the critical section, but also what we should >> do >> in a wait state -- maybe it is OK to leave the router spinning in >> place, >> but that can also burn the material... > > Moving to a safe place and waiting for an input sounds exactly like a > tool change to me. > > Every stage could have a "tool number" which might or might not > correspond to an actual tool. You then set "tool changed" by whatever > method is convenient.
That would work, but could end up being expensive (in terms of moving back and forth across the entire work piece). It would also probably work as well to check before entering the contested space and simply move just above the work piece and hold. That would still require an alternative function. EBo -- ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
