Chris Radek wrote: > On Sun, Sep 23, 2007 at 11:06:46PM -0500, Jon Elson wrote: > > >>So, I set both FERROR and >>MIN_FERROR to 0.01 (mm) and found that I would get the following >>error trip about 150 ms after motion started. The jerk at the >>start of the linear acceleration ramp caused the worst error of >>about .003mm, the error then decreased a lot, and was about >>.001mm when the following error was declared! So, the error >>never reached the limit. > > > There's axis.N.f-error-lim, which shows the trip threshold as it > changes proportional to velocity. If there's any bug with the trip > threshold, a plot of axis.N.joint-vel-cmd,
axis.N.f-error, Is pid.N.error different from axis.N.f-error, or should they be the same, just produced by different components that need them internally? > axis.N.f-error-lim, and axis.N.f-errored (trigger on this one) would > be very enlightening. Can you get a snapshot of this happening? I have to send this computer and control box back to the customer, but I can set up the same system here - I've saved all the files. I will try to do this shortly. One other note, this was a 400 MHz Pentium III that worked perfectly well under the BDI 4.30, but it is really sluggish to bring up such things as the calibration menu from Axis. It takes roughly a FULL MINUTE to bring up the calibration menu - I'm guessing it has to read the ini file a hundred times or something to get all the parameters. It works acceptably on a 600 MHz machine. Not a complaint, just a data point on where the minimum acceptable hardware is, now. Jon ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
