[aprssig] KPC3+ beacons

Robert Bruninga bruninga at usna.edu
Wed Apr 9 20:10:23 EDT 2008


> Our club just installed a KPC3+, firmware v9.1 
> as a digi.... However, the digi (W5RRR-1) is not 
> showing up as having been igated. Here's 
> the settings:

You are missing the "/" separator between LAT and LONG.
But in this case, you want it to be a New-N paradigm digi, 
So you want the overlay character to be "S".  In that case
You replace the "/" separator with the "S" overlay.

> LT 1 !2933.65N09505.32W#PHG5340 W3, STXn-N  JSCARC
> LT 2 !2933.65N09505.32W#PHG5340 W3, STXn-N  JSCARC
> LT 3 !2933.65N09505.32W#PHG5340 W3, STXn-N  JSCARC
> LT 4 !2933.65N09505.32W#PHG5340 W3, STXn-N  JSCARC

Should be:

> LT 1 !2933.65NS09505.32W#PHG5340 W3, STXn-N  JSCARC
> LT 2 !2933.65NS09505.32W#PHG5340 W3, STXn-N  JSCARC
> LT 3 !2933.65NS09505.32W#PHG5340 W3, STXn-N  JSCARC
> LT 4 !2933.65NS09505.32W#PHG5340 W3, STXn-N  JSCARC

Because it has a bad posit, many programs unfortunately will
ignore it.  Of course this was never part of the original APRS
design.  ALL APRS packets, no matter what are supposed to be
captured, and if the posit does not make sense, then a VICINITY
plot is supposed to be assigned (and marked) that shows the
vicinty as identified at least by being in the vicinity of the
first DIGI that heard it.

But alas... too many software follow-ons did not implement this
fundamental aspect of APRS... And so in those applications, the
stations do not exist until they get a perfect posit (right or
wrong)...

Bob, WB4APR





More information about the aprssig mailing list