
- etrex-30-tracking--woods
- 11-26-2011
![]() Re: etrex 30 tracking - woods
| macpacheco | 11-27-2011 |
![]() ![]() Re: etrex 30 tracking - woods
| Alan Browne | 11-27-2011 |
If you were Registered and logged in, you could reply and use other advanced thread options
1. Began into woods tracking:
10 GPS
1 WAAS
4 GLONASS - though, per the display 7 GLONASS were "visible". Houses =
and tress blocked them, I supose.
Uncertainty 3m (and briefly 2).
2. In the woods, lost WAAS and the "D" disappeared from the signal bars=20
of the GPS sats. Uncertainty went to 4 and pretty much stayed there.
7 - 9 GPS
2 - 4 GLONASS
WAAS occasional when in the few areas with a clear view south
3. After walking around for a bit, ended up at a good ground truth. Put =
both GPS' there (the other is a photo position recorder - a GPS without=20
a display - also recording at 1/5 s.); recorded the position after the=20
Garmin had re-acquired WAAS for 15 seconds. Uncertainty: 3 m.
When I got home and uploaded the tracks and waypoints.
The Garmin was off of the truth point by 7 metres. The photo tracker=20
was off by 3.
Next time I go to that truth point I'll turn off GLONASS.
Another _strange_ thing. At one point the GLONASS sat bars showed "D"=20
for differential. What's that all about?
Could it have been from SVN 33 (EGNOS 120 / AOR-E / W15.5=B0)?
More on that tomorrow - I'll go look for "33" to pop up - I wasn't=20
paying attention and it's not in the recording at all. But does seem to =
indicate that EGNOS data is leaking into the unit and the GLONASS range=20
is being corrected - maybe made the solution worse.
--=20
"I see!" said the blind man as he picked up his hammer and saw.
wrote:
Logic would suggest the "D" presence depends only on the IONO grid,
regardless of ephemeris/clock corrections availability. That would
explain why not all GPS satellites get a D, even though in North
America all GPS satellites in view should have an excellent ephemeris/
clock correction.
Minimum IONO uncertainty is 3 meters, and just outside of CONUS+Alaska
it jumps quickly to 4.5 meters and higher. Perhaps the receiver
considers GIVE of 4.5 or higher too low accuracy to give the satellite
a "D" status. That doesn't mean the IONO grid is or isn't used for
those satellites without a "D" status, just that the IONO grid isn't
good enough for a "D" status.
If you look at:
http://www.nstb.tc.faa.gov/incoming/igp_plot.png
You will see that GIVE jumps quite quickly with just 300-400 km away
from a station.
Just thinking out loud. Marcelo
> and tress blocked them, I supose.
> =A0 Uncertainty 3m (and briefly 2).
> 2. In the woods, lost WAAS and the "D" disappeared from the signal bars
> of the GPS sats. =A0 Uncertainty went to 4 and pretty much stayed there.
> =A0 7 - 9 GPS
> =A0 2 - 4 GLONASS
> =A0 =A0 =A0 =A0 WAAS occasional when in the few areas with a clear view s=
outh
> =A0 Uncertainty 3m (and briefly 2).
> 2. In the woods, lost WAAS and the "D" disappeared from the signal bars
> of the GPS sats. =A0 Uncertainty went to 4 and pretty much stayed there.
> =A0 7 - 9 GPS
> =A0 2 - 4 GLONASS
> =A0 =A0 =A0 =A0 WAAS occasional when in the few areas with a clear view s=
> 3. After walking around for a bit, ended up at a good ground truth. =A0Pu=
t
> both GPS' there (the other is a photo position recorder - a GPS without
> a display - also recording at 1/5 s.); recorded the position after the
> Garmin had re-acquired WAAS for 15 seconds. =A0Uncertainty: 3 m.
> When I got home and uploaded the tracks and waypoints.
> The Garmin was off of the truth point by 7 metres. =A0The photo tracker
> was off by 3.
> Next time I go to that truth point I'll turn off GLONASS.
> Another _strange_ thing. =A0At one point the GLONASS sat bars showed "D"
> for differential. =A0What's that all about?
> Could it have been from SVN 33 (EGNOS 120 / AOR-E / W15.5=B0)?
> More on that tomorrow - I'll go look for "33" to pop up - I wasn't
> paying attention and it's not in the recording at all. =A0But does seem t=
o
> a display - also recording at 1/5 s.); recorded the position after the
> Garmin had re-acquired WAAS for 15 seconds. =A0Uncertainty: 3 m.
> When I got home and uploaded the tracks and waypoints.
> The Garmin was off of the truth point by 7 metres. =A0The photo tracker
> was off by 3.
> Next time I go to that truth point I'll turn off GLONASS.
> Another _strange_ thing. =A0At one point the GLONASS sat bars showed "D"
> for differential. =A0What's that all about?
> Could it have been from SVN 33 (EGNOS 120 / AOR-E / W15.5=B0)?
> More on that tomorrow - I'll go look for "33" to pop up - I wasn't
> paying attention and it's not in the recording at all. =A0But does seem t=
> indicate that EGNOS data is leaking into the unit and the GLONASS range
> is being corrected - maybe made the solution worse.
> --
> "I see!" said the blind man as he picked up his hammer and saw.
> is being corrected - maybe made the solution worse.
> --
> "I see!" said the blind man as he picked up his hammer and saw.
Logic would suggest the "D" presence depends only on the IONO grid,
regardless of ephemeris/clock corrections availability. That would
explain why not all GPS satellites get a D, even though in North
America all GPS satellites in view should have an excellent ephemeris/
clock correction.
Minimum IONO uncertainty is 3 meters, and just outside of CONUS+Alaska
it jumps quickly to 4.5 meters and higher. Perhaps the receiver
considers GIVE of 4.5 or higher too low accuracy to give the satellite
a "D" status. That doesn't mean the IONO grid is or isn't used for
those satellites without a "D" status, just that the IONO grid isn't
good enough for a "D" status.
If you look at:
http://www.nstb.tc.faa.gov/incoming/igp_plot.png
You will see that GIVE jumps quite quickly with just 300-400 km away
from a station.
Just thinking out loud. Marcelo
On 2011-11-27 10:19 , macpacheco wrote:
I'm not concerned too much about WAAS. I'm interested in why I'm=20
getting "D" on some of the GLONASS birds. I think I saw sat 33 pop up - =
it is an EGNOS bird.
More to follow on that.
--=20
"I see!" said the blind man as he picked up his hammer and saw.
> wrote:
>> 1. Began into woods tracking:
>> 10 GPS
>> 1 WAAS
>> 4 GLONASS - though, per the display 7 GLONASS were "visible". Hou=
ses
>> 10 GPS
>> 1 WAAS
>> 4 GLONASS - though, per the display 7 GLONASS were "visible". Hou=
>> and tress blocked them, I supose.
>> Uncertainty 3m (and briefly 2).
>> 2. In the woods, lost WAAS and the "D" disappeared from the signal bar=
s
>> Uncertainty 3m (and briefly 2).
>> 2. In the woods, lost WAAS and the "D" disappeared from the signal bar=
>> of the GPS sats. Uncertainty went to 4 and pretty much stayed there.=
>> 7 - 9 GPS
>> 2 - 4 GLONASS
>> WAAS occasional when in the few areas with a clear view south=
>> 2 - 4 GLONASS
>> WAAS occasional when in the few areas with a clear view south=
>> 3. After walking around for a bit, ended up at a good ground truth. P=
ut
>> both GPS' there (the other is a photo position recorder - a GPS withou=
t
>> a display - also recording at 1/5 s.); recorded the position after the=
>> Garmin had re-acquired WAAS for 15 seconds. Uncertainty: 3 m.
>> When I got home and uploaded the tracks and waypoints.
>> The Garmin was off of the truth point by 7 metres. The photo tracker
>> was off by 3.
>> Next time I go to that truth point I'll turn off GLONASS.
>> Another _strange_ thing. At one point the GLONASS sat bars showed "D"=
>> When I got home and uploaded the tracks and waypoints.
>> The Garmin was off of the truth point by 7 metres. The photo tracker
>> was off by 3.
>> Next time I go to that truth point I'll turn off GLONASS.
>> Another _strange_ thing. At one point the GLONASS sat bars showed "D"=
>> for differential. What's that all about?
>> Could it have been from SVN 33 (EGNOS 120 / AOR-E / W15.5=B0)?
>> More on that tomorrow - I'll go look for "33" to pop up - I wasn't
>> paying attention and it's not in the recording at all. But does seem =
to
>> Could it have been from SVN 33 (EGNOS 120 / AOR-E / W15.5=B0)?
>> More on that tomorrow - I'll go look for "33" to pop up - I wasn't
>> paying attention and it's not in the recording at all. But does seem =
>> indicate that EGNOS data is leaking into the unit and the GLONASS rang=
e
>> is being corrected - maybe made the solution worse.
>> --
>> "I see!" said the blind man as he picked up his hammer and saw.
>> --
>> "I see!" said the blind man as he picked up his hammer and saw.
> Logic would suggest the "D" presence depends only on the IONO grid,
> regardless of ephemeris/clock corrections availability. That would
> regardless of ephemeris/clock corrections availability. That would
I'm not concerned too much about WAAS. I'm interested in why I'm=20
getting "D" on some of the GLONASS birds. I think I saw sat 33 pop up - =
it is an EGNOS bird.
More to follow on that.
--=20
"I see!" said the blind man as he picked up his hammer and saw.
- New model yellow eTrex
- Satellite Navigation
- 2005-06-10
- etrex 30 tracking
- Satellite Navigation
- 2011-11-25
- etrex 30 : GPS + GLONASS
- Satellite Navigation
- 2011-10-27
- GPS tracking device
- Satellite Navigation
- 2011-12-15
- etrex 30 arrived
- Satellite Navigation
- 2011-11-23
- etrex 30 - ordered
- Satellite Navigation
- 2011-11-20
- Etrex H repairs/spares
- UK GPS Discussions
- 2012-01-24
- Migratory Bird Tracking
- Satellite Navigation
- 2011-07-16






> =A0 10 GPS
> =A0 =A01 WAAS
> =A0 =A04 GLONASS - though, per the display 7 GLONASS were "visible". =A0H=