Il giorno mer, 30/11/2011 alle 18.04 +0100, Spiderdab ha scritto: > Il giorno mer, 30/11/2011 alle 16.44 +0000, andy pugh ha scritto: > > On 30 November 2011 16:33, Spiderdab <77...@tiscali.it> wrote: > > > > > any other idea? > > > > No, it's a mystery to me. The "ABORT" sets all velocities to zero > > prior to setting the selected axis to the requested speed, so it makes > > sense that that would be the reason you can only jog one axis at a > > time (And if you try to job more than one, the highest-numbered should > > always "win". Is that what you see? > > > do you mean axis_2 win on 1 and 0? > so if i jog two axes togheter 0 shold never move? > > i try.. no, it seems random, i mean the 'winning axis'. and also sometime one axis wins, sometime none wins, it just doesn't move anymore.
------------------------------------------------------------------------------ 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
