[wxsig] Changing T238+ destination callsign

[John Koster]

Wow, I really know nothing about APRS.  However, this really surprises me.  
If I'm understanding what I've read in the last couple of postings, a
station sending APRS is in effect broadcasting to a specific target
application by destination address?  I always thought everything was a
general broadcast to anyone listening (ignoring for the moment all the
confusing digipeater stuff).  I thought the destination address of a UI 
frame was irrelevant.

I always thought the receiving application looked at everything that came
in and filtered information to be displayed based on stuff embedded in the
data stream and only digis paid attention to the address field.

Please tell me that the applications have a way to open up to all APRS 
packets.  

-- 
73,
John, W9DDD

On Sat, 25 Feb 2006, George wrote:

> Will,
> The combinations of the following letters as destination addresses are 
> all reserved according to the APRS Protocol specification ver. 1.0.1
> APWxxx to WinAPRS S/W
> APXxxx to X-APRS, used also by XASTIR
> So APWX1W seems to conflict with the WinAPRS.
> See Chapter 4: APRS Data in the AX.25 Destination and Source Address 
> Fields in the above document.
> Note that also exist and other applications that use their own 
> destination addresses not mentioned in the document, such as OpenTracker 
> (APOT1), UI-View (APUxxx) e.t.c.
> Using AP1WX seems ok but I haven't see any address having a number as a 
> third character though the specs say that AP* is ok with * meaning up to 
> a total 6 (including AP) ALPHANUMERIC characters.
> Anyway ask Bob, WB4APR, for AP1WX. Maybe he maintains some form of a 
> list of the registered applications.
> 
> 73 de George SV2DOF
> 
> _______________________________________________
> wxsig mailing list
> wxsig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/wxsig
>