Am 22.10.2009 um 20:04 schrieb Jon Elson: > ...
> limit, and then the system becomes violently unstable. This is all > just > guessing from too little info, > hopefully we can get some plots of other signals from the stepgen to > see > in more detail what is > happening inside. >> Also note that G33 et-al are position-mode not velocity-mode. axis.2.f-error was just a stab in the dark, it was just the first signal which correlated to the sound stepgen just does what axis tells it to do: http://mah.priv.at/cgi-bin/viewvc.cgi/emc-syncmove/pos-cmd-steprate.png?revision=1.1&root=CVS&view=markup the wobble is already in axis.2.motor-pos-cmd so that takes stepgen out of the picture IMHO the encoder ist out of the picture as well because its simulated and that gives the same effect as the real one I guess I'll look into adding some probing hal pins in tp.c and see wether position update underrun can be observed it's more curiosity at this point - really I dont care too much because I'll fix it with a decent encoder and I think the overall approach - tracking position - is right as opposed to 'ah, index seen - let's jog down that pass' which strikes me a bit of fly-by-night exercise -Michael ps: her's a bonus video - yes, it almost sounded like this: http://www.youtube.com/watch?v=Ht96HJ01SE4 ;-) ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) 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/devconference _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
