[aprssig] APRS Local Info Initative TM-D710A compatibitility
la3qma at aprs.la
la3qma at aprs.la
Fri Apr 27 01:18:59 CDT 2012
Quoting "Ron Stordahl, AE5E" <ronn5in-aprssig at yahoo.com>:
> The APRS Local Info Initiative provides a format for local voice
> repeater objects, but fails to disclose the option to also include
> the repeater offset information.
> This information when received by a TM-D710A offers a one button QSY
> feature to set the B side to the local voice repeater setting the
> tone and offset automatically.
> In the case of the TM-D710A for VHF repeaters the offset is
> programmed to be "standard" based upon the frequency (-600 KHz in
> one range, +600 KHz in another), but for UHF the radio apparently
> provides no capability to define the standard shift (at least I
> can't find it!).
The TM-D710E and TM-D710A and the other TM-D710x use different
Most people having an TM-D710E is modifying it so that these repeater
shift now are wrong in some parts of the band.
And as you have discovered the QSY function is using the repeater
shift stored in the menu.
This is why i always use the QSY format that dictates the correct
offset frequency because i then know that all TM-D710s is doing the
;LA7BR *111111z6023.06N/00514.98Er434.700MHz T097 -2000kHz
;LA5BR *111111z6024.76N/00521.64Er145.750MHz T097 -0600kHz
> it does not end up on the APRS-IS network nor digipeated far far
> away. You >can keep it off of APRS-IS by terminating the path with
> the string ',NOGATE'. >IGates which are working correctly will not
> send such a packet to the >internet. The path itself should be
> short, perhaps only NOGATE so that no >area digipeater will repeat
> it. An exception would be when the object is >originated by a very
> short range digi and does need the 'local' high digi to >extend it
> to a mobile in range of said voice
> repeater. But going beyond this is unnecessary QRM and 'Vanity'.
Hmm when i don't have the digipeater at the same QTH as the QSY object
to the repeater i use either a path like WIDE2-1 if it's not to close
to the real position. If the station have more or less the same RF
range i'm using no path at all.
Been able to see the objects is important, so a NOGATE is probably not
a good idea unless you have the most frequent objects with NOGATE and
i.e once every hour a object with a "real" path.
It's the sysop of the IGATE that should limit whats going out on RF
not the object owner. Many people tend to send everything out on RF
but those sysops need to get some feedback that they have to limit this.
More information about the aprssig