Averaging AtoD samples

[HankMcSpank]

I think the Fast Average section might be modified so that instead of jumping to the spurious noise point, it will reject the sample entirely.

That should only take commenting 1 line from the original code.

I've broke the breadboard circuit up ....so can't test right yet. But this sounds cool.

How does the averging code decide whether what's coming in is spurious...or in fact the beginning of a new stream of samples (eg a new frequency arriving, which will generate a different comparator count - with it's own spurious counts).

I guess what I really need issome form of 'trigger' (or 'change' threshold) so that my program then knows that a new frequency is coming in (& is not just a spurious reading)...

For example, red test below is spurious count, blue is new frequency arriving (therefore count changes and starts coming in at around that new level)

5000,4999,5000,5001, 3956,5000,5001,5000,4999,5000,3789, 2570,2571,2569,2570,2571,18912569,2571....