[aprssig] KPC-3 DIGI settings for New n-N
bruninga at usna.edu
Wed Mar 2 09:32:13 CST 2005
Unfortunately, though, the next WIDE will
digipeat it because the second WIDE is now
an active path looking for a digipeat.
And in fact after the second one digipeats
it, then the first one will do it againtoo...
>>> ab9fx at aprs.pl 3/1/05 11:32:45 PM >>>
I did some simple tests, maybe we need some more. But it seems that
MYALIAS is very useful for limiting path like WIDE,WIDE,WIDE
If MYALIAS is WIDE then after digipeating packet with original path
WIDE,WIDE,WIDE appears as WIDE*,WIDE,WIDE and none of other digis WIDE
will repeat it again, because WIDE was already repeated.
> ----- Original Message -----
> From: "Robert Bruninga" <bruninga at usna.edu>
> To: <aprssig at lists.tapr.org>
> Sent: 01 March, 2005 10:42
> Subject: [aprssig] KPC-3 DIGI settings for New n-N
>>I finally found my own password for our local digi and
>> so finally got to change it to the new Paradigm..
>> Learned: The MYALIAS does digipeat but does not do callsign
>> substitution. Thus, MYALIAS of RELAY is not a good idea.
>> So I set my UIDIGI to ON RELAY,WIDE5-5,WIDE6-6,WIDE7-7
>> You might choose to use the MYALIAS of RELAY if you really
>> want to use all the UIDIGI parameters for trapping, but
>> you wont get the digi call. In my case, since this is an alt-freq
>> digi, it is mandatory that the RELAY get susbtituted by the
>> digi's call (99ANAP) so we know the packet originated on
>> 144.99 and how it got to 144.39.
>> aprssig mailing list
>> aprssig at lists.tapr.org
aprssig mailing list
aprssig at lists.tapr.org
More information about the aprssig