Index pulse seems to be in order. As it is an output it is however not possible to connect it directly to joint index-enable because this pin is a bidirectional IO.
Nicklas Karlsson sön 2025-05-04 klockan 06:57 -0500 skrev Stuart Stevenson: > Are you trying to see the index pulse on every revolution of the encoder? > > On Sun, May 4, 2025 at 6:45 AM Nicklas SB Karlsson <n...@nksb.eu> wrote: > > > It is an ordinary very common encoder have with a zero output. It does not > > have any index-enable net just an output. All > > encoders I have seen with an index output have been like this so therefore > > assume it is a very common problem how to > > connect these and simple solution available. > > > > I could of course create an index net or write a component with an IO > > output that write value only then edge is > > detected. Then it will be possible to connect this to joint index-enable > > as both are IO. > > > > Nicklas Karlsson > > > > > > sön 2025-05-04 klockan 10:26 +0100 skrev andy pugh: > > > On Sun, 4 May 2025 at 09:26, Nicklas SB Karlsson <n...@nksb.eu> wrote: > > > > > > > > Any simple solution to connect index pulse from encoder to joint > > index-enable? > > > > > > Are you sure you want to do that? Why? > > > > > > Typically the system sets the whole index-enable net, then when the > > > index pulse is seen it is taken low by the encoder counter, that > > > signals to the rest of the net that the index has been seen, > > > > > > Are you trying to home to index without an encoder counter? > > > > > > > > > > > > > _______________________________________________ > > Emc-users mailing list > > Emc-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/emc-users > > > > _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
