<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    It would also be interesting to have an FTM-350 owner see if this
    format works for them as well.  The D710 isn't the only APRS radio
    with a QSY function any more.  Of course, the FTM-350 needs to be in
    VFO (not memory) mode for it to even think about working.<br>
    <br>
    If this ever gets nailed down (it has been discussed before with
    less confirmation than is now available), I will consider making it
    easier to "properly" format QSY information in objects generated by
    APRSISCE/32.<br>
    <br>
    Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
    <br>
    On 4/30/2012 11:33 AM, Ron Stordahl, AE5E wrote:
    <blockquote
      cite="mid:1335799996.17517.YahooMailNeo@web125703.mail.ne1.yahoo.com"
      type="cite">
      <div style="color:#000; background-color:#fff; font-family:times
        new roman, new york, times, serif;font-size:12pt">
        <div><span>Richard et al</span></div>
        <div><br>
          <span></span></div>
        <div><span>I have confirmed that the format you list below for
            frequency objects works correctly with my D710A (USA Model),
            allowing single button QSY:</span></div>
        <div><br>
          <span></span></div>
        <div class="yiv2133051444MsoNormal" style="background:white;"><span
            class="yiv2133051444rawline"><span style="color:black;">;146.85TRF*111111z4804.29N/09606.79Wr146.850MHz
              TOFF - R45m</span></span></div>
        <div class="yiv2133051444MsoNormal" style="background:white;"><span
            style="color:black;">  </span></div>
        <div class="yiv2133051444MsoNormal" style="background:white;"><span
            class="yiv2133051444rawline"><span style="color:black;">;444.80TRF*111111z4807.60N/09610.63Wr444.800MHz
              T156 + R15m</span></span><span style="color:black;"></span></div>
        <span class="yui_3_2_0_22_1335797790269111"
style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">
        </span>
        <div><br>
          <span></span></div>
        <div><span>Out of interest I went on APRS.FI and by scrolling
            around the USA I picked the first 10 VHF objects I found. 
            Only 2 of them were properly formatted.  The deviation from
            the standard was remarkable.  Of the 2 that were correctly
            formatted, only one had the 'shift' indication of - or +. 
            The other that was 'correctly' formatted would have worked
            because on 2M the D710A defaults the offset depending upon
            the frequency.</span></div>
        <div><br>
          <span></span></div>
        <div><span>Of the first 10 UHF repeater objects, only 1 was
            correctly formatted as it did provide the offset marker (a
            +).  The rest varied from nonsense to close yet unworkable. 
            For some reason the D710A requires the offset info for 70
            CM, but not for 2 M.<br>
          </span></div>
        <div><br>
          <span></span></div>
        <div><span>I suspect the reason for so little adherence to the
            standard is that the example provided in  <a
              moz-do-not-send="true"
              href="http://www.aprs.org/localinfo.html">http://www.aprs.org/localinfo.html</a> 
            Specifically</span><br>
          <span></span></div>
        <div><font color="#000000" size="3">
            <li><font color="#FF0000"><font color="#000000"><font
                    color="#FF0000"><font color="#000000">
                      <div><font color="#FF0000"><font color="#000000"><b>BTEXT
                              ;FFF.FFxyz*111111zDDMM.hhN/DDDMM.hhWrTnnn
                              RXXm NETxxxxxx MTGxxxxx .........
                            </b></font></font></div>
                      <div><font color="#FF0000"><font color="#000000"><b>
                            </b></font></font></div>
                    </font></font></font></font></li>
          </font></div>
        <div><br>
        </div>
        <div>Does not include the needed frequency offset (needed for
          70CM repeaters and I believe desirable for 2M repeaters).<br>
        </div>
        <div><br>
        </div>
        <div>Of course some deviated from the above so much I wonder
          where they got their information!  </div>
        <div><br>
        </div>
        <div>While it is true that the number of D710A's as a proportion
          of the total APRS radios in use is small, it would be
          desirable to update the doc's so that this information is not
          so hard to find.</div>
        <div><br>
        </div>
        <div>Ron Stordahl, AE5E</div>
        <div><br>
        </div>
        <div><br>
          <blockquote style="border-left: 2px solid rgb(16, 16, 255);
            margin-left: 5px; margin-top: 5px; padding-left: 5px;">
            <div style="font-family: times new roman, new york, times,
              serif; font-size: 12pt;">
              <div style="font-family: times new roman, new york, times,
                serif; font-size: 12pt;">
                <div dir="ltr"> <font face="Arial" size="2">
                    <hr size="1"> <b><span style="font-weight:bold;">From:</span></b>
                    "Richard Sharp, KQ4KX" <a class="moz-txt-link-rfc2396E" href="mailto:kq4kx@arrl.net"><kq4kx@arrl.net></a><br>
                    <b><span style="font-weight: bold;">To:</span></b>
                    'TAPR APRS Mailing List' <a class="moz-txt-link-rfc2396E" href="mailto:aprssig@tapr.org"><aprssig@tapr.org></a> <br>
                    <b><span style="font-weight: bold;">Sent:</span></b>
                    Friday, April 27, 2012 6:23 PM<br>
                    <b><span style="font-weight: bold;">Subject:</span></b>
                    Re: [aprssig] APRS Local Info Initative TM-D710A
                    compatibitility<br>
                  </font> </div>
                <br>
                <meta http-equiv="x-dns-prefetch-control" content="off">
                <div id="yiv2133051444">
                  <style><!--
