<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
It's only a single-bit hit between his normal mbits: 010 and mbits:
000 for Emergency.<br>
<br>
I also looked at the lat/lons and given the number of warnings
coming out of aprs.fi, I decided that it was a wasted effort.<br>
<br>
Since the ToCall is the first thing transmitted, it even may be that
he doesn't have a long enough preamble to satisfy something along
the RF chain resulting in some garbling of the early bits of the
transmission.<br>
<br>
Only ears on the air in his vicinity will truly answer our
curiosities.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
<br>
<br>
<div class="moz-cite-prefix">On 8/8/2014 11:51 AM, andrewemt wrote:<br>
</div>
<blockquote cite="mid:SNT405-EAS63501F2AC2CA5564BCC8FAB8EE0@phx.gbl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>It is interesting that VE7HMW-9's packet tocall (destination)
callsign starts with all digits instead of letters, indicating
the Mic-E status bits are all zero. So, either someone is
"fixing" his tocall (maybe because it doesn't look like a valid
callsign, though this is worse), or he actually is sending
emergency. His latitude does look a little south for a
Canadian, but not unreasonably so for a mobile, considering
where his home fixed station is. You'd think that if those three
bits got mangled then more would have been mangled to give him a
totally ludicrous position instead of one relatively close to
home.</div>
<div><br>
</div>
<div>Just my $.02.</div>
<div><br>
</div>
<div>Andrew, KA2DDO</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-size:9px;color:#575757">Sent from my Verizon
Wireless 4G LTE smartphone</div>
</div>
<br>
<br>
-------- Original message --------<br>
From: "Lynn W. Deffenbaugh (Mr)" <a class="moz-txt-link-rfc2396E" href="mailto:ldeffenb@homeside.to"><ldeffenb@homeside.to></a> <br>
Date:08/08/2014 10:51 (GMT-05:00) <br>
To: TAPR APRS Mailing List <a class="moz-txt-link-rfc2396E" href="mailto:aprssig@tapr.org"><aprssig@tapr.org></a> <br>
Cc: <br>
Subject: Re: [aprssig] EMERGENCY test... <br>
<br>
<div style="background-color:#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="x_raw_line_err">2014-08-07 19:36:26 EDT: <b><a
moz-do-not-send="true"
href="http://aprs.fi/?c=raw&limit=&call=VE7HMW-9">VE7HMW-9</a></b>>461QTP,<a
moz-do-not-send="true"
href="http://aprs.fi/?c=raw&limit=&call=VE7DID">VE7DID*</a>,WIDE3-3,qAR,<a
moz-do-not-send="true"
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="x_raw_line_err">2014-08-07 19:38:26 EDT: <b><a
moz-do-not-send="true"
href="http://aprs.fi/?c=raw&limit=&call=VE7HMW-9">VE7HMW-9</a></b>>461QTP,<a
moz-do-not-send="true"
href="http://aprs.fi/?c=raw&limit=&call=VE7DID">VE7DID*</a>,WIDE3-2,qAR,<a
moz-do-not-send="true"
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="x_raw_line_err">2014-08-07 19:38:28 EDT: <b><a
moz-do-not-send="true"
href="http://aprs.fi/?c=raw&limit=&call=VE7HMW-9">VE7HMW-9</a></b>>4Y1PYW,WIDE1-1,qAR,<a
moz-do-not-send="true"
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="x_moz-cite-prefix">On 8/8/2014 10:31 AM, Keith
VE7GDH wrote:<br>
</div>
<blockquote 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>
</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="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</body>
</html>