Thanks Jeff, You are correct, this is undesirable. It is better than my current config of using the EOT's only as homing switches and using just the software based end of travel. Thanks for the help, much appreciated. Andrew
On Jan 29, 2008 9:03 AM, Jeff Epler <[EMAIL PROTECTED]> wrote: > You can accomplish what you need in HAL or ClassicLadder. For each > axis, there is a pin axis.N.homing which is TRUE when the joint is > homing. You can use these together with the single input signal to get > the "limit" signal. In "C"-like notation, this would be > on_limit = switch_input && !(axis_0_homing || axis_1_homing || > axis_2_homing) > > This configuration is undesirable, because if some bug causes motion on > one axis while another is homing, it won't be detectable within emc. > > Jeff > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
