Nope it didn't help. BUT, I tried to play around just to see if I find any changes that makes a difference at all. I lowered the step time/space/hold/setup a lot and that made the X and Y axis behave better, better speed obviously. But I still loose the Z position. When I'm running the axis test function in Stepconf I can measure mechanically that the Z axis (and X and Y as well) relly moves between -5 and +5 mm if I set the interval to 5 mm. But when I start Axis and executes my test code that moves Z between 0 and 10 in 200 repeats - it messes up. The first move doesn't seem to be correct and then I can see (as usual the last days) that the axis is not moving between 0 and 10, more like 2 and 8! Actually, I can see that happening by watching the Axis display too. The Z value never reaches zero, next move is already started around 2 mm.
I can describe the first move to Z 10 like when a person is lifting a box that looks very heavy but it's lightweight, the box will be lifted too high in expectation - or even thrown backwards. I don't think EMC expects anything about the weight, it behaves the same though. --S 2009/9/25 Sven Wesley <svenne.d...@gmail.com> > Ok, I'll try it. > --S > > 2009/9/25 Alex Joni <alex.j...@robcon.ro> > > Some drivers consider the 0->1 transition as active, the others 1->0. >> Based on the active transition the timings also change dramatically. >> Especially the times before a direction change, etc. >> >> Regards, >> Alex >> >> >> ------------------------------------------------------------------------------ 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
