Hi all,
Thanks for the tips. ill go through them and come back to you soon.
Best Regards
Ihab
On 29 August 2016 at 20:53, Ben Hilburn wrote:
> Hi Ihab -
>
> I recommend checking out this paper on performance counters & ctrlport.
> The dependency on `thrift` can be a bit painful, but these ar
Hi Ihab,
that's great!!
So, I see that others already pointed out the very handy htop / top
utilities, which can give you a rough idea of where the CPU is spent
within the blink of an eye, as well as the far more involved, but also
far more detailed controlport approach that can also tell you exa
Hi Ihab -
I recommend checking out this paper on performance counters & ctrlport. The
dependency on `thrift` can be a bit painful, but these are great tools in
GNU Radio for instrumenting your application and optimizing performance.
http://conferences.sigcomm.org/sigcomm/2013/papers/srif/p65.pdf
One way I check for bottlenecks it to run 'top -H' and watch the various
threads. If you see any one thread pegged at 100% then it needs to be
optimized. At least that's my method :)
On Mon, Aug 29, 2016 at 9:46 AM, Ihab Zine wrote:
> Hi Marcus,
>
> I have been through the GNU RADIO tutorials
Hi Marcus,
I have been through the GNU RADIO tutorials , I also dived into adapting
gr-dvbt, and it worked for me. But how can i find out where my transceiver
BER bottlenecks and where my computational bottlenecks come from? Is the a
method or steps i can follow? I need some hints on this.
Best R
Hi Ihab
> For frequency higher than 6 Ghz, a down converter can be used to over
> come this problem.
Exactly what we're saying!
> I think it can handle this rate. Please correct me if i'm Wrong.
You might be wrong! As said, this is a hard task, and it's very hard to
make things scale up on many
Hi Ron and Marcus,
For frequency higher than 6 Ghz, a down converter can be used to over come
this problem.
for the data rate and bandwidth, the PC i'm using has the following
specifications:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order:Little
Right, I should have mentioned that high rates are very CPU-intense.
In fact, it's not seldom that getting 50MS/s into a PC and processed
occupies a single CPU core completely. After all, we're talking about
1.6 Gb/s in pure samples, before they're even converted to what likely
is floating point,
Agree with all of Marcus' comments. However, the 150 to 326 Mbps
requirement may be quite difficult. To put things in perspective, my run
of the mill 3 GHz E5-1607 Xeon x86 processor can just barely decode
16QAM DVB-T at 16 Mbps. You'll probably need a high-end CPU with as many
cores as you can
Hi Ihab,
> 1) Frequency range: 1.5 - 38 GHz
since the B205 mini only goes up to 6 GHz, you're bound to use an
external mixer. The device you chose for that will completely depend on
your specific application's needs. Also note that finding something that
works as well at 1.5 GHz as it does on 38
Hi Ron,
1) Frequency range: 1.5 - 38 GHz
2) Bandwidth range : 2 - 56 MHz
3) Modulation : Qpsk - 256 QAM
4) Data rate range : 150Mbit/s - 326Mbit/s.
5) Error correction method : i thinks it is FEC.
Ihab
On 22 August 2016 at 12:33, Ihab Zine wrote:
> Hi All,
>
> I'm working on a project usin
You need to be more specific.
1) Frequency
2) Bandwidth
3) Modulation
4) Data rate
5) Error correction method
Ron
On 08/22/2016 04:33 AM, Ihab Zine wrote:
Hi All,
I'm working on a project using GnuRadio And USRP 205 mini, i'm at the
stage where i need to demodulate a microwave link signa
Hi All,
I'm working on a project using GnuRadio And USRP 205 mini, i'm at the stage
where i need to demodulate a microwave link signal.
Anyone has an experience with Microwave link or tried to do something similar?
Is it possiable to do it in gnuradio? or is there another approaches to do
it?
I'
13 matches
Mail list logo
