<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 6/25/2014 4:43 PM, Ron Stordahl,
AE5E wrote:<br>
</div>
<blockquote
cite="mid:1403729027.66726.YahooMailNeo@web163102.mail.bf1.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff;
font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial,
Lucida Grande, sans-serif;font-size:12pt"><br>
<div class="yui_3_16_0_9_1403708928864_23" style="color: rgb(0,
0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida Grande,sans-serif;
background-color: transparent; font-style: normal;">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.<br>
</div>
</div>
</blockquote>
<br>
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.<br>
<br>
<blockquote
cite="mid:1403729027.66726.YahooMailNeo@web163102.mail.bf1.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff;
font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial,
Lucida Grande, sans-serif;font-size:12pt">
<div class="yui_3_16_0_9_1403708928864_23" style="color: rgb(0,
0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida Grande,sans-serif;
background-color: transparent; font-style: normal;"><br>
</div>
<div class="yui_3_16_0_9_1403708928864_23" style="color: rgb(0,
0, 0); font-size: 16px; font-family: HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida Grande,sans-serif;
background-color: transparent; font-style: normal;">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 <a moz-do-not-send="true"
href="http://www.aprs.org/localinfo.html">APRS Local Info
Initiative</a> 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!</div>
</div>
</blockquote>
<br>
The following map shows the FreqSpec-containing stations across the
USA:<br>
<img src="cid:part2.07020600.07030700@homeside.to" alt=""><br>
Whereas the following one shows the ones that appear to be trying to
include frequency information, but they're not fully spec compliant:<br>
<img src="cid:part3.02070000.00080007@homeside.to" alt=""><br>
<br>
Issues flagged by APRSISCE/32 include, but are not limited to:<br>
<br>
No FTM-350: 147.165DE which says: T167 +060<br>
<br>
No MHz: EL-338340 which has: 442.250 T136 R63m n9umj<br>
<br>
PL tone: IRLP-7842 which has: 448.200MHz PL tone 100CONNECTED<br>
<br>
+offset: IRLP3381 which has: 147.200MHz+ PL103.5: LINK CLEAR<br>
<br>
Standalone +/-: 449.875-H which has: 449.875 - 5 107.2 PL VE6YXR
REPEATER SYSTEM<br>
<br>
k/m casing on range: 146.760dl which says: 146.760MHz T107 R50M
N7YET Dillon<br>
<br>
Decimal T/D/C: VE2OSR-9 which has: 447.1250Mhz T103.5 -500 QSO sur
VE2PCQ<br>
<br>
And here's one that might be usable by people, but not by radios!<br>
<br>
444.325NC which has: <a class="moz-txt-link-freetext" href="http://www.carolina440.net">http://www.carolina440.net</a> 444.325 Mhz PL 100
Hz<br>
<br>
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.<br>
<br>
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.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
</body>
</html>