I've been playing some lately with devices that don't provide an
inherent hardware timestamp, yet which can be run from a common clock,
and made coherent using cross-correlation estimation of timing offset.
Something that would make this easier--in that it would establish a
starting-point for cross correlation, and thus reduce the window size
over which one needs to estimate, would be if the scheduler could
insert a time tag of some sort the FIRST time it calls a work function
either initially or after a start() stop() start() sequence. This
would be crude, since it would be based on an OS-based timer, so it could
only act as a starting point.
That would allow one to then write a generic synchronizer block that
used a combination of rx_crude_time, and actual cross-correlation.
Is this a dumb idea?
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
