Here is the beacon setup that I came up with to conform to WB4APR's
recommendations for digi beacon rates at
This uses the absolute time function to send a single beacon packet at the
specified time every hour. You could actually send a different packet at each
interval, just create a separate .ini file for each different packet you want
to send. Digipeaters in the same area can stagger the @times to reduce beacon
clutter. I am using only a single beacon/ID packet; use of digi_id.ini for an
ID packet is disabled. My reasoning is that since the position beacon packets
are transmitted every 10 minutes and contain the station callsign in the from
callsign field, this constitutes a legal ID in the USA. If you are using a
"tactical callsign" for digi_call, you will want to put the actual station
callsign in the comment field of your beacon packet.
This format has been in use for several months at NU0C-1 and KA0WUX, and
seems to be working well.
; Send our position as beacon, this transmission also takes place when an
; "?APRS?" broadcast or query is received.
; Adapted by NU0C to conform to
; Regional 2-hop 60 minute ID. Sent at the top of the hour :01.
beacon: @1 all DIGI_DEST,WIDE2-2
; Local 10 minute ID sent at :11
beacon: @11 all DIGI_DEST
; Local 10 minute ID sent at :21
beacon: @21 all DIGI_DEST
; Area 1-hop 30 minute ID sent at :31
beacon: @31 all DIGI_DEST,WIDE2-1
; Local 10 minute ID sent at :41
beacon: @41 all DIGI_DEST
; Local 10 minute ID sent at :51
beacon: @51 all DIGI_DEST
TR7/RV7, TR6/RV6, T4XC/R4C, L4B, NCL2000, SB104A, R390A, GT550A/RV550A - all vintage, all the time!