[aprssig] Best format for a Repeater Item (350 bug)

Ron Stordahl, AE5E ronn5in-aprssig at yahoo.com
Thu Apr 25 11:34:58 EDT 2013

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:


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.

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.

I found http://dxspots.com/aprs/frequency_objects/D710A%20Compatible%20APRS%20Frequency%20Objects.htm 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.

Ron, AE5E

> From: Mark Cheavens <mcheavens at usa.net>
>To: TAPR APRS Mailing List <aprssig at tapr.org> 
>Sent: Thursday, April 25, 2013 9:33 AM
>Subject: Re: [aprssig] Best format for a Repeater Item (350 bug)
>Or as another idea:
>Create a web interface that if a digi operator entered the variables 
>into, it would "give" the proper configuration parameters.
>- It would also SHOW (simulated) what will be displayed on each of 
>the APRS radio's displays.
>I long thought about doing that for UiDigi. Could also be done for 
>T2's, KPC-3's, etc.
>At 08:39 AM 4/25/2013, Lynn W. Deffenbaugh (Mr) wrote:
>>On 4/25/2013 8:20 AM, Robert Bruninga wrote:
>>>>Bob!  You forgot the most important part that was recently discovered!
>>>>The Yaesu FTM-350 REQUIRES the frequency at the beginning of the
>>>All of the advantages of the FREQ objects come
>>>from them appearing in the STATION list on mobile radios.  It makes no
>>>sense to me to break that intentended system design due to a minor bug in
>>>the 350.
>>>Putting the FREQ in the OBJECT name as designed appears just fine and as
>>>intended in the 350 and the 350 can also sort them too.   So all of the
>>>original functionality of this FREQ system also works on the 350. The only
>>>thing the 350 won't do correctly is the QSY button.
>>I'm not proposing removing the frequency from the object name, but 
>>only parroted back the change that the original requester suggest. 
>>I'm all for putting the frequency in the list (object name), but I 
>>sure don't see how it hurts to put it also in the comment, 
>>especially since that's the format described at 
>>http://www.aprs.org/info/freqspec.txt (which, as I mentioned before, 
>>doesn't provide for PHG either).
>>We just need to nail down a consistent, adequately described (and 
>>reasoned - tell them why), most broadly usable (including ALL 
>>APRS-capable radio's capabilities if possible) format and THEN start 
>>"encouraging" the correction, update, and rollout of the frequency objects.
>>As this thread shows, there doesn't seem to be ONE consistent 
>>description of EXACTLY what someone should be putting out as a 
>>frequency specification object that works with more than just one 
>>vendor's APRS radios.
>>Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
>>PS.  BTW, you seemed to be fully in agreement with including the 
>>frequency in the comment to support Yaesu's the last time this was 
>>discussed.  I'm sorry if my failure to put the frequency back into 
>>the object name led you to believe I was proposing an elimination of 
>>that portion of the suggestions.
>>aprssig mailing list
>>aprssig at tapr.org
>aprssig mailing list
>aprssig at tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20130425/a98c1c98/attachment.html>

More information about the aprssig mailing list