Right.. that's what I meant :)
From: Tom Rondeau [mailto:trondeau1...@gmail.com]
Sent: Wednesday, October 19, 2011 2:45 PM
To: Nowlan, Sean
Cc: j...@ettus.com; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Error running benchmark_tx.py from "next" branch
On Wed, Oct 1
On Wed, Oct 19, 2011 at 6:39 AM, Nowlan, Sean
wrote:
> I think I was wrong; it looks like “bitrate” is used in the expected way
> – to indicate the transmission bit rate. However the code doesn’t take
> bits-per-symbol into account in uhd_interface.py (line 70):
>
> ** **
>
> asked_samp_rate
ilto:discuss-gnuradio-bounces%2Bsean.nowlan>=gtri.gatech@gnu.org<mailto:gtri.gatech@gnu.org>]
On Behalf Of Tom Rondeau
Sent: Tuesday, October 18, 2011 7:24 PM
To: j...@ettus.com<mailto:j...@ettus.com>
Cc: discuss-gnuradio@gnu.org<mailto:discuss-gnuradio@gnu.org>
Subject: Re: [Disc
ber 18, 2011 7:24 PM
> *To:* j...@ettus.com
> *Cc:* discuss-gnuradio@gnu.org
>
> *Subject:* Re: [Discuss-gnuradio] Error running benchmark_tx.py from
> "next" branch
>
> ** **
>
> On Tue, Oct 18, 2011 at 4:19 PM, Josh Blum wrote:
>
>
>
> On
s.com
Cc: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Error running benchmark_tx.py from "next" branch
On Tue, Oct 18, 2011 at 4:19 PM, Josh Blum
mailto:j...@ettus.com>> wrote:
On 10/18/2011 04:02 PM, Nowlan, Sean wrote:
> I tried with the E100's actual add
On 10/18/2011 04:23 PM, Tom Rondeau wrote:
> On Tue, Oct 18, 2011 at 4:19 PM, Josh Blum wrote:
>
>>
>>
>> On 10/18/2011 04:02 PM, Nowlan, Sean wrote:
>>> I tried with the E100's actual address and the loopback address
>>> (127.0.0.1) and both worked. I should also say it's a bit confusing
>>> t
On Tue, Oct 18, 2011 at 4:19 PM, Josh Blum wrote:
>
>
> On 10/18/2011 04:02 PM, Nowlan, Sean wrote:
> > I tried with the E100's actual address and the loopback address
> > (127.0.0.1) and both worked. I should also say it's a bit confusing
> > to call the command line switch "--address" when it's
n.nowlan=gtri.gatech@gnu.org[mailto:
> discuss-gnuradio-bounces+sean.nowlan=gtri.gatech@gnu.org] *On Behalf
> Of *Marcus D. Leech
> *Sent:* Tuesday, October 18, 2011 6:30 PM
> *To:* discuss-gnuradio@gnu.org
> *Subject:* Re: [Discuss-gnuradio] Error running benchmark_tx.py from
&g
o the right thing.
Thanks,
Sean
P.S. - Thank you for your hard work moving the gnuradio examples to UHD!
From: Tom Rondeau [mailto:trondeau1...@gmail.com]
Sent: Tuesday, October 18, 2011 7:06 PM
To: Nowlan, Sean
Cc: Marcus D. Leech; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Error
On 10/18/2011 04:02 PM, Nowlan, Sean wrote:
> I tried with the E100's actual address and the loopback address
> (127.0.0.1) and both worked. I should also say it's a bit confusing
> to call the command line switch "--address" when it's actually
> handling the arguments the same way as uhd_find_de
rg[mailto:
> discuss-gnuradio-bounces+sean.nowlan=gtri.gatech@gnu.org] *On Behalf
> Of *Marcus D. Leech
> *Sent:* Tuesday, October 18, 2011 6:30 PM
> *To:* discuss-gnuradio@gnu.org
> *Subject:* Re: [Discuss-gnuradio] Error running benchmark_tx.py from
> "next" bran
ss-gnuradio-bounces+sean.nowlan=gtri.gatech@gnu.org
[mailto:discuss-gnuradio-bounces+sean.nowlan=gtri.gatech@gnu.org] On Behalf
Of Marcus D. Leech
Sent: Tuesday, October 18, 2011 6:30 PM
To: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Error running benchmark_tx.py from "next" br
Perhaps this is the wrong place to post this error, but I'm hoping for
a quick response J
I'm getting a "network unreachable" error on an E100 when trying to
run benchmark_tx.py from the gnuradio "next" branch (Tom Rondeau?).
Command line & error, and output of uhd_usrp_probe are attached.
T
Perhaps this is the wrong place to post this error, but I'm hoping for a quick
response :)
I'm getting a "network unreachable" error on an E100 when trying to run
benchmark_tx.py from the gnuradio "next" branch (Tom Rondeau?). Command line &
error, and output of uhd_usrp_probe are attached.
Th
14 matches
Mail list logo
