After finding that my spindle encoder had drifted, and was counting
686 of the 720 counts, leading to rather unconveninally-pitched
threads, I find myself wondering if it would be sensible for the
encoder function to set a pin to counts since last index on every
index event. This could be
On Tue, 20 Dec 2011, andy pugh wrote:
Date: Tue, 20 Dec 2011 14:18:10 +
From: andy pugh bodge...@gmail.com
Reply-To: EMC developers emc-developers@lists.sourceforge.net
To: EMC developers emc-developers@lists.sourceforge.net
Subject: [Emc-developers] Encoder Diagnostics
After finding
On Tue, Dec 20, 2011 at 02:18:10PM +, andy pugh wrote:
After finding that my spindle encoder had drifted, and was counting
686 of the 720 counts, leading to rather unconveninally-pitched
threads, I find myself wondering if it would be sensible for the
encoder function to set a pin to
Chris Radek wrote:
There are lots of ways encoder hardware can
detect problems: invalid quadrature transitions, extra or missing
counts between indexes, and maybe more. If the encoder hardware knows
pulses per rev (which is not the current scale value it knows) it can
detect missing index
On Tue, 20 Dec 2011 11:49:42 -0600, Jon Elson wrote:
Chris Radek wrote:
There are lots of ways encoder hardware can
detect problems: invalid quadrature transitions, extra or missing
counts between indexes, and maybe more. If the encoder hardware
knows
pulses per rev (which is not the
EBo wrote:
I could see having that functionality as a compilable/loadable
diagnostic test so that it would not have to run all the time (ie saving
CPU cycles). I like the proposed functionality.
I actually have this test in some of my diagnostics. They set up the
encoder counter to
