> On 01/23/2020 12:32 PM, Lukas Haase via USRP-users wrote:
>> Hi,
>>
>> TO MY UNDERSTANDING, the USRP has an internal clock that is different from
>> host clock when running gnuradio (which makes sense because there are
>> buffers etc in between).
>> Example: I transmit a CW at f=1001, receive i
Hello everyone,
Sorry for the double message in the same thread, but I thought I would add some
of the things I discovered since yesterday in case anyone takes a look at this
thread.
First, it appears that I am not the only person to have this issue:
http://lists.ettus.com/pipermail/usrp-users
On 01/23/2020 12:32 PM, Lukas Haase via USRP-users wrote:
Hi,
TO MY UNDERSTANDING, the USRP has an internal clock that is different from host
clock when running gnuradio (which makes sense because there are buffers etc in
between).
Example: I transmit a CW at f=1001, receive it at f=1000 and t
You’re presumably transmitting a 10kHz tone at 80Mhz?
Is your counter locked to the same reference as the USRP?
Sent from my iPhone
> On Jan 23, 2020, at 5:30 PM, Remco Vink via USRP-users
> wrote:
>
>
> All,
>
> I am currently trying to generate a stable sine wave out of the B200 TX port
Hi,
TO MY UNDERSTANDING, the USRP has an internal clock that is different from host
clock when running gnuradio (which makes sense because there are buffers etc in
between).
Example: I transmit a CW at f=1001, receive it at f=1000 and then use gnuradio
to downconvert the remaining 1 MHz I run i
Sam,
I see want you mean but in my code I set the carrier freq once with set_tx_freq
(). Then I read the I Q data from a .dat file into the buffer and
stream this buffer continuously in a while loop.
The frequency hopping is done though my IQ modulation:
I = cos(omegan * t)
Q= sin(omegan*t)
with
