At zero position, you could make a mark on the motor shaft and the driven shaft. When zero is off, if the motor shaft is out then it could be the encoder or missing steps to driver board, or driver board fault. Hopefully the motor shaft is in correct position and something else slipped. If it's the motor not zeroing, I'd try swapping it with another axis from EMC in the config and wiring to eliminate parallel port problems, then swap the electricals with another axis. If everything that works on your other axis also works on the z axis, then that should narrow it down to the encoder. Maybe that can get it narrowed down to an EMC, rutex, or servo problem.
I don't know if this has been checked, but when direction reverses, is their a minimum time for the direction bit before the step bit? Thought perhaps EMC is telling it to go UP, but Rutex hasn't changed direction from DOWN yet. Good luck! RogerN ----- Original Message ----- From: "Sven Wesley" <svenne.d...@gmail.com> To: "Enhanced Machine Controller (EMC)" <emc-users@lists.sourceforge.net> Sent: Saturday, September 26, 2009 3:20 AM Subject: Re: [Emc-users] Engrave.py cuts deeper and deeper > This is the most annoying thing I've had in the workshop. > > Yesterday I tried all different kind of setups. I swapped the cards, > replaced one card, changed output pins on the parallel port, ran with > different speeds and accelerations, did a rerun with the tuning software, > swapped cables, checked the soldering, spring loaded the axis to > compensate > for the common G-force - with the same result. Zero has moved. > > The machine have ballscrews with a 60:22 timing belt reduction. The belt > wheel on the screw is clamped with a double nut assembly AND four lock > nuts. > I tried to turn it with force with no luck. I also made a mark to see if > it > moved compared to the nuts. And nope, it's rock solid. > I have two more things to try now. > 1. Replace the servo with another one, the only thing that might slip is > the > servo belt wheel, and it may be a problem with the encoder. > 2. To see if the unwanted offset happens with the tuning software. The > offset actually did happen when I run the test function in Stepconf, the > axis moves the distance set in the test window but it do really change the > zero position. Just to make sure it's not a EMC/Rutex problem I'll make > some > tests with the tuning app. > <snip> ------------------------------------------------------------------------------ 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
