[aprssig] TEMPn-N and callsign digipeating

[Robbie, wa9inf]

And of course, here we go again with the "blind" transmitting of all the 
.99 to .39 stuff. Unless of course, you do the "gentleman's" way of 
operating and have a receiver on .39 to "hold off" the tnc on from 
keying the .39 transmitter until the channel is clear??

Robbie

William McKeehan wrote:

>If all of the TEMPn-N digi's are on 144.99, then when you transmit back out on
>144.39, there will not be any digi's around to hear it, right?
>
>On Sun, May 28, 2006 6:05 pm, Robert Bruninga said:
>  
>
>>>>>wa7nwp at jnos.org 05/28/06 12:54 PM >>>
>>>>>          
>>>>>
>>>... getting some TEMPn-N activity here for Field Day.
>>>...   Does a TEMPn-N D700 mobile digi automatically
>>>digipeat on the stations callsign or will it be necessary
>>>to add it to the UIDIGI settings?
>>>      
>>>
>>Im not sure I follow, but TEMPn-N packets should work
>>just exactly like WIDEn-N packets, but of course will
>>only go through other TEMPn-N digis.  But since all
>>Field Day operations is on 145.01, instead of 144.39,
>>then other digi calls are not involved.
>>
>>Now this does bring up anotehr good idea for EMERGENCY
>>preparedness.  That is, local GURU's could decide what
>>local battery backed up-reliable digis BEST serve their
>>area in times of disaster, and maybe add TEMPn-N
>>support to those SPECIAL digis.  THis way, when the
>>disaster hits, and we might need to depend on TEMPn-N
>>paths, a few widely dispersed TEMPn-N digis could
>>really provide some support.
>>
>>BUT to get them away from any APRS QRM, maybe these
>>TEMPn-N digis sshould also be on another frequency.
>>AND since there is no way to add TEMPn-N to existing
>>digs (all only support one kind of traceable n-N at a time).
>>Maybe we are talking here about adding TEMPn-N
>>to the INFRASTRUCTURE already on a local underused
>>digital channel.  Then emergency APRS traffic can travel
>>WELL on this alternate channel without the QRM from
>>144.39.
>>
>>MAYBE the best place for this network is the APRS alt-input
>>channel of 144.99!   Remember, that being +600 from
>>144.39 lets this be an ideal place for low power trackers
>>to get into the network.  But it couild also be the backup
>>TEMPn-N network too!  SInce TEMPn-N would not normally
>>be used except in emergent situations...
>>
>>OK, how's this...
>>APRS ALT-INPUT digis listen on 144.99 and digipeat to
>>144.39 for low power trackers and special opeations.
>>These ALT-INPUT digis use the UIDIGI ALIAS of
>>WIDE1-1 so that mobiles and HT's using W1-1,W2-1
>>will get digipeated over to the 144.39 frequency.
>>
>>BUT this same digi has TEMPn-N in its UITRACE parameter
>>so that it also acts as a TEMPn-N (as a final hop over to
>>144.39)....  This way, these HIGH-SITE digipeaters that
>>are listening for low power trackers, can also be our
>>back-up network for listening to TEMPn-N digis (700
>>mobiles) when needed!   Wow, is this a good idea, or am
>>I missing something?
>>
>>Bob, Wb4APR
>>
>>
>>I'm thinking we may have to always add the local call
>>as one of the four UIDIGI aliases.
>>
>>73,
>>Bill
>>
>>_______________________________________________
>>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
>>
>>    
>>
>
>
>  
>