Hey all,
Running the
https://github.com/Borjis131/USRP-tests/blob/master/test_clock_synch_b210.cpp
example with two USRPs works. Even if I use get_time_now() instead of
get_time_last_pps(). So I don't know why the example shipped with uhd
doesn't work.
Thanks, Borja.
El 10/2/20 a las 13:44, Borja Iñesta Hernández via USRP-users escribió:
Hi all,
I just set up an Octoclock-G using the guide and now I can ping my
device. But checking the test_clock_sync example with my x310 USRP
something seems to be working bad. I run ./test_clock_synch
--clock-args addr=CLOCK_ADDRESS --usrp-args serial=USRP_SERIAL and
every time it has a 1 second offset between the USRP and the Octoclock
in all the comparisons. The clock in the USRP is always one second
delayed.
And in the test_clock_synch example changing: *(*times)[mboard] =
usrp->**get_time_now**(mboard)**.**get_full_secs**();*
to: *(*times)[mboard] =
usrp->**get_time_last_pps**(mboard).**get_full_secs**();
*
Works every time.
So, does anyone know why my USRP is one second delayed when I use
get_time_now() even if its supossed to work? Can I assume that my USRP
is synchronized to the Octoclock when im using get_time_last_pps()?
For my tests I have used this modified version of test_clock_synch
created to work with two USRPs but only using it with one.
https://github.com/Borjis131/USRP-tests/blob/master/test_clock_synch_b210.cpp
the code is from Urban Hankansson thread
http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2015-January/012227.html
Thanks, Borja.
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
