Order Tray | Contact Us | Home | SIG Lists

[aprssig] WinLink Stations on 144.39

Robert Bruninga bruninga at usna.edu
Thu Feb 3 15:27:44 UTC 2005


>>> jdbandman at earthlink.net 2/2/05 11:04:54 PM >>>
>I only noticed THREE stations listing 144.39. 
>Is it possible that these are simply typing errors 
>when the operator INTENDED to put in 144.93???

I dont think there is any problem here.  If I lived in the
middle of Mississippi and only saw 10 other people
on my map over the entire state and could only 
hear my local digi, and  thee channel is 99% quiet,
yet I was an avid localcommunications supporter, 
I might set up a WinLINKnode at my house just in case....

COnversly, If I did this anywhere where the net was
saturated (as in most populated areas), then
1) It wouild be dumb, because all the APRS QRM would
    make it basically useless
2) My peers would quickly inform me how stupid it was

SO I think this is not a problem to get concerned about
until all the facts about a particuolar installation are
considered..  THis is HAM radio.  Sometimes this all-
knowing-all-seeing perspective of the global APRS
and the WEB, tends to allow us to try to kibitz from
afar when the local network is nothing at al like maybe
the one in our area...

Just a thought
Bob






A.J. Farmer (AJ3U) wrote:

> I got a very quick reply from Steve, K4CJX.  He assured me that
operation of
> Winlink TelPac stations should not be happening on 144.39.  He's
going to
> put out a reminder on the Winlink reflector to make sure that people
know
> not to operate on 144.39.  If you are aware of a Winlink TelPac node
> operating in your area on 144.39, he asked that you notify him so
that he
> can address it directly with the node operator.
> 
> 73!
> 
> A.J. Farmer, AJ3U
> http://www.aj3u.com 
> 
> 
> -----Original Message-----
> From: A.J. Farmer (AJ3U) [mailto:ajfarmer at spenet.com] 
> Sent: Wednesday, February 02, 2005 10:09 PM
> To: 'TAPR APRS Mailing List'
> Subject: RE: [aprssig] WinLink Stations on 144.39
> 
> I just sent a friendly e-mail to K4CJX about this.  He is listed as
a
> primary contact on the Winlink website.  Hopefully he can help steer
Winlink
> users away from setting up on 144.39.
> 
> On a related note, it sure would be handy to have Winlink node
objects
> available on APRS just like what is being done for IRLP and Echolink
nodes.
> I believe this was discussed a while back.  I also mentioned this in
my
> e-mail to K4CJX for what it is worth.
> 
> Imagine arriving in a new area and seeing local IRLP, Echolink, and
Winlink
> node objects on your APRS map.  Now that is useful!!
> 
> A.J. Farmer, AJ3U
> http://www.aj3u.com 
>  
> 
> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org
[mailto:aprssig-bounces at lists.tapr.org] 
> On Behalf Of A.J. Farmer (AJ3U)
> Sent: Wednesday, February 02, 2005 9:47 PM
> To: 'TAPR APRS Mailing List'
> Subject: [aprssig] WinLink Stations on 144.39
> 
> I made a disurbing discovery today.  There are 15 registered WinLink
nodes
> operating on 144.39:
> 
> http://www.winlink.org/status/TelpacEx.aspx 
> 
> I found this out by accident when searching for a local node and
found one
> registered on 144.39!!
> 
> A.J. Farmer, AJ3U
> http://www.aj3u.com 
> 
> 
> _______________________________________________
> 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 
> 

-- 
73 de Jim, KU0G


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




More information about the aprssig mailing list