<div dir="ltr">Hi Bill,<br><div><br></div><div> Yes, that is the approach that we have had good success with in the past. Our Ettus based data acquisition scheme used in the software radar at Haystack does the same kind of arm/proceed on the next 1 PPS edge.</div><div><br></div><div>73</div><div>Phil W1PJE</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 22, 2020 at 5:22 PM Engelke, Bill via TangerineSDR <<a href="mailto:tangerinesdr@lists.tapr.org">tangerinesdr@lists.tapr.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-2824641284658322452WordSection1">
<p class="MsoNormal">Hello Phil:<br>
This could be the subject of a week-long workshop; but I will tell you how I have been coding it so far, using something that works nicely with DRF as it is today.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">When the user tells the system to start data acquisition, the Data Engine is to wait until the exact top of the next second to begin collecting data (plus or minus a few nanoseconds, anyway). Then, the unix time is passed as a uint_32 (unix
time being an integer second like 1633795200, which is about 4 PM today). I plug that into the global_start_sample in digital_rf_create_write_hdf5 (as modified by sample rate numerator & denominator, which usually work out to 1). This single time stamp is
used from then on, assuming that the DE clock is totally accurate. I think this is what you describe in your email; I like the simplicity of this, and I hope we can continue to use it.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">-regards- Bill AB4EJ<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b>From:</b> TangerineSDR <<a href="mailto:tangerinesdr-bounces@lists.tapr.org" target="_blank">tangerinesdr-bounces@lists.tapr.org</a>>
<b>On Behalf Of </b>Phil Erickson via TangerineSDR<br>
<b>Sent:</b> Tuesday, September 22, 2020 10:13 AM<br>
<b>To:</b> TAPR TangerineSDR Modular Software Defined Radio <<a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a>><br>
<b>Cc:</b> Phil Erickson <<a href="mailto:phil.erickson@gmail.com" target="_blank">phil.erickson@gmail.com</a>><br>
<b>Subject:</b> [EXTERNAL] [TangerineSDR] Simple question regarding time stamps<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi all,<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> Instead of searching through my cluttered inbox, I thought I'd ask a question about time stamps in the PSWS architecture: are these stored as floats/doubles or as integers?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"> I ask because we at Haystack (specifically Ryan Volz) have just run into yet another "doesn't port to architecture XXX" problem / regression test failure with a time stamp stored as a double in a DigitalRF implementation (on a RPi - 32
vs 64 bit), so I wanted to remind myself of what had been decided here. Our strong experience is that doing integer time stamps is greatly preferred because it has much less risk and is more future-proof. Digital RF for example uses integer ratios (M / N)
for encoding of fractional sample rates for this very reason.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"> I'm sure this has been discussed already, so if someone can point me to the particular place in the spec, that would be great.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">73<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Phil W1PJE<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<p class="MsoNormal">----<br>
Phil Erickson<br>
<a href="mailto:phil.erickson@gmail.com" target="_blank">phil.erickson@gmail.com</a><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
-- <br>
TangerineSDR mailing list<br>
<a href="mailto:TangerineSDR@lists.tapr.org" target="_blank">TangerineSDR@lists.tapr.org</a><br>
<a href="http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">----<br>Phil Erickson<br><a href="mailto:phil.erickson@gmail.com" target="_blank">phil.erickson@gmail.com</a><br></div>