<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Please DON'T!   <br>
    <br>
    Remember how many time's you've gone looking for an extra bit here
    or there.  There's a distinction between t and T, so why not a
    distinction between OFF and off and k/m vs K/M?  <br>
    <br>
    If there's case sensitivity on the first letters, and on MHz (and
    probably rx), then there should be case sensitivity throughout the
    specification for consistency, IMHO.  It's a SPECIFICATION, not a
    HACK.<br>
    <br>
    Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
    <br>
    On 5/8/2012 1:32 PM, Bob Bruninga wrote:
    <blockquote cite="mid:087201cd2d40$9584d600$c08e8200$@edu"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        color:black;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></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]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The
            intent was to key on the case of the first letter.  I can
            clarify that in the spec.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Bob<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
                <a class="moz-txt-link-abbreviated" href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a>
                [<a class="moz-txt-link-freetext" href="mailto:aprssig-bounces@tapr.org">mailto:aprssig-bounces@tapr.org</a>] <b>On Behalf Of </b>Lynn
                W. Deffenbaugh (Mr)<br>
                <b>Sent:</b> Tuesday, May 08, 2012 1:22 PM<br>
                <b>To:</b> Ron Stordahl, AE5E; TAPR APRS Mailing List<br>
                <b>Subject:</b> Re: [aprssig] FREQ Object radio issues
                (b)<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Spec says "Toff", not "TOFF", for a wide
          repeater (toff would be narrow).  Yes, the devil is in the
          details.<br>
          <br>
          And the jury is still out as to whether or not Yaeus's APRS
          radios are able to tune to frequency objects without the
          frequency in the comments, so if you set these up, have a
          Yaesu owner give them a QSY test (note that it is also my
          understanding that the FTM-350 must be in VFO mode for the
          QSY/Tune function to work).<br>
          <br>
          Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
          Win32<br>
          <br>
          PS. Thanks for posting these because I wasn't flagging the OFF
          as non-compliant in APRSISCE/32.  It will in the next
          development release.<br>
          <br>
          On 5/8/2012 1:00 PM, Ron Stordahl, AE5E wrote: <o:p></o:p></p>
        <div>
          <div>
            <p class="MsoNormal" style="background:white">I started all
              this ruckus on April 26 when I raised the issue of proper
              format to set up a D710A one button QSY.  <o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white">Based upon all
              the discussion I am returning to essentially my original
              proposal to send:<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white">;146.85TRF*111111z4804.29N/09606.79WrTOFF
              -060 R30m<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white">;444.80TRF*111111z4807.60N/09610.63WrT156
              +500 R15m<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white">Correct me if
              I am wrong but I believe this complies with the
              specification.  I realize including the offset on VHF is
              not necessary, but it gives me some satisfaction from the
              point of consistency to do so and makes it more
              understandable to the human reader.  Additionally one of
              our VHF repeaters on 147.00 has a non standard -600KHz
              shift when the standard is +600KHz, thus at least for that
              one -060 is required.  <o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white">I have just
              completed setting up these objects for 12 area repeaters,
              scattered over about 125 miles in NorthWestern Minnesota
              served by 8 APRS digipeaters.  Thankfully they are
              remotely programmable and can be reached from my central
              location directly or by up to 2 hops.  When remote
              programming is no longer possible, when these MFJ1270C's
              UIDIGI-ROM's die, I am finished as well!<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal" style="background:white">Ron, AE5E<o:p></o:p></p>
          </div>
          <div>
            <blockquote style="border:none;border-left:solid #1010FF
              1.5pt;padding:0in 0in 0in
              4.0pt;margin-left:3.75pt;margin-top:3.75pt;margin-bottom:5.0pt">
              <p class="MsoNormal" style="background:white"><o:p> </o:p></p>
              <div>
                <div>
                  <div>
                    <div class="MsoNormal"
                      style="text-align:center;background:white"
                      align="center"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif"">
                        <hr align="center" size="1" width="100%"></span></div>
                    <p class="MsoNormal" style="background:white"><b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif"">
                        Bob Bruninga <a moz-do-not-send="true"
                          href="mailto:bruninga@usna.edu"><bruninga@usna.edu></a><br>
                        <b>To:</b> 'TAPR APRS Mailing List' <a
                          moz-do-not-send="true"
                          href="mailto:aprssig@tapr.org"><aprssig@tapr.org></a>
                        <br>
                        <b>Sent:</b> Tuesday, May 8, 2012 10:54 AM<br>
                        <b>Subject:</b> [aprssig] FREQ Object radio
                        issues (b)</span><o:p></o:p></p>
                  </div>
                  <p class="MsoNormal"
                    style="margin-bottom:12.0pt;background:white"><br>
                    Here are some more notes I have found on some known
                    problems:<br>
                    <br>
                    Use of the "xyz" in the OBJECT NAME: <br>
                    <br>
                    > FFF.FF0xy object is OK and QSY is OK<br>
                    > FFF.FF5xy object is OK and QSY is OK<br>
                    > FFF.FFxyz object will not QSY in early D710
                    models.  Now fixed.<br>
                    <br>
                    > FFF.FFxyz objects of any format will not QSY
                    the FTM-350 (confirm?)<br>
                    <br>
                    Extra "0" on end of the +xxx or -xxx OFFSET format. 
                    The THD72 will accept<br>
                    extra characters after the required +xxx or -xxx. 
                    These will all give the<br>
                    proper offset:<br>
                    <br>
                    > 440.000MHz tOFF +500 Bob's radio <br>
                    > 440.000MHz tOFF +5000 Bob's radio <br>
                    > 440.000MHz tOFF +5000Bob's radio<br>
                    > 440.000MHz tOFF +5000000 Bob's radio<br>
                    > 440.000MHz tOFF +500Bob's radio<br>
                    <br>
                    BUT SHOULD N OT BE USED until confirmed all existing
                    radios can tolerate it.<br>
                    This was a proposed backwards-compatible future fix
                    to making the offset<br>
                    more human readable, because then we could recommend
                    the use of +5000<br>
                    instead of the +500.  But this CANNOT BE USED until
                    we have surveyed all<br>
                    radios to see if ALL radios can properly set the
                    offset if the additional<br>
                    "0" is included.  Or all radios are upgraded to do
                    so<br>
                    <br>
                    Here are some other known issues for the
                    Compatibility table of position<br>
                    Comments:<br>
                    <br>
                    Leading space:  (required, required-not, don't care)
                    - (Y, N, X)<br>
                    <br>
                    Xmits space:    (Transmits leading space) - (Y, N)<br>
                    <br>
                    Requires "MHz":  (Requires mixed case, allows any
                    case)    - (Y, N)<br>
                    <br>
                    Requires "MHz_": (Requires trailing space) - (Y, N)<br>
                    <br>
                    Xmits MHz_:      (Transmits trailing space) - (Y, N)<br>
                    <br>
                    Responds to +xxx and -xxx offsets - (Y, N)<br>
                    <br>
                    Transmits offsets +xxx and -xxx  - (Y, N)<br>
                    <br>
                    Allows extra trailing zero so that +600 works, where
                    only +60 is IAW spec -<br>
                    (Y, N)<br>
                    <br>
                    <br>
                    <br>
                    _______________________________________________<br>
                    aprssig mailing list<br>
                    <a moz-do-not-send="true"
                      href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>
                    <a moz-do-not-send="true"
                      href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig"
                      target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
                    <br>
                    <o:p></o:p></p>
                </div>
              </div>
            </blockquote>
          </div>
        </div>
        <p class="MsoNormal"><br>
          <br>
          <br>
          <o:p></o:p></p>
        <pre>_______________________________________________<o:p></o:p></pre>
        <pre>aprssig mailing list<o:p></o:p></pre>
        <pre><a moz-do-not-send="true" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><o:p></o:p></pre>
        <pre><a moz-do-not-send="true" href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><o:p></o:p></pre>
        <p class="MsoNormal"><o:p> </o:p></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>