On Nov 23, 7:08*pm, Alan Browne <alan.bro...@FreelunchVideotron.ca>
wrote:
> > Excerpt:
> > 1.
> > How does an SBAS (Satellite Based Augmentation System) system work?
> > SBAS systems improve the performances of GPS with the objective to
> > make it
> > useable for safety critical services. This is accomplished by
> > providing, by means
> > of separate (geostationary) signals of a set of corrections that
> > improve the
> > position and time calculation performed by the user satellite
> > receiver. EGNOS
> > provides these corrections not only for GPS but also for GLONASS.
>
> > So unless ESA (European Space Agency) has no idea what they're talking
> > about, EGNOS does provide corrections for GLONASS, besides taking
> > advantage of GLONASS satellites to better sample the ionosphere.
>
> How does it transmit them? *Does EGNOS broadcast on a frequency and
> modulation that GLONASS can pickup?
That's an excellent question. I have been trying to find something
like this:
www.nstb.tc.faa.gov/incoming/Waas_SV_Status.txt
for EGNOS, to no avail. That page gives the WAAS GPS clock and
ephemeris corrections in a very easy to read format.
There are pages that show VPL and HPL instantaneous, predicted and
past levels, without specifying if those levels are achieved with just
GPS or GPS+GLONASS.
Looking at the basic messages EGNOS defines, there is nothing GLONASS
specific, so the only possible way is each GLONASS SV has a distinct
ID (PRN) from GPS, and same broadcast format is used, with EGNOS
providing data for more PRNs (GPS + GLONASS). I'm not versed in
GLONASS details, but it looks like corrections for GPS/GLONASS/Galileo
can all be provided in the same format, fast/slow clock corrections,
clock change velocity, slow x/y/z ephemeris corrections, UDRE level,
and associated timestamps (validity window of each correction)
That's just an educated guess, but I really can't see a reason why it
doesn't work that way.
> > If that 2-3 meter uncertainty is 80% RMS, than its inline with actual
> > WAAS+GPS performance (GLONASS isn't making it worse). Looks very good
> > to me.
>
> What 2-3 meter uncertainty?
My bad, you said 3-4 meter. I wrote from memory and messed up the
figures. That's a little high for WAAS performance, depending on how
far you are from the nearest reference station.
> > With an abundance of satellites in view, the unit should be able to
> > weigh satellites that match each other and exclude/de weight the
> > others, regardless if they're GPS or GLONASS. The interesting question
> > is does it bother to do it. A RAIM algorithm of sorts.
>
> Would be nice. *Garmin are mum on how they mix the data.
Aren't all corporations mum on their internals. Always afraid of
giving something novel to the competition and/or showing their
customers some weakness.
> > The other very interesting test is to drive in downtown areas with
> > tall buildings all around and see if the unit can keep 5+ birds in
> > view at all time, that's the major value of GPS+GLONASS for a non
> > safety of life/not high accuracy unit.
>
> Keeping birds "in view" in urban canyons may be more a measure of
> failure than success. *Recent GPS receivers, esp. for hiking, have
> become very sensitive in order to get better performance in the woods.
> This also increases susceptibility to multipath.
True.