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: connect USRPE1XX to the internet (Abouda Yassine)
2. Re: connect USRPE1XX to the internet (Marcus D. Leech)
3. Re: 2xTX and 2xRX with LFRX and LFTX (Jeff Scaparra)
4. Newbie with pre-purchase questions... (Benito Horta)
5. USRP N210 25 MHz Harmonics (Knee, Peter A)
6. Re: USRP N210 25 MHz Harmonics (Marcus D. Leech)
7. Re: [EXTERNAL] Re: USRP N210 25 MHz Harmonics (Knee, Peter A)
8. Re: [EXTERNAL] Re: USRP N210 25 MHz Harmonics (Marcus D. Leech)
9. Re: USRP-users Digest, Vol 44, Issue 1 (Syed Aqeel Raza)
10. Re: How to stop "usrp_spectrum_sense.py"? (Syed Aqeel Raza)
11. Re: Newbie with pre-purchase questions... (Robert J. McIntyre)
12. Re: How to stop "usrp_spectrum_sense.py"? (Martin Braun)
13. Re: Full bandwidth streaming from X300 to disk (Perper)
14. Re: Full bandwidth streaming from X300 to disk (Marcus D. Leech)
15. B200 quadrature imbalance issue (King Chan)
----------------------------------------------------------------------
Message: 1
Date: Thu, 3 Apr 2014 18:54:00 +0200
From: Abouda Yassine <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] connect USRPE1XX to the internet
Message-ID:
<CAHkxc+m368vq_+SYB82v905mSL4=nzrdv+nj-xhnkz4jm0g...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello again,
I managed to connect the usrpe1xx to the internet when I restarted the
device sorry to bother.On the other hand I must update the embedded
GNURadio,lots of blocs are missing.How can I do that??
2014-04-03 17:13 GMT+02:00 Abouda Yassine <[email protected]>:
> Hello,
>
> I have one simple question,how can I connect the usrpe1xx to the Internet
> using Ethernet?
> thx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140403/501a993b/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 03 Apr 2014 12:59:58 -0400
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] connect USRPE1XX to the internet
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
> Hello again,
>
> I managed to connect the usrpe1xx to the internet when I restarted the
> device sorry to bother.On the other hand I must update the embedded
> GNURadio,lots of blocs are missing.How can I do that??
>
>
> 2014-04-03 17:13 GMT+02:00 Abouda Yassine <[email protected]
> <mailto:[email protected]>>:
>
> Hello,
>
> I have one simple question,how can I connect the usrpe1xx to the
> Internet using Ethernet?
> thx
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
okpg update; opkg upgrade
--
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/20140403/68723814/attachment-0001.html>
------------------------------
Message: 3
Date: Thu, 3 Apr 2014 13:10:24 -0400
From: Jeff Scaparra <[email protected]>
To: Matt Ettus <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] 2xTX and 2xRX with LFRX and LFTX
Message-ID:
<calwgea3yr+mcrc4ffmdx+-c_gm7u7syoapqh3b4jox+3rd7...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I tried to find a working example of using multiple channels with a single
LFTX LFRX BasicTX BasicRX or a TVRX2 and couldn't find anything. If anyone
had a grc file they could send me to help me understand what exactly I am
missing I would greatly appreciate it.
Thanks,
Jeff
On Thu, Apr 3, 2014 at 3:04 AM, Jeff Scaparra <[email protected]> wrote:
> My FFT on the RX chains started to bounce when I added the second RX. I
> can make a video if that isn't descriptive enough.
>
>
> On Wed, Apr 2, 2014 at 11:58 PM, Matt Ettus <[email protected]> wrote:
>
>>
>> You can still generate two independent signals on the TX outputs with
>> LFTX. Just generate them as real signals in the host (not I and Q), and
>> put the first on I and the second on Q. As long as you set the "center"
>> frequency to zero, this will work.
>>
>> I don't understand what you mean by poor results with the two RX chains.
>> I will take a look at your grc file.
>>
>> Matt
>>
>>
>> On Wed, Apr 2, 2014 at 8:42 PM, Jeff Scaparra <[email protected]> wrote:
>>
>>> well then Ian that is a problem. With dual DACs I thought there would be
>>> two TX chains. This is apparently not the case and I am wondering if two TX
>>> chains would fit in the FPGA image. I do need RX more than TX but having
>>> the TX chains would be nice for simulations and testing.
>>>
>>> Either way I don't understand the really poor results when using 2 RX
>>> chains and 1 TX.
>>>
>>> Jeff
>>>
>>>
>>> On Wed, Apr 2, 2014 at 9:08 PM, Ian Buckley <[email protected]>wrote:
>>>
>>>> Am I missing something? Is this a custom FPGA image? There is only 1 TX
>>>> chain in N210 (and 2 RX chains).
>>>>
>>>>
>>>> On Apr 2, 2014, at 5:04 PM, Jeff Scaparra <[email protected]> wrote:
>>>>
>>>> > I can't seem to get 2xTX and 2xRX to work on a USRP N210 with teh
>>>> LFRX and LFTX boards. I did get 1xTX and 2xRX to work but the 1 RX chains
>>>> were not clean and the FFT had lots of noise. I have attached the GRC file
>>>> that I have been working with. I get either a Floating point exception or
>>>> the python generated code just exits. I am running the latest git code on
>>>> ARCH. for the 1XTX and 2XRX I disable one of the TX chains in the grc file.
>>>> Any advice would be appreciated.
>>>> >
>>>> > I have the TX port connected to an attenuator and then to the RX
>>>> ports. A:A TX goes to A:A RX and A:B TX goes to A:B RX.
>>>> >
>>>> > Jeff
>>>> > <usrp signal.grc>_______________________________________________
>>>> > USRP-users mailing list
>>>> > [email protected]
>>>> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>>
>>>>
>>>
>>> _______________________________________________
>>> USRP-users mailing list
>>> [email protected]
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140403/0224a3ff/attachment-0001.html>
------------------------------
Message: 4
Date: Thu, 3 Apr 2014 14:36:14 -0400
From: Benito Horta <[email protected]>
To: [email protected]
Subject: [USRP-users] Newbie with pre-purchase questions...
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Also with SDR console you can have upto 6VFOs running simultaneously within the
Carved out spectrum. In windows I have been able to use the B200 with SDR# and
the SDR Radio V 2.2 software. Linux is better if you want to do much more
advanced things via Gnu radio etc..
With SDR# you need to load an older FPGA image to use it, it ships with the
EXTIO packaged at wiki.spench.net
this is available at http://wiki.spench.net/wiki/USRP_Interfaces
you can do that with b2xx_fx3_utils -I path to fpga.bin file in the directory
where you installed the files from the website
then b2xx_fx3_utils - W path to fpga.bin file in the directory where you
installed the files from the website
SDR console will work with the current FPGA bin.
both have pros and cons.
SDR# seems better suited for analyzing
SDR console seems better as a radio i.e. with the Multi VFOs and the
filters/demodulators seem to be better that the SDR#
I have the B200 it has two RX inputs which is nice, means I can have a general
omnidirectional for locating RF activity in the vicinity, then a directional
Yagi for source point location. You can switch between the two.
Now this stuff is CPU heavy. I have a dedicated workstation for this, 3770K
cpu, 8GB low latency memory and SSD's. and The cpu is averaging 40% utilization
with a 32RBW watching a 26Mhz section of bandwidth.
Anyhow this kind of capability would cost megabucks, and you would be paying
top dollar for gear from companies like Rhode & Schwarz. SDR is definitely the
wave of the future, this is the equivalent of experimenting with radio/deforest
tubes in the 1920s :)
------------------------------
Message: 5
Date: Thu, 3 Apr 2014 21:13:38 +0000
From: "Knee, Peter A" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] USRP N210 25 MHz Harmonics
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
All,
I just noticed that we have some fairly strong (up to ~25 dB above noise)
signals on data we receive using our N210. We've terminated the inputs and are
looking at the spectrum and see what look to be harmonics of a 25 MHz signal.
We opened up the box and noticed that there is a 25 MHz oscillator on the main
board. What is this used for?
I don't' recall seeing this with version 3.6 of the UHD but I've recently
upgraded to 3.7 and noticed this behavior.
Has anyone seen anything similar?
Thanks,
Peter Knee
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140403/27c4c6f6/attachment-0001.html>
------------------------------
Message: 6
Date: Thu, 03 Apr 2014 17:43:33 -0400
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] USRP N210 25 MHz Harmonics
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
> All,
>
> I just noticed that we have some fairly strong (up to ~25 dB above
> noise) signals on data we receive using our N210. We've terminated
> the inputs and are looking at the spectrum and see what look to be
> harmonics of a 25 MHz signal. We opened up the box and noticed that
> there is a 25 MHz oscillator on the main board. What is this used for?
>
> I don't' recall seeing this with version 3.6 of the UHD but I've
> recently upgraded to 3.7 and noticed this behavior.
>
> Has anyone seen anything similar?
>
> Thanks,
>
> Peter Knee
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
25MHz is the bog-standard clock frequency for Ethernet PHYs of all kinds.
--
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/20140403/b6847bb4/attachment-0001.html>
------------------------------
Message: 7
Date: Thu, 3 Apr 2014 21:47:14 +0000
From: "Knee, Peter A" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] [EXTERNAL] Re: USRP N210 25 MHz Harmonics
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Great thanks Marcus. After some gentle touching of the board, it does look
like we're seeing either the 100 MHz or the 25 MHz harmonics or both. I did
come across a previous discussion about shield cans and the like to help
improve some of this but at this point, if we just know what they are, and
where they're going to be, that should be sufficient.
-Peter Knee
From: USRP-users [mailto:[email protected]] On Behalf Of
Marcus D. Leech
Sent: Thursday, April 03, 2014 3:44 PM
To: [email protected]
Subject: [EXTERNAL] Re: [USRP-users] USRP N210 25 MHz Harmonics
All,
I just noticed that we have some fairly strong (up to ~25 dB above noise)
signals on data we receive using our N210. We've terminated the inputs and are
looking at the spectrum and see what look to be harmonics of a 25 MHz signal.
We opened up the box and noticed that there is a 25 MHz oscillator on the main
board. What is this used for?
I don't' recall seeing this with version 3.6 of the UHD but I've recently
upgraded to 3.7 and noticed this behavior.
Has anyone seen anything similar?
Thanks,
Peter Knee
_______________________________________________
USRP-users mailing list
[email protected]<mailto:[email protected]>
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
25MHz is the bog-standard clock frequency for Ethernet PHYs of all kinds.
--
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/20140403/1ce28903/attachment-0001.html>
------------------------------
Message: 8
Date: Thu, 03 Apr 2014 17:51:40 -0400
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] [EXTERNAL] Re: USRP N210 25 MHz Harmonics
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
> Great thanks Marcus. After some gentle touching of the board, it does
> look like we're seeing either the 100 MHz or the 25 MHz harmonics or
> both. I did come across a previous discussion about shield cans and
> the like to help improve some of this but at this point, if we just
> know what they are, and where they're going to be, that should be
> sufficient.
>
> -Peter Knee
>
>
Any mixed-signal radio (with both analog and digital in the same
enclosure) is going to experience some discrete spurs. It's unavoidable.
Modern front-ends can "see" down to incredibly low power levels, and
unless you go for very-expensive physical layout (multiple
physical subsystems in their own sub-enclosures), you'll see these spurs.
--
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/20140403/df2ab2c1/attachment-0001.html>
------------------------------
Message: 9
Date: Fri, 4 Apr 2014 09:53:31 +0800
From: Syed Aqeel Raza <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] USRP-users Digest, Vol 44, Issue 1
Message-ID:
<caga9icazv6+fjpvnvq+ejfpejw25yqvip9cysuesqphyb+o...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Martin,
Thanks for your email. Basically I want to program the usrp N200 in a way
that it should switch in between of relay mode and scanning mode with
respect to time. For that purpose, following are the tasks:
1. Integrate the two programs (i.e. tx_rx.py (relay mode) and
usrp_spectrum_sense.py) as an object into a new program.
2. Define the time frame for switching between the two objects program. For
example, in a minute 50 seconds are reserved for relaying mode while the
remaining 10 seconds for sensing mode.
These are the two most important tasks out of many others. Right now, I am
able to switch from relay mode to sensing mode but once the program start
with the sensing mode then it won't be returned to relay mode.
Yes, the delete_head() call block is remain a mystery for me yet. I am
trying to resolve the issue but if anyone has any suggestions then let me
know. Waiting for positive response.
Regards,
Syed Aqeel Raza
----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 31 Mar 2014 18:03:38 +0200
> From: Martin Braun <[email protected]>
> To: [email protected]
> Subject: Re: [USRP-users] How to stop "usrp_spectrum_sense.py"?
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Syed,
>
> It looks like you're not shutting down the receiver thread correctly.
> Also, remember the the delete_head() call blocks.
>
> What are you trying to achieve? Do you want to switch off the rx
> completely? Maybe for half duplex?
>
> If not, I suggest you continue emptying the rx queue, and simply discard
> the information.
>
> Martin
>
> On 03/30/2014 10:25 AM, Syed Aqeel Raza wrote:
> > Hi Everyone,
> >
> > The "usrp_spectrum_sense.py" program is used to sense the defined
> > spectrum range. Now, I want to stop it for a period of five second time
> > (e.g. from 55 to 59 seconds). For that purpose, I wrote the following
> > lines in python.
> >
> > ================================================
> > import usrp_spectrum_sense_updated
> >
> > import time
> >
> >
> >
> > class main_class():
> >
> >
> > # calling the 'usrp_spectrum_sense.py' program
> >
> >
> > def relay_func(self, tb):
> >
> > while 1:
> >
> >
> > curr_time = time.strftime('%S',time.localtime())
> >
> >
> > if int(curr_time)>=55:
> >
> > print 'Hello World"
> >
> > else:
> >
> > t = usrp_spectrum_sense_updated.ThreadClass()
> >
> > t.start()
> >
> >
> > tb = usrp_spectrum_sense_updated.my_top_block()
> >
> > try:
> >
> > tb.start()
> >
> > usrp_spectrum_sense_updated.main_loop(tb)
> >
> >
> > except KeyboardInterrupt:
> >
> > pass
> >
> > if __name__ == '__main__':
> >
> > tb = main_class()
> >
> > tb.relay_func(tb)
> >
> > ================================================
> >
> >
> > In the above program, I tried to stop sensing for the duration of 5
> > seconds (i.e. 55 ---- 59 seconds). The program works fine whenever I
> > execute it in between of the mentioned time and it shift automatically
> > to the sensing mode at time=0 second; but once it start sensing then it
> > never be returned to the print message 'hello world' even when the
> > condition is matched.
> >
> > Earliest and kind response is highly appreciated. Thanks.
> >
> > Regards,
> > Syed Aqeel Raza
> >
> >
> > _______________________________________________
> > USRP-users mailing list
> > [email protected]
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140404/44c104b3/attachment-0001.html>
------------------------------
Message: 10
Date: Fri, 4 Apr 2014 10:33:29 +0800
From: Syed Aqeel Raza <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] How to stop "usrp_spectrum_sense.py"?
Message-ID:
<caga9icbe3akbprvuba0s-zep_-zw-jmrxrofxfmorayaeny...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Martin,
Thanks for your email. Basically I want to program the usrp N200 in a way
that it should switch in between of relay mode and scanning mode with
respect to time. For that purpose, following are the tasks:
1. Integrate the two programs (i.e. tx_rx.py (relay mode) and
usrp_spectrum_sense.py) as an object into a new program.
2. Define the time frame for switching between the two objects program. For
example, in a minute 50 seconds are reserved for relaying mode while the
remaining 10 seconds for sensing mode.
These are the two most important tasks out of many others. Right now, I am
able to switch from relay mode to sensing mode but once the program start
with the sensing mode then it won't be returned to relay mode.
Yes, the delete_head() call block is remain a mystery for me yet. I am
trying to resolve the issue but if anyone has any suggestions then let me
know. Waiting for positive response.
Regards,
Syed Aqeel Raza
----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 31 Mar 2014 18:03:38 +0200
> From: Martin Braun <[email protected]>
> To: [email protected]
> Subject: Re: [USRP-users] How to stop "usrp_spectrum_sense.py"?
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Syed,
>
> It looks like you're not shutting down the receiver thread correctly.
> Also, remember the the delete_head() call blocks.
>
> What are you trying to achieve? Do you want to switch off the rx
> completely? Maybe for half duplex?
>
> If not, I suggest you continue emptying the rx queue, and simply discard
> the information.
>
> Martin
>
> On 03/30/2014 10:25 AM, Syed Aqeel Raza wrote:
> > Hi Everyone,
> >
> > The "usrp_spectrum_sense.py" program is used to sense the defined
> > spectrum range. Now, I want to stop it for a period of five second time
> > (e.g. from 55 to 59 seconds). For that purpose, I wrote the following
> > lines in python.
> >
> > ================================================
> > import usrp_spectrum_sense_updated
> >
> > import time
> >
> >
> >
> > class main_class():
> >
> >
> > # calling the 'usrp_spectrum_sense.py' program
> >
> >
> > def relay_func(self, tb):
> >
> > while 1:
> >
> >
> > curr_time = time.strftime('%S',time.localtime())
> >
> >
> > if int(curr_time)>=55:
> >
> > print 'Hello World"
> >
> > else:
> >
> > t = usrp_spectrum_sense_updated.ThreadClass()
> >
> > t.start()
> >
> >
> > tb = usrp_spectrum_sense_updated.my_top_block()
> >
> > try:
> >
> > tb.start()
> >
> > usrp_spectrum_sense_updated.main_loop(tb)
> >
> >
> > except KeyboardInterrupt:
> >
> > pass
> >
> > if __name__ == '__main__':
> >
> > tb = main_class()
> >
> > tb.relay_func(tb)
> >
> > ================================================
> >
> >
> > In the above program, I tried to stop sensing for the duration of 5
> > seconds (i.e. 55 ---- 59 seconds). The program works fine whenever I
> > execute it in between of the mentioned time and it shift automatically
> > to the sensing mode at time=0 second; but once it start sensing then it
> > never be returned to the print message 'hello world' even when the
> > condition is matched.
> >
> > Earliest and kind response is highly appreciated. Thanks.
> >
> > Regards,
> > Syed Aqeel Raza
> >
> >
> > _______________________________________________
> > USRP-users mailing list
> > [email protected]
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140404/b4569b52/attachment-0001.html>
------------------------------
Message: 11
Date: Thu, 3 Apr 2014 19:51:25 -0700
From: "Robert J. McIntyre" <[email protected]>
To: "'Benito Horta'" <[email protected]>, <[email protected]>
Subject: Re: [USRP-users] Newbie with pre-purchase questions...
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Thanks, everyone! I'll be placing an order shortly...
Cheers!
Robert
-----Original Message-----
From: USRP-users [mailto:[email protected]] On Behalf Of
Benito Horta
Sent: Thursday, April 03, 2014 11:36 AM
To: [email protected]
Subject: [USRP-users] Newbie with pre-purchase questions...
Also with SDR console you can have upto 6VFOs running simultaneously within
the Carved out spectrum. In windows I have been able to use the B200 with
SDR# and the SDR Radio V 2.2 software. Linux is better if you want to do
much more advanced things via Gnu radio etc..
With SDR# you need to load an older FPGA image to use it, it ships with the
EXTIO packaged at wiki.spench.net
this is available at http://wiki.spench.net/wiki/USRP_Interfaces
you can do that with b2xx_fx3_utils -I path to fpga.bin file in the
directory where you installed the files from the website then b2xx_fx3_utils
- W path to fpga.bin file in the directory where you installed the files
from the website
SDR console will work with the current FPGA bin.
both have pros and cons.
SDR# seems better suited for analyzing
SDR console seems better as a radio i.e. with the Multi VFOs and the
filters/demodulators seem to be better that the SDR#
I have the B200 it has two RX inputs which is nice, means I can have a
general omnidirectional for locating RF activity in the vicinity, then a
directional Yagi for source point location. You can switch between the two.
Now this stuff is CPU heavy. I have a dedicated workstation for this, 3770K
cpu, 8GB low latency memory and SSD's. and The cpu is averaging 40%
utilization with a 32RBW watching a 26Mhz section of bandwidth.
Anyhow this kind of capability would cost megabucks, and you would be paying
top dollar for gear from companies like Rhode & Schwarz. SDR is definitely
the wave of the future, this is the equivalent of experimenting with
radio/deforest tubes in the 1920s :)
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 12
Date: Fri, 04 Apr 2014 09:30:34 +0200
From: Martin Braun <[email protected]>
To: [email protected], "[email protected]"
<[email protected]>
Subject: Re: [USRP-users] How to stop "usrp_spectrum_sense.py"?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 04/04/2014 04:33 AM, Syed Aqeel Raza wrote:
> Hi Martin,
>
> Thanks for your email. Basically I want to program the usrp N200 in a
> way that it should switch in between of relay mode and scanning mode
> with respect to time. For that purpose, following are the tasks:
>
> 1. Integrate the two programs (i.e. tx_rx.py (relay mode) and
> usrp_spectrum_sense.py) as an object into a new program.
>
> 2. Define the time frame for switching between the two objects program.
> For example, in a minute 50 seconds are reserved for relaying mode while
> the remaining 10 seconds for sensing mode.
>
> These are the two most important tasks out of many others. Right now, I
> am able to switch from relay mode to sensing mode but once the program
> start with the sensing mode then it won't be returned to relay mode.
You might want to write a block that outputs data on two different
paths, instead of reconnecting blocks or using message queues.
> Yes, the delete_head() call block is remain a mystery for me yet. I am
> trying to resolve the issue but if anyone has any suggestions then let
> me know. Waiting for positive response.
I recommend not to use it at all (see comment above).
Also, you might get more results for these GNU Radio-specific questions
on the GNU Radio mailing list.
Cheers,
Martin
>
> Regards,
> Syed Aqeel Raza
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 31 Mar 2014 18:03:38 +0200
> From: Martin Braun <[email protected]
> <mailto:[email protected]>>
> To: [email protected] <mailto:[email protected]>
> Subject: Re: [USRP-users] How to stop "usrp_spectrum_sense.py"?
> Message-ID: <[email protected]
> <mailto:[email protected]>>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Syed,
>
> It looks like you're not shutting down the receiver thread correctly.
> Also, remember the the delete_head() call blocks.
>
> What are you trying to achieve? Do you want to switch off the rx
> completely? Maybe for half duplex?
>
> If not, I suggest you continue emptying the rx queue, and simply discard
> the information.
>
> Martin
>
> On 03/30/2014 10:25 AM, Syed Aqeel Raza wrote:
> > Hi Everyone,
> >
> > The "usrp_spectrum_sense.py" program is used to sense the defined
> > spectrum range. Now, I want to stop it for a period of five second
> time
> > (e.g. from 55 to 59 seconds). For that purpose, I wrote the following
> > lines in python.
> >
> > ================================================
> > import usrp_spectrum_sense_updated
> >
> > import time
> >
> >
> >
> > class main_class():
> >
> >
> > # calling the 'usrp_spectrum_sense.py' program
> >
> >
> > def relay_func(self, tb):
> >
> > while 1:
> >
> >
> > curr_time = time.strftime('%S',time.localtime())
> >
> >
> > if int(curr_time)>=55:
> >
> > print 'Hello World"
> >
> > else:
> >
> > t = usrp_spectrum_sense_updated.ThreadClass()
> >
> > t.start()
> >
> >
> > tb = usrp_spectrum_sense_updated.my_top_block()
> >
> > try:
> >
> > tb.start()
> >
> > usrp_spectrum_sense_updated.main_loop(tb)
> >
> >
> > except KeyboardInterrupt:
> >
> > pass
> >
> > if __name__ == '__main__':
> >
> > tb = main_class()
> >
> > tb.relay_func(tb)
> >
> > ================================================
> >
> >
> > In the above program, I tried to stop sensing for the duration of 5
> > seconds (i.e. 55 ---- 59 seconds). The program works fine whenever I
> > execute it in between of the mentioned time and it shift automatically
> > to the sensing mode at time=0 second; but once it start sensing
> then it
> > never be returned to the print message 'hello world' even when the
> > condition is matched.
> >
> > Earliest and kind response is highly appreciated. Thanks.
> >
> > Regards,
> > Syed Aqeel Raza
> >
> >
> > _______________________________________________
> > USRP-users mailing list
> > [email protected] <mailto:[email protected]>
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 13
Date: Fri, 04 Apr 2014 13:26:42 +0200
From: Perper <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Full bandwidth streaming from X300 to disk
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
W dniu 27.03.2014 20:26, Marcus D. Leech pisze:
>> My question was not about downsampling/ddc. I understand how that works.
>> My question was about going from 200 MHz down to 150 MHz, which would
>> presumably require an actual change to the A/D clock.
> Ah. Presumably because you're only *really* interested in 75Msps
sample-rate--100Msps too much, 50Msps too little?
>
> It has configurable clocking, so, yeah, you could likely change it to
150MHz master-clock rate if you
> wanted.
>
>
Hi Marcus,
What do you mean by saying there is "configurable clocking" in USRP
X300? You mean that you can change clock that enters ADC?
The datasheet of X300 says something about "Flexible clocking
architecture" but I couldn't find info what exactly is meant by this
statement.
--
Best Regards,
Piotr Krysik
>> John
>>
>>> -----Original Message-----
>>> From: USRP-users [mailto:[email protected]] On
Behalf Of
>>> Marcus M?ller
>>> Sent: Thursday, March 27, 2014 3:16 PM
>>> To: [email protected]
>>> Subject: Re: [USRP-users] Full bandwidth streaming from X300 to disk
>>>
> Yes, the USRP architecture allows you to downsample the ADC to the desired
> sampling rate, doing all the necessary filtering in-FPGA.
> So you specify 10Msps, you get an alias-free 10Msps :)
>
> Greetings,
> Marcus
>
> On 27.03.2014 20:13, Mann, John P. - 1003 - MITLL wrote:
> >>>> Marcus D. Leech <[email protected]> wrote:
> >>>>>> The analog daughtercards for X3xx series have 120Mhz of
> >>>>>> *complex* analog
> >>>> bandwidth,
> >>>>>> which is sampled by a 200Msps complex (I and Q) ADC. No violation
> >>>>>> of
> >>>> Nyquist involved at all.
> >>>>
> >>>> I was not aware that the 200 MHz ADC spec was already a quadrature
> >>>> rate. Thank you for clearing that up! So there is actually a ton of
> >>>> extra headroom to handle 120 MHz bandwidth coming out of the daughter
> >>>> boards... Can I easily lower the sample rate down to something like
> >>>> 150 MHz to save disk space?
> >>>>
> >>>> John Mann
> >>>>
> >>>>
> >>>>
------------------------------
Message: 14
Date: Fri, 04 Apr 2014 09:17:06 -0400
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Full bandwidth streaming from X300 to disk
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 04/04/2014 07:26 AM, Perper wrote:
> Hi Marcus,
>
> What do you mean by saying there is "configurable clocking" in USRP
> X300? You mean that you can change clock that enters ADC?
> The datasheet of X300 says something about "Flexible clocking
> architecture" but I couldn't find info what exactly is meant by this
> statement.
>
> --
> Best Regards,
> Piotr Krysik
>
As far as I know, you can just specify "master_clock_rate=" in the
deviice args, like other flexible-clocking USRPs such as B200, and B100.
>>> John
>>>
>>>> -----Original Message-----
>>>> From: USRP-users [mailto:[email protected]] On
> Behalf Of
>>>> Marcus M?ller
>>>> Sent: Thursday, March 27, 2014 3:16 PM
>>>> To: [email protected]
>>>> Subject: Re: [USRP-users] Full bandwidth streaming from X300 to disk
>>>>
>> Yes, the USRP architecture allows you to downsample the ADC to the desired
>> sampling rate, doing all the necessary filtering in-FPGA.
>> So you specify 10Msps, you get an alias-free 10Msps :)
>>
>> Greetings,
>> Marcus
>>
>> On 27.03.2014 20:13, Mann, John P. - 1003 - MITLL wrote:
>>>>>> Marcus D. Leech <[email protected]> wrote:
>>>>>>>> The analog daughtercards for X3xx series have 120Mhz of
>>>>>>>> *complex* analog
>>>>>> bandwidth,
>>>>>>>> which is sampled by a 200Msps complex (I and Q) ADC. No violation
>>>>>>>> of
>>>>>> Nyquist involved at all.
>>>>>>
>>>>>> I was not aware that the 200 MHz ADC spec was already a quadrature
>>>>>> rate. Thank you for clearing that up! So there is actually a ton of
>>>>>> extra headroom to handle 120 MHz bandwidth coming out of the daughter
>>>>>> boards... Can I easily lower the sample rate down to something like
>>>>>> 150 MHz to save disk space?
>>>>>>
>>>>>> John Mann
>>>>>>
>>>>>>
>>>>>>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 15
Date: Fri, 4 Apr 2014 11:24:02 -0400
From: King Chan <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] B200 quadrature imbalance issue
Message-ID:
<CACGfNRP5Pv+x2ef7ZvHDfd20O+XjZnwDh2aKi=rm_mwtnrj...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
I have exactly the same problem Simon Pack experienced (see his post
link below). By shifting the frequency though, it did enable the TX
quadrature correction. I can observe the TX spurious signal drop from
-32dBc to -57dBc on a spectrum analyzer once built-in correction is enable.
However, this will not enable the RX side quadrature correction. I can
observe similar level of spur by injecting a known clean signal from a
signal generator to the B200 receiver.
Any recommendation to enable the correction on the RX side too?
http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2014-March/008941.html
Thanks.
King
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140404/a615d817/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
End of USRP-users Digest, Vol 44, Issue 4
*****************************************
