[aprssig] Object Timestamps and 111111
Lynn W. Deffenbaugh (Mr)
ldeffenb at homeside.to
Sun Dec 12 15:36:06 CST 2010
Ok, so that's where the 111111 came from. Is it actually written down
somewhere that new APRS implementations can learn about it?.
What about the h format vs the z format, both of which seem to be valid
according to aprs101.pdf?
And what does the timestamp actually MEAN? Is it simply a timestamp of
the object's transmission? a date/time that the object is particularly
interested in? an expiration time?
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
PS. I hate to ask so many questions, but the devil is in the details.
Bob Bruninga wrote:
>>> Any pointers to the definition of the timestamp
>>> on object packets, especially the spec of the
>>> 111111 special value...
> Its a crutch for UIview that cannot be fixed. We needed a NULL value for the date/time stamp for objects that are either permanent or the source has no clock. We tried 000000z, but UIview then completely ignores the object. Not good.
> So, the only thing we can do is come up with another value. We chose 111111z as an easy to recognize null value.
> Bob, WB4APR
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig