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. B200 master_clock_rate multiple of 2.048MHz (Matthias P. Braendli)
2. Re: B200 master_clock_rate multiple of 2.048MHz (Marcus D. Leech)
3. Re: MIMO GPS? (Ralph A. Schmid, dk5ras)
4. Re: self calibration of usrp b210 (Martin Braun)
5. Re: FSK demodulation using USRP N200 & SBX 400-4400 Mhz in
Simulink (Martin Braun)
6. Re: USRP B2xx External Reference Frequency (Martin Braun)
7. Re: USRP(1) blinks like Arduino... (Martin Braun)
8. Re: USRP B2xx External Reference Frequency (Marcus Leech)
9. Re: USRP B2xx External Reference Frequency (Jacob Gilbert)
----------------------------------------------------------------------
Message: 1
Date: Sun, 16 Mar 2014 18:04:29 +0100
From: "Matthias P. Braendli" <[email protected]>
To: [email protected]
Subject: [USRP-users] B200 master_clock_rate multiple of 2.048MHz
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Hi all,
we are using USRPs as DAB transmitters, which uses a native sample rate
of 2.048Msps. Because of this, I really would like to run the USRP with
a master_clock_rate that is a multiple of this value.
The B200 sets a master clock slightly off: Using the enclosed test
program, I tried all possible multiples of 2048000, none of which
actually get accepted without change.
The confusing part is that UHD prints
-- Asking for clock rate 10.24 MHz
-- Actually got clock rate 10.24 MHz
but the values are different. You'll see in the .log that my UHD is
dirty, I've just added the
-- Warning ! Difference is -0.0418869 Hz !
debug output.
Is this due to a software limitation or a hardware limitation ?
Or is there another trick to achieve my desired sampling rate of
2.048Msps on a B200 ?
best regards,
Matthias
http://mpb.li
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.cpp
Type: text/x-c++src
Size: 1727 bytes
Desc: not available
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140316/3aee977d/attachment-0001.cpp>
-------------- next part --------------
linux; GNU C++ version 4.8.2 20140206 (prerelease); Boost_105500;
UHD_003.007.000-0-g7fef199d
OutputUHD:Creating the usrp device with: type=b200...
-- Operating over USB 2.
-- Initialize CODEC control...
-- Initialize Radio control...
-- Performing register loopback test... pass
-- Performing CODEC loopback test... pass
-- Asking for clock rate 32 MHz
-- Actually got clock rate 32 MHz
-- Performing timer loopback test... pass
OutputUHD:Using device: Single USRP:
Device: B-Series Device
Mboard 0: B200
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: FE-RX2
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: FE-TX2
...
UHD clock source is internal
UHD time source is none
-- Asking for clock rate 10.24 MHz
-- Actually got clock rate 10.24 MHz
-- Warning ! Difference is -0.0418869 Hz !
-- Performing timer loopback test... pass
FAILURE: 5
-- Asking for clock rate 12.288 MHz
-- Actually got clock rate 12.288 MHz
-- Warning ! Difference is 0.0694125 Hz !
-- Performing timer loopback test... pass
FAILURE: 6
-- Asking for clock rate 14.336 MHz
-- Actually got clock rate 14.336 MHz
-- Warning ! Difference is 0.031116 Hz !
-- Performing timer loopback test... pass
FAILURE: 7
-- Asking for clock rate 16.384 MHz
-- Actually got clock rate 16.384 MHz
-- Warning ! Difference is -0.00718061 Hz !
-- Performing timer loopback test... pass
FAILURE: 8
-- Asking for clock rate 18.432 MHz
-- Actually got clock rate 18.432 MHz
-- Warning ! Difference is -0.0454772 Hz !
-- Performing timer loopback test... pass
FAILURE: 9
-- Asking for clock rate 20.48 MHz
-- Actually got clock rate 20.48 MHz
-- Warning ! Difference is 0.0159569 Hz !
-- Performing timer loopback test... pass
FAILURE: 10
-- Asking for clock rate 22.528 MHz
-- Actually got clock rate 22.528 MHz
-- Warning ! Difference is -0.0223397 Hz !
-- Performing timer loopback test... pass
FAILURE: 11
-- Asking for clock rate 24.576 MHz
-- Actually got clock rate 24.576 MHz
-- Warning ! Difference is 0.138825 Hz !
-- Performing timer loopback test... pass
FAILURE: 12
-- Asking for clock rate 26.624 MHz
-- Actually got clock rate 26.624 MHz
-- Warning ! Difference is 0.100528 Hz !
-- Performing timer loopback test... pass
FAILURE: 13
-- Asking for clock rate 28.672 MHz
-- Actually got clock rate 28.672 MHz
-- Warning ! Difference is 0.0622319 Hz !
-- Performing timer loopback test... pass
FAILURE: 14
-- Asking for clock rate 30.72 MHz
-- Actually got clock rate 30.72 MHz
-- Warning ! Difference is 0.0239354 Hz !
-- Performing timer loopback test... pass
FAILURE: 15
-- Asking for clock rate 32.768 MHz
-- Actually got clock rate 32.768 MHz
-- Warning ! Difference is -0.0143612 Hz !
-- Performing timer loopback test... pass
FAILURE: 16
-- Asking for clock rate 34.816 MHz
-- Actually got clock rate 34.816 MHz
-- Warning ! Difference is -0.0526578 Hz !
-- Performing timer loopback test... pass
FAILURE: 17
-- Asking for clock rate 36.864 MHz
-- Actually got clock rate 36.864 MHz
-- Warning ! Difference is -0.0909543 Hz !
-- Performing timer loopback test... pass
FAILURE: 18
-- Asking for clock rate 38.912 MHz
-- Actually got clock rate 38.912 MHz
-- Warning ! Difference is -0.129251 Hz !
-- Performing timer loopback test... pass
FAILURE: 19
-- Asking for clock rate 40.96 MHz
-- Actually got clock rate 40.96 MHz
-- Warning ! Difference is -0.167547 Hz !
-- Performing timer loopback test... pass
FAILURE: 20
-- Asking for clock rate 43.008 MHz
-- Actually got clock rate 43.008 MHz
-- Warning ! Difference is -0.00638276 Hz !
-- Performing timer loopback test... pass
FAILURE: 21
-- Asking for clock rate 45.056 MHz
-- Actually got clock rate 45.056 MHz
-- Warning ! Difference is -0.0446793 Hz !
-- Performing timer loopback test... pass
FAILURE: 22
-- Asking for clock rate 47.104 MHz
-- Actually got clock rate 47.104 MHz
-- Warning ! Difference is -0.0829759 Hz !
-- Performing timer loopback test... pass
FAILURE: 23
-- Asking for clock rate 49.152 MHz
-- Actually got clock rate 49.152 MHz
-- Warning ! Difference is -0.121272 Hz !
-- Performing timer loopback test... pass
FAILURE: 24
-- Asking for clock rate 51.2 MHz
-- Actually got clock rate 51.2 MHz
-- Warning ! Difference is -0.159569 Hz !
-- Performing timer loopback test... pass
FAILURE: 25
-- Asking for clock rate 53.248 MHz
-- Actually got clock rate 53.248 MHz
-- Warning ! Difference is -0.197866 Hz !
-- Performing timer loopback test... pass
FAILURE: 26
-- Asking for clock rate 55.296 MHz
-- Actually got clock rate 55.296 MHz
-- Warning ! Difference is -0.236162 Hz !
-- Performing timer loopback test... pass
FAILURE: 27
------------------------------
Message: 2
Date: Sun, 16 Mar 2014 13:18:53 -0400
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] B200 master_clock_rate multiple of 2.048MHz
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
On 03/16/2014 01:04 PM, Matthias P. Braendli wrote:
> Hi all,
>
> we are using USRPs as DAB transmitters, which uses a native sample rate
> of 2.048Msps. Because of this, I really would like to run the USRP with
> a master_clock_rate that is a multiple of this value.
>
> The B200 sets a master clock slightly off: Using the enclosed test
> program, I tried all possible multiples of 2048000, none of which
> actually get accepted without change.
>
> The confusing part is that UHD prints
> -- Asking for clock rate 10.24 MHz
> -- Actually got clock rate 10.24 MHz
> but the values are different. You'll see in the .log that my UHD is
> dirty, I've just added the
> -- Warning ! Difference is -0.0418869 Hz !
> debug output.
>
> Is this due to a software limitation or a hardware limitation ?
>
> Or is there another trick to achieve my desired sampling rate of
> 2.048Msps on a B200 ?
>
> best regards,
> Matthias
>
> http://mpb.li
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Am I missing something? [And I freely admit that I could be missing
something in what you're asking for].
We're talking clock rate differences of roughly 1PPB. That is vastly
better than you actually need for DAB, and better than the 2PPM clock
oscillator
on the B200.
If you think that you can set an "exact" frequency anywhere in the
physical world, you're living in a state of conceptual sin.
For example, to routinely achieve an actual error of 1.0e-9, you'll need
an OCXO, 1.0e-11, a Rb source, 1.0-e12, a Cs source, 1.0e-14, a hydrogen
maser, and somewhere in there a GPSDO will fit as well. Note how
none of these are "exact", but rather, giving you more significant digits
closer to "exact".
What you're seeing is simply rounding error, since divider registers in
PLLs aren't infinitely wide, and IEEE-754 floating-point math isn't
infinitely precise.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140316/314bf056/attachment-0001.html>
------------------------------
Message: 3
Date: Mon, 17 Mar 2014 06:37:36 +0100
From: "Ralph A. Schmid, dk5ras" <[email protected]>
To: "'Matt Ettus'" <[email protected]>, "'Jason A. Donenfeld'"
<[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] MIMO GPS?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
However I see chances for some applications that one receiver could receive
another channel to trim the main channel accordingly. Of course this must be
done completely in software and is restricted to stuff like for example
2G/3G/4G, where commercial signals in the same band are around.
Ralph.
From: USRP-users [mailto:[email protected]] On Behalf Of Matt
Ettus
Sent: Sunday, 16 March, 2014 16:06
To: Jason A. Donenfeld
Cc: [email protected]
Subject: Re: [USRP-users] MIMO GPS?
You could use the b210's radio to listen to gps, but the 2nd channel would then
be forced to be on the same frequency. So unless your intended use is gps it is
impractical.
Matt
On Mar 15, 2014 6:33 PM, "Jason A. Donenfeld" <[email protected]> wrote:
Hi folks,
I assume it's possible for the B210 to listen to GPS. (Correct me if
I'm wrong.) Rather than paying for an expensive GPSDO, are there any
technical limitations in using one MIMO channel of the B210 for, say,
OpenBTS, and the other MIMO channel as a replacement for a GPSDO?
Excuse my ignorance if this is an under-thought question.
Thanks,
Jason
_______________________________________________
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/20140317/9d2d39ff/attachment-0001.html>
------------------------------
Message: 4
Date: Mon, 17 Mar 2014 15:06:10 +0100
From: Martin Braun <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] self calibration of usrp b210
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 14.03.2014 10:09, MITUL VEKARIYA wrote:
> Hi
> I was going through calibration guide
> http://files.ettus.com/uhd_docs/manual/html/calibration.html and it is
> mentioned that only daughter boards are supported.
> Does usrp api supports self calibration utility for B200/B210 device?
As Ben just posted in another thread, UHD/B200 makes use of the AD9361
internal calibration capabilities. There's no CAL "antenna" available on
the B200, so if you try and run one of the uhd_cal* utilities, it will
give an appropriate warning.
Martin
>
> Thanks
> Mitul Vekariya
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 5
Date: Mon, 17 Mar 2014 15:21:13 +0100
From: Martin Braun <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] FSK demodulation using USRP N200 & SBX
400-4400 Mhz in Simulink
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Adeel,
if I understand you correctly, you already set up the hardware, and now
all you need to do is connect the software?
Perhaps you can give us some pointers on what you still need to do.
Here's some factoids:
- Simulink has USRP-Support out-of-the-box
- This might help:
http://blogs.mathworks.com/pick/2010/02/26/synchronizing-a-matlab-gui-and-a-simulink-model/
- Simulink also has FSK-blocks ready to use
If you have more specific questions, just ask them here. Good luck with
your setup!
M
On 12.03.2014 16:44, Adeel Malik wrote:
> Hi All,
> We have recently procured USRP N200 along with SBX 400-4400
> MHz RF daughter board. As I am new to this field, I need a sample
> simulink model example that could implement an FSK demodulation and data
> recovery functionality.
>
> Specifically, we have an S-band transmitter of 5 Watt o/p, with centre
> freq set at 2250 MHz. As we need to send data at 1 Mbps, we have
> adjusted the RF transmitter bandwidth to 1.7 MHz. It means binary '1' is
> transmitted as 2250Mhz - 850 kHz signal and binary '0' is transmitted as
> 2250 Mhz + 850 kHz signal.
> We transmit the signal and receive at a distance of say 1 Km, with
> received power of roughly -60 dBm. We intend to downconvert the signal
> to IF band (say 30 Mhz) and then do baseband processing along with
> symbol timing recovery to account for carrier pahse offsets. The
> demodulated signal needs to be stored in a PC for BER analysis.
>
> Could someone suggest how I go about this using USRP hardware and simulink.
> Pls suggest if you require more informtion,
>
> Thanks,
> Adeel Malik
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
r
------------------------------
Message: 6
Date: Mon, 17 Mar 2014 15:25:00 +0100
From: Martin Braun <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] USRP B2xx External Reference Frequency
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 12.03.2014 16:44, Jacob Gilbert wrote:
> Hello,
>
> Is it possible for the USRP B2xx devices to be configured to accept a
> reference signal other than 10 MHz? I see this is possible with the USRP
> 2 series (by setting the PLL R Divider in firmware) but I have not seen
> anything for the B2xx. Specifically I would like to reference lock it to
> a 30.72 MHz reference.
Sure, just add the "master_clock_rate=30.72e6" parameters to the device
set call.
See also
http://files.ettus.com/uhd_docs/manual/html/usrp_b200.html#changing-the-master-clock-rate.
Martin
------------------------------
Message: 7
Date: Mon, 17 Mar 2014 15:30:19 +0100
From: Martin Braun <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] USRP(1) blinks like Arduino...
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 12.03.2014 19:13, G Mallery wrote:
> Balint,
>
> Thank you. That is indeed the case, but still not receiving any data
> on "start" from GQRX, or HDSDR (- haven't tried GRC). (Works fine on B100).
>
> Back to the drawing board...
Hey Guy,
are you saying you're using the exact same dboard in a B100 and a USRP1,
and it doesn't work in the USRP1? Is GQRX throwing an error?
Martin
>
> V/R,
>
> Guy - W6MSU
>
>
> _____________________________________________________
> /
> | Device: USRP1 Device
> | _____________________________________________________
> | /
> | | Mboard: USRP1
> | | serial: 4807cb58
> | |
> | | Time sources: none
> | | Clock sources: internal
> | | Sensors:
> | | _____________________________________________________
> | | /
> | | | RX DSP: 0
> | | | Freq range: -32.000 to 32.000 Mhz
> | | _____________________________________________________
> | | /
> | | | RX DSP: 1
> | | | Freq range: -32.000 to 32.000 Mhz
> | | _____________________________________________________
> | | /
> | | | RX Dboard: A
> | | | ID: WBX v3, WBX v3 + Simple GDB (0x0057)
> | | | Serial: ECR20V2XW
> | | | _____________________________________________________
> | | | /
> | | | | RX Frontend: 0
> | | | | Name: WBXv3 RX+GDB
> | | | | Antennas: TX/RX, RX2, CAL
> | | | | Sensors: lo_locked
> | | | | Freq range: 68.750 to 2200.000 Mhz
> | | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB
> | | | | Connection Type: IQ
> | | | | Uses LO offset: No
>
>
>
>
> On Wed, Mar 12, 2014 at 7:35 AM, Balint Seeber <[email protected]
> <mailto:[email protected]>> wrote:
>
> Hi G,
>
> The ExtIO will report the antenna list is empty when UHD reports
> there are no antennas on the current daughterboard. This occurs when
> you use a BasicRX, LFRX, no daughterboard, or a malfunctioning
> daughterboard (e.g. the EEPROM might be corrupt - you can use UHD to
> re-program this if it's a WBX/SBX/CBX for example).
>
> As Michael suggested, if you post the output of uhd_usrp_probe it
> should reveal more. Since it's the USRP 1, did you pass in the
> appropriate Device Hint to select the side of the USRP that contains
> the daughterboard you wish to use? (e.g. passing 'A', 'B', 'A:0', etc)
>
> Kind regards,
> Balint
>
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 8
Date: Mon, 17 Mar 2014 14:36:24 +0000 (UTC)
From: Marcus Leech <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [USRP-users] USRP B2xx External Reference Frequency
Message-ID: <1259599920.151029.1395066984454.JavaMail.mail@webmail07>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140317/adc29986/attachment-0001.html>
------------------------------
Message: 9
Date: Mon, 17 Mar 2014 11:58:21 -0400
From: Jacob Gilbert <[email protected]>
To: Martin Braun <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] USRP B2xx External Reference Frequency
Message-ID:
<CAC52AkDpW1ARqYktYbVJcEg5Dp=ddehfnvlvdjxvcq2qhnt...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Thank you for the response Martin.
Changing the master clock rate works well for me, but I am looking to
provide a frequency reference to the B210 (eg: J100 "10MHz") other than 10
MHz as Marcus mentioned. Is this possible?
I would look in the firmware myself for the PLL configuration, but I am
unable to locate/identify the firmware for the B2xx series in the UHD
source. It looks like it isn't there (I only see the FX2, X300, octoclock
and ZPU firmware) but maybe I am not understanding the source structure.
Could you point me in the right direction here?
Thanks,
Jacob
On Mon, Mar 17, 2014 at 10:25 AM, Martin Braun <[email protected]>wrote:
> On 12.03.2014 16:44, Jacob Gilbert wrote:
>
>> Hello,
>>
>> Is it possible for the USRP B2xx devices to be configured to accept a
>> reference signal other than 10 MHz? I see this is possible with the USRP
>> 2 series (by setting the PLL R Divider in firmware) but I have not seen
>> anything for the B2xx. Specifically I would like to reference lock it to
>> a 30.72 MHz reference.
>>
>
> Sure, just add the "master_clock_rate=30.72e6" parameters to the device
> set call.
>
> See also http://files.ettus.com/uhd_docs/manual/html/usrp_b200.
> html#changing-the-master-clock-rate.
>
> Martin
>
>
>
> _______________________________________________
> 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/20140317/d7a4b4cb/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 43, Issue 17
******************************************
