On Sun, 4 Apr 2021 at 16:26, Feral Engineer <[email protected]> wrote:
But that's how I have it set up. The prox is set as encoder index and it > finds it but after it finds it, it goes back to the position the machine > was at during startup. That's what I'm trying to fix. How do i fix this? The point of HOME_USE_INDEX is to home using the index of an encoder. The clue is rather in the name. You are not using an encoder, so it isn't working. This is what it meant to happen: Normal homing sequence. Then index-enable is asserted. The index is hit the encoder is zeroed (typically inside an FPGA) LinuxCNC spots that the encoder is zeroed, and looks at the encoder position. This position will be slightly past the index, due to timing. The current counts show the exact point that the encoder index happened. So the system can use the current joint.N.position-fb as an accurate home. But, in your case, the feedback is not from any sort of encoder, it is from a stepgen. Which isn't zeroed. Which is why, with your setup, the home position is taken to be the exact point that the stepgen was initialised. HOME_USE_INDEX works really very well, if used as intended. It doesn't work at all if enabled on an unsuitable system. In fact on your system the final result is exactly as if you had not homed at all. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
