[aprssig] on a multi-TNC digipeater, which callsign should be traced?
kennethfinnegan2007 at gmail.com
Sun Oct 11 13:59:48 EDT 2015
I can't tell you off hand what aprx does, but if you were to ask me, I'd
say I'd want it to use the outgoing TX callsign, since I made the argument
in my thesis that the last traced callsign may be used as part 97
identification. If I ever notice it doing something else, I would put it on
my list to fix it in aprx.
To give you an unopinionated answer, the specs say nothing on the issue.
On Oct 11, 2015 10:42 AM, "Tom Hayward via aprssig" <aprssig at tapr.org>
> I don't know the answer, but you might study what aprx does and implement
> it similarly.
> Tom KD7LXL
> On Oct 11, 2015 9:11 AM, "Andrew P. via aprssig" <aprssig at tapr.org> wrote:
>> I was just looking at the digipeat tracing code in my APRS program
>> (YAAC), and started wondering which callsign should be used for tracing
>> when doing a cross-band digipeat. For example, if the frame was received on
>> the port with callsign AP0RT-1 and digipeated out both TNC's AP0RT-1 and
>> AP0RT-2, which callsign should be used for the trace on the transmission
>> out AP0RT-2? The receiving port (AP0RT-1)? The transmitting port (AP0RT-2)?
>> Or both in receive-transmit order?
>> Just curious what the behavior should be for this.
>> Andrew, KA2DDO
>> author of YAAC
>> aprssig mailing list
>> aprssig at tapr.org
> aprssig mailing list
> aprssig at tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aprssig