On 02/26/2018 01:36 PM, Piotr Krysik via USRP-users wrote:
It's hard for me to understand why only one of the devices changes the
master clock rate at that moment. This seems a bit arbitrary. It would
be best that after creation of usrp_source the master clock rate
wouldn't be changed (unless user requests it).
It's NOT arbitrary on the B2xx series--the sample-rate interface in UHD
tries to provide maximum flexibility by changing the
master clock rate to achieve the desired sample-rate, UNLESS the user
has specified an explicit master-clock rate.
Since sample-rate can be changed after a USRP block is instantiated, I
don't see any way to achieve both goal simultaneously.
Anyway I should have expected something like this. Some time back I had
similar issue when doing GPS synchronization.
I attach version of 'recorder.py' that has some unnecessary sleeps removed.
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
