Stephen Wille Padnos wrote: > Kirk Wallace wrote: >> >>If FERROR is unused in my scenario, why do I get a following error >>message when the only change I make is from FERROR = 0.0002 to FERROR = >>0.0001? >> >> > > That is a very good question! :) > > Does that happen at any speed, or only on G0 (or other full speed) moves? Umm, he is using 2.1.7, maybe there has been a change since then. I've looked at the current code, and what you say, Steve, seems to be what it does now.
(I did see some strange behavior last week, with current trunk code, that also differs from this expected behavior, but I was NOT able to duplicate it. I may have misread which axis was causing the following error, as I had several badly tuned axes at the time, so the axis I was exercising might not have been the one that caused the trip, and I failed to notice that. After tuning all the axes, it DID seem to behave as expected.) Jon ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
