[aprssig] OpenAPRS for iPhone 2.3.1 Released

Gregory A. Carter gcarter at openaprs.net
Sat Jan 22 20:47:37 EST 2011

The main intent of setting a beaconing time and interval was to keep
objects alive for events or for a repeater owner to keep alive an
object showing the repeater and frequencies, in cases where the owner
may not have APRS at the site, they could at least send it through
APRS-IS even though it doesn't go to RF.  I might be inclined to add a
setting that will actually move the object in a specified direction if
the creator chooses to have it move.


On Sat, Jan 22, 2011 at 8:57 AM, Bob Bruninga <bruninga at usna.edu> wrote:
>> ... I checked this morning, and the object was
>> being sent every hour as expected...
> I am not following this thread, so ignore this comment if it is out of place, but APRS has two standard net-cycle times.
> These are 10 minutes for local DIRECT or special events and 30 minutes for regional or less dynamic situations.  The APRS spec established these standards so that users would have consistent expectations.  IN other words, 30 minutes of montiroing and  you should see EVERTYHING in the situation.
> There is one other standard, and that is time-out of 80 minutes.  If a station has not been heard in 80 minutes (2 retries at the standard 30 minute rate, then it is no longer a participating net memeber.
> FOr what it is worth.
> Bob, WB4APR
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig

OpenAPRS iPhone Edition

More information about the aprssig mailing list