On 05/31/2018 01:53 PM, Steve Gough wrote:
Thanks for the tip. Tried that as well, and I get the below. Device
address in the GRC parameter is set as : "addr=192.168.10.2
addr=192.168.10.5" (as attached)
File "/home/colosseum/Downloads/for_steve_gough2.py", line 37, in
__init__
chann
On 05/31/2018 01:24 PM, Steve Gough wrote:
Oh, I meant I edited the python from the GRC which you had sent to
print the number of motherboards using UHD's get_num_mboards
(https://files.ettus.com/manual/classuhd_1_1usrp_1_1multi__usrp.html#ae4efbbc6480fba44939b34c78d44d7e9),
and it returned 1.
On 05/31/2018 12:50 PM, Steve Gough wrote:
Thanks. That temporarily fixes the addressing issue. However, I am now
seeing the following error. Could you please tell me why this might be
happening?
File "/home/colosseum/Downloads/for_steve_gough.py", line 47, in __init__
self.uhd_usrp_source
Thanks. That temporarily fixes the addressing issue. However, I am now
seeing the following error. Could you please tell me why this might be
happening?
File "/home/colosseum/Downloads/for_steve_gough.py", line 47, in __init__
self.uhd_usrp_source_0.set_clock_source('external', 1)
File
"/hom
On 05/30/2018 04:45 PM, Steve Gough wrote:
Same error still, unfortunately even after setting the gateway and
subnet on the N210 via usrp_burn_mb_eeprom and power-cycling.
Ah!
Try this in your device args:
"addr=192.168.10.5 addr=192.168.10.2"
For the N210:
| | Mboard: N210r4
| |
Same error still, unfortunately even after setting the gateway and subnet
on the N210 via usrp_burn_mb_eeprom and power-cycling.
For the N210:
| | Mboard: N210r4
| | hardware: 2577
| | mac-addr: a0:36:fa:25:3e:96
| | ip-addr: 192.168.10.5
| | subnet: 255.255.255.0
| | g
On 05/30/2018 02:00 PM, Steve Gough wrote:
Thanks for the reply, Ian and Marcus.
I see. Could you please tell me what should be the values I must set
on the host and N210 for the gateway and subnet ?
Thanks!
Gateway addy should all be (assuming 192.168.10.x) subnet:
192.168.10.1
Subnet ma
Thanks for the reply, Ian and Marcus.
I see. Could you please tell me what should be the values I must set on the
host and N210 for the gateway and subnet ?
Thanks!
On Wed, May 30, 2018 at 12:36 PM, Ian Buckley via USRP-users <
usrp-users@lists.ettus.com> wrote:
> Those N210 settings are broken
Those N210 settings are broken also…bad subnet and gateway
> On May 30, 2018, at 9:26 AM, Marcus D. Leech via USRP-users
> wrote:
>
> On 05/30/2018 12:22 PM, Steve Gough via USRP-users wrote:
>> Hi Neel and USRP mailing list,
>>
>> The uhd_usrp_probe returns as follows:
>>
>> For the N210 wit
On 05/30/2018 12:22 PM, Steve Gough via USRP-users wrote:
Hi Neel and USRP mailing list,
The uhd_usrp_probe returns as follows:
For the N210 with WBX:
Mboard: N210r4
| | hardware: 2577
| | product: 30194
| | mac-addr: a0:36:fa:25:3a:6b
| | ip-addr: 192.168.10.4
| | subnet: 2
Hi Neel and USRP mailing list,
The uhd_usrp_probe returns as follows:
For the N210 with WBX:
Mboard: N210r4
| | hardware: 2577
| | product: 30194
| | mac-addr: a0:36:fa:25:3a:6b
| | ip-addr: 192.168.10.4
| | subnet: 255.255.255.255
| | gateway: 255.255.255.255
For the X31
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.
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
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
> wrote:
>
> On
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' faile
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
On 05/25/2018 01:22 PM, Steve Gough wrote:
Thanks Marcus.
I tried the following :
from gnuradio import gr
from gnuradio import uhd
addresses="addr0=192.168.10.5,addr1=192.168.10.2"
uhd_usrp_source_0 = uhd.usrp_source(",".join((addresses,
"")),uhd.st
On 05/25/2018 01:22 PM, Steve Gough wrote:
Thanks Marcus.
I tried the following :
from gnuradio import gr
from gnuradio import uhd
addresses="addr0=192.168.10.5,addr1=192.168.10.2"
uhd_usrp_source_0 = uhd.usrp_source(",".join((addresses,
"")),uhd.st
Thanks Marcus.
I tried the following :
from gnuradio import gr
from gnuradio import uhd
addresses="addr0=192.168.10.5,addr1=192.168.10.2"
uhd_usrp_source_0 = uhd.usrp_source(",".join((addresses,
"")),uhd.stream_args(cpu_format="fc32",channels=range(5),
On 05/24/2018 03:08 PM, Steve Gough via USRP-users wrote:
Oops- meant to say SBX is tuned to 2.4GHz. But the question remains
the same.
Thanks!
Multi-usrp will time-align all the streams going through it.
You'll need to make sure that your devices are set to use the external
REF clock, and t
Oops- meant to say SBX is tuned to 2.4GHz. But the question remains the
same.
Thanks!
On Thu, May 24, 2018 at 2:56 PM, Steve Gough wrote:
> Hi All,
>
>
> I have an X310 with two TwinRXs and an N210 with a WBX. The TwinRXs are
> listening to a signal at 5.8GHz, and the WBX is tuned to 2.4GHz. Th
21 matches
Mail list logo
