OK, well the gantry man page says: "All controlled joints track the commanded position (with a per-joint offset) unless in the process of homing. Homing is when the commanded position is moving towards the homing switches (as determined by the sign of search-vel) and the joint home switches are not all in the same state. When the system is homing and a joint home switch activates, the command value sent to that joint is "frozen" and the joint offset value is updated instead. Once all home switches are active, there are no more adjustments made to the offset values and all joints run in lock-step once more."
So I guess it does do that. Now if one home was physically installed where it trips 0.53" before physical end-of-travel, if this were NOT the gantry axis I'd just give its final machine coord as 0.53" and its machine coord is correct (0=end-of-travel). But in this one, say one gantry switch is mounted to trip at 0.5" but the other trips at 0.65". If homing acts like non-gantry joints, it would physically leave it at 0.5" and 0.65" and leave joint mode with it physically out of sync like that. Which would mean the joints are racked by 0.15" and will forever be locked like that because future moves are in axis mode, not joint mode. Does it have the ability to physically move the joints into alignment based on .ini parameters saying one switch is 0.15" off, or do I just need to keep physically remounting one switch until its trip point is "close enough" to the other? Danny ---- dan...@austin.rr.com wrote: > What's that mean? Does it just drive both in tandem until both switches are > TRUE, then call it homed? That wouldn't work, I need independent homing for > sure. > > Not sure what the Probotix code is saying but I'll try it out later: > > # join the home switch signals so that both switches have to be closed to > trigger a home position > net switches-y1 => gantry.0.joint.00.home > net switches-y2 => gantry.0.joint.01.home > > > > Danny > > ---- Charles Steinkuehler <char...@steinkuehler.net> wrote: > > On 8/24/2016 11:25 PM, dan...@austin.rr.com wrote: > > > I have a gantry router with 2x X motors. I'm using the "gantry" > > > component. > > > > > > Installing homing switches. Got the Y working right off the bat. > > > I can see the X1 and X2 switches trigger in HAL Scope so I'm good > > > to go. This is a wide gantry which can rack somewhat so independent > > > homing is essential. > > > > > > axis.0.home-sw-in axis.0.neg-lim-sw-in hooked up fine for the X1 > > > side. > > > > > > X2 axis is 3. axis.3.home-sw-in axis.3.neg-lim-sw-in do not exist > > > to connect to, neither one. > > > > If you are using the gantry HAL component (and not gantrykins), the > > motion planner runs as a standard Cartesian machine. You wire the two > > homing switches to the gantry component (gantry.N.joint.MM.home), > > which merges them and generates a single home switch output > > (gantry.N.home) that you connect to the motion planner. > > > > http://linuxcnc.org/docs/html/man/man9/gantry.9.html > > > > -- > > Charles Steinkuehler > > char...@steinkuehler.net > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > 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
