If you really need the PPS/timestamp, this is the right answer, but 4/5 times when users ask for access to PPS/time, they don't really need, so make sure you're in the right category. Does your block also consume data with timestamps? Then you probably don't want this. If you're tracking some real (wall clock) time, then you likely do.
--M On Fri, Jun 13, 2025 at 3:21 PM Brian Padalino <[email protected]> wrote: > If you are looking to get the radio time and the 1PPS into your block > using the icores yaml definitions, then check the timekeeper and pps > broadcast-listener here: > > > https://github.com/EttusResearch/uhd/blob/c354764c93b49c90be08958f942b9bcb7704cbd5/host/include/uhd/rfnoc/core/io_signatures.yml > > Then check the BSP files in that same path for the BSP connection name. > > You'll need to make some BSP connections like: > > - { srcblk: _device_, srcport: pps0, dstblk: yourblock, dstport: pps } > - { srcblk: _device_, srcport: time0, dstblk: yourblock, dstport: time } > > That should give you the 64-bit time and the 1PPS. > > Good luck. > > Brian > > On Fri, Jun 13, 2025 at 6:12 AM <[email protected]> wrote: > >> Pretty much what the title says, our goal is to sync the timestamps to >> the rising edge of the 1PPS signal such that they get reset exactly on the >> rising edge of the 1pps signal, and increment the count of a custom >> metadata tag, to the outgoing stream to the UHD application that we are >> working on. >> _______________________________________________ >> USRP-users mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
