|
From: | Fabien PELLET |
Subject: | Re: USRP N210 growing latencies |
Date: | Sat, 30 Oct 2021 00:20:32 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 |
Hi, Thanks for the answer.At the moment, it seems that catching the underflow message and then lock/unlock the flowgraph permits to reset the buffers and is enough for my application to get reasonnable and not growing forever latencies. I don't if someone know a better way like a C++ method that could do that more "elegantly".
If I need more predictible latencies in the futur, indeed, I will try to use tags as you suggest.
Regards, Fabien, F4CTZ. Le 27/10/2021 à 17:02, Sylvain Munaut a écrit :
Hi,OK I understand that. But is there any solution which permits to reset that growing propagation delay ? How to reset the flowgraph buffers without killing the application and restart it ? Is there any method that permits to purge and resync buffers of the flowgraph ?The USRP supports timestamps for RX and TX. So you get tags for when data was received / is supposed to be transmitted. Using a custom block to modify the RX tags into TX tags ( to change the RX timestamps to TX timestamps a bit into the future ), you should be able to achieve a constant controlled latency. Cheers, Sylvain
[Prev in Thread] | Current Thread | [Next in Thread] |