[aprssig] emergency beacon wide1-1ADDENDUM

[Bob Bruninga]

> I did alittle more snooping and noticed 
> that the compressed and non-compressed 
> packets are quite different times...
> WIDE1-1>N9MXQ-8... compressed ... TinyTrak3
> WIDE1-1>N789PH...  compressed ... KD0CVN-1 RV-9A
> WIDE1-1>N9MXQ-8...  A=000764
> WIDE1-1>N9MXQ-8...  A=000803

WIDE1-1 packets can come from anywhere in the world.  Remember, that is the power of a WIDE1-1 digi, in that it can be built from ANY old TNC without any special digi code, because all it does is digi the fixed callsign of "WIDE1-1".

THe correct way to do this is to use a TNC that at least supports an ALIAS of WIDE1-1.  It will work as a digi, but it will not do callsign substitution...

But if someone does not understand ALIASES, and actually makes his TNC MYCALL be WIDE1-1, then it will still work as a WIDE1-1 digi, but then its own beacon will be originated from "WIDE1-1" instead of its FCC call.  This is not good practice, though it doesnt hurt anything.  It just gets confusing.  

SO it appears that there is a fill-in WIDE1-1 digi within range of the N9MXQ digipeater that is missconfigured with the MYCALL of WIDE1-1 instead of the proper MYALIAS of WIDE1-1.

