First Start Up - E Stops

Hi Friends, 

Not sure this is the right place for this but here we are. I just about finishing transitioning my Queenbee Pro ( Link ) from mach 3 to LCNC with the help of a mesa 7i96s card. I have been following  this guide  as much as made sense and was able to get through the setup. My intent was to get though the setup then tune everything in once i am sure it all works. I am building a tangential cutter with a servo motor as the cutting head so i went with an XYZA setup and didn't include a spindle.

Now that i am through the setup i use the new desktop shortcut to open and start to try and run the machine and i click the estop in the top right (gmocappy) and get the following message, "External ESTOP is set, could not change state!". 

I have two e stops but one is configured in the pncconf as a custom input (was planning on putting them in series eventually or making the custom input an estop function if i can figure that out) and they're both NC. It doesn't go through any motors/drivers its simply ran from +24V Power Supply --> External Estop-->  Mesa Pin. Is this correct??

I am happy to provide any files or logs that can assist. 

 

The better way is to use estop_latch. There is a tutorial here
forum.linuxcnc.org/47-hal-examples/25861-external-e-stop
it is possible to daisy chain multiple estop_latch components together but its not documented anywhere
I found drawing a diagram of the connections helps to work it out.
Here is  video which may be useful

 

Thanks for the reply.

I added the code in the linked tutorial, does that bind it to a specific pin? It looks like the last line (below) assigns it to pin10? should I change this to the pin i have mine currently wired to? The video so far is very informative and ill use it as a reference when im out working on it tomorrow but no info on how to daisy chain them. I assume since they're NC i can just wire them in series to one input pin? or is that a no-no? 

okay so i went to that linked tutorial I commented out the existing estop loop and ended up actually testing code from the last entry on the first page (copied and pasted below) but modified with my pin for the estop.
Code i am using:



Now i am getting a similar error where it it thinks pins are double assigned. Should I have commented out other pin assignments? Or could i not be assinging the pin corectly? 
error message:

Progress!
I always comment out the line causing the error(s) so Linuxcnc opens, then review things in halshow and your hal file to get the right pin name etc but by the looks of this, its telling you the line number and the fault so maybe change the signal name to something like aa-pos_fb then review

We're getting somewhere!

So i went to line 258 and changed the signal name like you suggested and now i am getting a new error. It doesn't seem to recognize the way i called the pin out. I wish i was more familiar with how to trouble shoot these, see error below:

i don't know what the HOSTMOT function does in this context but its not in anywhere else in the file other than being loaded at the top of the .hal file

The ini variable is used to get your card settings from the ini file (Mesa 7i96s uses HOSTMOT2 driver)
Pncconf does this but personally, I hate it as it makes it hard to understand your hal file
You need to share your hal and ini files.

I definitely could've mangled something in the setup, files attached. Like i said before i was going broad strokes with the intention of tuning it in once i got the machine moving but i don't think i mess anything up too bad. 

Well, looks like you have
so you should remove or comment out this line
net remote-estop estop-latch.0.fault-in <= hm2_[HOSTMOT2](7i96S).0.gpio.04.in_not
and replace it with this

Great thank you!

I go the same error "..a-pos-_fb..." so i followed your advice and changed that to "aa-pos_fb" and got the program to open. Hooray!

naturally i powered the machine on with the touch button and went to press the estop wired to the mesa to test and the external estop, and it did nothing on the screen not stopped the machine. 

I seem to have mixed up some motor assignments so ill need to now find a way to reassign motors without going back through the pnconf setup again, any suggestions?