oops, in my earlier message I think I wrote "us" several times where I meant "ns". 30us (30000ns) period and 12us (12000ns) are typical base_periods and latencies.
... and for the purposes of registering a limit/home switch closure, that is only read every servo-period, which is typically 1ms (1000000ns) nominal. The motion controller will use whatever value was most recently read from the parport in the base-thread, so even if the hypothetical 42us is enough to see the index pulse (and I doubt it is for a decent high-resolution encoder moving at more than a snail's pace!) you would find that the motion controller will typically miss the index pulse if you're trying to use it as a home switch. In that case, you could use the 'edge' component in the base thread to create a 1.1ms pulse when the rising edge of index is seen, then use the edge output as the home switch input. Jeff ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
