Jeff Epler <[EMAIL PROTECTED]> wrote: > On Wed, Nov 15, 2006 at 08:39:49PM +0000, [EMAIL PROTECTED] wrote: > > This should probably be moved to the emc-developers list. It > > may be possible to implement synchronized I/O in time for > > the version 2.1 release. > > We have synchronized digital (not analog) I/O -- just 4 bits or so, set > by m-codes. But I think the "synchronization" is like that for spindle > control--task waits for the motion queue to empty, then takes the > non-motion action, then starts up motion again. There are hooks and partial code for both digital and analog I/O, and there are signs that the original intent was to be able to "attach" the commands to motion queue entries, so the I/O would be updated on the fly as the trajectory planner pulls each move from the queue. This would work even when blending motions.
However, hooks and partial code do not make a working system. I think we would have to review the entire chain from interpreter down to the motion controller and see what else is needed. Unfortunately I won't be home much this evening, but maybe tomorrow we can toss around some ideas on IRC. The recent work that went into synchronizing things like feed override enable to motion might be applicable. Regards, John Kasunich ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
