On 01/30/2020 01:56 PM, Daniel Estévez wrote:
Hi all,
Something that I just learned from a quick Google search. It seems that
GNU Radio 3.8 support in gr-limesdr is now done:
https://github.com/myriadrf/gr-limesdr/issues/44
Best,
Daniel.
There are bunches of us who write applications that
El 30/1/20 a las 16:09, Marcus Müller (GNU Radio maintainer) escribió:
> Consider gr-limesdr not working on GNU Radio 3.8 (I didn't even know
> that): 3.8 has been announced for years, and I think Lime would
> actually be the party in need of keeping up with their customers'
> needs, not us. I
Hi Ralph,
thanks for reaching out!
Well, I'm coming from exactly the other side as you: GNU Radio's
version hell is finally getting reduced.
You see, we've been stuck with GNU Radio 3.7 for what feels like
forever. That meant that a lot of technically necessary stuff, like
using Python 3,
Hi,
> > > I know, this is mainly a matter of the people who maintain such
> > > projects...and I have no idea how the awareness for this could be
> > > sharpened.
> >
> > Paying the maintainer usually helps.
>
> Sure, in a commercial world things work this way. In a hobbyists world
> however
Hi,
> > I know, this is mainly a matter of the people who maintain such
> > projects...and I have no idea how the awareness for this could be sharpened.
>
> Paying the maintainer usually helps.
Sure, in a commercial world things work this way. In a hobbyists world however
the projects just die
First investigate if your problem is related to LimeSDR source.
Simply connect a time sink to the output of thee Lime Source.
Autoscale to see if the signal is present .
In one of my attempt, this signal was very low and has only 2
different values like a binary