Bob, WB4APR
>
>Also, that the un-compressed altitudes are pretty low for around here - groung level is 800-900 MSL.  Are those the MI locations?
>
>--
>73, Steve, K9DCI
>You know that sea of entropy we were going to drown in?  Well, upon closer examination, it turned out to be ignorance.  S. Noskowicz 1987
>
>
>--- On Sat, 3/14/09, Steve Noskowicz <noskosteve at yahoo.com> wrote:
>
>> From: Steve Noskowicz <noskosteve at yahoo.com>
>> Subject: Re: [aprssig] emergency beacon called wide1-1 today
>> To: "TAPR APRS Mailing List" <aprssig at tapr.org>
>> Date: Saturday, March 14, 2009, 9:36 PM
>> Hi guys,
>>    
>>  I did a little snooping of these packets to see if any of
>> this stuff stuck (in my head), and I may or may not be
>> confused.  So am I getting warm?
>> 
>>  It's Saturday 8:40 pm and I know I'm after the
>> fact and not an expert, but looking at the raw packets on
>> Findu with the time stamp (...&time=1)
>> 
>> 1 - I don't know the TT#, so,   is this an APRS
>> message?
>> 20090314025953,WIDE1-1>N9MXQ-8,WIDE2-1,qAR,W9DRR-10:>TinyTrak3
>> v1.1
>> 
>>   ANYWAY, on the next one, isn't this a Mic-E packet
>> (it "looks" like one)?
>> 20090314143643,WIDE1-1>N789PH,WIDE2-1,qAR,W9DRR-10:`tR7+{A'/"S)}KD0CVN-1
>> RV-9A
>>   THEREFORE isn't the "N789PH" Mic-E DATA
>> (destination address field - Latitude digits) that only
>> LOOKS like an "N" number ??
>>   Checking the spec, "N" isn't a valid Mic-E
>> Destination Address field character (if I read the spec
>> correctly M, N and O are skipped) - this is mangled data, no
>> ??
>> 
>> Then, these next two are NOT in a compresssed format!  Can
>> TT-3 do both?  
>> 20090314160005,WIDE1-1>N9MXQ-8,WIDE2-1,qAR,W9DRR-10:!4215.42N/08850.45W>001/000/A=000764
>> 20090314160300,WIDE1-1>N9MXQ-8,WIDE2-1,qAR,W9DRR-10:!4216.03N/08851.01W>326/007/A=000803
>>    I didn't bother to check, but they do look near me
>> somewhere.
>> 
>> Now let's look at the time [my punctuation] of that
>> second "N" number packet:
>> 2009 03-14 14:36:43   [cont next line]
>> ,WIDE1-1>N789PH,WIDE2-1,qAR,W9DRR-10:`tR7+{A'/"S)}KD0CVN-1
>> RV-9A
>> 
>> Then, go to the findu Packets for the 'real'
>> station call "N789PH" 
>> around the SAME time:
>> 2009 03-14 14:36:40   [cont next line]
>> ,N789PH>TR1P3Y,N9ZIP-15,N8IYX-4,WIDE2*,qAR,NK8X-3:`tW$+qA'/"S*}
>> 
>>   Now, comparing the two Mic-E Information data (Longitude
>> digits) fields, WIDE1-1     `tR7+{A'/"S)  
>> N789PH      `tW$+qA'/"S*}
>>   I realize that it is too late in the day to attempt this
>> field and quit.
>> 
>>   Is this a matter of confusing two different stations
>> because of the mangled Mic-E Latitude (Destination address
>> field) data - that "looks" like the N-number ? 
>> Huh?
>> 
>> My brain hurts.
>> --
>> 73, Steve, K9DCI
>> You know that sea of entropy we were going to drown in? 
>> Well, upon closer examination, it turned out to be
>> ignorance.  S. Noskowicz 1987
>> 
>> 
>> --- On Sat, 3/14/09, Rusty Hemenway
>> <nnn0fjk at gmail.com> wrote:
>> 
>> > From: Rusty Hemenway <nnn0fjk at gmail.com>
>> > Subject: Re: [aprssig] emergency beacon called wide1-1
>> today
>> > To: "'TAPR APRS Mailing List'"
>> <aprssig at tapr.org>
>> > Date: Saturday, March 14, 2009, 8:21 PM
>> > Is there someone in the area that can give him a call
>> and
>> > help him set it up
>> > correctly? 
>> > 
>> >  
>> > 
>> > From: aprssig-bounces at tapr.org
>> > [mailto:aprssig-bounces at tapr.org] On Behalf
>> > Of Greg D.
>> > Sent: Saturday, March 14, 2009 5:43 PM
>> > To: aprssig at tapr.org
>> > Subject: Re: [aprssig] emergency beacon called wide1-1
>> > today
>> > 
>> >  
>> > 
>> > Last position (about 30 min ago) shows the plane in
>> front
>> > of the hangar at
>> > the Anoka County airport.  Presumably he'll be
>> home
>> > soon.  Google says it's
>> > about a 20 minute commute.
>> > 
>> > Greg  KO6TH
>> > 
>> > 
>> > > From: ve7gdh at rac.ca
>> > > To: aprssig at tapr.org
>> > > Date: Sat, 14 Mar 2009 13:17:29 -0700
>> > > Subject: Re: [aprssig] emergency beacon called
>> wide1-1
>> > today
>> > > 
>> > > Chuck W3YNI wrote...
>> > > 
>> > > Subject: Re: [aprssig] emergency beacon called
>> wide1-1
>> > today
>> > > 
>> > > > Actually spoke to some folks from CAP. Gave
>> them
>> > what I believed
>> > > > was the tailnumber at the time (now
>> confirmed)
>> > along with last known
>> > > > coordinates from the beacon.
>> > > >
>> > > > Guy I spoke to is a ham and knew what APRS
>> is -
>> > he sent it up the
>> > > > chain.
>> > > 
>> > > and posted by Rusty (K1GGS?)...
>> > > 
>> > > >
>> >
>> WIDE1-1>N789PH,WIDE2-1,qAR,W9DRR-10:`tR7+{A'/"S)}KD0CVN-1
>> > RV-9A
>> > > 
>> > > The odd thing is that the "callsign" is
>> > WIDE1-1 and N789PH (presumably
>> > > the tail number) is the destination instead of
>> the
>> > "callsign". The
>> > > owners callsign appears to be KD0CVN as indicated
>> in
>> > the status text.
>> > > Don't know why he would include an SSID
>> there!
>> > Also according to the
>> > > status text, it's an RV-9A.
>> > > 
>> > > I know the above doesn't show a path of
>> WIDE1-1,
>> > but looking at the
>> > > tracker that IS using a "callsign" of
>> > N789PH...
>> > > 
>> > >
>> http://aprs.fi/?c=raw&call=N789PH&limit=1000
>> > > 
>> > > it is using a path of WIDE1-1,WIDE2-1. Surely if
>> it
>> > really is a plane
>> > > wouldn't use a path of WIDE1-1,WIDE2-1 - hi!
>> > > 
>> > > Also, looking at
>> > http://aprs.fi/?c=raw&call=WIDE1-1&limit=50
>> > > it is possible that there is more than one
>> station
>> > with a misconfigured
>> > > "callsign" of WIDE1-1.
>> > > 
>> > > 2009-03-14 14:36:43 UTC:
>> > > WIDE1-1>N789PH,WIDE2-1,qAR,W9DRR-10
>> > > :`tR7+{A'/"S)}KD0CVN-1 RV-9A [Invalid
>> > characters in mic-e packet]
>> > > 
>> > > There's that "KD0CVN-1 RV-9A"
>> again...
>> > or possibly it's one and the same
>> > > beacon. What a tangled web it is!
>> > > 
>> > > The callsign of WIDE1-1 must have been programmed
>> in
>> > accidentally. While 
>> > > it is possible that a mangled MIC-E packet may be
>> > involved for the 
>> > > "emergency" beacon, perhaps it would be
>> a
>> > good recommendation for planes 
>> > > to not use MIC-E to lessen the chance of a
>> mangled
>> > MIC-E packet making 
>> > > it look like an emergency beacon. Just a thought.
>> > > 
>> > > 73 es cul - Keith VE7GDH
>> > > --
>> > > "I may be lost, but I know exactly where I
>> > am!"
>> > > 
>> > > 
>> > > _______________________________________________
>> > > aprssig mailing list
>> > > aprssig at tapr.org
>> > >
>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>> > 
>> >   _____  
>> > 
>> > Windows LiveT Groups: Create an online spot for your
>> > favorite groups to
>> > meet. Check it out.
>> >
>> <http://windowslive.com/online/groups?ocid=TXT_TAGLM_WL_groups_032009>
>> > 
>> > 
>> > _______________________________________________
>> > aprssig mailing list
>> > aprssig at tapr.org
>> > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>> 
>> 
>>       
>> 
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
>
>      
>
>_______________________________________________
>aprssig mailing list
>aprssig at tapr.org
>https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig