<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.3">
</HEAD>
<BODY BGCOLOR="#ffffff">
Good info Steven.<BR>
<BR>
On Tue, 2006-10-17 at 17:52 -0400, Steven Stimpson (N1OHX) wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000"> </FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000"> </FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<FONT COLOR="#000000">----- Original Message ----- </FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<B><FONT COLOR="#000000">From:</FONT></B><FONT COLOR="#000000"> <A HREF="mailto:k8rra@ameritech.net">(Skip) K8RRA</A> </FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<B><FONT COLOR="#000000">To:</FONT></B><FONT COLOR="#000000"> <A HREF="mailto:nos-bbs@lists.tapr.org">TAPR xNOS Mailing List</A> </FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<B><FONT COLOR="#000000">Sent:</FONT></B><FONT COLOR="#000000"> Tuesday, October 17, 2006 4:02 PM</FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<B><FONT COLOR="#000000">Subject:</FONT></B><FONT COLOR="#000000"> Re: [nos-bbs] JNOS PMBO - correction - should be using QRG, not Dial !</FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
<FONT COLOR="#000000">The one constant seems to be: Get close then tweek a little.</FONT><BR>
<BR>
<FONT COLOR="#000000">In the past year I have not seen a good "tuning the radio" guide using various TNC models.</FONT><BR>
<FONT COLOR="#000000">If anyone has, I'd love to see it? </FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000"> </FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000"> WInlink2K needed a standard convention. I am looking at</FONT></FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">the MBO list right now, and for pactor2 they use 1400/1600</FONT></FONT><BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
That is the standard 200hz split, but not the default SCS PCT- I or II tones dialed up by my PCT-II.<BR>
I have not looked "under the covers" to find if SCS is offset a bit for the default 1200/1400 or if airmail software sets the custom 1400/1600 - the devil is in the detail...
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">tone pairs. pactor2 can be inverted, like packet can.</FONT></FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">They publish the frequencies as CENTER. For Dial</FONT></FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">frequency you subtract 1.5. N7QDN is on 14.069.9 center,</FONT></FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">and the software does the math for you and insists</FONT></FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">14.068.4 USB is your correct dial freq.</FONT></FONT><BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
Makes sense.<BR>
Part of the point I raise is in the wide variety of TNC's and the (seeming) lack of documentation treatment leaving you and me to engineer a solution for ourselves. Perhaps that is part of the hobby?<BR>
I have not exhausted the winlink documentation, so what I'm seeking may be there.<BR>
On the other hand, winlink may publish the transmission standard as you quote and leave calibration of our end to us depending on our choice of equipment and software.<BR>
It is also true I don't know how many TNC's airmail automates...
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000"> </FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000"> SInce airmail may be used for some of these forwarding ideas,</FONT></FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">maybe the Winlink2K guidelines should be followed. Would</FONT></FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">be a lot easier for end-users if Jnos is put into service</FONT></FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">as an alternative to the standard MBO.</FONT></FONT><BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
If ampr.org develops a hf pactor presence like winlink has, I expect some standard will emerge? In the meantime I expect airmail can get on board with winlink interface automation without too much arithmetic. And given the earlier data you can get within 100hz using Maiko's info, or "exactly" on if you also have a DXP38 with defaults set. For example: under the presumption that DSP38 mark of 2125 is equivalent to winlink 1600 mark, then report to airmail the Maiko USB frequency is (2125-1600) = 525hz lower to "cheat" the existing config. [I made a couple assumptions that may red flag the above, but I'll stand by the concept.]<BR>
<BR>
I guess it remains to be seen if Maiko automates jnos as deeply as airmail. In some sense I hope *not*, or if he does that he chooses to approach configuration with a script to accommodate adjustment for the wide variety of TNCs that do pactor to some extent...<BR>
<BR>
I'm thinking the variety justifies a paper on the subject. Once you get the RF frequencies straightened out, then comes the protocol I wish you the best of luck...
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000"> </FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">73,</FONT></FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#000000">Steven-n1ohx</FONT></FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000"> </FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">nos-bbs mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</A></FONT>
<FONT COLOR="#000000"><A HREF="https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs">https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</A></FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>