Skip to content
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

bladerf: swap I/Q? #69

Closed
wildy opened this issue Oct 1, 2017 · 4 comments
Closed

bladerf: swap I/Q? #69

wildy opened this issue Oct 1, 2017 · 4 comments

Comments

@wildy
Copy link

wildy commented Oct 1, 2017

Hi.

I just started using bladeRF with SDRangel and noticed that when I'm changing the center frequency, signals actually go in the opposite direction, which is, AFAIK, the sign of that you'd need to swap I/Q.
Gqrx has this option and when I checked it I could see signals the right way, but in SDRangel I can't see such an option.
I would very much like to see this option in SDRangel if it's not implemented already. Thanks.

@f4exb
Copy link
Owner

f4exb commented Oct 2, 2017

I use BladeRF regularly and I know that the frequencies go the right way. What you see are probably ghost images. There is no need for I/Q swap. This feature would be useful if you had distinct inputs for I and Q like soundcard input.

@f4exb f4exb added wontfix and removed wontfix labels Oct 2, 2017
@wildy
Copy link
Author

wildy commented Oct 4, 2017

Why then do I have a signal at, say, 433.125 but when I set the device frequency to 433.000 I see it at 432.875, while in Gqrx I can see it at its proper frequency?

@f4exb
Copy link
Owner

f4exb commented Oct 7, 2017

Hello,

what are these settings in the BladeRF plugin GUI in this case:

  • sample rate (SR)
  • decimation (Dec)
  • center frequency position (Fc)
  • RF bandwidth (BW)

Also since the frequency is 433.125 I suppose you don't use the XB200 optional board. You must make sure it is not engaged in this case (xb200 combo).

In any case this is not an I/Q swap problem.

Best regards.

@f4exb
Copy link
Owner

f4exb commented Oct 21, 2017

Closed as no reply from logger and non issue actually

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants