On 03/15/2018 10:54 AM, Андрей 1 via USRP-users wrote:
Hello
Earlier I already wrote about big times for the example of
twinrx_freq_hopping
http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2018-February/027782.html
Can anyone analyze the source code(rx_samples_c in the attachment) and
say why it turns out such a strange result (TestTwinRX) when called
set_rx_lo_source.
Thank you
I will observe that if you want to check for real-time, as opposed to
CPU-occupancy-time, using clock() is not the right tool.
I'd use gettimeofday() or similar.
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