#yiv2133051444  
 _filtered #yiv2133051444 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
 _filtered #yiv2133051444 {font-family:Consolas;panose-1:2 11 6 9 2 2 4 3 2 4;}
#yiv2133051444  
#yiv2133051444 p.yiv2133051444MsoNormal, #yiv2133051444 li.yiv2133051444MsoNormal, #yiv2133051444 div.yiv2133051444MsoNormal
        {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"serif";}
#yiv2133051444 a:link, #yiv2133051444 span.yiv2133051444MsoHyperlink
        {color:blue;text-decoration:underline;}
#yiv2133051444 a:visited, #yiv2133051444 span.yiv2133051444MsoHyperlinkFollowed
        {color:purple;text-decoration:underline;}
#yiv2133051444 p.yiv2133051444MsoPlainText, #yiv2133051444 li.yiv2133051444MsoPlainText, #yiv2133051444 div.yiv2133051444MsoPlainText
        {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"sans-serif";}
#yiv2133051444 span.yiv2133051444rawline
        {}
#yiv2133051444 span.yiv2133051444EmailStyle18
        {font-family:"sans-serif";color:#1F497D;}
#yiv2133051444 span.yiv2133051444PlainTextChar
        {font-family:"sans-serif";}
#yiv2133051444 .yiv2133051444MsoChpDefault
        {font-size:10.0pt;}
 _filtered #yiv2133051444 {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv2133051444 div.yiv2133051444WordSection1
        {}
--></style>
                  <div>
                    <div class="yiv2133051444WordSection1">
                      <div class="yiv2133051444MsoNormal"><span
style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">Ron,
                          try the following…</span></div>
                      <div class="yiv2133051444MsoNormal"><span
style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">
                           </span></div>
                      <div class="yiv2133051444MsoNormal"
                        style="background:white;"><span
                          class="yiv2133051444rawline"><span
                            style="color:black;">;146.85TRF*111111z4804.29N/09606.79Wr146.850MHz
                            TOFF - R45m</span></span></div>
                      <div class="yiv2133051444MsoNormal"
                        style="background:white;"><span
                          style="color:black;">  </span></div>
                      <div class="yiv2133051444MsoNormal"
                        style="background:white;"><span
                          class="yiv2133051444rawline"><span
                            style="color:black;">;444.80TRF*111111z4807.60N/09610.63Wr444.800MHz
                            T156 + R15m</span></span><span
                          style="color:black;"></span></div>
                      <div class="yiv2133051444MsoNormal"><span
style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">
                           </span></div>
                      <div class="yiv2133051444MsoPlainText"><span
                          style="color:#376092;">According to pg. 25-26
                          in the D710’s "getting acquainted with APRS
                          & EchoLink" manual it should be in this
                          format.  </span><span style="color:#376092;">If
                          the repeater object is formatted with just a
                          “-“ or “+” it uses the radios default offset
                          setting for that band.  So, the only time
                          specifying the exact offset would be for odd
                          split repeaters.  Note the offset indicator
                          after the TOFF & T156 (the offset should
                          have a space on both sides).   </span><span
                          style="color:#376092;">If the repeater is
                          narrowband the 'T' should be lowercase (tOFF
                          or t156).    If the repeater transmits the PL
                          tone it should be C156 (c156 for narrowband). 
                        </span><span style="color:#376092;">Since the 2m
                          side of the D710 has auto offset the indicator
                          on the object isn’t actually necessary –
                          unless a user has the auto offset turned off. 
                          I would recommend using the offset indicator
                          for 2m regardless just for consistency.  For
                          the 70cm side though the offset indicator is
                          required.  Having the frequency listed in full
                          at the beginning of the payload will enable
                          the frequency display on the D710’s station
                          list on the right side.</span></div>
                      <div class="yiv2133051444MsoNormal"><span
style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">
                           </span></div>
                      <div class="yiv2133051444MsoNormal"><span
style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">Hope
                          this helps…</span></div>
                      <div class="yiv2133051444MsoNormal"><span
style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">
                           </span></div>
                      <div class="yiv2133051444MsoNormal"><span
style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">Richard</span></div>
                      <div class="yiv2133051444MsoNormal"><span
style="font-size:11.0pt;font-family:"sans-serif";color:#1F497D;">
                           </span></div>
                    </div>
                  </div>
                </div>
                <meta http-equiv="x-dns-prefetch-control" content="on">
                <br>
                _______________________________________________<br>
                aprssig mailing list<br>
                <a moz-do-not-send="true"
                  ymailto="mailto:aprssig@tapr.org"
                  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>
                <br>
              </div>
            </div>
          </blockquote>
        </div>
      </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>