Re: Grc bus issues.

Indeed, it is! On 18.03.21 18:44, Nicholas Long wrote: > Sorry, 3.8.2.0 > > Is that the most recent 3.8 version? > > On Thu, Mar 18, 2021, 12:34 Marcus Müller > wrote: > > Could you share the full version? e.g. 3.8.22.3 ? > > On 18.03.21 18:32, Nicholas L

GRCon 2021 Quick Survey [Responses Needed]

Hello! We are gathering information to help with planning GRCon 2021, which is scheduled to take place 20-24 September, 2021 in Charlotte, NC. The survey is anonymous and should literally take only a few seconds to complete. Please take a moment and answer the 2 questions here when you have a ch

Re: Grc bus issues.

Sorry, 3.8.2.0 Is that the most recent 3.8 version? On Thu, Mar 18, 2021, 12:34 Marcus Müller wrote: > Could you share the full version? e.g. 3.8.22.3 ? > > On 18.03.21 18:32, Nicholas Long wrote: > > 3.8 > > > > On Thu, Mar 18, 2021, 12:30 Marcus Müller > > wrote

Project call coming up TODAY

In 15 minutes, the project call is going to happen: https://twitch.tv/gnuradio If you have any questions, do ping us in the chat there or on Matrix. Want to be part of this or a future call? Don't hesitate to reach out! Cheers, Marcus

Re: Grc bus issues.

Could you share the full version? e.g. 3.8.22.3 ? On 18.03.21 18:32, Nicholas Long wrote: > 3.8 > > On Thu, Mar 18, 2021, 12:30 Marcus Müller > wrote: > > Hi Nick, > what GNU Radio version are you on? > > Best regards, > Marcus > > On 18.03.21

Re: Grc bus issues.

Hi Nick, what GNU Radio version are you on? Best regards, Marcus On 18.03.21 17:34, Nicholas Long wrote: > So I have a block that has 100 streaming inputs and 1 message input. I have a > second block > that outputs 25 streams per block (technically this is a meta python block > made up of 25 >

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

Grc bus issues.

So I have a block that has 100 streaming inputs and 1 message input. I have a second block that outputs 25 streams per block (technically this is a meta python block made up of 25 smaller sub blocks). To properly connect these I need to connect 4 of these generating block to the sink block. To dea

Stable RCs 3.8.3.0-rc1 and 3.9.1.0-rc1

GNU Radio is broadcasting two new stable release candidates. These are expected to become final releases within the next week. Check out the releases at: https://github.com/gnuradio/gnuradio/releases See the changelogs at: https://github.com/gnuradio/gnuradio/blob/maint-3.8/CHANGELOG.md https://g

Re: raspberry pi + dvb-t2

Ok, thanks! On March 18, 2021 1:01:41 PM UTC, Ron Economos wrote: >There are no libvolk optimizations for the LDPC encoder. I don't even >think it's possible. The encoder is just a giant XOR, but the XOR >operands are not from contiguous locations in memory. > >Ron > >On 3/18/21 05:42, Adrian M

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

HackRF | FSK Modulation minimal example for 1MHz FSK deciation

Hi community, I have been trying to create FSK modulation with HackRf but I couldn't make it work. I have explained some of my trials on stackoverflow[1] , but I am just asking here if you can you help me wi

Re: raspberry pi + dvb-t2

There are no libvolk optimizations for the LDPC encoder. I don't even think it's possible. The encoder is just a giant XOR, but the XOR operands are not from contiguous locations in memory. Ron On 3/18/21 05:42, Adrian Musceac wrote: Hi Ron, Tangential to the subject only, do you know if LDPC

Re: raspberry pi + dvb-t2

Hi Ron, Tangential to the subject only, do you know if LDPC has optimizations for ARM archs in libvolk? Arm64 mainly. Thanks, Adrian On March 18, 2021 11:54:42 AM UTC, Ron Economos wrote: >I haven't tried it, but it may be possible on a Raspberry Pi 4. I >wouldn't bother with anything less tha

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: raspberry pi + dvb-t2

I haven't tried it, but it may be possible on a Raspberry Pi 4. I wouldn't bother with anything less than a RPi4. I have successfully run a modified DVB-T2 flow graph on a Beagleboard-X15, but only at 5 MHz channel width (5.714285 Msps). I've attached the flow graph. It uses short frames and 5

raspberry pi + dvb-t2

Hi all, Is there any experience in transmitting DVB-T2 with gnuradio and raspberry pi (any version)? I just wonder if it can work real-time with about 9 MHz sampling frequency of 8 MHz DVB-T2. Thank you! BR, AGD

Re: Generator error flow graph

Looking more deeply into this, I figure out that this flowgraph must not be used with conventionnal FM Signal there is in /gnuradio/gr-analog/examples/ an FM emitter fm_tx.grc use this to generate dummy.dat ( (*)rename the file at your convenie

Re: Generator error flow graph

Hi Frédérique About dummy.dat . The dummy.dat file (see file source in tyour flowgraph) is a binary file which is not present in the example folder containing a list of complex samples. You have to find some recorded FM Signal to run the flowgraph. Gnuradi

RE: Generator error flow graph

Hi Cinaed, Sorry but I am beginner in USRP. What is the file dummy.dat please ? I don't have front end hardware. If I run fmtest.py I have no problem but my target is to generate my own python code with my flow graph. Thanks you very much for your help. Fred De : Cinaed Simson Envoyé : mercr