[aprssig] trying to beacon our local repeater--aprx

[Martin (DK3ML)]

Hi J...
You have to put the QSY info first and then the comment " Tx-iGate
Repeater "

And the QSY information needs to follow the specification very strictly.
One space too much and it will not work.

Here you will find the docs + examples:

http://www.aprs.org/info/freqspec.txt

This is what I use for a local repeater here:
145.662MHz tOFF -060 73 de DK3ML

So in your case maybe something like:

147.600MHz t103 -060 Tx-iGate Repeater

Not sure how to put the range there, too, but it should be described in
the link above.

Does your trx support to send the QSY information? In that case it might
be the easiest way to just set up your radio for the repeater and then
send a beacon with QSY enabled and then you should see the right format
at aprs.fi

73 Martin, DK3ML


Am 24.01.2018 um 20:58 schrieb MJ Inabnit:
> I now this is silly question, but I am confused.  My beacon is sent but
> I don't think I have the comment data correct.  In many places I've
> visited, my aprs radio will hear a beacon that reports a local repeater.
>  My radio then pops it up and I can push a button and the data sets my
> radio automatically so I can use the repeater.
>
> I've pasted a bit of my config file below.  How should it be?
>
> # Basic beaconed thing is positional message of type "!":
> #
> #beacon symbol "R&" lat "0000.00N" lon "00000.00E" comment "Rx-only iGate"
>
> beacon symbol "I&" $myloc comment "Tx-iGate Repeater 147.60 147.000rx tn
> 103.5 r50m"
>
> #
>
> Thanks for any help.
>
> 73
> j
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20180124/73a01c2d/attachment.html>