[aprssig] bad paths and digipeaters?

scott at opentrac.org scott at opentrac.org
Mon Nov 29 20:33:47 EST 2004

Sounds like an ugly hack.  Better to just use that PIC to speak KISS and
take over all UI digipeating functions itself - then you can implement all
the path-trimming rules you want.


-----Original Message-----
From: aprssig-bounces at lists.tapr.org
[mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Wes Johnston
Sent: Monday, November 29, 2004 4:57 PM
To: aprssig at lists.tapr.org
Subject: [aprssig] bad paths and digipeaters?

Here's an idea... if you use a kpc3 or similar type TNC as a digipeater,
MON ON, and hook a basic stamp to the serial port.  The TNC will copy each
packet to the serial port just before digipeating, right?  Have the basic
read the packet, count the hops and if it determines that the count exceeds
local custom, have it interrupt the PTT line to the radio.  It could pull a
relay in to interrupt whilst watching the PTT pin from the TNC to release.
would keep the relay pulled in until the TNC released PTT, the let the relay
drop.  This would have the effect of allowing an external processor to
interrupt the TNC's access to the radio.  Each basic stamp (or PIC, or
could be programmed to respond, err inhibit, based on a different number of
hops determined by the local sys op.

As an example, a user sending out WIDE7-7 in a path would be digipeated by
kpc3 firmware.  But if this PTT interrupter saw WIDE7-3, and the digipeat
limit was set to 3, then it would interrupt the PTT when the tnc tried to
digipeat WIDE7-3.


aprssig mailing list
aprssig at lists.tapr.org

More information about the aprssig mailing list