Hello,
I am trying to understand the spec for the Ettus TCXO for the B200, and for
GPSDOs in general.
The performance when the oscillator is unlocked is clearly stated as 75
ppb. The spec says this deviation is primary driven by temperature
(Frequency Stability Over Temperature = +/- 7.5e-8)
Wha
via USRP-users <
usrp-users@lists.ettus.com> wrote:
> On 07/27/2020 09:05 PM, Aaron Smith via USRP-users wrote:
>
> Hello all,
>
> I am trying to output a sine wave from a B200 using custom code, or the
> UHD tx_waveform example. In either case, when I view the output on an
&
Hello all,
I am trying to output a sine wave from a B200 using custom code, or the UHD
tx_waveform example. In either case, when I view the output on an o-scope,
there is not a pure sine wave. The output looks more triangular wave. I
have used this scope with other B200s and the same code to get a
al is typically surprisingly large--it's
> 1PPS +/- a few 10s of nanoseconds, and the phasing of that 1PPS with
> respect to the 10MHz signal isn't, I think, necessarily a "standard".
>
>
> On Tue, Jun 23, 2020 at 1:06 PM Marcus D. Leech via USRP-users <
>
020 02:45 PM, Aaron Smith via USRP-users wrote:
> > Hello,
> >
> > I am attempting to release a transmission from an X310 every second.
> > To accomplish this, I must measure, and calibrate the delay in the RF
> > front end of the radio for my chosen sample rate. I'd l
Hello,
I am attempting to release a transmission from an X310 every second. To
accomplish this, I must measure, and calibrate the delay in the RF front
end of the radio for my chosen sample rate. I'd like the transmission to be
released within 1 clock cycle of the rising edge of the PPS.
I am fee
I pulled down the master branch of UHD about 2 months ago.
My version is 3.15.0.HEAD-0-gaea0e2de.
On Mon, Jun 15, 2020, 4:54 PM Marcus D. Leech
wrote:
> On 06/15/2020 06:51 PM, Aaron Smith wrote:
>
> Yes, transmissions within the same session are consistent. If I destroy
> the MultiUSRP object
Yes, transmissions within the same session are consistent. If I destroy the
MultiUSRP object and recreate it (restart my transmit script), the timing
will change. If I repeat hundreds of transmissions without restarting the
timing is stable to the expected accuracy of my TOA measurements.
On Mon,
I am using a master clock rate of 48 MHz and a sample rate of 8 MHz.
On Mon, Jun 15, 2020, 4:41 PM Marcus D. Leech
wrote:
> On 06/15/2020 03:42 PM, Aaron Smith wrote:
> > I am using the python api.
> >
> > usrp = uhd.usrp.MultiUSRP()
> >
> > # Set gain, clock rate, sample rate etc...
> >
> > usr
ith one channel. Do I have to utilize the other
> channel in some way to resolve the random delay?
>
> Thanks,
> Aaron
>
> On Fri, Jun 12, 2020 at 8:19 PM Marcus D. Leech via USRP-users <
> usrp-users@lists.ettus.com> wrote:
>
>> On 06/12/2020 10:07 PM, Aaron Smith
to resolve the random delay?
Thanks,
Aaron
On Fri, Jun 12, 2020 at 8:19 PM Marcus D. Leech via USRP-users <
usrp-users@lists.ettus.com> wrote:
> On 06/12/2020 10:07 PM, Aaron Smith via USRP-users wrote:
>
> Robin - with your insight I see that other users have addressed this on
>
> dividers randomly introduce a 0-degree or 180-degree phase shift when they
> come up.
>
>
>
> On Fri, Jun 12, 2020 at 4:08 PM Aaron Smith via USRP-users <
> usrp-users@lists.ettus.com> wrote:
>
>> All of the devices share a 10 MHz reference that is generated from
t
> there's an extra flop in the logic for the PPS timing chain somewhere -- as
> in, the clock starts ticking on the first tick after PPS comes in. I've
> made that error about half a million times, myself.
>
> Nick
>
> On Fri, Jun 12, 2020 at 2:23 PM Aaron Smith via U
Hello all,
I have two separate, but related, questions.
I am trying to trigger an RF transmission every second, and I am receiving
the transmission with a receiver that has very precise time stamps. I am
driving the receiver with the same 1 PPS source as the B200 and N210. For
my simple test, I w
14 matches
Mail list logo
