On 23 December 2010 14:05, Jeff Epler wrote:
> In my view, here's what an encoder implementation should do:
> * maintain counts internally as a 64-bit value
Yes, half a million years of 4000-count 4000-rpm spindle time should be enough.
--
atp
"Torque wrenches are for the obedience of fools a
andy pugh wrote:
> How do the various encoder modules cope with rawcount rollover?
> I am thinking specifically in terms of spindle-mounted encoders which
> may roll over an s32 in a few hours. It is obviously unlikely that any
> axis could rotate in one direction for that long.
>
>
Actually, a
On 23 December 2010 14:05, Jeff Epler wrote:
> Of our encoder implementations, it looks like only software and pluto
> do this! The rest maintain counts in a 32-bit type as far as I can tell.
I suspect that for my purposes it makes no difference what their
internal representation is, as the raw
In my view, here's what an encoder implementation should do:
* maintain counts internally as a 64-bit value
* calculate position and velocity based on the 64-bit counts
* truncate the 64-bit value to 32 bits for the s32 counts output
in the normal way
Of our encoder implementations, it looks
How do the various encoder modules cope with rawcount rollover?
I am thinking specifically in terms of spindle-mounted encoders which
may roll over an s32 in a few hours. It is obviously unlikely that any
axis could rotate in one direction for that long.
I have a HAL component that uses rawcounts
