[aprssig] Packet routing, path specification.

[scott at opentrac.org]

Sort of.  I've got a KPC-3 in the garage with TWO OpenTrackers hanging off
the radio port with simple 'Y' connectors.  One does weather and the other
does telemetry.  The main limitation is that the trackers can't hear the TNC
and don't know when it's transmitting.  That could probably be fixed with a
bit more wiring, but then it's not just an off-the-shelf 'Y' cable.  I avoid
the problem by coordinating the beacon times, but that wouldn't work for
something active like a digipeater.

Scott
N1VG

> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org 
> [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Jason Winningham
> Sent: Thursday, June 23, 2005 8:04 AM
> To: TAPR APRS Mailing List
> Subject: Re: [aprssig] Packet routing, path specification.
> 
> 
> On Jun 23, 2005, at 9:39 AM, <scott at opentrac.org> wrote:
> 
> > Hmm, maybe I ought to offer a 'bounty' to get rid of those.  Like 
> > maybe 50% off an OpenTracker if you promise to take your old, dumb 
> > tracker off the air.  =]
> 
> Scott, didn't you have a way figured out for the OT to share 
> a radio with a TNC?
> 
> If so, TNC users could either add a tracker to their existing 
> rig and improve the network, _or_ they could sell the TNC, 
> buy an OT, and probably have $$ left over...
> 
> -Jason
> kg4wsv
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 
>