Thomas Kaiser wrote: >> > MIN_FERROR = 10000.0 > > I add this to avoid the following error. I know I have to change after I > could set up this machine right, but is this really needed? I don't have > any feedback from the axis, So how can EMC2 detect a following error? > EMC2 is only sending pulses to the axis and assumes that the axis moves > this distance. I am wrong on this one?
You don't have feedback from the actual motors, but you do have feedback from the step generators. In this case, since the base period isn't fast enough to allow the step generator to keep up with the commanded velocity, you would get a following error. The solution is to lower the max velocity to something less than 25mm/second. Later you can experiment with different base periods to see if you can go faster - without some testing and math, you can't know whether the drives or the computer are the limit. Most computers can run base period faster than 100uS. If your drives really need a 40uS long step pulse, you do not want to use "doublestep". Doublestep is a technique used to improve the maximum step rate when using drives that need very short step pulses. Unfortunately for you stepconf uses doublestep by default. Most drives work very well with doublestep, and stepconf is intended to be helpful for "most people", at the expense of not covering some unusual cases. If your drives really need 40uS long pulses, you will have to adjust your configuration manually. Regards, John Kasunich ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
