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: E100 external reference and PPS (Nowlan, Sean)
2. Re: E100 external reference and PPS (Nick Foster)
3. Re: E100 external reference and PPS (Nowlan, Sean)
4. Checking sensors during TX (Nowlan, Sean)
5. Re: Transceiver IC max2829 (John Malsbury)
6. Transmit DC Offset Calibration (Steve Peters)
7. Reusing a block for multiple iterations (Tinajayce Mathews)
8. Re: Broken gpsdo or bad antenna? (Dario Lombardo)
9. Re: Broken gpsdo or bad antenna? (Dario Lombardo)
----------------------------------------------------------------------
Message: 1
Date: Tue, 19 Jun 2012 18:26:14 +0000
From: "Nowlan, Sean" <[email protected]>
To: "Nowlan, Sean" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [USRP-users] E100 external reference and PPS
Message-ID: <195933287DC65748BA7AE867BA8E430B621BDF36@apatlisdmbx02>
Content-Type: text/plain; charset="us-ascii"
Hi,
It has been 3 weeks and nobody has responded to this question. Is there
anything special I need to do to enable the external reference and PPS inputs
on the E100 (rev. 3)? My only thoughts are that 1) there's something magic I
have to do to get the E100 in the mood to use the external reference, or 2) the
GPSDO unit I'm using is broken and the E100 can't lock to it.
Since the E100 (rev. 3) isn't configured to automatically detect the Jackson
Labs GPSDO and read its RS-232 output, I used Pin 3 to confirm that the GPSDO
is locked.
Any thoughts? Also, if Ettus has the rev. 3 schematic available somewhere, that
would be very helpful. Thank you!
Best regards,
Sean Nowlan
From: [email protected]
[mailto:[email protected]] On Behalf Of Nowlan, Sean
Sent: Friday, May 25, 2012 6:12 PM
To: [email protected]
Subject: [USRP-users] E100 external reference and PPS
Hi all,
I have an E100 (rev 3) and I would like to use an external reference and PPS. I
soldered straight SMA connectors onto J10 and J13 (REF IN and PPS IN,
respectively). I'm supplying a 10MHz and PPS reference to the board, but I'm
not sure how to tell the clock gen circuit to use the external reference.
I tried set_clock_source("external", 0) but the reference won't lock. Do I need
to burn an EEPROM setting as with the N2xx? Is there a jumper I need to change?
FYI I installed UHD 3.4.2 release.
Thanks,
Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120619/c5bbda35/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 19 Jun 2012 11:33:48 -0700
From: Nick Foster <[email protected]>
To: "Nowlan, Sean" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] E100 external reference and PPS
Message-ID:
<CALALHJUmQ5nzQ2saGYsKPk1rD9==Gy9gJofaTK2Arz=nmwf...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
On Tue, Jun 19, 2012 at 11:26 AM, Nowlan, Sean
<[email protected]>wrote:
> Hi, ****
>
> ** **
>
> It has been 3 weeks and nobody has responded to this question. Is there
> anything special I need to do to enable the external reference and PPS
> inputs on the E100 (rev. 3)? My only thoughts are that 1) there?s something
> magic I have to do to get the E100 in the mood to use the external
> reference, or 2) the GPSDO unit I?m using is broken and the E100 can?t lock
> to it.
>
For 10MHz ref, set J15 across pins 2&3, and use
the set_clock_source(?external?, 0) command. How are you verifying lock?
> ****
>
> ** **
>
> Since the E100 (rev. 3) isn?t configured to automatically detect the
> Jackson Labs GPSDO and read its RS-232 output, I used Pin 3 to confirm that
> the GPSDO is locked.
>
Did you obtain the Jackson Labs GPSDO from Ettus or from Jackson Labs?
--n
> ****
>
> ** **
>
> Any thoughts? Also, if Ettus has the rev. 3 schematic available somewhere,
> that would be very helpful. Thank you!****
>
> ** **
>
> Best regards,****
>
> Sean Nowlan****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Nowlan, Sean
> *Sent:* Friday, May 25, 2012 6:12 PM
> *To:* [email protected]
> *Subject:* [USRP-users] E100 external reference and PPS****
>
> ** **
>
> Hi all,****
>
> ** **
>
> I have an E100 (rev 3) and I would like to use an external reference and
> PPS. I soldered straight SMA connectors onto J10 and J13 (REF IN and PPS
> IN, respectively). I?m supplying a 10MHz and PPS reference to the board,
> but I?m not sure how to tell the clock gen circuit to use the external
> reference.****
>
> ** **
>
> I tried set_clock_source(?external?, 0) but the reference won?t lock. Do I
> need to burn an EEPROM setting as with the N2xx? Is there a jumper I need
> to change?****
>
> ** **
>
> FYI I installed UHD 3.4.2 release.****
>
> ** **
>
> Thanks,****
>
> Sean****
>
> _______________________________________________
> 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/20120619/a061d70a/attachment-0001.html>
------------------------------
Message: 3
Date: Tue, 19 Jun 2012 20:27:04 +0000
From: "Nowlan, Sean" <[email protected]>
To: Nick Foster <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] E100 external reference and PPS
Message-ID: <195933287DC65748BA7AE867BA8E430B621BDFED@apatlisdmbx02>
Content-Type: text/plain; charset="us-ascii"
>> OK, good. The reason I ask is ours are modified to work at 6V and you'll fry
>> a JL-sold device since it's expecting 5V.
Right, I had heard that. Glad I wasn't in danger of frying anything!
Unfortunately those fixes didn't help. I'm starting to suspect a firmware or
FPGA image issue. What's also bizarre is that I don't hear a peep out of the
TX/RX port when I run benchmark_tx.py. I don't even see a carrier tone. I don't
think it's the RFX900 board I'm using since it has no problems when used with
an N200.
I'm using the image e1xx-003 image with UHD 3.4.2 maint branch (built myself).
Any ideas what could be happening?
Thanks,
Sean
On Tue, Jun 19, 2012 at 11:41 AM, Nowlan, Sean
<[email protected]<mailto:[email protected]>> wrote:
Thanks! I'll definitely give that a shot.
I'm verifying ref_lock using get_mboard_sensor("ref_locked"), 0) and GPS lock
by pin 3 on the Firefly (see page 4 of the Jackson Labs manual:
http://www.jackson-labs.com/assets/uploads/main/firefly_1A_manual.pdf ). I'm
using the GPSDO sold from Ettus.
Sean
From: Nick Foster [mailto:[email protected]<mailto:[email protected]>]
Sent: Tuesday, June 19, 2012 2:37 PM
To: Nowlan, Sean
Subject: Re: [USRP-users] E100 external reference and PPS
Attached is the relevant page of the E100 schematic for R3.
--n
On Tue, Jun 19, 2012 at 11:33 AM, Nick Foster
<[email protected]<mailto:[email protected]>> wrote:
On Tue, Jun 19, 2012 at 11:26 AM, Nowlan, Sean
<[email protected]<mailto:[email protected]>> wrote:
Hi,
It has been 3 weeks and nobody has responded to this question. Is there
anything special I need to do to enable the external reference and PPS inputs
on the E100 (rev. 3)? My only thoughts are that 1) there's something magic I
have to do to get the E100 in the mood to use the external reference, or 2) the
GPSDO unit I'm using is broken and the E100 can't lock to it.
For 10MHz ref, set J15 across pins 2&3, and use the
set_clock_source("external", 0) command. How are you verifying lock?
Since the E100 (rev. 3) isn't configured to automatically detect the Jackson
Labs GPSDO and read its RS-232 output, I used Pin 3 to confirm that the GPSDO
is locked.
Did you obtain the Jackson Labs GPSDO from Ettus or from Jackson Labs?
--n
Any thoughts? Also, if Ettus has the rev. 3 schematic available somewhere, that
would be very helpful. Thank you!
Best regards,
Sean Nowlan
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Nowlan, Sean
Sent: Friday, May 25, 2012 6:12 PM
To: [email protected]<mailto:[email protected]>
Subject: [USRP-users] E100 external reference and PPS
Hi all,
I have an E100 (rev 3) and I would like to use an external reference and PPS. I
soldered straight SMA connectors onto J10 and J13 (REF IN and PPS IN,
respectively). I'm supplying a 10MHz and PPS reference to the board, but I'm
not sure how to tell the clock gen circuit to use the external reference.
I tried set_clock_source("external", 0) but the reference won't lock. Do I need
to burn an EEPROM setting as with the N2xx? Is there a jumper I need to change?
FYI I installed UHD 3.4.2 release.
Thanks,
Sean
_______________________________________________
USRP-users mailing list
[email protected]<mailto:[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/20120619/e0cf6b0e/attachment-0001.html>
------------------------------
Message: 4
Date: Tue, 19 Jun 2012 20:50:37 +0000
From: "Nowlan, Sean" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] Checking sensors during TX
Message-ID: <195933287DC65748BA7AE867BA8E430B621BE010@apatlisdmbx02>
Content-Type: text/plain; charset="us-ascii"
This may be a dumb question, but is it safe to run a thread that polls for
GPSDO GPS lock and get_time_now() on a regular interval while transmitting? Or
even to read NMEA sentences regularly and feed them to GPSd while transmitting?
Best regards,
Sean Nowlan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120619/eb3283c2/attachment-0001.html>
------------------------------
Message: 5
Date: Tue, 19 Jun 2012 16:31:21 -0700
From: John Malsbury <[email protected]>
To: Huldi Michael <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] Transceiver IC max2829
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Huldi,
If you're interested in understanding how to interact with the XCVR2450,
please look at db_xcvr2450.cpp. If you wish to reduce the ref input
frequency you can decrease the output frequency of the AD9510(may have
other consequences), or by increase the divide value of the AD9515 on
the daughterboard. However, it seems that tuning works with the
constraints currently set in db_xcvr2450.cpp, so I would start with that
as a baseline for your application.
Just out of curiosity, what are your intentions with the microblaze?
Are you trying to produce some sort of frequency hopping capability, or
are you trying to create a standalone radio with the microblaze? There
may be an easier path.
-John
On 06/19/2012 04:30 AM, Huldi Michael wrote:
>
> Yes, with USRP N210 and daughterboard xcvr2450.
>
> *From:*John Malsbury [mailto:[email protected]]
> *Sent:* Dienstag, 19. Juni 2012 13:23
> *To:* Huldi Michael
> *Cc:* [email protected]
> *Subject:* Re: [USRP-users] Transceiver IC max2829
>
> Are you developing this on a usrp, with an xcvr2450?
>
> John
>
>
>
> On Tuesday, June 19, 2012, Huldi Michael <[email protected]
> <mailto:[email protected]>> wrote:
> > Hello,
> >
> > In the datasheet of the transceiver IC MAX2829, which is on the
> daughterboard xcvr2450, I read that the reference oscillator input on
> pin 30 need to be 20 -- 44 MHz. But I measured a clock of 50 MHz on
> this pin. Does someone have an explanation for that?
> >
> > I have to know this because I write my own driver in C for the
> transceiver IC. The transceiver IC is driven of my microblaze via SPI.
> Perhaps someone has already done similar work?!
> >
> > Huldi Michael
> >
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120619/6ba60a4f/attachment-0001.html>
------------------------------
Message: 6
Date: Tue, 19 Jun 2012 23:34:38 -0500
From: Steve Peters <[email protected]>
To: [email protected]
Subject: [USRP-users] Transmit DC Offset Calibration
Message-ID:
<CANgtPkg7ma_yLEr4QBwJ=69LSjB=fwa0i-qnsy9kwrkpb-b...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello,
I'm hoping there is a crucial step to the DC calibration that I'm
overlooking. The DC offset calibration is only making my DC offset worse.
For my setup, I'm using tx_waveforms --freq=301e6 --rate=1e6
--wave-type=CONST --ampl=0.0. Without the calibration, the received sine
wave has an amplitude of about 0.004, and with the calibration the
amplitude is about 0.01 (transmission over a wire with 30dB attenuation to
attempt fairness between tests). This is well above the noise floor.
I've tried setting --nsamps=1000000 and focusing on the narrow band that
I'm operating in, but it never seems to actually reduce the DC offset.
When running the calibration, I disconnect the internal SMB cable from the
GDB. Am I missing some other crucial step to the calibration?
I'm running UHD 3.4.1 on USRP N210s, rev4.
When the TX and RX are connected to a common 10 MHz source, the sine wave
goes away (as expected). Unfortunately this isn't a long term solution to
the problem for me.
Best regards,
Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120619/d50dd234/attachment-0001.html>
------------------------------
Message: 7
Date: Tue, 19 Jun 2012 23:41:52 -0500
From: Tinajayce Mathews <[email protected]>
To: [email protected]
Subject: [USRP-users] Reusing a block for multiple iterations
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi All,
I wanted to use a C++ block and run it multiple number of times. For eg: I am
using a block to run one iteration. If I needed the results from this block
again in the continuing iterations, is there a work around for it. I am using a
hierarchical block and calling it like a function. I wonder if this is
possible. Any help is appreciated.
Thanks a lot for your help.
Regards,
T Mat
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120619/b66d17ac/attachment-0001.html>
------------------------------
Message: 8
Date: Wed, 20 Jun 2012 09:26:12 +0200
From: Dario Lombardo <[email protected]>
To: John Malsbury <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Broken gpsdo or bad antenna?
Message-ID:
<caoyjjftsc5q+w4a_5l_zybsuq9-fvaupybvliemkzz_xldx...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
On 19/giu/2012, at 13:45, John Malsbury <[email protected]> wrote:
Just for grins, can you remove the eeprom config that enables the internal
gpsdo?
The eeprom is set to internal when using gpsdo from jackson labs, according
to instructions.
What results do you see from kal when the internal tcxo on the motherboard
is used?
Around 200 hz of offset.
BTW, are you getting reasonable gga strings that correlate to your known
position?
Yes, more or less they are ok. Afaik, I can see 7 to 9 sats.
John
On Tuesday, June 19, 2012, Dario Lombardo < <[email protected]>
[email protected]> wrote:
> Hi Josh
>
> On Tue, Jun 19, 2012 at 1:14 PM, John Malsbury < <[email protected]>
[email protected]> wrote:
>>
>> Dario,
>>
>> Forgive me if I am not able to see your previous posts as I am answering
from my phone. Are you saying there is
>> 11 khz of error in the 10 mhz ref, or some frequency set to a
daughterboard LO?
>
> I'm saying that error is the output of kalibrate.
>
>>
>> You mention using an external reference. I don't think you would
achieve lock if this were the issue, but have you ensured the jumper is in
the proper configuration?
>
> When using the front panel connectors, I moved the jumper J510 to select
them. In this case I got 0 Hz of error at my first try. To be sure, I
disconnected the gpsdo from the mainboard.
>
>>
>> Are you selecting default or external as the ref source in your software?
>
> When using the gpsdo, I moved the jumper J510, then configured the eeprom
to "internal". In this case I suppose that the N210 automatically selects
the gpsdo. In fact every time I run something I see
> -- Opening a USRP2/N-Series device...
> -- Current recv frame size: 1472 bytes
> -- Current send frame size: 1472 bytes
> -- Found a Jackson Labs GPS
> -- Setting references to the internal GPSDO
> -- Initializing time to the internal GPSDO
> no matter if any "external ref" is used or not. In kal, I got that error
with and without the "-x" switch.
>>
>> John
>>
>> On Tuesday, June 19, 2012, Dario Lombardo < <[email protected]>
[email protected]> wrote:
>> > Hi all
>> > After many tries with my gpsdo, I still can't get a good clock.
>> > I've written a sw that continuously polls the gps_locked and the
ref_locked sensors. Both of them are always locked, that means that my
antenna is getting a quite "clear" sky view.
>> > I've connected the front panel connectors of my N210 to a cesium
clock/pps generator, and I get 2 to 0 Hz of error with kal. That should
mean that my usrp works fine and the kal commands are <http://good.hu/>
good.hu
>> > I've left the usrp turned on, with the gps antenna connected, for over
20 hours, but kal still gives me around 11 kHz of error.
>> > I think that one of these 2 things is happening:
>> > 1) my gpsdo card is broken. What can I do to ensure that this is not
the case? And if this is the case, what can I do?
>> > 2) my antenna can't give a signal that is clear enough, so the gpsdo
isn't unable to give me the clock.
>> > What do you think about the above cases?
>> > Any help appreciated.
>> > Dario.
Just for grins, can you remove the eeprom config that enables the internal
gpsdo? What results do you see from kal when the internal tcxo on the
motherboard is used?
Are you getting reasonable gga strings that correlate to your known
position?
John
On Tuesday, June 19, 2012, Dario Lombardo < <[email protected]>
[email protected]> wrote:
> Hi Josh
>
> On Tue, Jun 19, 2012 at 1:14 PM, John Malsbury < <[email protected]>
[email protected]> wrote:
>>
>> Dario,
>>
>> Forgive me if I am not able to see your previous posts as I am answering
from my phone. Are you saying there is
>> 11 khz of error in the 10 mhz ref, or some frequency set to a
daughterboard LO?
>
> I'm saying that error is the output of kalibrate.
>
>>
>> You mention using an external reference. I don't think you would
achieve lock if this were the issue, but have you ensured the jumper is in
the proper configuration?
>
> When using the front panel connectors, I moved the jumper J510 to select
them. In this case I got 0 Hz of error at my first try. To be sure, I
disconnected the gpsdo from the mainboard.
>
>>
>> Are you selecting default or external as the ref source in your software?
>
> When using the gpsdo, I moved the jumper J510, then configured the eeprom
to "internal". In this case I suppose that the N210 automatically selects
the gpsdo. In fact every time I run something I see
> -- Opening a USRP2/N-Series device...
> -- Current recv frame size: 1472 bytes
> -- Current send frame size: 1472 bytes
> -- Found a Jackson Labs GPS
> -- Setting references to the internal GPSDO
> -- Initializing time to the internal GPSDO
> no matter if any "external ref" is used or not. In kal, I got that error
with and without the "-x" switch.
>>
>> John
>>
>> On Tuesday, June 19, 2012, Dario Lombardo < <[email protected]>
[email protected]> wrote:
>> > Hi all
>> > After many tries with my gpsdo, I still can't get a good clock.
>> > I've written a sw that continuously polls the gps_locked and the
ref_locked sensors. Both of them are always locked, that means that my
antenna is getting a quite "clear" sky view.
>> > I've connected the front panel connectors of my N210 to a cesium
clock/pps generator, and I get 2 to 0 Hz of error with kal. That should
mean that my usrp works fine and the kal commands are <http://good.hu/>
good.hu
>> > I've left the usrp turned on, with the gps antenna connected, for over
20 hours, but kal still gives me around 11 kHz of error.
>> > I think that one of these 2 things is happening:
>> > 1) my gpsdo card is broken. What can I do to ensure that this is not
the case? And if this is the case, what can I do?
>> > 2) my antenna can't give a signal that is clear enough, so the gpsdo
isn't unable to give me the clock.
>> > What do you think about the above cases?
>> > Any help appreciated.
>> > Dario.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120620/5dead2d8/attachment-0001.html>
------------------------------
Message: 9
Date: Wed, 20 Jun 2012 10:06:42 +0200
From: Dario Lombardo <[email protected]>
To: Nick Foster <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Broken gpsdo or bad antenna?
Message-ID:
<CAOYJJfsmYxsiDOVLOqTFXjBQ=gs9enepaxn5cuens0y7nwl...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Nick
That's a good point, I didn't think about it.
So, my setup now is as follows:
- gpsdo has just 1 connection to the motherboard, the power supply
- 10 MHz and pps sma cables are connected to the front panel
- J510 jumper is in position 1-2
- eeprom gpsdo is set to "none"
That's the output from kal, with and without -x switch:
$ ./kal -c 37
linux; GNU C++ version 4.5.1 20100924 (Red Hat 4.5.1-4); Boost_104400;
UHD_003.004.002-128-g12f7a5c9
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
UHD Warning:
The hardware does not support the requested RX sample rate:
Target sample rate: 0.270833 MSps
Actual sample rate: 0.271739 MSps
kal: Calculating clock frequency offset.
Using GSM-900 channel 37 (942.4MHz)
average [min, max] (range, stddev)
+ 207Hz [198, 216] (18, 4.685140)
overruns: 0
not found: 0
$ ./kal -c 37 -x
linux; GNU C++ version 4.5.1 20100924 (Red Hat 4.5.1-4); Boost_104400;
UHD_003.004.002-128-g12f7a5c9
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
UHD Warning:
The hardware does not support the requested RX sample rate:
Target sample rate: 0.270833 MSps
Actual sample rate: 0.271739 MSps
kal: Calculating clock frequency offset.
Using GSM-900 channel 37 (942.4MHz)
average [min, max] (range, stddev)
- 20.648kHz [-20736, -20565] (171, 49.960464)
overruns: 0
not found: 0
That's what I got around 10 minutes after the power on.
On Tue, Jun 19, 2012 at 4:53 PM, Nick Foster <[email protected]> wrote:
> Dario,
>
> Also, please try configuring the USRP for "external" reference as you did
> for the cesium test previously. Then connect the GPSDO to the external
> reference input and see if kal gives reasonable error.
>
> It does seem like you may have a faulty reference input.
>
> --n
>
> On Tue, Jun 19, 2012 at 4:45 AM, John Malsbury <[email protected]>wrote:
>
>> Just for grins, can you remove the eeprom config that enables the
>> internal gpsdo? What results do you see from kal when the internal tcxo on
>> the motherboard is used?
>>
>> BTW, are you getting reasonable gga strings that correlate to your known
>> position?
>>
>>
>> John
>>
>> On Tuesday, June 19, 2012, Dario Lombardo <[email protected]>
>> wrote:
>> > Hi Josh
>> >
>> > On Tue, Jun 19, 2012 at 1:14 PM, John Malsbury <[email protected]>
>> wrote:
>> >>
>> >> Dario,
>> >>
>> >> Forgive me if I am not able to see your previous posts as I am
>> answering from my phone. Are you saying there is
>> >> 11 khz of error in the 10 mhz ref, or some frequency set to a
>> daughterboard LO?
>> >
>> > I'm saying that error is the output of kalibrate.
>> >
>> >>
>> >> You mention using an external reference. I don't think you would
>> achieve lock if this were the issue, but have you ensured the jumper is in
>> the proper configuration?
>> >
>> > When using the front panel connectors, I moved the jumper J510 to
>> select them. In this case I got 0 Hz of error at my first try. To be sure,
>> I disconnected the gpsdo from the mainboard.
>> >
>> >>
>> >> Are you selecting default or external as the ref source in your
>> software?
>> >
>> > When using the gpsdo, I moved the jumper J510, then configured the
>> eeprom to "internal". In this case I suppose that the N210 automatically
>> selects the gpsdo. In fact every time I run something I see
>> > -- Opening a USRP2/N-Series device...
>> > -- Current recv frame size: 1472 bytes
>> > -- Current send frame size: 1472 bytes
>> > -- Found a Jackson Labs GPS
>> > -- Setting references to the internal GPSDO
>> > -- Initializing time to the internal GPSDO
>> > no matter if any "external ref" is used or not. In kal, I got that
>> error with and without the "-x" switch.
>> >>
>> >> John
>> >>
>> >> On Tuesday, June 19, 2012, Dario Lombardo <[email protected]>
>> wrote:
>> >> > Hi all
>> >> > After many tries with my gpsdo, I still can't get a good clock.
>> >> > I've written a sw that continuously polls the gps_locked and the
>> ref_locked sensors. Both of them are always locked, that means that my
>> antenna is getting a quite "clear" sky view.
>> >> > I've connected the front panel connectors of my N210 to a cesium
>> clock/pps generator, and I get 2 to 0 Hz of error with kal. That should
>> mean that my usrp works fine and the kal commands are good.hu
>> >> > I've left the usrp turned on, with the gps antenna connected, for
>> over 20 hours, but kal still gives me around 11 kHz of error.
>> >> > I think that one of these 2 things is happening:
>> >> > 1) my gpsdo card is broken. What can I do to ensure that this is not
>> the case? And if this is the case, what can I do?
>> >> > 2) my antenna can't give a signal that is clear enough, so the gpsdo
>> isn't unable to give me the clock.
>> >> > What do you think about the above cases?
>> >> > Any help appreciated.
>> >> > Dario.
>>
>> Just for grins, can you remove the eeprom config that enables the
>> internal gpsdo? What results do you see from kal when the internal tcxo on
>> the motherboard is used?
>>
>> Are you getting reasonable gga strings that correlate to your known
>> position?
>>
>>
>> John
>>
>> On Tuesday, June 19, 2012, Dario Lombardo <[email protected]>
>> wrote:
>> > Hi Josh
>> >
>> > On Tue, Jun 19, 2012 at 1:14 PM, John Malsbury <[email protected]>
>> wrote:
>> >>
>> >> Dario,
>> >>
>> >> Forgive me if I am not able to see your previous posts as I am
>> answering from my phone. Are you saying there is
>> >> 11 khz of error in the 10 mhz ref, or some frequency set to a
>> daughterboard LO?
>> >
>> > I'm saying that error is the output of kalibrate.
>> >
>> >>
>> >> You mention using an external reference. I don't think you would
>> achieve lock if this were the issue, but have you ensured the jumper is in
>> the proper configuration?
>> >
>> > When using the front panel connectors, I moved the jumper J510 to
>> select them. In this case I got 0 Hz of error at my first try. To be sure,
>> I disconnected the gpsdo from the mainboard.
>> >
>> >>
>> >> Are you selecting default or external as the ref source in your
>> software?
>> >
>> > When using the gpsdo, I moved the jumper J510, then configured the
>> eeprom to "internal". In this case I suppose that the N210 automatically
>> selects the gpsdo. In fact every time I run something I see
>> > -- Opening a USRP2/N-Series device...
>> > -- Current recv frame size: 1472 bytes
>> > -- Current send frame size: 1472 bytes
>> > -- Found a Jackson Labs GPS
>> > -- Setting references to the internal GPSDO
>> > -- Initializing time to the internal GPSDO
>> > no matter if any "external ref" is used or not. In kal, I got that
>> error with and without the "-x" switch.
>> >>
>> >> John
>> >>
>> >> On Tuesday, June 19, 2012, Dario Lombardo <[email protected]>
>> wrote:
>> >> > Hi all
>> >> > After many tries with my gpsdo, I still can't get a good clock.
>> >> > I've written a sw that continuously polls the gps_locked and the
>> ref_locked sensors. Both of them are always locked, that means that my
>> antenna is getting a quite "clear" sky view.
>> >> > I've connected the front panel connectors of my N210 to a cesium
>> clock/pps generator, and I get 2 to 0 Hz of error with kal. That should
>> mean that my usrp works fine and the kal commands are good.hu
>> >> > I've left the usrp turned on, with the gps antenna connected, for
>> over 20 hours, but kal still gives me around 11 kHz of error.
>> >> > I think that one of these 2 things is happening:
>> >> > 1) my gpsdo card is broken. What can I do to ensure that this is not
>> the case? And if this is the case, what can I do?
>> >> > 2) my antenna can't give a signal that is clear enough, so the gpsdo
>> isn't unable to give me the clock.
>> >> > What do you think about the above cases?
>> >> > Any help appreciated.
>> >> > Dario.
>> >
>>
>> _______________________________________________
>> 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/20120620/713eee20/attachment-0001.html>
------------------------------
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
End of USRP-users Digest, Vol 22, Issue 20
******************************************
