-
Notifications
You must be signed in to change notification settings - Fork 322
Description
As mentioned here: http://www.aprs.org/newN/ProportionalPathing.txt
It is a good idea for some objects to be beaconed with much shorter paths more frequently, and only going wider paths with less frequency. This allows, for instance, a traveler heading into an area, to have a list of digis in the area they're heading towards, while also ensuring that someone who has just turned on their radio will get local
info.
Configuring this in Direwolf doesn't seem directly possible.... I did something like this with timeslots and every
:
#OBEACON sendto=0 compress=0 lat=37.794143008 long=-77.93201899 height=350 objname=444.650ml power=50 gain=6 alt=100 SYMBOL=/r FREQ=444.650 OFFSET=+5 TONE=203.5 COMMENT="W4FEG" slot=0:10 via=DIRECT every=1
OBEACON sendto=0,IG compress=0 lat=37.794143008 long=-77.93201899 height=350 objname=444.650ml power=50 gain=6 alt=100 SYMBOL=/r FREQ=444.650 OFFSET=+5 TONE=203.5 COMMENT="W4FEG" slot=0:15 via=WIDE1-1 every=3
OBEACON sendto=0 compress=0 lat=37.794143008 long=-77.93201899 height=350 objname=444.650ml power=50 gain=6 alt=100 SYMBOL=/r FREQ=444.650 OFFSET=+5 TONE=203.5 COMMENT="W4FEG" slot=0:20 via=WIDE1-1,WIDE2-1 every=9
OBEACON sendto=0 compress=0 lat=37.794143008 long=-77.93201899 height=350 objname=444.650ml power=50 gain=6 alt=100 SYMBOL=/r FREQ=444.650 OFFSET=+5 TONE=203.5 COMMENT="W4FEG" slot=0:25 via=WIDE1-1,WIDE2-2 every=27
This is a little ugly and tough to manage changes in, and Direwolf complains that there need to be a whole number worth of beacons every hour, and then, if you have a few of these, when the WIDE2-2
fires, the DIRECT
and WIDE1-1
and WIDE2-1
beacons are also firing.
Obviously if every minute we want to go DIRECT
, and every 3 minutes we want to go WIDE1-1
, I don't want to fire beacons for DIRECT
path and WIDE1-1
path at minute 3...
How can this be worked around?