[aprssig] Digi "Location-Based" Callsigns and Objects
brett.friermood at gmail.com
Fri Jul 25 09:54:45 CDT 2014
Being objects you don't have to do anything differently than you are
doing now. The originating station of course has to identify as usual,
so if you are using a tactical callsign common practice is to put your
legal callsign in the comment of the station's own beacons. As long as
one of these is sent every 10 minutes, the station is legally
identified for all packets being transmitted whether they are
digipeated positions from other stations or objects sourced from
The source callsign of an object should be the actual on-air callsign
of the originating station in most cases. In your situation why would
you feel the objects need to be sourced from your callsign while being
originated from the digipeater?
On Tue, Jul 22, 2014 at 1:44 PM, David Andrzejewski
<david at davidandrzejewski.com> wrote:
> With all this talk of using location-based callsigns on digis, I thought I'd
> experiment with changing mine. However, I want to ensure that I'm doing it
> right, especially with regards to IDing correctly.
> I'm using aprx on a Raspberry Pi, and I beacon a few repeater objects.
> If I set the source call to my callsign on those object packets, that will
> "break the link" - e.g., it will be coming from "KD8TWG-1" but my digi will
> be beaconing itself as something different, so nobody will have KD8TWG-1 in
> their lists.
> I'm thinking I could put it in the comment? The thing is, I include the
> repeater's callsign in the comment, so how would I avoid confusion there?
> Here's one of my repeaters:
> object "146.94"
> symbol "/r"
> lat "4130.33N"
> lon "08111.41W"
> comment "146.940MHz T110 -060 W8DES"
> My current thought is I could change the comment to:
> comment "146.940MHz T110 -060 W8DES (de KD8TWG)"
> - Dave/KD8TWG
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig