Novice Help - Same Song, Different Dance - Homing

Evening/morning.  I have been trying to figure out homing on my own and am struggling, finally have to acquiesce throwing in the towel and asking for help.  I've read the various versions of the help docs about homing and looked at numerous threads here helping others with the same conundrum to no avail.

I have a Mesa 7i76E Axis configuration of X Y1 Y2 Z.  I have been trying to see if I could figure out and just get the X-axis to home and am striking out.  I have PNP proximity switches at all minimum positions acting as min limit and home switch and software max limits defined.  The PNP's LEDs are illuminated when not triggered, LED goes out when triggered.  The issue is when attempting to Home X the the proximity sensor LED goes out, HAL Meter shows the state change from FALSE to TRUE but X axis does not back off after the triggering event, it keeps on trucking in the neg dir.  I have to kill the power to the machine in Axis to stop further movement.  I turn the machine power via Axis back on, jog to pos dir, shut down LinuxCNC, and stare at the HAL and INI files, not sure where to go.

Attached is my "developer/experimental/learning" HAL and INI file.

Please help.  Thank you.

- Darryl

linuxcnc.org/docs/2.9/html/config/ini-ho...l#sec:homing-section
try:[JOINT_0]HOME_SEQUENCE = 1
[JOINT_1]HOME_SEQUENCE = -2
[JOINT_2]HOME_SEQUENCE = -2
[JOINT_3]HOME_SEQUENCE = 3

Your problem appears to be in HAL:

In the above snippet, the "#" means that whole line is commented out - thus not active.
So the result is that the "joint.0.home-sw-in" pin isn't connected in HAL to anything.

Try uncommenting those lines (remove the # symbol).  To check if it's working without running the machine, start LCNC and take it out of estop & enable the machine ("ON").

Then open halshow and add the above pins and signals to the watchlist.  You can then manually trigger your proxy and see if pin "joint.0.home-sw-in" activates when your proxy triggers.

If it doesn't, you may have to invert the signal by connecting to [HMOT](CARD0).7i76.0.0.input-04-not instead.

Same thing for the #net x-neg-limit line.  If you wish to use the same proxy for the negative limit, you'll have to uncomment that line as well.

Thanks, but I already know the sequence numbering. My question pertained to specifically the X-axis and only the X-Axis not backing off after the proximity triggered.

spumco wrote:

Your problem appears to be in HAL:

Code:

#net x-home-sw => joint.0.home-sw-in net x-home-sw => [HMOT](CARD0).7i76.0.0.input-04 net x-neg-limit => joint.0.neg-lim-sw-in #net x-neg-limit => [HMOT](CARD0).7i76.0.0.input-04 net x-pos-limit => joint.0.pos-lim-sw-in In the above snippet, the "#" means that whole line is commented out - thus not active. So the result is that the "joint.0.home-sw-in" pin isn't connected in HAL to anything. Try uncommenting those lines (remove the # symbol).  To check if it's working without running the machine, start LCNC and take it out of estop & enable the machine ("ON"). Then open halshow and add the above pins and signals to the watchlist.  You can then manually trigger your proxy and see if pin "joint.0.home-sw-in" activates when your proxy triggers. If it doesn't, you may have to invert the signal by connecting to [HMOT](CARD0).7i76.0.0.input-04-[b]not instead. Same thing for the #net x-neg-limit line.  If you wish to use the same proxy for the negative limit, you'll have to uncomment that line as well.[/b]

 

Yes, I am firly certain it is the HAL file.  Yes, I know about the comment symbol too as I put them there - not wanting to lose the original syntax.  With the x-home-sw sig line enabled the homing sequence moves right, the positive direction.  With the line commented out the homing moves desired direction, left, to the proximity sensor.  As said, I see the proximity sensor state change in HAL.  I've tried the "-not" version too and there is no triggering event at all.  I am pretty sure I don't have the wiring defined correctly.  I *THINK* I have the correct "HOME" parameter settings in the INI file.

Are you sure the basic axis direction is right? ie. jogging positively makes the axis move positively?

Linuxcnc's idea of axis direction must be right first.

Then limit switch state needs to be right.
ie. linuxcnc should start with the homing switch clear (false) unless it on the homing switch.

Then you confirm proper homing direction.

It's easy to get distracted by homing direction for instance when the problem is actually the homing switch state or the basic axis direction.