-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
measure noise floor #85
Comments
Hello, as an intern in mlabs, I am following the above comment to do a quick test to measure the noise floor of the Pounder's mixer_ch_0 output, which is connected to the Stabilizer ADC_0. My hardware test setup: My software test setup: Both LO and RF signals meet at the mixer and the mixer IF output is logged from the Stabilizer ADC_0 data streaming. we guess the FFT peak at around 0.055 kHz could be the 50 Hz mains hum. I also connect stabilizer ADC_0 to a SIGLENT SDS2074X Plus oscilloscope with a SMA coaxial cable to look at the mixer output. A quick FFT of the signal in the oscilloscope is put here as a don't-be-serious reference. With limited oscilloscope bandwidth, I am not sure about the accuracy with this internal FFT function . So better check this again if someone has a proper spectrum analyzer. I also tried setting LO = RF = 100 MHz while other parameters are kept the same and the phase is adjusted until no dc. Here is the Stabilizer ADC_0 data and seems somehow picking up something else. Similarly, I do it again with LO = RF = 103 MHz and the phase adjusted until no dc. Here is the Stabilizer ADC_0 data plot. It's my first time to do such noise measurement, feel free to let me know if there is anything I should improve, thank you. |
Measuring anything with scope requires caution. First, turn off the target's power supply but keep all the wires and loops the same. At least GND of the input power. MEasure with scope. Then turn on the power. MEasure again. You will often see very little difference due to the scope cable and ground loop pickup. |
cf #84 (comment)
The text was updated successfully, but these errors were encountered: