You basicly only care about the index before you start the synchronized movement. It will sit there, and wait for the index. If it misses one, it will grab the next one (or at least the one it sees). Each index will still constrain to the same spindle orientation, so the thread will not be affected by this. (of course the above is only valid if you're not missing any A/B counts). Once the synchronized movement is started it will be synchronized to the A/B counts.
Regards, Alex > On Wed, 19 Aug 2009 22:30:10 -0500, you wrote: > >>On Wed, Aug 19, 2009 at 10:11:19PM -0500, Jon Elson wrote: >> >>> you could put in a one-shot chip to stretch the index pulse >> >>I said it once already but I don't think everyone caught it: on a >>spindle encoder used for threading and tapping, it doesn't matter >>the slightest bit if you miss the index sometimes. > > How many is sometimes? > >>You certainly must not stretch it longer than one count, whatever >>you do. You would make the cure worse than the problem. > > Why - does it read on both rising and falling edge? > > Steve Blackmore ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
