requency?
> > > > > > > > > >
> > > > > > > > > > On Tue, 2019-07-16 at 18:32 +0200, sumit kumar wrote:
> > > > > > > > > > > Ok, so for a constant source, in the time domain you
> > will see a f
The USRP has a DC offset removal filter in the FPGA. A carrier sent at 0Hz
is exactly the same as DC offset, and will be removed. Zero-IF receiver
architectures (like the USRP) intrinsically have DC offset imperfections.
The filter can be disabled in the USRP Source "FE Options" tab. It is not
good
If you are on Linux you could just create a file in tmpfs (i.e. RAM).
Use a File Sink with a file in "/dev/shm" for instance (see "man mount"
to configure tmpfs).
Of course you then probably need a lot of RAM (or can capture only small
durations). But it is much faster than disk I/O...
Müller, Mar
Hi Marcus,
I'm using Raspbian buster, which is their latest release.
Thanks,
---
Barry Duggan
On 2019-07-18 05:03, Müller wrote:
Hi Barry,
which OS / Linux Distro (I presume) are you using on your Pi?
Best regards,
Marcus
On Wed, 2019-07-17 at 22:09 -0400, Barry Duggan wrote:
Hi,
Today I
Hi all,
Thank you very much for your emails.
But no tip works fine.
I wanted only to learn how is USRP working with GNU radio, I thought that
the RX chain in the USRP was different.
But I am not the beginner in electronic and RF circuits.
Anyway, no problem, I don't ask more information about this
Hi Jonas,
Thank you!
I know that I send the signal plus carrer signal.
I wanted only to explain in a simple way my problem.
Best Regards,
Simona
Il giorno gio 18 lug 2019 alle ore 12:11 Jonas Manthey <
jonas.mant...@u-blox.com> ha scritto:
> Hi,
>
>
>
> You don’t send a sine with frequency 0,
Hi,
You don’t send a sine with frequency 0, you send a carrier that is modulated
by a sine with a frequency of 0. A sine with a frequency of 0 is 0: sin(2 pi f)
= sin(2 pi 0) = sin(0) = 0.
So your carrier is modulated with a zero, which I *think* ends up in no carrier
at all, not sure right n
Hi,
I know this list contains a lot of recipients but I'd just like to thank you
and all contributors for this major release, looking forward to check it soon.
Keep up the good work!
Cheers,
Jonas
-Original Message-
From: Discuss-gnuradio
[mailto:discuss-gnuradio-bounces+jonas.manthey
I'll simply pull the stereotypical software guy card:
Then you'll need get faster storage, and probably a faster PC.
Really, run an analysis ("perf top -ag" is an excellent tool for that)
where your computer is stuck spending most of its time during
operation. Optimize your resources where it mat
I agree the problem is the amount of samples so I have dropped the idea
of storing samples but is there a way to handle such sampling rates in
gnuradio? I would like to know the time stamp of the data received which
i am unable to access using tag debug. I don't know why but it suddenly
stops d
The problem is not the metadata, the problems is the sheer amount of
samples.
Best regards,
Marcus
On Thu, 2019-07-18 at 13:18 +0530, SG wrote:
> Hi,
>
> Thanks for your reply.
>
> Now that since metadata can't be saved to a file, how can we keep track
> of timestamp of the received packets? I
Hi Barry,
which OS / Linux Distro (I presume) are you using on your Pi?
Best regards,
Marcus
On Wed, 2019-07-17 at 22:09 -0400, Barry Duggan wrote:
> Hi,
>
> Today I tried to install gnuradio in my Raspberry Pi. I encountered the
> following problems:
>
> A. In https://github.com/gnuradio/gn
Hi,
Thanks for your reply.
Now that since metadata can't be saved to a file, how can we keep track
of timestamp of the received packets? I can use tag debug to display the
timestamps of received signal but when flowgraph starts demodulating
data it looses track of timestamp display on console
13 matches
Mail list logo
