Eric H. Johnson wrote: > John, > > The only change in the configuration between 2.2.8 and pre-2.3 is the > addition of the NO_FORCE_HOME value in the ini file. > > I know the timing is very tight, because just upping the debounce duration > applied to the home input by a small amount resulted in running into the > hard stop. That is back to the value used under 2.2.8 as well. > > I know how to adjust it out, I just wanted to make sure that there was no > change to the homing sequence, since I don't believe I have changed the > configuration. > > Thanks, > Eric >
I stand by my earlier advice - get to know halscope, it is an extremely powerfull debugging tool. For example, Chris mentioned that debounce has changed - I don't think that change would have modified that delay thru the debounce component, but halscope can let you directly measure that delay. There is NOTHING better than intelligently interpreted experimental data. You have a repeatable difference between two versions, I'm sure that with halscope and some thought you can either find the root cause, or narrow it down to something that would let someone more familiar with the code find the root cause. Regards, John Kasunich ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
