-
Notifications
You must be signed in to change notification settings - Fork 210
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
Stemlab 128.88-16 Origin of TX spurs in 3rd Nyquist Zone and possible remedy? #1059
Comments
Thank you for the tests. I will try to reproduce this effect.
Yes, the TX I/Q rate is fixed and it is always 48k. |
Thanks Pavel. BTW, the fundamental signal has these spurs at better than -80dBc, measured at 10.7 MHz with a notch filter supressing the carrier. For my application I consider to take the fundamental tx signal and upconvert it by the 122.88 MHz clock (using an older transverter which used an external 130MHZ LO). |
Hi Pavel, SMPS Noise
FW DependencyBecause Edwin did not observed die dependency of Spurs on the RX I/Q data rate I tested the behavior with the oldest FW I found: red-pitaya-alpine-3.12-armv7-20200628.zip
So there may have been a FW change responsible for the new spurs. And because it increases the spurs (more and up to 10 stronger) it would be useful to fix, even if the presumably SMPS generated spurs still persist. |
Thank you for testing different versions. Looking at the changes between 20200628 and 20210427, I think only the following changes could affect this SDR application: |
Hi Pavel, Thanks for looking into this issue. |
Description of the setup:
Description of the problem:
a) 384kHz I/Q data rate
a) 192kHz I/Q data rate
Steps to reproduce the problem:
Stemlab powered from analog DC power supply.
10 dB attenuator directly on output did no change the relative spur level.
I wonder what causes these spurs and why do they vary with the I/Q data rate (I assume this to be the rate of the the rx data stream).
Is my assumption correct, that the tx I/Q data rate is always 48kHz?
Thank you.
The text was updated successfully, but these errors were encountered: