| |
ZL3AI > APRDIG 07.02.03 12:00l 238 Lines 9249 Bytes #999 (0) @ WW
BID : 853-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 03, 3/6
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<IK1ZNW<IR0NET<VK3TE<ZL2BAU<ZL3VML
Sent: 030205/0847Z @:ZL3VML.#80.NZL.OC #:58834 [Chch-NZ] FBB7.00i $:853-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: New spec - working notes
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Mon, 3 Feb 2003 16:19:51 -0000
X-Message-Number: 8
>Even with more precision, Kelvin will require more bits to express the
>same thing. You could use a range of +/- 64 C (hopefully sufficient!)
>and have a fractional bit giving you 0.5 C resolution.
The BUFR format uses 12 bits for Kelvin readings - that ought to be enough
for our purposes. I'll see if I can come up with a format that has the
required resolution and range without wasting too many bits. I don't mind
so much putting a couple of 4-bit values in one byte, but I don't like
packing 12 bits here, 5 there, 2 more someplace else, and so on.
>you could have two fractional bits for 0.25 C resolution. +43 would not
>be enough though - we had a 44.5 C degree day here in Melbourne
>(Australia) just over 1 week ago.
Hey, I may not know metric conversions, but I know my Midnight Oil lyrics.
=]
"The Western Desert / lives and breathes / at 45 degrees"
And since visiting New Zealand, I know what "Holden wrecks" are, too. =]
Scott / N1VG
----------------------------------------------------------------------
Subject: Re: Future spec
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Mon, 3 Feb 2003 16:23:49 -0000
X-Message-Number: 9
I think the way I've seen this dealt with other places is by the use of
DEFINEs to alias the appropriate data type.
Do you have any suggestions on how the format could be structured to better
allow cross-platform decoding?
Scott / N1VG
----------------------------------------------------------------------
Subject: RE: JAVA-capable Radio
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Mon, 3 Feb 2003 16:30:42 -0000
X-Message-Number: 10
A radio/tnc combo with embedded Java and a good SDK would be interesting...
but it sounds like a lot of development work. The cellphone industry has a
big driving factor there - downloads are one of the more profitable services
they provide these days. It'd be cool, but I don't know if anyone's got the
resources to do it right.
<intro to Java removed for the benefit of digest subscribers>
----------------------------------------------------------------------
Subject: RE: JAVA-capable Radio
From: Jeff King <jeff@aerodata.net>
Date: Mon, 3 Feb 2003 11:54:15 -0500
X-Message-Number: 11
Scott:
Take a look at:
http://www.ibutton.com/TINI/index.html
which is a embedded processor that is programmable in Java. Full tcp/ip
stack, ethernet, 4 serial ports, one wire, digital I/O, etc.
Granted, it into itself is not a complete radio/tnc combo, but it might be
the good start for a prototype.
--
Jeff King, jeff@aerodata.net on 02/03/2003
----------------------------------------------------------------------
Subject: And some more questions...
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Mon, 3 Feb 2003 17:20:08 -0000
X-Message-Number: 12
One of the message types I'm defining is Estimated Position Error. This
will handle both positional ambiguity, for when you've got a manually
entered location and aren't sure exactly where you are, and also direct EPE
reporting from a GPS unit. Right now it can handle 0-65,536 meters. If you
can't figure out where you are within a 65km radius, you've got more serious
problems. But what about sub-meter reporting? Anyone see a need for this?
Any other thoughts on position error?
Also, I never really heard anything about rainfall reporting requirements.
How should it be reported? I'm hesitant to include 'raw' counts, because
they don't really mean anything if you don't know when the counter was last
reset, and how big your bucket is.
Here's an idea: How about just reporting the rainfall rate as a single
value, like the WMO BUFR format, and then giving the option of a 'rainfall
history' message that would include 1-hour, 24-hour, since midnight, and
whatever other historical readings are deemed necessary?
Scott / N1VG
----------------------------------------------------------------------
Subject: Re: And some more questions...
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 3 Feb 2003 12:35:48 -0500 (EST)
X-Message-Number: 13
On Mon, 3 Feb 2003, Miller Scott Contr 30SCS/FTI wrote:
>One of the message types I'm defining is Estimated Position Error. This
>will handle both positional ambiguity, for when you've got a manually
>entered location and aren't sure exactly where you are, and also direct EPE
>reporting from a GPS unit. Right now it can handle 0-65,536 meters. If you
>can't figure out where you are within a 65km radius, you've got more serious
>problems.
APRSdos uses also a 250 mile or so ambiguity for DX spots. This was
arrived at by looking at the world map of callsigns and noticing that
that number would produce an ambituity circle that covered the vast
majority of the 300 countries on that list.
Nothing at all magic about that number... but it is bigger than the 65
Km..
Bob
----------------------------------------------------------------------
Subject: Re: And some more questions...
From: Jeff King <jeff@aerodata.net>
Date: Mon, 3 Feb 2003 13:07:18 -0500
X-Message-Number: 14
On Mon, 3 Feb 2003 17:20:08 -0000, Miller Scott Contr 30SCS/FTI wrote:
>One of the message types I'm defining is Estimated Position Error.
Scott:
Be careful with this one. To the best of my knowledge, this is a Garmin
generated number, not part of the GPS NMEA spec. (although I'd love to be
wrong here, as EPE makes life alot easier).
I believe EPE is derived from VDOP and HDOP, in a garmin proprietary manner.
I actually need to talk to them today, I'll drop them a note about this to
confirm.
>But what about sub-meter reporting? Anyone see a need for this?
By sub-meter, you mean less then a meter? Yes, I'd like to see this even if
we don't have the accuracy in the GPS. It is useful when we collect
historical data and can time filter repeative data, like for example
looking for roads and lane matching.
It really is a trade off... if you have some bits left over, I say use them
for this. But at a minimum I'd like to see about 30-50 cm accuracy.
-Jeff
----------------------------------------------------------------------
Subject: RE: And some more questions...
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Mon, 3 Feb 2003 18:14:31 -0000
X-Message-Number: 15
My understanding is that the EPE number you see on a Garmin display is
indeed generated by a proprietary Garmin formula based on VDOP, HDOP, and
some other internal factors, too. I'm creating a message format to report
DOP values directly, for those that care about GPS data quality, but error
in meters is much easier to deal with. It might even be a simple static
value for information purposes. In any case, it's still an optional field.
Let me know if you find out anything more from Garmin, or if someone's got a
formula for rough estimation based on PDOP.
Scott / N1VG
----------------------------------------------------------------------
Subject: RE: And some more questions...
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Mon, 3 Feb 2003 18:15:51 -0000
X-Message-Number: 16
Found this on the web, not sure how old it is:
Quote follows from Garmin Engineering
Joe,
The EPE is an estimation based upon the information the receiver
can determine. SA consists of artificial clock errors and
artificial ephemeral errors. Both of these effects, as well as
atmospheric effects, can result in a positional area of uncer-
tainty, which can be measured and will add to the receivers EPE.
Bias errors cannot be measured and will typically not be detected
in the EPE calculation.
The 12XL will typically have a better EPE than other units due to
the 12 channel correlator and the use of all tracked satellites
in the positional computation.
EPE is an estimation, rather than a measurement, but all
measurable factors are used in the estimation algorithm. We
consider the details of our EPE and FOM calculations proprietary.
We calculate EPE our own way. URE and HDOP are definitely
significant factors in the calculation. We calculate an over-
determined solution, and fully understand the characteristics of
SA, and are able (in our opinion) to provide for a better
estimate of current position error than the simplistic calcula-
tions will indicate.
Many folks have and will demand to know our specific calcula-
tions, but we consider these to be proprietary and we do not
release the specific formulas. This is similar in our FOM
calculation, we use a lot of finesse in our software which other
manufacturers have not been able to duplicate. This is further
evidenced by Dr. Wilson's reports on our accuracy compared to
other receivers. If the tests were performed, I believe you would
see closer correlation between our EPE values and actual errors,
as compared to other manufacturers units.
Garmin International
----------------------------------------------------------------------
Read previous mail | Read next mail
| |