Setting up limit switches and a bunch of other things

Bevins, this is from your post:

loadrt estop_latch
addf estop-latch.0 servo-thread
net estop-loopout iocontrol.0.emc-enable-in <= estop-latch.0.ok-out
net estop-loopin iocontrol.0.user-enable-out => estop-latch.0.ok-in
net estop-reset iocontrol.0.user-request-enable => estop-latch.0.reset
net remote-estop estop-latch.0.fault-in <= hm2_7i92.0.7i76.0.0.input-00-not

BigJohnT:

# estop
loadrt estop_latch
addf estop-latch.0 servo-thread
net estop-loopout iocontrol.0.emc-enable-in <= estop-latch.0.ok-out
net estop-loopin iocontrol.0.user-enable-out => estop-latch.0.ok-in
net estop-reset iocontrol.0.user-request-enable => estop-latch.0.reset
net remote-estop estop-latch.0.fault-in <= parport.0.pin-in10-not

They are IDENTICAL except for the last line. If I put either one into my HAL file, I get the attached photo. HAL will not even start up.

The last line I put is for  a mesa card. JT is for a parallel port card.

What does the debug portion of that error page say. That will tell you what is wrong.

 

It says that this doesn't exist :
net remote-estop estop-latch.0.fault-in <= parport.0.pin-in10-not

I then tried switching it over to "pin-10-in-not", and then it gave me the same error only now it was because I selected something used by the ESTOP. So I switched it back, and it doesn't exist again.

As I've said, I'm okay with F1 and a physical kill switch, even if they aren't the same button. I can still run the machine this way safely. Switch pin 10 to unused and leave the ESTOP physically plugged in and I can physically kill the power to the board. Or I can use F1 to stop HAL. I just have to hit both buttons to completely stop everything.

I can't run the machine at all with out this homing issue solved, apparently. I can use the jog controls and the DRO, but if I wanted a manual mill I would have built one.

Copy and paste from further up in the HAL file.  

And that's how that turned out. At this point I am assuming bad installation from the .iso file. Also just burned a copy of 2.7 Wheezy.  Not ready to nuke the install yet, but I'm getting there.

EDIT:

Tried this instead -
 halcmd: show pins 

Same error as the photo.  I'm done beating my head against this wall.  It's a waste of time.

The install is probably OK

halcmd is normally run from a terminal window, it looks like you are trying to
launch it from halshow. You can run commands like "show pin"
(without the halcmd) from halshow but I'm not sure where a file (like pin.txt)
would be created since I don't know what the default path of the running LinuxCNC
instance is .

If you run:

halcmd show pin >pin.txt

from a terminal, pin.txt will be created in the current directory

Actually glad I went ahead with the reinstall.  Stepconf on 2.7 included the missing homing entries. Now the punchline - the ESTOP and limit switches are behaving identically and none of the proposed fixes are working for this version either, and are giving me exactly the same error messages. That screams hardware incompatibility to me. Which sucks because I am waiting to find out if I'm going to paint a few houses or begin a lucrative career in fast food to pay the bills,  am down to my last $150, and am not going to spend it on a different BOB.

EDIT: Scratch that part about the limit switches, they are all now configured for NC again and set to HOME in stepconf with X &Y inverted so that they travel the correct direction, and they all work in sequence correctly. So that leaves the ESTOP as the only thing not working.