<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
VE7HMW-9's emergency beacons are showing up at aprs.fi's raw
packets. However, they're flagged with issues, so they aren't
processed into his database.<br>
<br>
I suspect that there's a digipeater or IGate in the area that has
PASSALL enabled and is gating invalid packets to the APRS-IS causing
the Mic-E bits (mbits: below) to be 000.<br>
<br>
<span class="raw_line_err">2014-08-07 19:36:26 EDT: <b><a
href="http://aprs.fi/?c=raw&limit=&call=VE7HMW-9">VE7HMW-9</a></b>>461QTP,<a
href="http://aprs.fi/?c=raw&limit=&call=VE7DID">VE7DID*</a>,WIDE3-3,qAR,<a
href="http://aprs.fi/?c=raw&limit=&call=UBC39">UBC39</a>:`2Txm"Q>/]"3m}2004 BUICK REGAL=
<b>[Rate limited (< 5 sec)]</b></span><br>
type: location<br>
format: mice<br>
srccallsign: VE7HMW-9<br>
dstcallsign: 461QTP<br>
latitude: 46.19 °<br>
longitude: -122.9486666666667 °<br>
course: 253 °<br>
speed: 18.52 km/h<br>
altitude: -5 m<br>
symboltable: /<br>
symbolcode: ><br>
mbits: 000<br>
posresolution: 18.52 m<br>
posambiguity: 0<br>
comment: ]2004 BUICK REGAL=<br>
<br>
<span class="raw_line_err">2014-08-07 19:38:26 EDT: <b><a
href="http://aprs.fi/?c=raw&limit=&call=VE7HMW-9">VE7HMW-9</a></b>>461QTP,<a
href="http://aprs.fi/?c=raw&limit=&call=VE7DID">VE7DID*</a>,WIDE3-2,qAR,<a
href="http://aprs.fi/?c=raw&limit=&call=VA7REF-1">VA7REF-1</a>:`2Txm"Q>/]"3m}2004 BUICK REGAL=
<b>[Location changes too fast (adaptive limit)]</b></span><br>
type: location<br>
format: mice<br>
srccallsign: VE7HMW-9<br>
dstcallsign: 461QTP<br>
latitude: 46.19 °<br>
longitude: -122.9486666666667 °<br>
course: 253 °<br>
speed: 18.52 km/h<br>
altitude: -5 m<br>
symboltable: /<br>
symbolcode: ><br>
mbits: 000<br>
posresolution: 18.52 m<br>
posambiguity: 0<br>
comment: ]2004 BUICK REGAL=<br>
<br>
And then there's this interestingly corrupted packet:<br>
<br>
<span class="raw_line_err">2014-08-07 19:38:28 EDT: <b><a
href="http://aprs.fi/?c=raw&limit=&call=VE7HMW-9">VE7HMW-9</a></b>>4Y1PYW,WIDE1-1,qAR,<a
href="http://aprs.fi/?c=raw&limit=&call=VA7REF-1">VA7REF-1</a>:EGAL=
<b>[Unsupported packet format]</b></span><br>
srccallsign: VE7HMW-9<br>
dstcallsign: 4Y1PYW<br>
<br>
So it appears to this outside observer that there's something going
on between the RF environment and the APRS-IS. But if you actually
received the Emergency packets on your radio (and it wasn't a
third-party packet), then it would seem to indicate a bad digipeat
rather than a bad Igate.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
<br>
<div class="moz-cite-prefix">On 8/8/2014 10:31 AM, Keith VE7GDH
wrote:<br>
</div>
<blockquote cite="mid:53E4DF2C.3080905@rac.ca" type="cite">A few
times over the last week or so, a few emergency beacons have been
received from a VE7HMW-9, but the operator says he didn't have it
set to emergency. The emergency beacon was decoded by an FTM-400D
and also showed at findu.com, but not on aprs.fi.
<br>
<br>
For a test, I will be sending several emergency beacons from
VE7GDH-9 in a few minutes with a status text of...
<br>
<br>
"This is a test - NOT an emergency."
<br>
<br>
</blockquote>
<br>
</body>
</html>