[aprssig] OpenAPRS WEB page

[Gregory A. Carter]

So is there an actual writeup on this somewhere?

I'd be happy ton parse it or add support for it if it's actually part of the
protocol but it would help to know the specifics of what the parser should
expect.

I'm guessing you just have to take a guess that if 5 digits follow PHG then
they are also indicating beacon times?

Greg

NV6G
OpenAPRS.Net

On Wed, Aug 20, 2008 at 1:42 PM, Robert Bruninga <bruninga at usna.edu> wrote:

> > The PGH strings which I have set up contains a
> > fifth number representing the number of beacons
> > per hour. For LD1FA, 4. For my home call, 2.
> > But they are regarded as the first part of the
> > rest of the status message, rather than part of
> > the PHG, on oaprs. And the explanation window
> > only speaks about 4 digits after the characters
> > 'PGH'.
>
> Yes, the 5th digit was used as a possible way of seeing no only
> eomeones effective RF range but by also sestting the beacons per
> hour, one could tell how reliably he was being received.  But
> this depended on parsers to "assume" a delimiter after the
> original SPEC values of PHGxxxx,text......  So we found we could
> replace that  comma delimiter with that beacon rate digit.
>
> But this was probably mostly forgotten.  But it is good that you
> raise it up.  It would be nice to get feedback on any/all
> systems that by-luck, parse the 5th digit and do not mess up
> their text, and those that do.  It wuold be nice to see how the
> D710 handles it because we can fix that...
>
> Bob, WB4APR
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20080820/a6a06980/attachment.html>