<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Arial">The dual launch announced earlier is over. The
final summary page is now on my website at:<br>
<br>
<a class="moz-txt-link-rfc2396E" href="http://wa8lmf.net/LiveTrack"><http://wa8lmf.net/LiveTrack></a><br>
<br>
Major APRS-IS issues were evident <br>
<br>
</font>
<p><font face="Verdana">The actual downlink for APRS data from the
balloons to the ground was on a private channel, that was then
retransmitted on the usual 144.39 frequency to find it's way to
igates and the APRS-IS </font><font face="Verdana">(APRS
Internet System)</font><font face="Verdana">.</font></p>
<p><font face="Verdana">Tracking of these launches were marred by
severely-delayed packets being injected into the APRS-IS. This
causes more recently reported data to be superseded by older
data. The result is tracks that "hyper-jump"
forward-backward-forward-backward. In the case of aerial
vehicles like balloon, they also bounce up and down in
altitude. (Note the "grass" of vertical jumps on the AE0SS-11
vertical profile graph, and the hiccups on both profiles.) </font>
</p>
<p><font face="Verdana">Delays in passing packets from the TNC to
the attached computer is a known bug in KPC3+ TNCs operated in
KISS mode connected to a computer. The problem appears randomly
after several days or weeks of operation, and can be cleared by
issuing the RESET command to the TNC or by cycling it's power
OFF and then back ON. This problem primarily affects home
digi/igate stations, since they typically use a computer-based
setup. It does not affect KPC3+ TNCs operating in stand-alone
mode, as would be the case with most remotely located
digipeaters. </font>
</p>
<p><font face="Verdana">Further, these launches were marred by
one or more TNCs at digipeater or igate sites operating in
PASSALL mode (a.k.a. "junque" mode). Numerous posits with
impossible values were passed including elevations hundreds of
feet below sea level, wild hyper-jumps 100s of miles at
right-angles to the track path, and multiple corrupted versions
of the two balloons' callsigns.</font></p>
<p><font face="Verdana">The tracks were further confused by the
balloon trackers apparently being powered up (for a test??) on
the south side of the Denver metro area, before being taken to
the launch site. Or were these posits sent before the GPS
receivers achieved lock at the launch site?<br>
</font></p>
<p><font face="Verdana"><br>
</font></p>
<hr size="2" width="100%"><br>
--<br>
<br>
Stephen H. Smith wa8lmf (at) aol.com <br>
EchoLink Node: WA8LMF or 14400 [Think bottom of the 2M
band]<br>
Skype: WA8LMF<br>
Home Page: <a class="moz-txt-link-freetext" href="http://wa8lmf.net">http://wa8lmf.net</a><br>
<br>
===== Vista & Win7 Install Issues for UI-View and Precision
Mapping =====<br>
<a class="moz-txt-link-freetext" href="http://wa8lmf.net/aprs/UIview_Notes.htm#VistaWin7">http://wa8lmf.net/aprs/UIview_Notes.htm#VistaWin7</a><br>
<br>
*** HF APRS over PSK63 ***<br>
<a class="moz-txt-link-freetext" href="http://wa8lmf.net/APRS_PSK63/index.htm">http://wa8lmf.net/APRS_PSK63/index.htm</a><br>
<br>
"APRS 101" Explanation of APRS Path Selection & Digipeating <br>
<a class="moz-txt-link-freetext" href="http://wa8lmf.net/DigiPaths">http://wa8lmf.net/DigiPaths</a> <br>
<br>
<br>
<p><font face="Verdana"><br>
</font>
</p>
<br>
</body>
</html>