On Mon, Nov 12, 2012 at 01:38:40PM +0000, andy pugh wrote: > It was my understanding that setting both of these to 1 would allow > all home and all limit switches to use the same pin. > Reports from tjb1 seem to indicate that this is not the case. > I haven't done any testing (no Linux machine to hand) but was the > intention that these parameters together should be able to allow > configuration of a single-pin setup?
No, HOME_IS_SHARED means if the home switch is already active when homing of this axis starts, abort because reversing the axis won't necessarily be the way to get it deactivated. If XYZ homes are all together, and one of the axes is on the home switch, you can't safely home anything without manual intervention first. HOME_IGNORE_LIMITS means an axis homes to one of its limit switches so if THAT AXIS gets a limit switch trip during homing, don't error. The problem you have is handled by neither of these: when one axis homes, all the others see a limit switch trip. There is no ini setting that ignores ALL limits when ANY axis is homing, which is what I think you want. Per-axis homing state is available on hal pins from motion; you could use those to mask the limit signals to the other axes. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
