Send USRP-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."


Today's Topics:

   1. Re: disabling dc offset correction loop in FPGA
      (Lapointe, Benjamin - 1008 - MITLL)
   2. Re: disabling dc offset correction loop in FPGA (Josh Blum)
   3. Re: SBX simultaneous transmit receive problem... (salman dinani)
   4. B100 Connection Problem (Rob Rhinehart)
   5. Re: B100 Connection Problem (Josh Blum)
   6. Re: B100 Connection Problem (Rob Rhinehart)
   7. Calibration on USRP1 (Stefano Speretta)
   8. Re: SBX simultaneous transmit receive problem... (Marcus D. Leech)
   9. Re: Calibration on USRP1 (Marcus D. Leech)


----------------------------------------------------------------------

Message: 1
Date: Mon, 26 Mar 2012 18:29:15 -0400
From: "Lapointe, Benjamin - 1008 - MITLL" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] disabling dc offset correction loop in FPGA
Message-ID:
        <mailman.54.1332864013.11180.usrp-users_lists.ettus....@lists.ettus.com>
        
Content-Type: text/plain; charset="us-ascii"

I tried using the API hooks recommended below, but to no avail.  In my 
rx_samples_to_file before making the call to recv_to_file, I added the 
following lines:

usrp->set_rx_dc_offset(false);
std::complex<double> dc_offset(0.5, 0.5);
usrp->set_rx_dc_offset(dc_offset);

I tried changing the dc_offset from 0.0 to 1.0, but the dc offset in my data is 
still auto corrected.

Does anyone have any idea what I am doing wrong?

Thanks,
-ben
________________________________________
From: [email protected] [[email protected]] 
On Behalf Of Josh Blum [[email protected]]
Sent: Friday, March 23, 2012 3:43 PM
To: [email protected]
Subject: Re: [USRP-users] disabling dc offset correction loop in FPGA

On 03/23/2012 12:40 PM, Lapointe, Benjamin - 1008 - MITLL wrote:
> Hi,
>
>
>
> I am trying to look at a DC signal with the LFRX board.  In an old forum
> post, somebody mentioned that the ADC DC offset correction loop in the FPGA
> needs to be disabled.  Is it possible to disable it in the HDL of the FPGA?
> Or inside something like rx_samples_to_file?
>
>
>

There is an API hook to automatic disable DC offset correction. See:
http://files.ettus.com/uhd_docs/doxygen/html/classuhd_1_1usrp_1_1multi__usrp.html#a7beb49c1a04a81b3e7569db482453746

-josh

_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com



------------------------------

Message: 2
Date: Mon, 26 Mar 2012 16:20:30 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] disabling dc offset correction loop in FPGA
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1



On 03/26/2012 03:29 PM, Lapointe, Benjamin - 1008 - MITLL wrote:
> I tried using the API hooks recommended below, but to no avail.  In my 
> rx_samples_to_file before making the call to recv_to_file, I added the 
> following lines:
> 
> usrp->set_rx_dc_offset(false);
> std::complex<double> dc_offset(0.5, 0.5);
> usrp->set_rx_dc_offset(dc_offset);
> 
> I tried changing the dc_offset from 0.0 to 1.0, but the dc offset in my data 
> is still auto corrected.
> 
> Does anyone have any idea what I am doing wrong?
> 

After setting set_rx_dc_offset(dc_offset),
I can see a DC level in uhd_fft.py plot,
and on the I and Q channels in scope mode, uhd_fft.py -S.
This means auto removal is definitely disabled.

What model USRP are you using? I have not tested this on USRP1, but the
other models share a common FPGA codebase.

-josh



------------------------------

Message: 3
Date: Tue, 27 Mar 2012 09:35:38 +0500
From: salman dinani <[email protected]>
To: Mike McLernon <[email protected]>
Cc: "[email protected]" <[email protected]>,    usrp-users
        <[email protected]>,   "[email protected]"
        <[email protected]>
