In line 403 you have:
Code:
net estop-reset iocontrol.0.user-request-enable => estop-latch.0.reset
this creates the signal "estop-reset" by connecting the output pin "estop-reset iocontrol.0.user-request-enable" to the input pin "estop-latch.0.reset" which is fine. You have an output pin and an input pin:
Code:
iocontrol.0.user−request−enable
(Bit, Out) TRUE when the user has requested that estop be cleared
Code:
estop-latch.N.reset bit in
but then after that you also have:
Code:
net estop-out-MO estop-latch.0.reset => oneshot.0.in
here you are trying to create a new signal "estop-out.MO by connecting two inputs which is not possible. If you want to connect "oneshot.0.in" to "estop-latch.0.reset" then you need to do it like this (after having created the signal "estop-reset" line 403):
net estop-reset => oneshot.0.in
OR you could add the input "oneshot.0.in" to the line where you create the signal "estop-reset" in line 403:
net estop-reset <= iocontrol.0.user-request-enable => estop-latch.0.reset => oneshot.0.in
Note the "<=" and "=>" are ignored and are only there to visualize inputs and outputs for the user. LinuxCNC already knows which pins are input and which pins are outputs. When you define a signal you need to connect it to only one output pin and then you can connect it to as many input pins as you want.
