I did a test like the one Jon suggests yesterday with 150 repeats between Z 10 and Z 20, and the offset ends up around 2.2 mm even if I go really slow. I just recently setup this machine and haven't really started to use it until now, so it's a new machine and a new problem. I'm using Rutex 990H cards and Minerva (Yaskawa robot) servo's rated 67 V/10 A, and I have so much power in the electric feed I can use the control box as a welding machine .
I did a new configuration with Stepconf, will that really work with servo's? It says in the documentation that it should handle any step/dir config but I only see stepper motor settings and not really something that is servo related. I searched through the Wiki but didn't find a guide how to config a servo system, only some tips and ideas. 3 AM this morning I was too tired to start fiddeling with some example copy ini-files though. I'll try to test the encoders like stated here http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Tuning_EMC2/HAL_PID_Loops later today. Any suggestions or recommendations on servo config's muchly appreciated! Regards, Sven 2009/9/23 Jon Elson <el...@pico-systems.com> > Chris Radek wrote: > > On Tue, Sep 22, 2009 at 11:43:30PM +0200, Sven Wesley wrote: > > > > > >> BTW, I'm running servo's... :) > >> > Well, what servos, what interface? If you have Gecko 340 drives (that's > a 320 with a pulse > multiplier) it can be messed up by the direction signal changing too > soon after tha last > step pulse. It continues to generate the multiplier setting of > encoder-scale moves which SHOULD > have all been made in the same direction, as the computer intended > them. But, the output moves > immediately change direction when the direction signal is changed. So, > each time you change > direction, some number of encoder counts are made in the wrong > direction, and the error can > accumulate. There are hold time settings in stepgen that can prevent this. > > This is only one particular sort of error that can develop in step-servo > systems. Interference > between motor drive signals and the encoder signals are another, and of > course a bad encoder > is another possibility. Also simple mechanical slippage between the > motor and leadscrew has > tripped up more than one person. > > Jon > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
