Hi all, Is there any way to maintain the clock source and time source settings (used for synchronizing multiple USRPs through, say, an external GPSDOs) after the a host session has finished. I'm particularly interested in maintaining the settings used here: https://files.ettus.com/manual/page_sync.html#sync_commonref_pps
Platform: USRP N210 with SBX or WBX card talking to a Linux host over ethernet. USRP is always connected to an external GPSDO with 1PPS and 10 Mhz coax connections. Some more context: I'm building a complex application that involves first synchronizing a bunch of USRP devices and then performing a chain of sampling operations. Each USRP always has a connection (10 MHz + 1PPS) to an external GPSDO. I was hoping to simplify this application by separating it out into two explicit parts which could hopefully be called seperately: 1. a synchronization app and 2. the sampling app. However, I've noticed that the clock and time sources revert back to their default 'internal' setting after the synchronization app's session has completed (because the usrp virtual device has been destroyed). I'm wondering if there is a way to maintain their synchronization sources even after the usrp device is closed so other applications that would run later could benefit from the previous synchronization (every application would not have to run synchronization again and which would also reduce latency). I'm not particularly talking about writing to USRP's permanent memory (though if is the way to achieve this result, I'd be open to it) but in this scenario, the USRP is always powered while different applications on a host computer start, terminate and perform some UHD operations (not at the same time). Cheers,
_______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
