|
From: | Adam Gorski |
Subject: | RE: Modifying Offset Stream Tag |
Date: | Tue, 23 Jun 2020 14:11:41 +0000 |
Nick, Jeff, Thank you for the detailed feedback. I am indeed doing multilateration on ADS-B signals, will investigate procuring a GPSDO for accurate timing.
The way I understand it, once I’m using the GPSDO to acquire an accurate timestamp the offset added to each message will still be at a minimum 500ns (at 2Msps). Is there anything that can be done to decrease this amount?
Thanks, Adam Gorski Virginia Tech Applied Research Corporation (VT-ARC) Wireless Communications Systems Engineer 410-818-3188 From: Nick Foster <bistromath@gmail.com> I think you are misunderstanding what the tag offset represents. The timestamp is coming from datetime.datetime.utcnow() in init(), and the tag offset added to that is just the offset (samples since the flowgraph started) of the burst divided
by the sample rate. Because the burst offset is in samples and not seconds, its resolution is limited to 1/samp_rate. Thus, at 2Msps, the resolution is limited to 500ns. In any case, Gnuradio knows nothing at all about time -- it only knows about
samples. To play Clippy for a bit, it sounds like you're trying to do multilateration on ADS-B signals. The approach being used in gr-adsb will not work for this. You cannot use the host clock (i.e., datetime) because its accuracy is nowhere near
what is required (if you're using PTP/IEEE-1588 with a local timeserver you'll be closer, but it will still be a mess). You need to synchronize the radio to GPS time either using a built-in GPSDO, or an external one. If the radio is not synchronized to a GPSDO, then instead of one problem you will have two: the initial time (since it's CPU time) will be wrong, and the time offset will drift over time (since the sample rate of the radio will not be synchronized). Nick On Sun, Jun 21, 2020 at 2:56 PM Adam Gorski <Adam.Gorski@vt-arc.org> wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |