On 12 January 2013 20:53, Michael Haberler <[email protected]> wrote:
> what's ferror is actually about? AFAICT it serves really a single purpose, > namely triggering a 'following error' condition if it gets too large. Indeed. And for tuning the PID loop you probably want to look at the PID error instead. > - disable ferror and following error tripping altogether in motion (and then > motion is too fat anyway, and it's not in the ten commandments it _has_ to be > there) > - for PID configs, use a (possibly separate) maximum detector for > abs(pid.error) to trip > - for stepper configs, use a (possibly separate) detector which trips on > abs(commanded pos - stepgen.N.position-fb). An interesting idea. The only danger is that it is easier for people to make bad setups and not know. But I seem to spend a lot of time making components that can lie back to motion about the feedback position just to avoid f-error. I think that if you were starting from scratch f-error tripping would be a HAL not motion object. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
