On 17 October 2011 14:57, Tom Easterday <tom-...@bgp.nu> wrote: > Ok, as I mentioned I have tried this to no avail:
> MMAX_VELOCITY = 75 > MMAX_ACCELERATION = 360 That was what I was meaning, yes. What were the settings for MAX)VELOCITY and MAX_ACCELERATION that you used with those values? Overshoot-and-return seems very odd indeed, I would only expect to see that with a PID component in the loop. I guess that it might be possible to see it with an accelleration calculation from an overshot position. I find myself wondering if your velocity commands are exceeding the width of the register access to the Mesa card. I would need to look at the driver code to see if that is possible. -- atp "Torque wrenches are for the obedience of fools and the guidance of wise men" ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
