Usually, when tuning my Lime board (to, for instance, a NWR station), I get a spectrum like this:
Just what you’d expect. (I’m not sure what the broader bands are—they move in the opposite direction of tuning, or sometimes vanish if I tune e.g. 163.550 instead of 162.550. Any ideas what they might be?)
Sometimes, though, I get something like this:
When I do, the pattern stays more or less the same tuning up and down the spectrum. (I’ve seen a similar issue on higher bands, too.) Eventually, on a tune operation, it goes away on its own, without any indication as to why.
Is this faulty hardware? Does SDRAngel set some registers incorrectly when tuning?
jafa
7 March 2020 15:00
2
Hi,
I see the same problem at 161MHz with a similar spectrum plot where half is missing and it starts to look right towards the higher end of the channel:
Hi,
I have the LimeSDR Mini generating 6MHz wide QAM256 cable TV channels… testing setting the transmit center frequency from 57MHz to 999MHz.
If I select a frequency from 641MHz to 649MHz the LimeSDR Mini doesn’t output anything (no channel power).
If I select a frequency from 320MHz to 323MHz the LimeSDR Mini has similar symptoms. At 323MHz I can see some channel power but not across the full 6MHz bandwidth.
If I set any other center frequency in the 57MHz to 999MHz range I see channel pow…
Another post looks related and suggests a cause:
I found this behavior using CubicSDR and was able to reproduce with LimeSuite as well.
I have a signal at ~59 MHz (RX port). I can see it when I’m tuned to 60 Mhz, and can’t at 61 MHz. I noticed this is the range when VCO switch should occour (VCOH → VCOL):
[image]
To reproduce in LimeSuite, at SXR tab:
calculate and tune to 80Mhz (VCOM is autoselected),
calculate and tune to 60 Mhz (VCOH is autoselected).
calculate and tune to 61 MHz (VCOM!!! is autoselected)
Note, it’s not deterministic,…
Nick
Thanks for the heads up. I’m tracking your thread—I’m looking forward to seeing whether a different LimeSDR fixes your problem.
Wonder if this happens on Windows as well? Could be a Linux driver problem.