[aprssig] Local Repeater Displays on Mobiles
Ron ve1aic at yahoo.comThu Jan 25 00:25:27 UTC 2007
- Previous message: [aprssig] Local Repeater Displays on Mobiles
- Next message: [aprssig] Local Repeater Displays on Mobiles
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks for more input Pete. I like the callsign-R but I was considering some other angles too. Not only how it displays on my D7, but also how it appears on my GPS (Fortrex201). With callsign-R the '-R' is truncated on the GPS which is not so bad but the use of the rptr freq really shows up better than just another callsign on the little screen. In order to get the freq to fit I had to drop the decimal point and then add the '-R' to make it work right. So here's what I'm using for now: ;146670-R *111111z4612.74N/06320.46WrVE1CRA R60km IR2030 and ;146715-R *111111z4620.59N/06325.50WrVE1UHF Rng60km In the first one I wanted to include IRLP info so I shortened both the Range and IRLP to the minimum and it looks good on my D7 now. I don't think you meant that the RNGxxxx was actually decoded as much as it was easy to compare that range 'number' to the next screen which shows the actual direction and distance to the object. In my case I added the 'km' to the number to indicate km. On D7 it shows as: 146670-R OBJECT <-VY2TPH VE1CRA R60 km IR2030 FN86HF /r 9.7km <- On my Fortex201 it shows up as Waypoint '146670'. 73, Ron VE1AIC > Date: Tue, 23 Jan 2007 20:49:05 -0600 > From: "AE5PL Lists" <HamLists at ametx.com> > Subject: RE: [aprssig] Local Repeater Displays on Mobiles > To: "TAPR APRS Mailing List" <aprssig at lists.tapr.org> > Message-ID: > > <478F6623898BBC4DBD692A223D28298A1D2B1A at amewebsrvr.webametx.local> > Content-Type: text/plain; charset="US-ASCII" > > 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 > <-MYCALL > > 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 ____________________________________________________________________________________ TV dinner still cooling? Check out "Tonight's Picks" on Yahoo! TV. http://tv.yahoo.com/
- Previous message: [aprssig] Local Repeater Displays on Mobiles
- Next message: [aprssig] Local Repeater Displays on Mobiles
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
