Chris Radek wrote: > On Thu, Jul 09, 2009 at 04:28:23PM +0100, Leslie Newell wrote: > >> Watching GPIO 28 with halmeter I can see the index so the hardware is >> working correctly, going TRUE when the index is active. >> When I home, it appears to ignore the index completely. The machine hits >> the home switch, backs off then stops almost immediately when the switch >> breaks, ignoring the index. >> Watching axis.0.index-enable with halmeter I see it go TRUE for a moment >> when the switch releases then almost immedaitely FALSE again. > > index-enable is set true by the motion controller when it wants to > start the index search (this will be after finding the switch), then > it is set false by the hardware/driver when index is found. The time > the index-enable is true is the search time. > > I think it's actually working. Your index might be closer to your > switch than you expect, so you think it's not reading it.
This was my first guess as well. Les, can you tell us what part of this behavior you think is wrong? > What is GPIO 28? I don't understand this part. GPIO 28 is the I/O pin used for Index for encoder #5 on the firmware Les is using. He's watching the raw value on the input pin, bypassing the encoder, to verify that his wiring is correct. <http://git.linuxcnc.org/gitweb?p=emc2.git;a=blob;f=src/hal/drivers/mesa-hostmot2/firmware/5i20/SV12.PIN;h=81b34cd09277063c63671a3f529ad929e0a738a9;hb=d4a642fcb69e5f5c2d61af6429403e807e780f25#l87> -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
