Donnie Timmons wrote: > What is the pin name for the encoder index input off the 7i33? What the > Hostmot2 pin name? Is there a signal that has to be named? I start homing and > as soon as the limit/home is made the latch vel starts and never finds the > index. > I gave up on sharing the input for the limit with the home and jump the > physical limit to a new hardware pin. Sure is a waste of I/O doing that.
I'm not exactly sure what you're asking for, but i'll try to answer... On the 50-pin J1 connector of the 7i33, pin 9 is named IDX1, pin 11 is IDX0, pin 33 is IDX3, and pin 35 is IDX2. These pins carry the index signal from the encoder to the AnyIO board. IDX0 is the index signal from the first encoder, IDX1 is the second encoder, etc. I'm getting this information from page 4 of Mesa's manual for the 7i33. Note that these pins line up nicely with the index pins of the HostMot2 servo firmwares. On the hostmot2 driver side, there are two ways to determine pinouts. One way is to look at the syslog after you've started your EMC2 configuration - the hostmot2 driver logs the actual pinout it's using there. The other way is to look at the PIN file corresponding to the firmware BIT file you're sending to the AnyIO board. This will tell you what the firmware *can* do with all the pins. Both of these sources will tell you that (on the 5i23) IO#4 is pin 9 on P2, and is the index for the second encoder. If you wanted to look at the logic value on the second encoder's index pin, you'd look at hm2_5i23.0.gpio.004.in. Does this make sense? -- Sebastian Kuzminsky ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
