> Ok, just disregard prev msg. Dunno what I was thinking when I wrote that
crap.

I just wrote a lengthy response to that message before I got to this one.
Hopefully it will help anyway.

> The high byte overflows in one direction.

You have to make sure to use truncation instead of rounding when dividing by
256.  See my example in the other message.

> The high byte looks like it basically works as filter output (when
overflow fixed)
> The low byte is just plain nuts...

As expected.  See my other message.



********************************************************************
Olin Lathrop, embedded systems consultant in Littleton Massachusetts
(978) 742-9014, olin@embedinc.com, http://www.embedinc.com

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.