multiple estops on separate pins
- LeonDolnicar
- Offline
- New Member
-
Less
More
- Posts: 3
- Thank you received: 0
14 Aug 2025 09:59 #333394
by LeonDolnicar
multiple estops on separate pins was created by LeonDolnicar
Hello,
I am running a thre axis CNC mill with stepper motors with mesa 7i76eu. I wanted to connect stepper driver alarm outputs to mesa and have them triger emergency stop. I am also planning on adding two additional Estop buttons. I wired them up but then noticed that linuxCNC setup wizard only lets me select one output as emergency stop. Is there a way I can select multiple inputs as emergency stop, or do I have to wire the buttons in parallel and connect them to one input.
I am running a thre axis CNC mill with stepper motors with mesa 7i76eu. I wanted to connect stepper driver alarm outputs to mesa and have them triger emergency stop. I am also planning on adding two additional Estop buttons. I wired them up but then noticed that linuxCNC setup wizard only lets me select one output as emergency stop. Is there a way I can select multiple inputs as emergency stop, or do I have to wire the buttons in parallel and connect them to one input.
Please Log in or Create an account to join the conversation.
- JT
-
- Away
- Administrator
-
Less
More
- Posts: 1009
- Thank you received: 520
14 Aug 2025 11:40 #333397
by JT
Replied by JT on topic multiple estops on separate pins
There's a couple of ways, you could use the
Mesa Configuration Tool
or you can add the
estop_latch
component yourself.
JT
JT
Please Log in or Create an account to join the conversation.
- rodw
-
- Offline
- Platinum Member
-
Less
More
- Posts: 11388
- Thank you received: 3822
14 Aug 2025 11:50 #333399
by rodw
Replied by rodw on topic multiple estops on separate pins
estop-latch is the right way to go with these but a better way is to use joint.N.amp-fault-in IN BIT Should be driven TRUE if an external fault is detected with the amplifier for this joint.
ref: linuxcnc.org/docs/stable/html/man/man9/motion.9.html
This will halt motion.
Your drives may also have a estop input which disables the drive on an estop.
ref: linuxcnc.org/docs/stable/html/man/man9/motion.9.html
This will halt motion.
Your drives may also have a estop input which disables the drive on an estop.
Please Log in or Create an account to join the conversation.
- Todd Zuercher
-
- Offline
- Platinum Member
-
Less
More
- Posts: 5034
- Thank you received: 1467
14 Aug 2025 12:22 #333405
by Todd Zuercher
Replied by Todd Zuercher on topic multiple estops on separate pins
You can use logic components such as and2 to connect multiple signals to one. But I'm not sure I see the advantage of doing so with an e-stop. Generally an e-stop loop is all in hardware, and the e-stop input to Linuxcnc is merely to inform it of the loop's state.
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 20616
- Thank you received: 7014
14 Aug 2025 12:27 #333406
by tommylight
Replied by tommylight on topic multiple estops on separate pins
Drive alarms should be wired to joint.n.amp-fault in hal, not to e-stop,
The following user(s) said Thank You: rodw
Please Log in or Create an account to join the conversation.
- rodw
-
- Offline
- Platinum Member
-
Less
More
- Posts: 11388
- Thank you received: 3822
14 Aug 2025 12:39 #333408
by rodw
Replied by rodw on topic multiple estops on separate pins
Yes as I said. Much cleaner to maintainDrive alarms should be wired to joint.n.amp-fault in hal, not to e-stop,
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 20616
- Thank you received: 7014
14 Aug 2025 13:11 #333413
by tommylight
Replied by tommylight on topic multiple estops on separate pins
Rod, i did not read your post past "estop-latch is the right way to go", and you know the reason why.
Sorry, this time i should have continued.
Thank you.
Sorry, this time i should have continued.
Thank you.
The following user(s) said Thank You: rodw
Please Log in or Create an account to join the conversation.
Time to create page: 0.059 seconds