<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:812065426;
mso-list-type:hybrid;
mso-list-template-ids:6047460 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">In <a href="https://scranton.zoom.us/rec/play/tMd4JO39-j43H4WQ5gSDC_AtW9S_ffmsgHcd-KJZy0uzUiIAZlPwMuQSYbeIYiPAWTSPSeb1nkzcpCCR?startTime=1587063159000&_x_zm_rtaid=NMAJy4E0RWahMdU1UXtvsg.1587138515458.823452708c432bc18700b9c14edfeb54&_x_zm_rhtaid=286">
yesterday’s HamSCI research telco</a>, we discussed several ideas on how to accomplish several goals with the TangerineSDR; a summary is below for your review and comment.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">We currently think that the Data Engine (DE) will have the capacity to simultaneously collect up to 8 channels of data for observing Doppler shift in carrier frequencies, i.e., WWV
at 2.5, 5, 10, 15, 20 MHz plus CHU at 3.33, 7.335 and 14.670 MHz. We think we can do this by observing excursions of up to +/- 1 Hz from the carrier frequency with a
<b>precision of 0.01 Hz, with measurements taken every second </b>(see next point).<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">In earlier discussions on this board, it has been stated that this kind of precision (10 milliHz) would require a 102.4 second sample time; this assumes the processing is linear. CWRU
is using a non-linear method in the low-cost approach to extract a frequency estimate, which uses fldigi to achieve the 10 milliHz resolution once per second, and it was discussed that TangerineSDR could be set up to do this as well. (Reference here:
<a href="http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.1017.4615&rep=rep1&type=pdf">
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.1017.4615&rep=rep1&type=pdf</a> )<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">I won’t try to explain the method mentioned above, as it is at the very limits of my understanding; however, a couple of observations…<o:p></o:p>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1">The CWRU low-cost system uses fldigi to implement the frequency estimator, and in looking at fldigi I see that it requires sound card input. In the case of the TangerineSDR, we will
have buffers of IQ data. I don’t think I want to use some sort of kludge to take the buffers and somehow emulate a sound card (do I?) – another option might be to implement the frequency estimator algorithm in the Small Board Computer (SBC) of the TangerineSDR.
If we could/should do this, I would ask for a volunteer to code it; I fear that if I try to do it, it would take far too long for me to get up the learning curve. The code (C++) for the algorithm as used in fldigi is online (included with hundreds of other
routines; see <a href="http://www.w1hkj.com/files/fldigi/">http://www.w1hkj.com/files/fldigi/</a> ). A third option might be to persuade the fldigi team to support buffer or file input.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1">As I understand, the frequency estimator outputs a single value: the strongest signal in the band. A downside of this is that there seems to be a lot of other possible information
in the data (Steve Cerwin has shown data he has collected showing Doppler effects but with multiple structures including various modes in both time and frequency domain). We need some guidance from the science community: what data do we really need to do the
desired science?? Maybe we need to implement/support both raw data collection & frequency estimation at the same time(?)<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1">In yesterday’s call, we discussed that we should be able to specify an 8 ksps sample rate and a center frequency, and get the desired 10 milliHz resolution – frankly, I am still fuzzy
on the details of this, so I wish someone (David Kazdan? Kristina?) would chime in and explain, for the record, how this works.<o:p></o:p></li></ol>
</li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Channel configuration settings for the DE:<o:p></o:p>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1">The DE will be able to tell the SBC what data rates it supports. We are working with 2-byte command codes; in general, a command ending in “?” is a query, i.e., send the DE the command
“S?” and it answers “AK” , a simple health check. Send the DE the command “R?” – it will respond with a table such as the following:<o:p></o:p></li></ol>
</li></ol>
<p class="MsoNormal" style="margin-left:.75in"> 1 2000 2 4000 3 8000 4 16000 etc. – where each entry is 2 integers: an index and a sample rate (Hz). To put a channel into data rate of 8000 sps, we put 3 into the channel setting.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in"><o:p> </o:p></p>
<p class="MsoNormal">Please comment! -73- Bill, AB4EJ<o:p></o:p></p>
</div>
</body>
</html>