Subject: Re: [USRP-users] SBX simultaneous transmit receive problem...
Message-ID:
        <cadt0h5beetvkf3jtdorye+-zhibytru6yp4fa2nkm0a4hbk...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"

Hi Mike,

Thanks for reminding the Data Len port feature.. I forgot to connect
that..:)..Mike but my problem still remains the same.. :(.. why cant
i receive the  same signal transmited by transmit port..

Is there any limitation of hardware or software or am i doing some thing
wrong??

Regards
Salman Dinani

On Mon, Mar 26, 2012 at 6:22 PM, Mike McLernon
<[email protected]>wrote:

>  Hi Salman,****
>
> ** **
>
> Your block diagram indicates that you are not using the *Data Len* output
> port from the SDRu Receiver block.  When using the block, we strongly
> advocate that you use that port as an enable signal to control an enabled
> subsystem that holds all the downstream processing after the SDRu Receiver
> block.  See the sdruFMMono demo for an example:****
>
> ** **
>
> ****
>
> ** **
>
> Using that port will not speed up the switchover between Tx and Rx, but it
> will ensure that your captured workspace variable has only good data.****
>
> ** **
>
> See the *Using Conditional Execution in Receiver Processing* section of
> the *Getting Started with the SDRu* FAQ for more info.  You can access
> the *Getting Started* FAQ by typing ?help sdru? at the MATLAB command
> line.****
>
> ** **
>
> Hth,****
>
> Mike****
>
> ** **
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *salman dinani
> *Sent:* Monday, March 26, 2012 12:32 AM
> *To:* [email protected]; usrp-users; [email protected]; Ian Buckley
> *Subject:* Re: [USRP-users] SBX simultaneous transmit receive problem...**
> **
>
> ** **
>
> Hi all ,****
>
> ** **
>
> I want to ask is about the switching of USRP from TX to RX mode in
> MATLAB.. I transmit a signal, and then stop transmitting further,  and then
> wants to receive that transmitted signal on RX2..This cycles
> continues.. what I am observing is that USRP takes alot of time to switch
> from Transmit mode to receive mode.Because of this when USRP starts
> receiving there is no signal to receive..(since when it was transmitting,
> RX was off..According to my observation..)..Its a half duplex operation...
> ****
>
> ** **
>
>  I have attached the snap shot of my project....****
>
> ** **
>
> 1. Is it a MATLAB driver that takes alot time to B/W TX and RX or any
> hardware limitation??****
>
> ** **
>
> Regards****
>
> Salman Dinani****
>
> ** **
>
> On Fri, Mar 23, 2012 at 4:52 PM, Mike McLernon <
> [email protected]> wrote:****
>
> Hello Salman,****
>
>  ****
>
> We have not done rigorous testing on duplex operation with our SDRu blocks
> and System objects, and at this time we are not claiming support for full
> duplex operation.  I am aware of users that have gotten half duplex to
> work, but we plan to invest more in the full duplex workflow in the near
> future.****
>
>  ****
>
> Hth,****
>
> Mike****
>
>  ****
>
>  ****
>
> *From:* salman dinani [mailto:[email protected]]
> *Sent:* Friday, March 23, 2012 1:06 AM
> *To:* usrp-users; Mike McLernon; [email protected]; Ian Buckley
> *Subject:* SBX simultaneous transmit receive problem...****
>
>  ****
>
> Hi all,****
>
>  ****
>
> I am using SBX daughtercard with USRP N200 with MATLAB R2011b. SBX has two
> ports "TX/RX" and "RX"...I am transmitting one signal from port 1 and
> receiving the other signal at the very same time from port 2..I was getting
> good results and every thing seems to work perfect...But when i tried to
> receive the signal ,transmitted by SBX itself, i didn't get any thing..I
> connected both the ports with a wire and a attenuator , i didnt received
> any signal..After a very careful observation,i have observed that only one
> operation is been perform at one time..either transmit or receive..USRP
> first transmit and than switches to receive...!!This switching of operation
> take place so fast that it seems both are working simultaneously.. I dont
> why its happening because transmitter and receiver has got separate LO's
> and SBX is supported for full duplex mode.. ****
>
>  ****
>
> 1. My observation is correct??****
>
> 2. Is it hardware issue that only one operations is performed at a time?**
> **
>
> 3. Or its driver or MATLAB/Simulink interface limitation??****
>
>  ****
>
> Regards****
>
>  ****
>
> Salman Dinani****
>
> ** **
>
>  ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120327/991d1280/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 69836 bytes
Desc: not available
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120327/991d1280/attachment-0001.png>

------------------------------

Message: 4
Date: Tue, 27 Mar 2012 01:48:26 -0400
From: Rob Rhinehart <[email protected]>
To: [email protected]
Subject: [USRP-users] B100 Connection Problem
Message-ID:
        <CA+W74gY2i=lfgl0vohbhctv68itara5fc67e7c57b-zu26t...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hello, a couple days ago my B100 was working great, but upon reinstall of
ubuntu 12.04 I can't communicate with it.

$ sudo uhd_find_devices
linux; GNU C++ version 4.6.3; Boost_104601; UHD_003.004.000-6-g793c8c00

No UHD Devices Found

dmesg sees it:
[57323.509991] usb 3-1: new high-speed USB device number 5 using xhci_hcd

lsusb sees it:
Bus 002 Device 004: ID 8086:0188 Intel Corp. WiMAX Connection 2400m
Bus 003 Device 005: ID 2500:0002  <-------- this is the USRP

I've tried recompiling UHD both with script and manually on two different
computers and still can't get a response from uhd_find_devices or
uhd_usrp_probe. Am I missing something?

Thank you,
Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120327/63822d49/attachment-0001.html>

------------------------------

Message: 5
Date: Mon, 26 Mar 2012 23:05:35 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] B100 Connection Problem
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1



