[aprssig] Digi and Voice Repeater Beacon Question

Robert Bruninga bruninga at usna.edu
Tue Apr 5 14:46:18 CDT 2016


Thanks for asking!



Yes, DIGI should beacon its own data once every 10 minutes direct AND once
every hour via 1 hop.

The local FREQ object shouldbe evry 10 minutes DIRECT

The IGate should be every 10m via 1 hop.  Or if that is too much in your
area, it shold be every 30 minutes.



It looks like you have read http://aprs.org/localinfo.html



Bob, WB4APR


------------------------------

*From:* jason arends via aprssig <aprssig at tapr.org>
*To:* aprssig at tapr.org
*Sent:* Tuesday, April 5, 2016 2:10 PM
*Subject:* [aprssig] Digi and Voice Repeater Beacon Question



I currently have a Pi running a tx/rx digi in my area where we have no APRS
coverage. It's low altitude and covers a small area and I currently beacon
my own digi object and also a frequency object for the popular voice
repeater in the area.



Our local radio club is planning on putting an APRS digi on the same site
as that voice repeater, which has no Internet access, so I will be changing
my station to a tx/rx igate only and I'm going to be setting up the
digipeater that will go on-site.



My question is, what should the digi beacon - both it's own digi object and
the repeater frequency object at the same location? Also for my tx igate,
should the path be just the local digi, instead of any wide-type paths? I'm
assuming it would be the same also if I wanted to send objects for local
events and meetings, just path directly to that digi so it stays in the
area?



This is what I'm currently sending for the local repeater, if you have any
feedback on that, it would also be appreciated:



;147.210MO*111111z3706.  N/09424.  WrT915 R35m Net M1930 W0IN



Thanks, I'm pretty new to APRS and want to get it right.



~jason

K0JAA


_______________________________________________
aprssig mailing list
aprssig at tapr.org
http://www.tapr.org/mailman/listinfo/aprssig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20160405/a5d3fd35/attachment.html>


More information about the aprssig mailing list