ESTOP issues - iocontrol.0.user-enable-out not going "true"
- Henk
- Offline
- Platinum Member
Less
More
- Posts: 395
- Thank you received: 80
01 May 2022 03:44 #241763
by Henk
ESTOP issues - iocontrol.0.user-enable-out not going "true" was created by Henk
HI
Im not sure why im not getting this right, one would think that after 15 successful linuxcnc retrofits i would be able to sort this one out, but no.....
Same as my other LCNC installations, i create a hard-wired estop circuit that ends as an input on a mesa card, in this case a 7i77, input number 5.
The signal connected to this pin is fed to Classicladder for some further interlocks, and from classicladder output number 49, it is connected to iocontrol.0.emc-enable-in via signal "estop-ext"
24v dc => estop switch (NC) => mesa input => classicladder => iocontrol.0.emc-enable-in
iocontrol.0.user-enable-out => switch on drive power, lub pumps, hydraulics etc (this does not turn "true" after iocontrol.0.emc-enable-in turns "true")
Expected behaviour is that when i trigger the physical estop switch, Axis gui estop button will respond, and that the pin iocontrol.0.user-enable-out will also change state.
What is happening is that the gui button (top left) responds as it should, but the pin iocontrol.0.user-enable-out does not. I verified this using hal configuration-show. Pin iocontrol.0.emc-enable-in change to "true", but iocontrol.0.user-enable-out stays "false"
If possibe, please point out my obvious error
Thanks
Henk
Im not sure why im not getting this right, one would think that after 15 successful linuxcnc retrofits i would be able to sort this one out, but no.....
Same as my other LCNC installations, i create a hard-wired estop circuit that ends as an input on a mesa card, in this case a 7i77, input number 5.
The signal connected to this pin is fed to Classicladder for some further interlocks, and from classicladder output number 49, it is connected to iocontrol.0.emc-enable-in via signal "estop-ext"
24v dc => estop switch (NC) => mesa input => classicladder => iocontrol.0.emc-enable-in
iocontrol.0.user-enable-out => switch on drive power, lub pumps, hydraulics etc (this does not turn "true" after iocontrol.0.emc-enable-in turns "true")
Expected behaviour is that when i trigger the physical estop switch, Axis gui estop button will respond, and that the pin iocontrol.0.user-enable-out will also change state.
What is happening is that the gui button (top left) responds as it should, but the pin iocontrol.0.user-enable-out does not. I verified this using hal configuration-show. Pin iocontrol.0.emc-enable-in change to "true", but iocontrol.0.user-enable-out stays "false"
If possibe, please point out my obvious error
Thanks
Henk
Please Log in or Create an account to join the conversation.
- Henk
- Offline
- Platinum Member
Less
More
- Posts: 395
- Thank you received: 80
01 May 2022 03:57 #241764
by Henk
Replied by Henk on topic ESTOP issues - iocontrol.0.user-enable-out not going "true"
Running 2.8.2 on Buster
Please Log in or Create an account to join the conversation.
- Henk
- Offline
- Platinum Member
Less
More
- Posts: 395
- Thank you received: 80
02 May 2022 02:02 #241824
by Henk
Replied by Henk on topic ESTOP issues - iocontrol.0.user-enable-out not going "true"
Well, it seems that what i didn't do what I thought I had done in the past....
Only one of my configs actually switch on some stuff when the estop is released, and on that one I used the pin halui.estop.is-activated.
Solved.
Only one of my configs actually switch on some stuff when the estop is released, and on that one I used the pin halui.estop.is-activated.
Solved.
Please Log in or Create an account to join the conversation.
Time to create page: 0.063 seconds