On 03/26/2012 10:48 PM, Rob Rhinehart wrote:
> Hello, a couple days ago my B100 was working great, but upon reinstall of
> ubuntu 12.04 I can't communicate with it.
> 
> $ sudo uhd_find_devices
> linux; GNU C++ version 4.6.3; Boost_104601; UHD_003.004.000-6-g793c8c00
> 
> No UHD Devices Found
> 
> dmesg sees it:
> [57323.509991] usb 3-1: new high-speed USB device number 5 using xhci_hcd
> 
> lsusb sees it:
> Bus 002 Device 004: ID 8086:0188 Intel Corp. WiMAX Connection 2400m
> Bus 003 Device 005: ID 2500:0002  <-------- this is the USRP
> 
> I've tried recompiling UHD both with script and manually on two different
> computers and still can't get a response from uhd_find_devices or
> uhd_usrp_probe. Am I missing something?
> 

Did you build UHD with B100 support? In other words, was libusb1.0-dev
installed when you compiled uhd?

Are you able to run sudo uhd_usrp_probe? If so, maybe you didnt setup
udev:
http://files.ettus.com/uhd_docs/manual/html/transport.html#setup-udev-for-usb-linux

-josh



------------------------------

Message: 6
Date: Tue, 27 Mar 2012 02:55:51 -0400
From: Rob Rhinehart <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [USRP-users] B100 Connection Problem
Message-ID:
        <ca+w74gysuyulubzac+qrvrnup8s0_hhguy0e0oda4zxcpxa...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

On Tue, Mar 27, 2012 at 2:05 AM, Josh Blum <[email protected]> wrote:
>
>
> On 03/26/2012 10:48 PM, Rob Rhinehart wrote:
> > Hello, a couple days ago my B100 was working great, but upon reinstall of
> > ubuntu 12.04 I can't communicate with it.
> >
> > $ sudo uhd_find_devices
> > linux; GNU C++ version 4.6.3; Boost_104601; UHD_003.004.000-6-g793c8c00
> >
> > No UHD Devices Found
> >
> > dmesg sees it:
> > [57323.509991] usb 3-1: new high-speed USB device number 5 using xhci_hcd
> >
> > lsusb sees it:
> > Bus 002 Device 004: ID 8086:0188 Intel Corp. WiMAX Connection 2400m
> > Bus 003 Device 005: ID 2500:0002  <-------- this is the USRP
> >
> > I've tried recompiling UHD both with script and manually on two different
> > computers and still can't get a response from uhd_find_devices or
> > uhd_usrp_probe. Am I missing something?
> >
>
> Did you build UHD with B100 support? In other words, was libusb1.0-dev
> installed when you compiled uhd?
>
> Are you able to run sudo uhd_usrp_probe? If so, maybe you didnt setup
> udev:
>
> http://files.ettus.com/uhd_docs/manual/html/transport.html#setup-udev-for-usb-linux
>
> -josh
>

