[aprssig] KPC-9612 Firmware

Robert Bruninga bruninga at usna.edu
Tue Feb 13 10:11:16 EST 2007


> > Where can I purchase firmware for the KPC-9612 that 
> > will provide APRS digipeating capability? 
> 
> I assume it only has basic MYCALL and MYALIAS digipeating?

Maybe it will also digipeat on its MYNODE and MYBBS callsigns
too?  In that case you could have four possible aliases.
WIDE1-1, WIDE2-2, WIDE2-1 and WIDE3-3 and the MYGATE call will
digipeat across ports, though I am not sure what that could be
used for since the other port is 9600 baud.

Ah, you could make MYGATE be WIDE3-3 and then all 1200 baud
WIDE3-3 packets would get digipeated at 9600 baud on the other
port so these could still be monitored by the sysop on another
frequency, but they would not add QRM on the APRS channel if it
was an N=2 area.

Just brainstorming... Bob


> Then about the only thing it can do is WIDE1-1 and WIDE2-2
> digipeating.  In a pinch, it can be used as follows:
> 
> Set MYCALL to WIDE1-1 and MYALIAS to WIDE2-2 and it will
support
> the first hop of just about everyone who is properly using the
> New-N paradigm.  But it will not bring in any second hops from
> out of area.
> 
> Or set MYALIAS to WIDE2-1 if many people in your area are
using
> the mobile path of WIDE1-1,WIDE2-1 and you will pick up their
> second hop and the second hop of any fixed stations using
> WIDE2-2 paths.
> 
> Problem is if anyone else in the world is using this trick,
they
> your digi posits on FINDU will ping-pong.  But that is a
APRS-IS
> problem and not a local RF problem.  But the ham call in the
> beacon.
> 
> Bob, WB4APR
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 





More information about the aprssig mailing list