ESTOP button behavior
03 Jan 2021 02:55 #193921
by rodw
Replied by rodw on topic ESTOP button behavior
So which of you guys is going to come buy and fix the insinkerator that broke here?
Daang! thats right neither of you live in the southern hemisphere! I'll have to fix it myself!
Daang! thats right neither of you live in the southern hemisphere! I'll have to fix it myself!
Please Log in or Create an account to join the conversation.
- Todd Zuercher
-
- Offline
- Platinum Member
-
Less
More
- Posts: 5007
- Thank you received: 1441
03 Jan 2021 03:48 #193926
by Todd Zuercher
Replied by Todd Zuercher on topic ESTOP button behavior
How broken is it? They often just need to be forced to turn a bit to clear a jam, then they work fine again. Might need to pull out any foreign objects too.
Please Log in or Create an account to join the conversation.
03 Jan 2021 09:25 #193936
by cmorley
Can you show me how your pins are connected - or maybe your HAL files?
iocontrol.0.emc-enable-in
iocontrol.0.user-enable-out
iocontrol.0.user-request-enable
Thanks
Replied by cmorley on topic ESTOP button behavior
I just wanted to see if you've had a chance to delve into the hardware handshake, etc. at all. Also see if there's anything you need from me/something I might test for you?
Can you show me how your pins are connected - or maybe your HAL files?
iocontrol.0.emc-enable-in
iocontrol.0.user-enable-out
iocontrol.0.user-request-enable
Thanks
Please Log in or Create an account to join the conversation.
- snowgoer540
-
Topic Author
- Offline
- Moderator
-
Less
More
- Posts: 2388
- Thank you received: 779
03 Jan 2021 19:43 - 03 Jan 2021 21:09 #193979
by snowgoer540
Sure (it's the direct output from pncconf):
HAL file attached in case you need it
Replied by snowgoer540 on topic ESTOP button behavior
Can you show me how your pins are connected - or maybe your HAL files?
Sure (it's the direct output from pncconf):
# --- ESTOP-EXT ---
net estop-ext <= hm2_5i25.0.7i76.0.0.input-00
# ---estop signals---
net estop-out <= iocontrol.0.user-enable-out
net estop-ext => iocontrol.0.emc-enable-inHAL file attached in case you need it
Last edit: 03 Jan 2021 21:09 by snowgoer540.
Please Log in or Create an account to join the conversation.
- snowgoer540
-
Topic Author
- Offline
- Moderator
-
Less
More
- Posts: 2388
- Thank you received: 779
06 Jan 2021 13:48 #194219
by snowgoer540
Replied by snowgoer540 on topic ESTOP button behavior
In addition to the estop behavior, we did run into another issue:
When clicking a line in the preview, the Gcode always highlights 1 line ahead of the actual move. I am not sure if that's a qtvcp thing, or? But it seems off nonetheless.
When clicking a line in the preview, the Gcode always highlights 1 line ahead of the actual move. I am not sure if that's a qtvcp thing, or? But it seems off nonetheless.
Please Log in or Create an account to join the conversation.
06 Jan 2021 14:00 #194220
by cmorley
Replied by cmorley on topic ESTOP button behavior
the estop problem is being difficult.
Mostly because AXIS behavior is not really how linuxcnc was meant to work IMO.
Never the less trying to get the same behavior has been a bit allusive...
Preview line yes Phill told me -Qtvcp problem.
Getting the clic-gcode-line-see-it-in-the-display problem is being a pain mostly because of the same first problem.
Thanks for the report.
Mostly because AXIS behavior is not really how linuxcnc was meant to work IMO.
Never the less trying to get the same behavior has been a bit allusive...
Preview line yes Phill told me -Qtvcp problem.
Getting the clic-gcode-line-see-it-in-the-display problem is being a pain mostly because of the same first problem.
Thanks for the report.
Please Log in or Create an account to join the conversation.
- snowgoer540
-
Topic Author
- Offline
- Moderator
-
Less
More
- Posts: 2388
- Thank you received: 779
06 Jan 2021 14:04 - 06 Jan 2021 14:05 #194222
by snowgoer540
Curious, how would you expect it to behave?
Shoot, sorry to double report. My fault.
Replied by snowgoer540 on topic ESTOP button behavior
I think my real vote would be no GUI ESTOP at all, but it seems people here really seem to want it.the estop problem is being difficult.
Mostly because AXIS behavior is not really how linuxcnc was meant to work IMO.
Never the less trying to get the same behavior has been a bit allusive...
Curious, how would you expect it to behave?
Preview line yes Phill told me -Qtvcp problem.
Getting the clic-gcode-line-see-it-in-the-display problem is being a pain mostly because of the same first problem.
Thanks for the report.
Shoot, sorry to double report. My fault.
Last edit: 06 Jan 2021 14:05 by snowgoer540.
Please Log in or Create an account to join the conversation.
06 Jan 2021 14:30 #194230
by cmorley
Replied by cmorley on topic ESTOP button behavior
I agree with losing the button on the screen if you have a real button.
Of course you can remove it if you don't want it.
Linuxcnc has an estop output pin, it should be AND with the external estop input and an external estop chain. then the button works fine.
Axis uses a button that acts like a toggle switch and a momentary switch at the same time. The button look follows the estop state of linuxcnc but you can still push it when it's down and it will stay down if state doesn't change.
And in this case you can ignore the estop out process
I have to make some custom bitton behavior in QT to make this work the same. I'm confident I can do it just takes some research.
Of course you can remove it if you don't want it.
Linuxcnc has an estop output pin, it should be AND with the external estop input and an external estop chain. then the button works fine.
Axis uses a button that acts like a toggle switch and a momentary switch at the same time. The button look follows the estop state of linuxcnc but you can still push it when it's down and it will stay down if state doesn't change.
And in this case you can ignore the estop out process
I have to make some custom bitton behavior in QT to make this work the same. I'm confident I can do it just takes some research.
The following user(s) said Thank You: snowgoer540
Please Log in or Create an account to join the conversation.
- snowgoer540
-
Topic Author
- Offline
- Moderator
-
Less
More
- Posts: 2388
- Thank you received: 779
06 Jan 2021 14:59 #194233
by snowgoer540
Replied by snowgoer540 on topic ESTOP button behavior
I guess it's sometimes unfortunate that the predecessor sets precedence.
I'd rather not remove it from my setup as every update to QTPlasmaC would be in conflict. At any rate, when it's the Axis way, it's really a non-issue as the physical estop takes charge. I never have to touch the GUI one.
I do appreciate the effort, and I'm sure the Axis folks appreciate you carrying their legacy
I'd rather not remove it from my setup as every update to QTPlasmaC would be in conflict. At any rate, when it's the Axis way, it's really a non-issue as the physical estop takes charge. I never have to touch the GUI one.
I do appreciate the effort, and I'm sure the Axis folks appreciate you carrying their legacy
Please Log in or Create an account to join the conversation.
07 Jan 2021 07:45 #194330
by rodw
Nah it was tripping breakers and I could turn it by hand. It has gone to the dump to be replaced by a stainless steel version which hopefully won't rust out.
Replied by rodw on topic ESTOP button behavior
How broken is it? They often just need to be forced to turn a bit to clear a jam, then they work fine again. Might need to pull out any foreign objects too.
Nah it was tripping breakers and I could turn it by hand. It has gone to the dump to be replaced by a stainless steel version which hopefully won't rust out.
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.086 seconds