_______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>

Yes I ran probe but nothing found. I setup udev correctly I believe, forgot
to metion:

$ cat /etc/udev/rules.d/uhd-usrp.rules
ACTION=="add", BUS=="usb", SYSFS{idVendor}=="fffe",
SYSFS{idProduct}=="0002",
MODE:="0666"
ACTION=="add", BUS=="usb", SYSFS{idVendor}=="2500",
SYSFS{idProduct}=="0002",
MODE:="0666"

libusb1.0-dev was installed when I compiled. Just tried it again. No luck.

$ sudo uhd_usrp_probe
linux; GNU C++ version 4.6.3; Boost_104601; UHD_003.004.000-6-g793c8c00

Error: LookupError: KeyError: No devices found for ----->
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120327/a0d19ad6/attachment-0001.html>

------------------------------

Message: 7
Date: Tue, 27 Mar 2012 09:23:01 +0200
From: Stefano Speretta <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] Calibration on USRP1
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Dear all,

I use a USRP1+WBX to perform spectrum analysis and I always see a spike 
in DC in the FFT. I tried playing with the DC offset correction
but the spike is always there. I also used an offset in the LO and the 
spike is smaller but always there. I've seen somebody reporting that
the calibration helps reducing this problem so I would like to try it in 
my USRP1.

What part of the calibration script is actually not supported by the 
USRP1? What may I require to write in order to do the calibration on a 
USRP1?

Cheers,
Stefano



------------------------------

Message: 8
Date: Tue, 27 Mar 2012 08:17:45 -0400
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] SBX simultaneous transmit receive problem...
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"

