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 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 :) 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
