<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Spec says "Toff", not "TOFF", for a wide repeater (toff would be
narrow). Yes, the devil is in the details.<br>
<br>
And the jury is still out as to whether or not Yaeus's APRS radios
are able to tune to frequency objects without the frequency in the
comments, so if you set these up, have a Yaesu owner give them a QSY
test (note that it is also my understanding that the FTM-350 must be
in VFO mode for the QSY/Tune function to work).<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
<br>
PS. Thanks for posting these because I wasn't flagging the OFF as
non-compliant in APRSISCE/32. It will in the next development
release.<br>
<br>
On 5/8/2012 1:00 PM, Ron Stordahl, AE5E wrote:
<blockquote
cite="mid:1336496440.85975.YahooMailNeo@web125705.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>I started all this ruckus on April 26 when I raised
the issue of proper format to set up a D710A one button
QSY. <br>
</span></div>
<div><span><br>
</span></div>
<div><span>Based upon all the discussion I am returning to
essentially my original proposal to send:</span></div>
<div><br>
<span></span></div>
<div><span>;146.85TRF*111111z4804.29N/09606.79WrTOFF -060 R30m</span></div>
<div><span> ;444.80TRF*111111z4807.60N/09610.63WrT156 +500 R15m</span></div>
<div><br>
<span></span></div>
<div><span>Correct me if I am wrong but I believe this complies
with the specification. I realize including the offset on
VHF is not necessary, but it gives me some satisfaction from
the point of consistency to do so and makes it more
understandable to the human reader. Additionally one of our
VHF repeaters on 147.00 has a non standard -600KHz shift
when the standard is +600KHz, thus at least for that one
-060 is required. <br>
</span></div>
<div><span><br>
</span></div>
<div><span>I have just completed setting up these objects for 12
area repeaters, scattered over about 125 miles in
NorthWestern Minnesota served by 8 APRS digipeaters.
Thankfully they are remotely programmable and can be reached
from my central location directly or by up to 2 hops. When
remote programming is no longer possible, when these
MFJ1270C's UIDIGI-ROM's die, I am finished as well!</span></div>
<div><br>
<span></span></div>
<div><span>Ron, AE5E</span></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>
Bob Bruninga <a class="moz-txt-link-rfc2396E" href="mailto:bruninga@usna.edu"><bruninga@usna.edu></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>
Tuesday, May 8, 2012 10:54 AM<br>
<b><span style="font-weight: bold;">Subject:</span></b>
[aprssig] FREQ Object radio issues (b)<br>
</font> </div>
<br>
Here are some more notes I have found on some known
problems:<br>
<br>
Use of the "xyz" in the OBJECT NAME: <br>
<br>
> FFF.FF0xy object is OK and QSY is OK<br>
> FFF.FF5xy object is OK and QSY is OK<br>
> FFF.FFxyz object will not QSY in early D710
models. Now fixed.<br>
<br>
> FFF.FFxyz objects of any format will not QSY the
FTM-350 (confirm?)<br>
<br>
Extra "0" on end of the +xxx or -xxx OFFSET format. The
THD72 will accept<br>
extra characters after the required +xxx or -xxx. These
will all give the<br>
proper offset:<br>
<br>
> 440.000MHz tOFF +500 Bob's radio <br>
> 440.000MHz tOFF +5000 Bob's radio <br>
> 440.000MHz tOFF +5000Bob's radio<br>
> 440.000MHz tOFF +5000000 Bob's radio<br>
> 440.000MHz tOFF +500Bob's radio<br>
<br>
BUT SHOULD N OT BE USED until confirmed all existing
radios can tolerate it.<br>
This was a proposed backwards-compatible future fix to
making the offset<br>
more human readable, because then we could recommend the
use of +5000<br>
instead of the +500. But this CANNOT BE USED until we
have surveyed all<br>
radios to see if ALL radios can properly set the offset
if the additional<br>
"0" is included. Or all radios are upgraded to do so<br>
<br>
Here are some other known issues for the Compatibility
table of position<br>
Comments:<br>
<br>
Leading space: (required, required-not, don't care) -
(Y, N, X)<br>
<br>
Xmits space: (Transmits leading space) - (Y, N)<br>
<br>
Requires "MHz": (Requires mixed case, allows any case)
- (Y, N)<br>
<br>
Requires "MHz_": (Requires trailing space) - (Y, N)<br>
<br>
Xmits MHz_: (Transmits trailing space) - (Y, N)<br>
<br>
Responds to +xxx and -xxx offsets - (Y, N)<br>
<br>
Transmits offsets +xxx and -xxx - (Y, N)<br>
<br>
Allows extra trailing zero so that +600 works, where
only +60 is IAW spec -<br>
(Y, N)<br>
<br>
<br>
<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>