Order Tray | Contact Us | Home | SIG Lists

[aprssig] PACCOMM TNC & WIDEn-N clarification

Brad [VE3BSM] lists.nospam at bpsmicro.com
Fri Oct 21 12:14:01 UTC 2005


Thanks all. I'm not sure if putting in a hard-coded digi call is a great
idea in all cases, since it tends to make your beacons out rather
"directional". The WIDE2-1,WIDE2-1 approach seems ideal.

As it turns out, after discussing this exercise with the digi owner, we're
going to move forward with an "upgrade" to UIDIGI for both his PacComm-based
digis. 

-----Original Message-----
From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org]
On Behalf Of Robert Bruninga
Sent: Thursday, October 20, 2005 11:31 PM
To: aprssig at lists.tapr.org; k9opo-1 at sbcglobal.net
Subject: Re: [aprssig] PACCOMM TNC & WIDEn-N clarification

Ah yes!  In fact, thats what I thought it said.
Ill go fix it...   Bob

>>> k9opo-1 at sbcglobal.net 10/20/05 11:23 PM >>>
At 10:16 PM 10/20/2005, Robert Bruninga wrote:

>But I now see this confuses people and appears to contradict other 
>writings.  Maybe I should change that to FIXED stations in the vicnity 
>of those old digis should use the path of WIDE2-1,WIDE2-1 etc..

Seems like FIXED stations should be using the actual digi callsign first,
then it doesn't matter what kind of a TNC it is or how it's setup.

Roger Grady  K9OPO





More information about the aprssig mailing list