[aprssig] winlink

[Robert Bruninga]

Jjim,
Since D7's can only see the first 20 bytes of the
text, the freq will not be seen by one of them.  And I
see no reason for the grid nomenclature at all, since
APRS can see exactly where it is.  And the kenwood
COMPUTES the grid on receipt.

I'd use the CALL of the node as the name.  And if
it is 4 letters then make it K4HG-link
or 5 letters make it K4HGA-lnk
or 6 letters make it KA4HGA-lk
then for the first 20 chars of the comment field, make it
WinLINK, 145.750 at AA County EOC or what ever

On the Kenwood  D7 this would display as:

WA6OFT:
WinLINK,
145.750 at

and on the D700, the additional 8 more characters will show,.

Bob

>>> spider at rivcom.net 12/29/04 11:27 PM >>>

----- Original Message ----- 
From: "Robert Bruninga" <bruninga at usna.edu>
To: <aprs at kd4rdb.com>; <aprssig at lists.tapr.org>
Sent: Wednesday, December 29, 2004 3:14 PM
Subject: Re: [aprssig] winlink


> Re; WinLINK:
>
> Yep, I think so too.  ALready today, I have been monnitoring
> the local WINlink channel and have seen another APRS user
> use it.  I think it is ideal for the bulk traffic and the ARRL
> seems to endorse it.
>
> Today, I'm going to add a LOCAL object for the local
> WinLINK station (on PARS) so that locals can see it on their
> radios.  Note, this is a LOCAL-DIRECT object so it does no
> damage beyond the area where it can be used.
>
> Bob, WB4APR

Bob,

All the WinLink Telpac and HF nodes are Shown on FireNet.  If you
connect 
there and watch, you will see them.
Please check the format we are using:
WLNK-3>APWL2K,TCPIP,WA6OFT-1,WA7RAT-10,WIDE2-1* <UI>:;DM24UD 
*300403z3408.75N/11417.50WnWL2K Port,WA6OFT,145.550,1200,PARKER, AZ

It gives any Igate connected to FireNet the ability to Gate these
objects 
locally to RF.  And the reason we encourge this is the same exact reason
you 
just explained.  APRS users can see where the nodes are without being 
connected to the internet.
As an example, An Igate connected to a filtered port might have a range 
filter set at 100km or whatever his local area is.  he would then gate
any 
Telpac node object that was within his filter range.

73

Jim, WA6OFT





>
>>>> aprs at kd4rdb.com 12/29/04 3:40:33 PM >>>
>>From what I've read so far about winlink, and the power point show, it
> looks to
> me like winlink is a winner.  I haven't even downloaded the software
> yet, but I
> see that it allows us to divert email automatically from internet to
> radio if
> internet fails.  It uses standard email programs like MS outlook and
> eudora.
> The end user doesn't need to know anything except the name of the
> winlink mail
> server to program into his email program (in the case of an EOC lan).
> wow...
>
> It seems that winlink has done for HF email what aprs did for packet
> radio...
> made it extremely simple to use.  And the less time we spend
finegeling
> the
> system, the more time we can spend communicating.  wow!
>
> http://www.winlink.org/Presentations/ARES.ppt is a great slide show,
> but a
> little confusing to me a times... wish I had a narrator!  Some of the
> slides
> are a tweek "busy"....  Can't wait to find out more!
>
> Looks like we have a hand in glove complimentary system to go right
> along with
> APRS.
>
> Wes
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
> 




_______________________________________________
aprssig mailing list
aprssig at lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig