<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>A year ago after buying a D710A I updated the digi's in my area to transmit objects which would be D710A compatible, at least as regards frequency/offset setting for area voice repeaters. After some testing I came up with this:</span></div><br><div><a href="http://dxspots.com/aprs/frequency_objects/D710A%20Compatible%20APRS%20Frequency%20Objects.htm">http://dxspots.com/aprs/frequency_objects/D710A%20Compatible%20APRS%20Frequency%20Objects.htm</a></div><div><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">I posted it in the D710A Yahoo Group, the result of which was that although the information I presented was compatible with the D710A, it was not with the FTM-350. I posted a request on the
FTM-350 Yahoo Group to see if I could get some assistance from an owner, but never received a reply. As such I have not made any progress beyond the D710A in my local area.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">One quirk (?) of the D710A is that the offset must be stated on UHF, while on VHF a default is applied. However in my area the repeater on 147.00 uses a offset of -060. If this is not stated in the object the D710A will use an offset of +060. I have elected to state the offset information on both UHF and VHF for uniformity.</div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color:
transparent; font-style: normal;"><br></div><div class="yui_3_7_2_18_1366901269203_412" style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">I found <a href="http://dxspots.com/aprs/frequency_objects/D710A%20Compatible%20APRS%20Frequency%20Objects.htm">http://dxspots.com/aprs/frequency_objects/D710A%20Compatible%20APRS%20Frequency%20Objects.htm</a> confusing. Perhaps others do as well, as when traveling outside my own area few digi's transmit what will allow proper QSY on my D710A.</div><div class="yui_3_7_2_18_1366901269203_412" style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><br></div><div class="yui_3_7_2_18_1366901269203_61" style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent;
font-style: normal;">Ron, AE5E<br></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><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"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Mark Cheavens <mcheavens@usa.net><br> <b><span style="font-weight: bold;">To:</span></b> TAPR APRS Mailing List <aprssig@tapr.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Thursday, April 25, 2013 9:33 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [aprssig] Best format for a Repeater Item (350 bug)<br> </font> </div>
<div class="y_msg_container"><br>Or as another idea:<br>Create a web interface that if a digi operator entered the variables <br>into, it would "give" the proper configuration parameters.<br><br>- It would also SHOW (simulated) what will be displayed on each of <br>the APRS radio's displays.<br><br>I long thought about doing that for UiDigi. Could also be done for <br>T2's, KPC-3's, etc.<br><br>Mark<br>KC5EVE<br>At 08:39 AM 4/25/2013, Lynn W. Deffenbaugh (Mr) wrote:<br>>On 4/25/2013 8:20 AM, Robert Bruninga wrote:<br>>>>Bob! You forgot the most important part that was recently discovered!<br>>>>The Yaesu FTM-350 REQUIRES the frequency at the beginning of the<br>>>comment!<br>>><br>>>All of the advantages of the FREQ objects come<br>>>from them appearing in the STATION list on mobile radios. It makes no<br>>>sense to me to break that intentended system design due to a minor bug
in<br>>>the 350.<br>>><br>>>Putting the FREQ in the OBJECT name as designed appears just fine and as<br>>>intended in the 350 and the 350 can also sort them too. So all of the<br>>>original functionality of this FREQ system also works on the 350. The only<br>>>thing the 350 won't do correctly is the QSY button.<br>><br>>I'm not proposing removing the frequency from the object name, but <br>>only parroted back the change that the original requester suggest. <br>>I'm all for putting the frequency in the list (object name), but I <br>>sure don't see how it hurts to put it also in the comment, <br>>especially since that's the format described at <br>><a href="http://www.aprs.org/info/freqspec.txt" target="_blank">http://www.aprs.org/info/freqspec.txt </a>(which, as I mentioned before, <br>>doesn't provide for PHG either).<br>><br>>We just need to nail down a consistent, adequately
described (and <br>>reasoned - tell them why), most broadly usable (including ALL <br>>APRS-capable radio's capabilities if possible) format and THEN start <br>>"encouraging" the correction, update, and rollout of the frequency objects.<br>><br>>As this thread shows, there doesn't seem to be ONE consistent <br>>description of EXACTLY what someone should be putting out as a <br>>frequency specification object that works with more than just one <br>>vendor's APRS radios.<br>><br>>Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>><br>>PS. BTW, you seemed to be fully in agreement with including the <br>>frequency in the comment to support Yaesu's the last time this was <br>>discussed. I'm sorry if my failure to put the frequency back into <br>>the object name led you to believe I was proposing an elimination of <br>>that portion of the
suggestions.<br>><br>>_______________________________________________<br>>aprssig mailing list<br>><a ymailto="mailto:aprssig@tapr.org" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>><a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br><br>_______________________________________________<br>aprssig mailing list<br><a ymailto="mailto:aprssig@tapr.org" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br><a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br><br><br></div> </div> </div> </blockquote></div> </div></body></html>