On 11 April 2011 06:05, Farzin Kamangar <[email protected]> wrote: > I see the home switch > trip then home switch release then seeing the index pulse and now the > instead of stopping, the position changes to what it was when it hit > the home switch and tries to go back to position 0. Therefore it does not > stop at the index pulse. This is weird.
Index detection is handled in the base thread (or the hardware with non p-port systems). index-enable is set true by the motion controller, and when the low-level code or hardware sees an index pulse it zeros the encoder counts and sets index-enable to false. It is done this way because it is quite unlikely that the motion controller can check the index line frequently enough to not miss the index pulse, but the base thread functions can't handle floating point variables. I am not entirely sure what index homing does (I have never tried to use it) but it will have to work inside this structure. Presumably the reason you see the position go to the previous position on the index is that that is the zero position of the coordinate system. -- atp "Torque wrenches are for the obedience of fools and the guidance of wise men" ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
