rev1 add-on board: noisy signals at high sample rates #4

The currently available high sampling rates, 48kS/s and 96kS/s, produce very noisy signal data with the new add-on board.

This could be due to the hardware; however, the lower sampling rates use x4 oversampling and seemingly have much more accurate signal data. If a hardware change will not be the solution, we may want to look into oversampling at all sample rates.

The currently available high sampling rates, 48kS/s and 96kS/s, produce very noisy signal data with the new add-on board. This could be due to the hardware; however, the lower sampling rates use x4 oversampling and seemingly have much more accurate signal data. If a hardware change will not be the solution, we may want to look into oversampling at all sample rates.

Made a commit that enables oversampling for the two rates. Exactly 96kS/s is not achievable in our current setup though, so we're settling with 96.05263kS/s for now.

May be worth while to investigate the hardware; it probably is not optimal.

Made [a commit](https://github.com/tcsullivan/stmdsp/commit/6dc46a5952cf3702e34dbcafafdcd51c2d205e95) that enables oversampling for the two rates. Exactly 96kS/s is not achievable in our current setup though, so we're settling with 96.05263kS/s for now. May be worth while to investigate the hardware; it probably is not optimal.

Turns out the noise is 90% due to incorrect wiring of the audio jacks. Using the pin header instead provides much cleaner input and output.

The jacks will be fixed in hardware revision two, so I'm going to close this issue for now. I'll bring it back if rev2 still has significant issues.

Turns out the noise is 90% due to incorrect wiring of the audio jacks. Using the pin header instead provides much cleaner input and output. The jacks will be fixed in hardware revision two, so I'm going to close this issue for now. I'll bring it back if rev2 still has significant issues.

Labels Milestones

rev1 add-on board: noisy signals at high sample rates #4