Thank you guys, I think I'm going to stick to what I was planning. Use the alarm component to inhibit the feed or turn off the machine via the motion.enable pin and use the external e-stop button to turn off the contactors that feed the servos. I have it this way on the other machines but I can't access to the config right now.
It's funny but being used to only turn on and put the machine to work makes me forget some basic stuff I already did a few years ago. I need to play with this stuff more often I guess :). El vie., 10 abr. 2020 a las 9:17, andy pugh (<bodge...@gmail.com>) escribió: > On Fri, 10 Apr 2020 at 03:44, Leonardo Marsaglia <ldmarsag...@gmail.com> > wrote: > > > I plan to use the motion.enable pin as a machine turn off mechanism in > case > > some alarm trigger but the condition is not quite severe to call for an > > e-stop. > > motion.enable should theoretically be more reliable than the iocontrol > pins that are generally used in the e-stop chain, as it runs in the > realtime motion thread, not the userspace iocontrol component. > > But it is probably unwise to rely 100% on either, so the e-stop loop > should have hardware effects too. > > I have generally considered the iocontrol parts of the e-stop loop as > mainly to allow a soft-estop and to let the controller know when > e-stop has been hit. > > I agree, neither the docs nor the code give much clue what the pin is > intended for. > > -- > atp > "A motorcycle is a bicycle with a pandemonium attachment and is > designed for the especial use of mechanical geniuses, daredevils and > lunatics." > — George Fitch, Atlanta Constitution Newspaper, 1912 > > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
