Re: LimeSDR | Sinewave test | Glitchy behavior

Opps - ignore the following -I just realized  in my mind I was going the wrong direction - I got twisted:   "If you were to add a signal source of 48 kHz, you would need to add a rational sampler in front of the WBFM block for a quadrature rate of 480 kHz" If you add a 48 kHz signal inste

Re: LimeSDR | Sinewave test | Glitchy behavior

 Hi Anish - I would argue the flowgraph is a potentially a  model for a broken audio device :). That is, the input signal to the WBFM block is not a 48 kHz signal - it's a null source, but you're telling the WBFM block to expect an input frequency of 48 kHz. If you were to add a signal sourc

Re: LimeSDR | Sinewave test | Glitchy behavior

Hi. I performed some more tests and report the results on this thread. https://discourse.myriadrf.org/t/glitchy-behavior-gr-limesdr-limesdr-usb-sinewave-test/7022/10?u=vu2tve I'd love some advice with which I can produce a simple FM modulated sinewave with gnuradio and limesdr. If someone on this

Re: LimeSDR | Sinewave test | Glitchy behavior

So far as I am able to tell with my limited knowledge of limesdr and gnuradio, it seems like some kind of issue with the right settings to me. The gr-limesdr provides a sink block that allows one to use an .ini file instead of the settings done via the block's settings. I will have access to the r

Re: LimeSDR | Sinewave test | Glitchy behavior

Hi Anish - yes, I removed the LImeSDR block from the flow graph. I inserted a throttle instead since I didn't have any front end hardware available at the time. I do have a WBFM receiver using gnuradio running on a HackRF which works great. But I'm using low pass filter taps in the complex

Re: LimeSDR | Sinewave test | Glitchy behavior

Hi Cinaed, But this is without the actual LimeSDR sink block? Or with it? Because, I can produce a clean sinewave with a HackRF, but not the LimeSDR. On Sun, Mar 21, 2021 at 1:07 AM Cinaed Simson wrote: > Hi Anish - I think I may have found the problem. > > When the complex rational resampler

Re: LimeSDR | Sinewave test | Glitchy behavior

Hi Anish - I think I may have found the problem. When the complex rational resampler is on the out put of the WBFM, it bothered me  later that I couldn't see the top of the signal. The scale on QT GUI SINK was clipping the signal but not the computational noise. In the QT GUI SINK, if I set

Re: LimeSDR | Sinewave test | Glitchy behavior

In my case , when running flowgraph, python3 is taking 135% of 8 core  it 16% approximately of all CPU (used top + shift i to get 16%) On 18/03/2021 15:31, Jeff Long wrote: Then it's most likely a performance thing. Check the processor

Re: LimeSDR | Sinewave test | Glitchy behavior

Then it's most likely a performance thing. Check the processor utilization (top with threads mode). The RR is probably maxed out trying to upsample. There's a FIR at 12 MS/s implied there. On Thu, Mar 18, 2021 at 9:43 AM Christophe Seguinot < christophe.segui...@orange.fr> wrote: > Hi all > > The

Re: LimeSDR | Sinewave test | Glitchy behavior

Yes exactly the same results whitout the selector. On 18/03/2021 15:06, Jeff Long wrote: I see you're using the second SDR in a separate part of the flowgraph for testing. That is not a problem. I thought you were doing SDR->SDR.

Re: LimeSDR | Sinewave test | Glitchy behavior

I see you're using the second SDR in a separate part of the flowgraph for testing. That is not a problem. I thought you were doing SDR->SDR. Something else that could be happening - there was a change to the Selector block just after 3.8.2.0. The 3.8.2.0 behavior is to require an equal number of s

Re: LimeSDR | Sinewave test | Glitchy behavior

Here are two debug logs from LimeSuite GUI. In one, I load the settings that gnuradio does to the limesdr and see the debug log. The other is the settings file which the sdrangel writes. If I diff them, among other differences, this is what I see in the end of the sdrangel-debug-log DEBUG: Selecte

