On Friday 25 March 2016 15:35:46 Sebastian Kuzminsky wrote: > On 03/25/2016 01:26 PM, Nicklas Karlsson wrote: > > As someone mentioned before a the an axis/joint may/will run away in > > case of an encoder failure. > > > > It would be possible to detect an encoder failure by comparing > > output signal with encoder signal. A velocity signal may be > > integrated and do not allow to wander to much or an encoder error > > will be detected. A torque signal would be worse. > > An encoder that fails into runaway (motion erroneously detected when > none is occurring) or that fails into stop (no motion detected when > motion *is* occurring) will both result in a following error, > precisely for the reason you say above: linuxcnc compares the > commanded position with the feedback position from the encoder.
Which does not work when applied to a spindle motor, unless my toy lathe is miss-configured. I've had the encoder signals go aglay on my lathe, and that sends it wide open until I smash the e-stop, which kills power to the motors psu. And looking at the ini right now, it is quite probable that its miss-configured, that stanza of my config does NOT have either a FERROR or a MIN_ERROR entry. That stanza was 100% hand composed when I put LCNC on that machine. My bad, obviously. Starter value suggestions? And, what do those default to in that event? Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
