| |
ZL3AI > APRDIG 26.01.07 08:03l 154 Lines 5960 Bytes #999 (0) @ WW
BID : 9618-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 31 #27, 3/3
Path: DB0FHN<DB0MRW<DB0SON<DB0SIF<DB0ROF<DB0ACH<DB0PKE<DB0RES<F5GOV<F4BWT<
IW2OAZ<ZL2BAU
Sent: 070126/0638Z @:ZL2BAU.#79.NZL.OC #:29209 [Waimate] $:9618-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 16
Date: Tue, 23 Jan 2007 20:52:04 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Local Repeater Displays on Mobiles
>Hi Bob, I suspect many people (like me) were sending
>the repeater objects from their client station....
>So now I've moved my repeater object to the UIDIGI
>node beacon text but there is a problem.
>
>;146.670- *111111z4612.74N/06320.46WrPHG8560 IRLP 2030
>
>Shows up as a fixed station with the senders CALL.
ARGH!! You are right. OK, here is the receommended new format that will
work. We will send the objects in 3rd party format so that the PHG will
work correctly.
BT }146.670->APOBJ:4612.74N/06320.46WrPHG8560 IRLP2030 VE1CRA
These will all be sent to the APOBJ TOCALL and we can use that as the
universal indicator of a permanent object.
>A second problem I see with having the object name as
>the repeater frequency instead of its callsign is the
>duplication problem where popular repeater frequencies
>will overwrite each other.
Ah, but only on FINDU and other global collectors of data. The purpose of
these local objects is locally only. And there would never be two
repeaters on the same frequency in the same area. The fix is for FINDU and
other collectors of global data to recognize that the TOCALL of APOBJ
specifies a permanent object that should not be overwirtten by anyone
except the original sender.
Thanks for the feedback. Ill fix the other docs. Besides, this format is
slightly shorteer anyway...
Bob, WB4APR
------------------------------
Message: 17
Date: Tue, 23 Jan 2007 20:49:05 -0600
From: "AE5PL Lists" <HamLists_at_ametx.com>
Subject: RE: [aprssig] Local Repeater Displays on Mobiles
Personally, I prefer the display in the D7 and D700 with the repeater
callsign and a SSID of R which is easy to spot and recognize as a
repeater as it goes by or as you look in the heard list (using standard
object format with callsign-R as the object name). This also removes
any guesswork with propagation wiping out local repeaters. I also
prefer using RNGxxxx instead of PHGxxxx because it is obvious in the D7
and D700 if I am in range of the repeater. The format I have used which
makes the repeater callsign, range, frequency, and tone all visible on a
D7 (so of course, on a D700) is:
;RPTRCL-R *111111z4612.74N/06320.46WrRNG0020 146.74- 110.9 Club Initials
This causes RPTRCL-R (replace RPTRCL with the repeater callsign) to be
displayed when received and to be listed in the posit list. When you go
to the actual listing, you see on a D7:
OBJECT
RNG0020 14
6.74- 110.
Symbol and distance.
I know it is an object, not an APRS station, broadcast by MYCALL. I know
it has a range of 20 miles and it is on 146.74, minus shift, 110.9 tone
(there is only 110 tone as is the case with all other tones). I see the
repeater symbol and I know if I am within the 20 mile range because of the
distance shown.
If you want to persist in broadcasting frequencies as the ID using the
third-party packet format, then add,TCPIP* to the third-party path (not the
RF path) so it won't get back into APRS-IS. Personally, I would like to
look at a map of say Annapolis on the web and see what repeaters are
identified in the area as "APRS-user-friendly" but your method precludes
that from happening. My method does not.
73,
Pete Loveall AE5PL
pete at ae5pl.net
------------------------------
Message: 18
Date: Wed, 24 Jan 2007 16:25:02 +1030
From: Ben Lindner <vk5jfk_at_activ8.net.au>
Subject: Re: [aprssig] TM-D700A MANAULS ECTS
Not all VKs are the same Juilen. Please keep giving the information
Ben Lindner
VK5JFK
------------------------------
Message: 19
Date: Wed, 24 Jan 2007 01:18:44 -0500
From: "Wes Johnston, AI4PX" <wes_at_kd4rdb.com>
Subject: Re: [aprssig] TM-D700A MANAULS ECTS
Really and truely.... there was a day before aprs when everyone used
connected mode packet. Many of the things that Julien mentions bring back
to mind the tools we used in those days. Not that they were bad tools at
all, but we have become so accustomed to having our PC's or d700's decode
each packet for us and many of us have forgotten about the other modes
available in a TNC. Or how to run a TNC from a terminal program. (anyone
remember using monochome TTY terminals for packet? I had a Wyse).
I can remember when I was fascinated watching the guys in the Chattanooga
TN area jokingly give their TNCs aliases like Saturn, Jupiter and Mars and
changing their UI paths to route packets thru all three in a big
unconnected UI frame chat room. It never dawned on me (or them at the
time) that they could have named all the digipeaters with the same alias...
that inspiration I suppose goes to Bob B.
I'm sure many newcomers to ham radio might not even know that connected
mode once existed commonly on air. And knowing conv mode and connected
mode would certainly aid in their understanding of the path specifications
we use now in aprs. I mean heck, I had completely forgotten about
mailboxes and hadn't thought about using one for literally 10 or 11 years.
Heck I still remember being excited to come home from work and see the mail
led blinking on the TNC and reading messages from friends in germany. Of
course it took days to get a message thru the bbs systems (thanks ALLUS
forsale messages) and by the time the satellite keps made it to my local
bbs they were over a week old usually, but still it was exciting!
Much of Julien's information is old hat to many on this list, but I'd say
that 1/3 of the people would appreciate the reminder of all the hoops we
can make a TNC jump thru, and another 1/3 are newbies who can stand to be
exposed to this info anyway.
Keep it coming Julien... it's a good effort!
Wes
------------------------------
aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
End of aprssig Digest, Vol 31, Issue 27
Read previous mail | Read next mail
| |
