discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Bug with USRP2/SBX and UHD when launching the acq


From: Emmanuel Caillé
Subject: Re: [Discuss-gnuradio] Bug with USRP2/SBX and UHD when launching the acquisition
Date: Mon, 8 Aug 2011 11:04:49 +0200

2011/8/8 Emmanuel Caillé <address@hidden>:
> 2011/8/5 Marcus D. Leech <address@hidden>:
>> On 05/08/2011 10:33 AM, Emmanuel Caillé wrote:
>>>
>>> Hello all,
>>>
>>> I have a problem with my USRP2 (with a SBX board) :
>>> Most of times when I launch the acquisition, no data are received.
>>>
>>> For example with uhd_fft.py :
>>>
>>> $ uhd_fft.py
>>> linux; GNU C++ version 4.5.2; Boost_104200; UHD_003.002.001-fc349d3
>>> -- Opening a USRP2/N-Series device...
>>> -- Current recv frame size: 1472 bytes
>>> -- Current send frame size: 1472 bytes
>>>
>>> and the FFT Plotter appear but is empty.
>>>
>> Also, what do you get with
>>
>> uhd_usrp_probe --args "addr=192.168.10.2"  (or whatever you've set the IP
>> addr of the USRP2 to).
>>
>>
>
> There are no samples (autoscale don't do anything) and there are no
> timeout errors.
> I perfectly ping the device (with 0% packet loss).
> I don't understand why sometimes it works and at other times it
> doesn't (without changing any option).
>
> $ uhd_usrp_probe
> linux; GNU C++ version 4.5.2; Boost_104200; UHD_003.002.001-fc349d3
>
> -- Opening a USRP2/N-Series device...
> -- Current recv frame size: 1472 bytes
> -- Current send frame size: 1472 bytes
>  _____________________________________________________
>  /
> |       Device: USRP2 / N-Series Device
> |     _____________________________________________________
> |    /
> |   |       Mboard: USRP2-REV4
> |   |   rev: 1024
> |   |   mac-addr: 00:50:c2:85:3a:a4
> |   |   ip-addr: 10.66.160.164
> |   |   gpsdo: none
> |   |   serial: 2724
> |   |
> |   |   Time sources: none, external, _external_, mimo
> |   |   Clock sources: internal, external, mimo
> |   |   Sensors: mimo_locked, ref_locked
> |   |     _____________________________________________________
> |   |    /
> |   |   |       RX DSP: 0
> |   |   |   Freq range: -50.000 to 50.000 Mhz
> |   |     _____________________________________________________
> |   |    /
> |   |   |       RX DSP: 1
> |   |   |   Freq range: -50.000 to 50.000 Mhz
> |   |     _____________________________________________________
> |   |    /
> |   |   |       RX Dboard: A
> |   |   |   ID: SBX (0x0054)
> |   |   |   Serial: E7R10Y0XS
> |   |   |     _____________________________________________________
> |   |   |    /
> |   |   |   |       RX Subdev: 0
> |   |   |   |   Name: SBX (0x0054)
> |   |   |   |   Antennas: TX/RX, RX2
> |   |   |   |   Sensors: lo_locked
> |   |   |   |   Freq range: 68.750 to 4400.000 Mhz
> |   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
> |   |   |   |   Connection Type: IQ
> |   |   |   |   Uses LO offset: No
> |   |   |     _____________________________________________________
> |   |   |    /
> |   |   |   |       RX Codec: A
> |   |   |   |   Name: ltc2284
> |   |   |   |   Gain Elements: None
> |   |     _____________________________________________________
> |   |    /
> |   |   |       TX DSP: 0
> |   |   |   Freq range: -250.000 to 250.000 Mhz
> |   |     _____________________________________________________
> |   |    /
> |   |   |       TX Dboard: A
> |   |   |   ID: SBX (0x0055)
> |   |   |   Serial: E7R10Y0XS
> |   |   |     _____________________________________________________
> |   |   |    /
> |   |   |   |       TX Subdev: 0
> |   |   |   |   Name: SBX (0x0055)
> |   |   |   |   Antennas: TX/RX
> |   |   |   |   Sensors: lo_locked
> |   |   |   |   Freq range: 68.750 to 4400.000 Mhz
> |   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
> |   |   |   |   Connection Type: QI
> |   |   |   |   Uses LO offset: No
> |   |   |     _____________________________________________________
> |   |   |    /
> |   |   |   |       TX Codec: A
> |   |   |   |   Name: ad9777
> |   |   |   |   Gain Elements: None
>
> (I had the same problem when I used the 192.168.10.2 IP)
>

I fixed my problem : I replaced my Gigabit Switch with a crossed cable
and know everything work fine.

Thanks for your advices.

--
Emmanuel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]