Weiler DZ26 Millturn Conversion

I have already asked in another estop related chat but maybe that was too old of a thread.
I have been trying to incorporate the rather complicated estop relais functionality from the original machine setup and have messed up my estop logic along the way and can not recover from all changes i have made in the meantime.
Even the easy setup i am running right now is unable to recover GUI estop from True status. I have checked behaviour in halscope and everything seems to work correctly, except somethings holding on to halui.estop.is-activated. I can find nothing about what kernel nets exist, linking internal pins to ...is-activated. What problem could be the source of that behaviour?
Thank you all


net not_aus_fault     => halui.estop.activate

setp oneshot.0.width 0.1
setp edge.0.in-edge FALSE          
setp timedelay.0.on-delay 0.05     
setp timedelay.0.off-delay 0
net not_aus_ok         => iocontrol.0.emc-enable-in
net not_aus_ok         => edge.0.in
net estop-ok-rising    <= edge.0.out => oneshot.0.in
net estop-reset-raw    <= oneshot.0.out => timedelay.0.in
net estop-reset-pulse  <= timedelay.0.out => halui.estop.reset

 

The logic for setting that HAL pin is here, it just reports the system state:
github.com/LinuxCNC/linuxcnc/blob/master..._intf/halui.cc#L2167

Is halui.estop.activate being driven at all? Is it false?

Thanks for the github link. I will look into it in detail.

Currently everything is doing what it´s supposed to do, signal wise.
When i disable the estop relais (hardware wise) i can see a reset pulse as described in the hal excerpt above, using halscope.
halui.estop.is-activated just stays in estop.
If i set F1 in gmoccapy, the GUI puts out a warning about external estops being set. I have literally no idea what net could be the reason for that behaviour.

Finding all necessary inputs for systemstate estop in those linux systemfiles on github is above my paygrade. What could trigger estop internally?
iocontrol.user-enable-out has to be TRUE aswell for estop reset to work? 

iocontrol.0.emc-enable-in probably needs to be true to release the e-stop condition. Is that happening?