Motor declarations break analog module

[Joe Ross]

Why did you choose to set the average bits to 30? By my calculations, you'll get a new value every 4 hours or so (if the FPGA even supports a value that large). A more reasonable value is 10, which will get you updates at about 50hz.

If you actually wanted it to average 30 samples, you should set the average bits to 5, since 2^5 is 32.

[nathanww]

I beleieve the person who put that in thought that 30 bits=30 samples, or she might have just been testing an extreme amount because we were having problems with noise on the input. I have to check with her, though. In any case, the FPGA seems to be limiting it to a more reasonable number since the update rate is at least 10 hz.

[nathanww]

And it is fixed!

What happened, we believe, was that the 30-bit averaging, combined with the motor stuff, was using too much FPGA memory and the errors that we were getting were the result of an out-of-memory condition. The system now works after we reduced the averaging bits to 10.