What are the netmask settings of the N210 and X310?
("uhd_usrp_probe" will show this)And just to be sure, they have different MAC addresses, right? What are the IP address and netmask of your host? --Neel Pandeya On 25 May 2018 at 15:12, Steve Gough via USRP-users < usrp-users@lists.ettus.com> wrote: > Hmmm. There's no other 192.168.10.2 on the network. > > There are only two devices of interest connected to the switch : a > 192.168.10.2 (X310) and a 192.168.10.5 (N210). Both are visible by > uhd_find_devices. > > Furthermore, things work fine when I use the timed commands on the > TwinRX's of the X310 alone. It's only when I add an N210, does this problem > crop up. > > On Fri, May 25, 2018 at 3:39 PM, Ian Buckley <i...@ionconcepts.com> wrote: > >> This is purely speculative given how stale I am on X310…but could there >> be more than one device located to those IP addresses? >> I’d pull out Wireshark and see what MAC addresses’s I’m seeing on ping >> returns perhaps? >> >> > On May 25, 2018, at 12:36 PM, Marcus D. Leech via USRP-users < >> usrp-users@lists.ettus.com> wrote: >> > >> > On 05/25/2018 03:27 PM, Steve Gough wrote: >> >> Thanks Marcus. >> >> >> >> >> >> I get the same error. >> >> >> >> ------------------------------------ >> >> colosseum@colosseum-ThinkPad-T430:~/wireless/lp_door/doppler/usrp_sync$ >> python ~/Downloads/for_steve_gough.py >> >> WARNING: Config file '/home/colosseum/.gnuradio/config.conf' failed >> to parse: >> >> std::exception >> >> Skipping it >> >> WARNING: Config file '/home/colosseum/.gnuradio/config.conf' failed >> to parse: >> >> std::exception >> >> Skipping it >> >> WARNING: Config file '/home/colosseum/.gnuradio/config.conf' failed >> to parse: >> >> std::exception >> >> Skipping it >> >> linux; GNU C++ version 5.4.0 20160609; Boost_105800; >> UHD_003.011.000.git-78-gf70dd85d >> >> >> >> >> >> UHD Error: >> >> Device discovery error: ValueError: Could not resolve device hint >> "addr=192.168.10.2" to a single device. >> >> >> >> UHD Error: >> >> Device discovery error: ValueError: Could not resolve device hint >> "addr=192.168.10.5" to a single device. >> >> >> >> Traceback (most recent call last): >> >> File "/home/colosseum/Downloads/for_steve_gough.py", line 95, in >> <module> >> >> main() >> >> File "/home/colosseum/Downloads/for_steve_gough.py", line 84, in main >> >> tb = top_block_cls() >> >> File "/home/colosseum/Downloads/for_steve_gough.py", line 36, in >> __init__ >> >> channels=range(5), >> >> File >> >> "/home/colosseum/src/gr-prefix/lib/python2.7/dist-packages/gnuradio/uhd/__init__.py", >> line 122, in constructor_interceptor >> >> return old_constructor(*args) >> >> File >> >> "/home/colosseum/src/gr-prefix/lib/python2.7/dist-packages/gnuradio/uhd/uhd_swig.py", >> line 2686, in make >> >> return _uhd_swig.usrp_source_make(*args) >> >> RuntimeError: LookupError: KeyError: No devices found for -----> >> >> Device Address: >> >> addr0: 192.168.10.2 >> >> addr1: 192.168.10.5 >> >> >> >> >> >> I can ping both 192.168.10.2 and 192.168.10.5 . >> >> >> >> Could you please let me know why this might be happening ? I can >> sample align 2 N210s though. By simply changing the IP address and >> #channels in the usrp.uhd_source() call. >> >> >> > I can't make sense of this. >> > >> > Perhaps Martin Braun can comment, or one of the other X310 dev team? >> > >> > I don't have an N210 in my lab, so I can't reproduce it. >> > >> > >> > >> > _______________________________________________ >> > 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 > >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
