On Tue, Apr 23, 2019 at 2:06 PM Fabian Schwartau via USRP-users < [email protected]> wrote:
> Hi everyone, > > I just found another strange thing. Can get_time_now() be in any case > blocking? Like long blocking? It takes more than 1 second to return! > I am heavily using timed commands, but I tried a clear_command_time() > before calling get_time_now() with no effect. It would also make no > sense at all to be able to set a command time for get_time_now(). > According to documentation the command just reads the registers in the > USRPs and returns them - no need to wait for anything. > Any ideas? > Reading registers isn't the fastest thing in the world, but you shouldn't be utilizing get_time_now() heavily for a real time system. Taking a second sounds like something is wrong, but I'm still curious why you're constantly asking for the time. The idea behind that is to understand the current time the radio has, figure out what you want to do when you first start a stream or do something, then use sample counting to understand when things are supposed to be happening. So, why do you keep asking for the time? What's the use case you're trying to figure out? Brian
_______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
