On Tue, Oct 18, 2011 at 4:18 PM, Nowlan, Sean <sean.now...@gtri.gatech.edu>wrote:
> Also in benchmark_tx.py I noticed that calling “-m qpsk” and “-m bpsk” > still default to their differential versions unless I explicitly use the > “--non-differential” switch. Was this intended? I assumed that specifying > “*psk” vs. “d*psk” would do the right thing. > No intentional, and I thought I had it working correctly. It's an issue with the OptionParser and having two options with the same name. They step on each other. I need to figure out a better way to handle that. > Thanks,**** > > Sean**** > > ** ** > > P.S. – Thank you for your hard work moving the gnuradio examples to UHD! > You're welcome! Tom > > > *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 running benchmark_tx.py from > "next" branch**** > > ** ** > > On Tue, Oct 18, 2011 at 4:02 PM, Nowlan, Sean <sean.now...@gtri.gatech.edu> > 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_devices, etc. handle the “--args” switch. For instance, I > also got it to run with --address=”type=e100”. Also it’d be nice (but not > necessary) to have the program automatically detect if it’s an E100 since it > will never be controlling devices other than itself.**** > > **** > > Sean**** > > ** ** > > You're right about the address-->args thing. I started doing all of this on > a USRP N210, so it was always the systems IP address for me, so that's what > it became. Now, to remember all of the places where I did it and correct for > it...**** > > ** ** > > As for the auto-detection, I suppose it's possible to tap into the UHD's > find_devices feature and just default to the first one it finds as opposed > to a static default. I'll talk with Josh about doing this.**** > > ** ** > > Tom**** > > ** ** > > **** > > **** > > *From:* discuss-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" branch**** > > **** > > 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.**** > > **** > > Thanks!**** > > Sean**** > > **** > > Probably needs a --args that tells UHD to go looking for the e100 > interface, rather than whatever its default is. > > Perhaps Josh can comment on the search order that UHD uses when you don't > explicitly specify a device, and is that order > different on an e100? > > **** > > -- **** > > Marcus Leech**** > > Principal Investigator**** > > Shirleys Bay Radio Astronomy Consortium**** > > http://www.sbrac.org**** > > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio**** > > ** ** >
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
