Hi Neel, Thanks for the reply, I tried the suggestion:
* augment your device string with type=n2xx* And this is what I get: *uhd_find_devices --args="type=n200"No UHD Devices Found* Thanks. Best, Dev Joshi, PhD Postdoctoral Research Associate Department of Physics and Engineering The University of Scranton C: 617 775 9712 On Tue, Oct 27, 2020 at 10:10 AM Neel Pandeya <neel.pand...@ettus.com> wrote: > Hello Dev Joshi: > > Is the N200 directly connected to the host computer? > > What are the IP addresses and netmask of the host and the N200? Do you > have a gateway address configured? > > Earlier, Marcus suggested trying to augment your device string with > "type=n2xx". Did you try that? > > --Neel Pandeya > > > > On Mon, 19 Oct 2020 at 17:20, Marcus D. Leech via USRP-users < > usrp-users@lists.ettus.com> wrote: > >> On 10/19/2020 05:32 PM, Dev Joshi via USRP-users wrote: >> >> Hello everyone, >> >> I hope everyone is keeping well through these unusual times. I am writing >> to request assistance on an issue I am facing while running Ettus N200 >> device. The device is installed to receive high frequency radio waves and >> it is connected to an internet port by an Ethernet cable as is the >> computer (Ubuntu). I can ping the device from the terminal of the computer. >> But, whenever I invoke the USRP N200 using any command, it doesn't work as >> shown below : >> >> uhd_find_devices --args="addr=xx.xx.xxx.xx" >> [INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; >> UHD_3.15.0.HEAD-0-gaea0e2de >> No UHD Devices Found >> >> But, if I pass the command soon after the first invocation, it works as >> shown below: >> >> uhd_find_devices --args="addr=xx.xx.xxx.xx" >> [INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; >> UHD_3.15.0.HEAD-0-gaea0e2de >> -------------------------------------------------- >> -- UHD Device 0 >> -------------------------------------------------- >> Device Address: >> serial: 31D09D8 >> addr: xx.xx.xxx.xx >> name: >> type: usrp2 >> >> And, subsequent invocations in the near future work. And, it applies for >> any other command I have used to invoke the >> USRP device. I would greatly appreciate suggestions from experienced >> users in this list. And, one more issue, the above command used to work >> without passing the "addr" argument. But recently, it doesn't respond if I >> don't pass that argument. >> >> I would greatly appreciate suggestions on these two points. >> >> Thanks. >> >> Best, >> Dev >> >> >> augment your device string with type=n2xx >> >> >> _______________________________________________ >> USRP-users mailing list >> USRP-users@lists.ettus.com >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >> >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
