[aprssig] Pocket Tracker???

[Wes Johnston]

That's easy enough.... you have a 2nd receiver on 144.39.  You wire the
TNC's XCD input to the squelch on that receiver.  Kantronics did this
internally with their kpc4 dual 1200 TNC years ago... it has a "one
radio" command that will prevent either 1/2 of the TNC from transmitting
if the other 1/2 sees a carrier.  You an do the same with a kpc3's XCD
input.

Wes

Stan Coleman [NØYXV] wrote:
> First time I heard this idea it sounded like a simple easy way to setup an alt
> input frequency. After I thought about it for a while I came up with only one
> possible problem with it. If the Digi is listening on 144.99 and transmitting
> on 144.39 it won't know about possible collisions it's creating on 144.39.
> 
> Just an idea but wouldn't it be better to try this idea with an IGate instead of
> a Digi? Then you could transmit and receive on the same alt frequency. You could
> even setup the IGate to tranmit certian calls from APRS-IS into your alt
> frequency system. This would allow you to transmit from 144.39 over to your alt
> frequency. At least this way you wouldn't create collisions on an already busy
> channel.
> --
> Totally mad. Utter nonsense. But we'll do it because it's
> brilliant nonsense.
>      - Douglas Noel Adams
> 
> 
> Quoting Robert Bruninga <bruninga at usna.edu>:
> 
> 
>>An ALT-INPUT digi works by listening on 144.99 and
>>digipeating over to 144.39 so that these trackers
>>tracks join in with traffic on the main channel, but
>>with local priority.
>>
>>Bob, WB4APR
>>
>>_______________________________________________
>>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
> 
> 
>