Re: LimeSDR | Sinewave test | Glitchy behavior

Using two SDRs, one as a source and one as a sink, gives you a two-clock problem. The Time Sink would still show correctly because it has no clock. On Thu, Mar 18, 2021 at 9:43 AM Christophe Seguinot < christophe.segui...@orange.fr> wrote: > Hi all > > There is something wrong in this simulation.

Re: LimeSDR | Sinewave test | Glitchy behavior

Hi all There is something wrong in this simulation. Attached is a flowgraph with a selectable Lime SDR Source, and a RTL-SDR dongle as receiver. I tested this with a Lime SDR Mini. I was suspecting a Lime SDR issue, however this is not so

Re: LimeSDR | Sinewave test | Glitchy behavior

Okay. That seems to be one of the issues. Once I move the rational resampler block to after the WBFM block, it seems to go away. However, there is still a very perceptible difference in the quality of the signal (gnuradio v/s sdrangel), and there seems to be a lot of noise in the gnuradio-produced

Re: LimeSDR | Sinewave test | Glitchy behavior

You're probably underflowing then (your CPU is not able to deliver enough samples to the LimeSDR sink block). With the FM flow graph, reduce the sweep time on your o-scope to see if you're actually transmitting 100% of the time. Ron On 3/18/21 05:13, Anish Mangal wrote: And, if I try the atta

Re: LimeSDR | Sinewave test | Glitchy behavior

And, if I try the attach gnuradio file, which is just a constant source of value '1' going to the limesdr sink block, I actually see a sine-ish wave without the glitchy behavior. On Thu, Mar 18, 2021 at 5:31 PM Anish Mangal wrote: > I tried your grc and got the same result. > > See the waveform'

Re: LimeSDR | Sinewave test | Glitchy behavior

I tried your grc and got the same result. See the waveform's envelope in this oscilloscope capture. Note the timebase. https://drive.google.com/file/d/1b7PnpmvFfdQTDIwALuOzb22AzeffzR2w/view?usp=sharing This isn't happening in SDRAngel. On Thu, Mar 18, 2021 at 3:49 AM Cinaed Simson wrote: > I m

Re: LimeSDR | Sinewave test | Glitchy behavior

I moved the rational resampler block from the output side to the input side of the WBFM. The output of WBFM block needs to match the input of your LimeSDR. I don't have the LimeSDR software installed so I couldn't look inside the sink block. -- Cinaed P.S - yes, you can post GRC's on the ma

Re: LimeSDR | Sinewave test | Glitchy behavior

I linked the grc file in the original email. Attaching it here as well. (Don't know if the mailing list allows attachments) On Wed, Mar 17, 2021 at 1:40 PM Cinaed Simson wrote: > > Hi Anish - since this is a g

Re: LimeSDR | Sinewave test | Glitchy behavior

Hi Anish - since this is a gnuradio mailing list, the starting point would be to post your GRC - which is an yaml or text file. -- Cinaed On 3/16/21 11:19 PM, Anish Mangal wrote: Hi! Any pointers to where I can start debugging this? Maybe run gnuradio-companion in debug mode? Do more simple

Re: LimeSDR | Sinewave test | Glitchy behavior

Hi! Any pointers to where I can start debugging this? Maybe run gnuradio-companion in debug mode? Do more simpler tests? Any other suggestions? I have a HackRF One and will try the exact same comparison there too ... SDRAngel & grc On Mon, Mar 15, 2021 at 7:32 PM Anish Mangal wrote: > Hi, > >

LimeSDR | Sinewave test | Glitchy behavior

Hi, To properly explain the issue I'm facing, I recorded a video showing Oscilloscope waveforms. https://drive.google.com/file/d/11anGShu-I3NhL9Jet6YAiyBprvwP4kDc/view?usp=sharing The gnuradio flowgraph is here: https://drive.google.com/file/d/1xQz1Kp_feAO1YrZRXXnMF25XEGgqVPSw/view?usp=sharing