Hal confusion

Booting into Axis, Failure Is:
LINUXCNC - 2.7.11
Machine configuration directory is '/home/jack/linuxcnc/configs/bridgeport'
Machine configuration file is '1BP.ini'
Starting LinuxCNC...
(time=1566230313.311088,pid=7391): Registering server on TCP port 5005.
(time=1566230313.311205,pid=7391): running server for TCP port 5005 (connection_socket = 3).
.
iocontrol: machine: 'LINUXCNC-1BP' version '2.7.8'
Found file(REL): ./1BPstepper.hal
Found file(REL): ./2X-BoxPinOutTest.hal
./2X-BoxPinOutTest.hal:125: Pin 'parport.2.pin-03-out' was already linked to signal 'estopactivated'
Shutting down and cleaning up LinuxCNC...

Line 66 in 2X-BoxPinOutTest.hal is apparently causing a problem.
I cannot find where the name "estopactivated" is mentioned in any file being used, 1BP.ini, 1BPstepper.hal, or 2X-BoxPinOutTest.hal Files are attached.
What can be causing this error? (By the way - It used to work ok, but apparently something has gotten contaminated.)
Is there a better way to connect the hal pin "halui.estop.is-activated" to a parallel port pin?
jensor

the halui pin you use needs to be in a postgui file
you can use the motion pin
iocontrol.0.user-enable-out

You have a conflict in2X-BoxPinOutTest.hal:

net estopactivated halui.estop.is-activated parport.2.pin-03-out
...

net allhomed logic.0.and parport.2.pin-03-out

In line 66 of the file 2X-BoxPinOutTest.hal is the line then again in in line 126 you tried to connect the same parallel port pin
Any pin name can only be used once in all of your active hal files.

Replacing:
net estopactivated halui.estop.is-activated parport.2.pin-03-out
With:
net estopactivated iocontrol.0.user-enable-out parport.2.pin-03-out
Leads to error:
LINUXCNC - 2.7.11
Machine configuration directory is '/home/jack/linuxcnc/configs/bridgeport'
Machine configuration file is '1BP.ini'
Starting LinuxCNC...
(time=1566237632.285896,pid=10078): Registering server on TCP port 5005.
(time=1566237632.286038,pid=10078): running server for TCP port 5005 (connection_socket = 3).
.
iocontrol: machine: 'LINUXCNC-1BP' version '2.7.8'
Found file(REL): ./1BPstepper.hal
Found file(REL): ./2X-BoxPinOutTest.hal
./2X-BoxPinOutTest.hal:66: Pin 'iocontrol.0.user-enable-out' was already linked to signal 'enable'
Shutting down and cleaning up LinuxCNC...

So this command isn't available before the postgui file

Postgui has nothing to do with it. It is the fact that you already used that pin name earlier on line 49.

Todd Zuercher wrote: then again in in line 126 you tried to connect the same parallel port pin

Code:

net allhomed logic.0.and parport.2.pin-03-out

.

You can omit that line or change the pin out number.

You're right on line 126. My mistake, however still a problem.

Todd -
48 # create a signal for the estop loopback
49 net enable iocontrol.0.user-enable-out iocontrol.0.emc-enable-in
no reference to parport.2.pin-03-out there.
Doing a search in the file shows only one instance of parport.2.pin-03-out since I deleted it on line 126.

Still get same original error:
iocontrol: machine: 'LINUXCNC-1BP' version '2.7.8'
Found file(REL): ./1BPstepper.hal
Found file(REL): ./2X-BoxPinOutTest.hal
./2X-BoxPinOutTest.hal:66: Pin 'iocontrol.0.user-enable-out' was already linked to signal 'enable'
Shutting down and cleaning up LinuxCNC...

So still the question how can it already be linked?

Search for multiple occurrences of: iocontrol.0.user-enable-out

No other occurrences of "iocontrol.0.user-enable-out".

jensor