[aprssig] Digipeater Symbol Overlays

David Andrzejewski david at davidandrzejewski.com
Wed Oct 19 10:39:52 CDT 2016


I am a bit confused now. 

My station NEWBRY is both a high-profile digipeater and a two-way igate. 

I am currently using the T& symbol, because it transmits IS packets with a WIDE2-1 path. And that's what symbols-new.txt says to use. 

Is that correct, or should I use I# as Kenneth's notes state?

It seems like perhaps I# would be better, because although that doesn't indicate that it's a two-way igate, it does indicate that it is both a digipeater and igate, which T& does not. 

- Dave


-- 

David Andrzejewski
E-mail/iMessage/Jabber: david at davidandrzejewski.com
PGP Key ID: 5EBA8A72


> On Oct 18, 2016, at 17:37, Frank Knobbe <k4fhk at knobbe.us> wrote:
> 
>> On Mon, 2016-10-17 at 23:21 -0700, Kenneth Finnegan wrote:
>> 
>> My suggestion for a suggested set of Digipeater overlays for us to
>> promote to users is as follows:
>> 
>> /# - Generic WIDEn-N digipeater
>> 1# - WIDE1-1/direct-only digipeater
>> A# - Alternate input (i.e. 144.990MHz) digipeater
>> I# - I-gate equipped digipeater
>> S# - SSn-N local net alias digipeater
>> X# - eXperimental digipeater
> 
> 
> Would it make sense to reserve a symbol, say C#, for cross-band digi?
> One that digis' VHF onto UHF? (The other direction may not be
> desirable).
> 
> Cheers,
> Frank
> 
> 
> PS: On the viscous digi thread, I personally see it more of a mode of
> operation. I think with any symbol, one should focus on the primary
> reason/task for the device. For example, my TX Igate is a standard Igate
> symbol with T overlay, but it also viscously digipeats anything our high
> digis didn't catch (like a fill-in-as-needed digi...lol). But, it's
> primarily a TX Igate, so I chose that symbol.
> 
> Since the viscous digi is primarily a direct-only digipeater, I think a
> 1# would be more appropriate. The fact that the direct-only digi is also
> viscous seems secondary, at least to me.
> 
> 
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20161019/4aa9bb30/attachment.html>


More information about the aprssig mailing list