[aprssig] Sanity Check on My Repeater Object

Robert Bruninga bruninga at usna.edu
Thu Jan 26 08:46:54 CST 2017


Pretty much correct.   This triggers a new thought I will post in the next
email…  Bob, WB4aPR



*From:* aprssig [mailto:aprssig-bounces at tapr.org] *On Behalf Of *Kenneth
Finnegan
*Sent:* Wednesday, January 25, 2017 9:07 PM
*To:* TAPR APRS Mailing List
*Subject:* [aprssig] Sanity Check on My Repeater Object



Greetings,



I'm doing some consulting work and trying to write a digi config including
a repeater object beacon. I wanted to post what I've come up with to get a
sanity check that I'm on the right course:



MYCALL>APRS:;RPTCALL/R*111111zDDMM.mmN/DDDMM.mmWr444.075MHz T100 +500



A live object with an object name based on the repeater's callsign



Timestamp of 111111z since this is a permanent object in a static config
file per http://www.aprs.org/info/object-perm.txt



Latitude and Longitude (which I'll fill in eventually) with a symbol of /r
for a repeater per http://www.aprs.org/symbols/symbolsX.txt



The APRS101.pdf document on page 58 doesn't make it seem like a 7 byte data
extension like course/speed is optional for object reports, but I'm seeing
lots of packets excluding it, including examples on
http://www.aprs.org/info/freqspec.txt so we go straight into the freq spec
for the repeater



A freq spec data extension for 444.075MHz, only encode of 100Hz (If I
recall correctly C100 would be both encode and decode 100Hz?) and a
positive 5MHz offset.  I think I might have raised this before, but I'm
guessing "Tone" Tnnn means encode and "CTCSS" Cnnn means encode and decode?



Does this seem correct? Does this work with current radios? Much of the
older object documentation only refers to frequency objects, but the newer
articles include mention of the echolink objects with much more meaningful
names.

--
Kenneth Finnegan, W6KWF
http://blog.thelifeofkenneth.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20170126/f1ed8f83/attachment.html>


More information about the aprssig mailing list