On 03/10/2018 02:43 AM, 賴明煊 via USRP-users wrote:
Hi
The problem of my last e-mail "Problem of Octoclock" has been solved.
That is, I can see my Octoclock-G using "uhd_find_devices" and
"uhd_usrp_probe".
I follow the instructions as the link to update EEPROM.
https://files.ettus.com/manual/pag
On 03/10/2018 12:06 AM, Nick Foster wrote:
I uh what? I don't see why that would be the case. The whole reason
U103 exists is to switch between a GPSDO (if present) and an external
reference.
I vaguely recall now (and it might just be a false memory) that there
was a problem with cross-talk bet
I'm using the rx_samples_to_file to capture the data.
I have pure noise connected to input. If I plot first few milliseconds of
IQ data I see some pull-in process. Interestingly enough this pull-in time
doesn't depend on parameter "--setup".
Is it some fancy IQ calibration?
When does the samples
On 03/10/2018 08:41 PM, Sailor Jerry via USRP-users wrote:
I'm using the rx_samples_to_file to capture the data.
I have pure noise connected to input. If I plot first few milliseconds
of IQ data I see some pull-in process. Interestingly enough this
pull-in time doesn't depend on parameter "--s
On 03/10/2018 09:26 PM, Sailor Jerry wrote:
Thanks a lot Marcus,
Let me restate my question in terms of the rx_samples_to_file.cpp
code. What line of code does turn the RX logic on?
I thought that once I'm passed check_locked_sensor() everything is
initialized. I guess the right answer is
Thanks a lot once again Marcus. I'm so grateful for a level oh help I get
on this forum.
On Sat, Mar 10, 2018 at 7:11 PM, Marcus D. Leech wrote:
> On 03/10/2018 09:26 PM, Sailor Jerry wrote:
>
> Thanks a lot Marcus,
>
> Let me restate my question in terms of the rx_samples_to_file.cpp code.
> Wh
