Order Tray | Contact Us | Home | SIG Lists

[aprssig] KPC-3+ digi setup oddity

KA7O ka7o at ka7o.net
Wed May 2 02:13:06 UTC 2012


Your TNC is function exactly as designed.

BEACON - send the contents of BTEXT using the TOCALL of Beacon.

BTEXT - defines what the contents of said beacon will be.

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. If I'm remembering 
correctly, there is an option to set the path for each LT buffer as well 
- you can send posits every 10 minutes with 1 hop, every 30 with 3 hops, 
etc.

73

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




More information about the aprssig mailing list