Hi!
We are testing the Octoclock-G. In this case, we attempted to connect
this dispositive to an X410. The problem is determinating when the
USRP and the Octoclock are synchronized.
The test_sync_clock script should confirm this, but we are unsure of
the results. With both devices on, the test passes. However, when i
turn off one device and turn on again the test still passes ,no matter
what i do, the result is always correct.
Is there another way to confirm the synchronization? I read about
checking certain register with uhd_usrp_probe, but i didn’t find
anything relevant.
I would appreciate any insights from someone who has tested the
OctoClock and knows the best approach.
Best regards,
Álvaro
That script checks the "ref_locked" sensor on the USRP, and if it's
getting 10MHz on the 10MHz REF clock input, that sensor will
show as "true". The Octoclock-G starts producing 10MHz on its 10Mhz
clock outputs as soon as it is powered up, and that
10MHz will get dragged into synchronization with GPS usually within a
few 10s of seconds of powering up.
You can use the "get_sensor" API on the USRP clock to check the
"gps_locked" sensor on the Octoclock-G -- check the source
code of the test_clock_synch application. Around line 70, it checks
a couple of sensors on the clock interface.
On 02/03/2025 10:30, ardelgado@gradiant.org wrote:
>
> Hi!
>
> We are testing the Octoclock-G. In this case, we attempted to connect
> this dispositive to an X410. The problem is determinating when the
> USRP and the Octoclock are synchronized.
>
> The test_sync_clock script should confirm this, but we are unsure of
> the results. With both devices on, the test passes. However, when i
> turn off one device and turn on again the test still passes ,no matter
> what i do, the result is always correct.
>
> Is there another way to confirm the synchronization? I read about
> checking certain register with uhd_usrp_probe, but i didn’t find
> anything relevant.
>
> I would appreciate any insights from someone who has tested the
> OctoClock and knows the best approach.
>
> Best regards,
> Álvaro
>
That script checks the "ref_locked" sensor on the USRP, and if it's
getting 10MHz on the 10MHz REF clock input, that sensor will
show as "true". The Octoclock-G starts producing 10MHz on its 10Mhz
clock outputs as soon as it is powered up, and that
10MHz will get dragged into synchronization with GPS usually within a
few 10s of seconds of powering up.
You can use the "get_sensor" API on the USRP clock to check the
"gps_locked" sensor on the Octoclock-G -- check the source
code of the test_clock_synch application. Around line 70, it checks
a couple of sensors on the clock interface.
>
> _______________________________________________
> USRP-users mailing list -- usrp-users@lists.ettus.com
> To unsubscribe send an email to usrp-users-leave@lists.ettus.com
