-
Notifications
You must be signed in to change notification settings - Fork 452
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
Remote TCP Input - FFT does not fix offset on axis X #1377
Comments
In my mind at least, the frequency offset should only be used if decimation is enabled (and you have that set to 1 in the pic) |
Maybe i missed some details on my last post than can help. The original signal is 2Ms/s, i am down converting it to 48khz, the signal you see on the image is being generated on 482.650 kHz but the FFT graph is centering it on 482.500 where the SDR center freq is configured, so that is the reason i guess the offset should be considered. If we see the FFT it says to me that the signal is at 482.500kHz when is not. |
Yep, didn't look closely enough at your screenshot. Will fix. |
Thank you... 👍 |
Implemented in v7.6.2 |
Hey nice work on RemoteTCP Sink. I was using it and i get notice that the FFT graph on axis X doesn't fix accordding to the offset i setup on the plugin parameters, always is centered on the device center frequency e.g:
With these configuration the FFT graph is centering on 482.500, i guess it should be on 482.650 kHz right? or is this the behavior intended?. I am attaching an image of the escenario to support my comment in case i couldn't explain properly 🐱
Thank you... 👍
The text was updated successfully, but these errors were encountered: