Dwayne Reid scribbled:
> How fast a response do you need?  I tend to average all my a/d
> readings but
> I also work with slowly changing signals (temperature, usually).
>
> For example, a simple 64 times averaging filter fits nicely into a 16 bit
> value (10 or 11 or 12 bits useable, depending upon the noise source) and
> gets rid of most of the noise as well.

I'm aiming about >=10 samples per sec from 5 simultaneous lines.
Won't store this data -- just looking for peaks and lows and
recording those.

I have averaged 8 samples in the past.  Actually, I kept a queue
of 8 readings, shifted one out and a new one in on each sample,
and averaged the queue for display output.

I'm worried that with too many samples being averaged, I'm
reducing my chance of catching peaks.  (Don't have formal
specs on how fast the signal changes, so I'll avoid stating any
guesstimates here.

Guess it's easy to experiment directly first and see what
happens...


Thanks,
-Neil.

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body