On 03/27/2012 12:35 AM, salman dinani wrote:
> Hi Mike,
>
> Thanks for reminding the Data Len port feature.. I forgot to connect 
> that..:)..Mike but my problem still remains the same.. :(.. why cant 
> i receive the  same signal transmited by transmit port..
>
> Is there any limitation of hardware or software or am i doing some 
> thing wrong??
>
> Regards
> Salman Dinani
>
Do you literally mean the same signal transmitted by your transmit 
port?  Or the *response* to that transmission?  Since as Mike has already
   stated, only half-duplex is supported in MatLab, it would be a 
violation of causality to be able to receive the signal you just 
transmitted.

> On Mon, Mar 26, 2012 at 6:22 PM, Mike McLernon 
> <[email protected] <mailto:[email protected]>> wrote:
>
>     Hi Salman,
>
>     Your block diagram indicates that you are not using the /Data Len/
>     output port from the SDRu Receiver block.  When using the block,
>     we strongly advocate that you use that port as an enable signal to
>     control an enabled subsystem that holds all the downstream
>     processing after the SDRu Receiver block.  See the sdruFMMono demo
>     for an example:
>
>     Using that port will not speed up the switchover between Tx and
>     Rx, but it will ensure that your captured workspace variable has
>     only good data.
>
>     See the /Using Conditional Execution in Receiver Processing/
>     section of the /Getting Started with the SDRu/ FAQ for more info. 
>     You can access the /Getting Started/ FAQ by typing ?help sdru? at
>     the MATLAB command line.
>
>     Hth,
>
>     Mike
>
>     *From:*[email protected]
>     <mailto:[email protected]>
>     [mailto:[email protected]
>     <mailto:[email protected]>] *On Behalf Of *salman
>     dinani
>     *Sent:* Monday, March 26, 2012 12:32 AM
>     *To:* [email protected] <mailto:[email protected]>; usrp-users;
>     [email protected] <mailto:[email protected]>; Ian Buckley
>     *Subject:* Re: [USRP-users] SBX simultaneous transmit receive
>     problem...
>
>         Hi all ,
>
>         I want to ask is about the switching of USRP from TX to RX
>         mode in MATLAB.. I transmit a signal, and then stop
>         transmitting further,  and then wants to receive that
>         transmitted signal on RX2..This cycles continues.. what I am
>         observing is that USRP takes alot of time to switch from
>         Transmit mode to receive mode.Because of this when USRP starts
>         receiving there is no signal to receive..(since when it was
>         transmitting, RX was off..According to my observation..)..Its
>         a half duplex operation...
>
>          I have attached the snap shot of my project....
>
>         1. Is it a MATLAB driver that takes alot time to B/W TX and RX
>         or any hardware limitation??
>
>         Regards
>
>         Salman Dinani
>
>         On Fri, Mar 23, 2012 at 4:52 PM, Mike McLernon
>         <[email protected]
>         <mailto:[email protected]>> wrote:
>
>         Hello Salman,
>
>         We have not done rigorous testing on duplex operation with our
>         SDRu blocks and System objects, and at this time we are not
>         claiming support for full duplex operation.  I am aware of
>         users that have gotten half duplex to work, but we plan to
>         invest more in the full duplex workflow in the near future.
>
>         Hth,
>
>         Mike
>
>         *From:*salman dinani [mailto:[email protected]
>         <mailto:[email protected]>]
>         *Sent:* Friday, March 23, 2012 1:06 AM
>         *To:* usrp-users; Mike McLernon; [email protected]
>         <mailto:[email protected]>; Ian Buckley
>         *Subject:* SBX simultaneous transmit receive problem...
>
>         Hi all,
>
>         I am using SBX daughtercard with USRP N200 with MATLAB R2011b.
>         SBX has two ports "TX/RX" and "RX"...I am transmitting one
>         signal from port 1 and receiving the other signal at the very
>         same time from port 2..I was getting good results and every
>         thing seems to work perfect...But when i tried to receive the
>         signal ,transmitted by SBX itself, i didn't get any thing..I
>         connected both the ports with a wire and a attenuator , i
>         didnt received any signal..After a very careful observation,i
>         have observed that only one operation is been perform at one
>         time..either transmit or receive..USRP first transmit and than
>         switches to receive...!!This switching of operation take place
>         so fast that it seems both are working simultaneously.. I dont
>         why its happening because transmitter and receiver has got
>         separate LO's and SBX is supported for full duplex mode..
>
>         1. My observation is correct??
>
>         2. Is it hardware issue that only one operations is performed
>         at a time?
>
>         3. Or its driver or MATLAB/Simulink interface limitation??
>
>         Regards
>
>         Salman Dinani
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com


-- 
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120327/37a771d6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 69836 bytes
Desc: not available
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120327/37a771d6/attachment-0001.png>

------------------------------

Message: 9
Date: Tue, 27 Mar 2012 08:19:15 -0400
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Calibration on USRP1
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 03/27/2012 03:23 AM, Stefano Speretta wrote:
> Dear all,
>
> I use a USRP1+WBX to perform spectrum analysis and I always see a 
> spike in DC in the FFT. I tried playing with the DC offset correction
> but the spike is always there. I also used an offset in the LO and the 
> spike is smaller but always there. I've seen somebody reporting that
> the calibration helps reducing this problem so I would like to try it 
> in my USRP1.
>
> What part of the calibration script is actually not supported by the 
> USRP1? What may I require to write in order to do the calibration on a 
> USRP1?
>
> Cheers,
> Stefano
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
Calibration support requires support in the FPGA.  The USRP1 FPGA 
functionality has been frozen for several years.



-- 
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org





------------------------------

_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com


End of USRP-users Digest, Vol 19, Issue 27
******************************************

Reply via email to