[aprssig] APRS Messenger Android released
bruninga at usna.edu
Thu Jun 13 09:17:25 CDT 2013
For events, I always recommend 1 minute reporting... but recognizing
that the channel can only support about 12 such cars operating simplex
(no digis) or maybe 6 of them operating via 1 hop. Any higher rate or
# of cars will reduce reliability.
Unless you go to Split operation (Digi's inpu on 144.99 and output on
144.39, then you can double the one-hop rate back up to 12 cars...
The idea is, for max reliablity y ou only want the channel 20% loaded.
Or you can use time slotting to significantly increase this.
On Wed, Jun 12, 2013 at 9:43 PM, Eric Lorenz K9LGE <k9lge at emlorenz.com> wrote:
> Hi Bob,
> Ok, I think I understand that (still learning the ins and outs of APRS). The
> perspective I was coming from...for the application I was thinking of
> (tracking SAG positions of vehicles in a public service event) a 3 minute
> beacon would be problematic...as we are trying to accurately track position
> for deployment purposes- we generally try to either use Smartbeaconing, or
> set beacon rates of 30 secs to 1 minute.
> Eric K9LGE
> Eric Lorenz
> Communications/Safety Chair
> American Diabetes Association
> Tour de Cure/Chicago
> On Jun 12, 2013 7:15 PM, "Robert Bruninga" <bruninga at usna.edu> wrote:
>> > Just out of curiosity...any reason why you chose to have one fixed
>> > beacon
>> > rate?
>> Some of us like the deterministic nature of fixed rates. It provides
>> all kinds of useful information.
>> 1) You can know when to expect an update
>> 2) You can easily judge coverage by looking at the separation of dots
>> 3) You can easily see speed by looking at the separati of dots
>> 4) You can judge network performance and consistancy
>> 5) Your performance is deterministic.
>> 6) Expectations are consistent
>> Bob, WB4APR
>> aprssig mailing list
>> aprssig at tapr.org
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig