[aprssig] Kenwood D710 & Yaesu FTM-350AR Compatible Frrequency Objects

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Wed Jun 25 16:33:49 CDT 2014

On 6/25/2014 4:43 PM, Ron Stordahl, AE5E wrote:
> to add the FTM-350 & FTM-400.  The update increases the length of the 
> object by 11 bytes.  Hopefully this will not significantly increase 
> the packet error rate.  I do wish that the Yaesu radios did follow the 
> spec for frequency objects, but they don't, requiring the frequency 
> information to be duplicated in the tail section of the object.

They did follow the spec which allows the object to be of any name and 
provides for the frequency at the beginning of the comment.  The bit 
they left out is picking the frequency up from the object name. At least 
they did something that can be compatible with the Kenwood APRS radios 
and don't require double beacons of the same information in two 
different formats.

> Not that I expect too many to see this and correctly program their 
> digi's!  If you surf around on aprs.fi you will see there is a 
> scarcity such objects.  There are metropolitan areas without a single 
> frequency object, or at least one in correct format. Perhaps Bob's 
> document APRS Local Info Initiative 
> <http://www.aprs.org/localinfo.html> could be updated to make it a bit 
> easier to understand.  That was what I was trying to do with my puny 
> document effort, which I realize few will ever see!

The following map shows the FreqSpec-containing stations across the USA:

Whereas the following one shows the ones that appear to be trying to 
include frequency information, but they're not fully spec compliant:

Issues flagged by APRSISCE/32 include, but are not limited to:

No FTM-350: 147.165DE which says: T167 +060

No MHz: EL-338340 which has: 442.250 T136 R63m n9umj

PL tone: IRLP-7842 which has: 448.200MHz PL tone 100CONNECTED

+offset: IRLP3381 which has: 147.200MHz+ PL103.5: LINK CLEAR

Standalone +/-: 449.875-H  which has: 449.875 - 5  107.2 PL  VE6YXR 

k/m casing on range: 146.760dl which says: 146.760MHz T107 R50M N7YET Dillon

Decimal T/D/C: VE2OSR-9 which has: 447.1250Mhz T103.5 -500 QSO sur VE2PCQ

And here's one that might be usable by people, but not by radios!

444.325NC which has: http://www.carolina440.net 444.325 Mhz PL 100 Hz

If you run APRSISCE/32 and select View / Freq w/Issues, you can ask the 
local stations to get their beacons to be spec-compliant. APRSISCE/32 
will rummage through an entire packet trying to find frequency 
information which it parses and displays, but radios aren't as smart.

Oh, and the most frequent issue is the No FTM-350 because the frequency 
is only in the object name and not in the comment.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20140625/419a9293/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jaibedjd.png
Type: image/png
Size: 26971 bytes
Desc: not available
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20140625/419a9293/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dajefghj.png
Type: image/png
Size: 28485 bytes
Desc: not available
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20140625/419a9293/attachment-0001.png>

More information about the aprssig mailing list