The mailer blocked the message with a screenshot, so the screenshot is here instead: https://picasaweb.google.com/lh/photo/nTHztK6a02lwmvdgiCxV99MTjNZETYmyPJy0liipFm0?feat=directlink
The docs (and code) seem to say that user-enable-out should be 0 when e-stop.is-activated. This is not the case here. ---------- Forwarded message ---------- From: Roger Moore <[email protected]> Date: 2 June 2013 14:46 Subject: Re: stopin it To: andy pugh <[email protected]> Dunno I wondered if it was that it was expecting momentary contact on halui.estop.activate It is being tripped when a closed contact on the piltz dropped the 24V on the input, so once it was active it remained active. I’ve now put that through a one shot with various pulse width from 0.1 to 1 second. setp enable_delay.on-delay 0.5 setp enable_delay.off-delay 0 #setp enable_delay2.on-delay 0 #setp enable_delay2.off-delay 0 setp estop_act_mom.width 0.25 net momey estop_act_mom.in <= hm2_5i25.0.7i77.0.0.input-12-not net mom estop_act_mom.out halui.estop.activate net estop-out iocontrol.0.user-enable-out hm2_5i25.0.7i77.0.0.output-00 net estop-in hm2_5i25.0.7i77.0.0.input-11 iocontrol.0.emc-enable-in #input from reset switch net reset_estop enable_delay.in hm2_5i25.0.7i77.0.0.input-10-not net reset_estop halui.estop.reset On 6/2/13, andy pugh <[email protected]> wrote: > On 2 June 2013 09:40, Roger Moore <[email protected]> wrote: > >> I could do something whereby a relay closes across the drive ok chain, >> but that sort of defeats the object of the unit. If those contact weld >> or whatever. > > I am not an expert on this aspect of things, but I do know that the > normal advice is that the software shouldn't be a critical part of the > e-stop logic. > It's fine for the software to inhibit things, but the e-stop should > still work if the computer has crashed. > (ideally it should additionally work _because_ the computer has crashed) > >> I’ve now got a situationwhereby: >> halui.estop.activate = true >> halui.estop.is-activated = true >> iocontrol.0.emc-enable-in =false >> iocontrol.0.user-enable-out =true >> so it doesn’t seem that halui.estop.activate sets >> iocontrol.0.user-enable-out to 0. > > That doesn't fit with what the manpage says: > http://www.linuxcnc.org/docs/html/man/man1/io.1.html > > There is a bit more information in the actual iocontrol code: > http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=blob;f=src/emc/iotask/ioControl.cc;h=4ddaa1e59bc94d11f25cc0c0ad15bafda51a1693;hb=refs/heads/v2.5_branch > > And the actual code (around line 981) looks like it tries to set > user-enable-out. However, it happens in response to a message, rather > than polling a state. I wonder what can prevent the message from being > sent? > > -- > atp > If you can't fix it, you don't own it. > http://www.ifixit.com/Manifesto > -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
