[aprssig] KPC-3+ digi setup oddity

[Bob Bruninga]

> Instead of using BTEXT for your posit string, 
> I suggest taking a look at the LT 1-4 strings 
> and the BLT 1-4 for the timing... [and LTP 1-4 for the paths]

Do not forget that that those 5 total potential beacons from the KPC3 should
be used for not only the digi's own beacon, but also for local info.  Please
see http://aprs.org/fix14439.html for the digi settings and/or
/localinfo.html for how to set the local frequency objects.  

Typically 2 beacons are for the digi, one direct every 10 minutes and the
other via 2 hops every hour.  That leaves three for LOCALINFO objects via
the DIRECT path every 10 minutes.  And yes, the BTEXT only uses BEACON, but
the LTP's can contain the APN391...  Bob, Wb4APR

On 05/01/2012 07:26 PM, Stephen - K1LNX wrote:
> I've got a KPC-3+ with 9.1 firmware that I'm trying to setup as a
> fill-in digipeater and something is baffling me. I set my unproto to
> APN391, beacon to 10 minutes and my btext as follows:
>
> BTEXT    !3616.98N108222.54W#K1LNX W1 digi - Johnson City, TN
>
> Yet, when it beacons it sends it to beacon instead of APN391 (unless I'm
> misinterpreting something which is highly possible):
>
> K1LNX-1>BEACON:<UI>:
> !3616.98N108222.54W#K1LNX W1 digi - Johnson City, TN
>
> Monitoring from another radio/tnc does indeed indicate that the beacons
> are being sent to "beacon" instead of APN391 as I would expect.
>
> What could I be missing here?
>
> tnx and 73
> Stephen
> K1LNX
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig


_______________________________________________
aprssig mailing list
aprssig at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig