Order Tray | Contact Us | Home | SIG Lists

[aprssig] Gating Objects from Internet to RF (fina?l)

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Wed Jul 22 16:40:46 UTC 2009


The only mod I'd make is that the source call be the station's call.  We 
are beaconing positions here, but OBJECTs.  I'll be suppressing any 
object ID that I've seen on APRS-IS in the recent past (2 weeks 
currently) not created by my script.  There will be no collisions nor 
co-opting of other stations by the originating call, only objects that 
appear to be owned by that station (the information is certainly owned 
by that station) that were injected by someone else on their behalf.

I have not yet seen an issue with sourcing the packet from the station's 
callsign.

Lynn (D) - KJ4ERJ

Robert Bruninga wrote:
> We hashed most of this all out a few years ago back when we
> first got into discussions with Echolink to put out APRS info.
> I still like the format we came up with back then and the one we
> eneded up with in the APRS frequency spec for Echolink nodes:
>
>   
>> HEADER:  KJ4ERJ>APELNK: 
>> POSIT:   ;EL-255256*211554z5125.53NE00604.37E0
>> COMMENT: 438.700MHz T000 Rxxm STATUS CALL ...
>>     
>
> This will display on the existing 10,000+ kenwoods as:
>
> +------------+
> | EL-123456  |
> | 438.700MHz |
> | Tnnn Rxxm  |
> | STATUS..   | CALL ... is only viewable on bigger cilents
> +------------+
>
> And the Echolink node callsign will show up on newer radios and
> all other APRS clients to the maximum length allowed.  
>
> HOWEVER.  I do think we can improve this a bit, and simply take
> the single letter abbreviation for the STATUS and combine that
> with the CALLSIGN in the last line so that ALL useful
> information is provided to the mobile operator.  Here is that
> proposal:
>
> HEADER:  KJ4ERJ>APELNK: 
> POSIT:   ;EL-255256*211554z5125.53NE00604.37E0
> COMMENT: 438.700MHz T000 Rxxm S CALL
>
> This will display as:
>
> +------------+
> | EL-123456  |
> | 438.700MHz |
> | Tnnn Rxxm  |
> | S CALL..   |
> +------------+
>
> The only problem is that there is only 6 bytes for the CALL, and
> so the -R or -L is missing to the mobile operator, but I don't
> think that is important information for the mobile operator?
> Does it make any difference?  It will show on longer displays or
> on 4 letter calls.  
>
> The typical mobile operator's use of this info is to MESSAGE a
> buddy and say "CALL ME ON EL-123456".  And he doesn't even need
> the call, just the node number.
>
> Here are the status bytes provided by Lynn:
> F = Offline
> N = Online
> C = Conference
> B = Busy
>
> Anyway, I think that about summarizes everyon's comments
>
> Bob, Wb4APR
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
>   




More information about the aprssig mailing list