|
Cellular forums Home > Archive > Garmin GPS > March 2006 > Backlight Level Does Not Stay
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Backlight Level Does Not Stay
|
|
| emanon 2006-03-01, 5:48 pm |
| I have a Vista Cx and am really enjoying it. This is my first GPS and I'm
glad I went higher than entry level.
I did the setup as shown in the manual. No problems with the directions. One
thing I noticed, though, is I selected 25% for the backlight level, but
everytime I turn the GPS on in a dark situation, the backlight level is at
the lowest setting and I have to manually reset it. Nothing else seems out
of the ordinary.
Is anyone else having this problem? For me, this falls into the category of
"minor annoyance" so it's not like I'm ready to pack it back up and send it
off to Garmin. I just don't thing this should be behaving like it is.
| |
| McTrack 2006-03-05, 11:48 pm |
| I have a new Legend Cx and it does exactly the same thing. Sure woud
be nice if the backlight setting would actually stick like all the
other settings...
emanon wrote:
> I have a Vista Cx ...
>
> I selected 25% for the backlight level, but
> everytime I turn the GPS on in a dark situation, the backlight level is at
> the lowest setting and I have to manually reset it. Nothing else seems out
> of the ordinary.
| |
| emanon 2006-03-06, 5:48 pm |
| Nice to know I'm not the only one. Hmm... I'm a newbie at this, so I'm only
guessing, but is this possibly a factory defect? Maybe there's a firmware
fix in the future for this. I'm going to drop Garmin Tech Support an e-mail
and see what they say.
"McTrack" <mctrack57@hotmail.com> wrote in message
news:1141606076.232966.175050@e56g2000cwe.googlegroups.com...
> I have a new Legend Cx and it does exactly the same thing. Sure woud
> be nice if the backlight setting would actually stick like all the
> other settings...
>
>
> emanon wrote:
at[color=darkred]
out[color=darkred]
>
| |
| McTrack 2006-03-06, 11:48 pm |
| Been playing with this some more and I found that the backlight setting
in the display setup screen does actually do something. If you hit the
On/Light button twice after turning the unit on, it comes back to your
preset level (was previously using the thumbstick each time). So it
seems it was meant to act this way. But I emailed them too - perhaps
we can get them to update the firmware. :)
| |
| McTrack 2006-03-07, 11:48 pm |
| Ok, Garmin's Tech Support said the reason it does this is "in case the
batteries are drained to the point where it will not power the unit on
a higher backlight level."
So there we have it.
| |
| emanon 2006-03-07, 11:48 pm |
|
"McTrack" <mctrack57@hotmail.com> wrote in message
news:1141776695.874841.278000@v46g2000cwv.googlegroups.com...
> Ok, Garmin's Tech Support said the reason it does this is "in case the
> batteries are drained to the point where it will not power the unit on
> a higher backlight level."
>
> So there we have it.
>
Ah, got it. "It's an undocumented feature, not a bug" ;-{)}
| |
| McClurg Chevrolet, Pontiac, Buick 2006-03-08, 5:48 pm |
| My GPS V did that, when I pushed the backlight up to it's brightest level
with low batteries, the unit would turn off. As long as I keep the backlight
level down low, I didn't have any problem. Replaced the batteries and the
problem disappeared.
"emanon" <emanon@erehwon.com> wrote in message
news:jOOdnWxk8KLPsZP
ZnZ2dneKdnZydnZ2d@ad
elphia.com...
>
> "McTrack" <mctrack57@hotmail.com> wrote in message
> news:1141776695.874841.278000@v46g2000cwv.googlegroups.com...
> Ah, got it. "It's an undocumented feature, not a bug" ;-{)}
>
>
| |
|
| >I have a Vista Cx and am really enjoying it. This is my first GPS and I'm
>glad I went higher than entry level.
>
>I did the setup as shown in the manual. No problems with the directions. One
>thing I noticed, though, is I selected 25% for the backlight level, but
>everytime I turn the GPS on in a dark situation, the backlight level is at
>the lowest setting and I have to manually reset it. Nothing else seems out
>of the ordinary.
>
>Is anyone else having this problem? For me, this falls into the category of
>"minor annoyance" so it's not like I'm ready to pack it back up and send it
>off to Garmin. I just don't thing this should be behaving like it is.
>
This is by design behavior - I was on the phone with tech support on
this a couple of weeks ago.
Here is something even more irritating, suppose you are working on
something in the menu and it needs to do an off route recalculation -
it throws up the box to say it is doing it (on the ique off route
calculation can be made silent) and then when its done - you go back
to the main screen and lose anything you are working on in the menu. I
regard that as a bug a let Garmin know so.
Here are a few other things regarding the CX:
1. No way to turn the accuracy circle off like the models I own.
2. They explained autocalibrate for me and I am still not sure what
exactly it does - not documented.
3. Fixed and moving locations for altimeter / baramoter appear to me
to both do the exact same thing.
4. Many of the menu items are actually reachable by hitting the menu
button in the menu - not very intuitive - for example, if you load up
overlapping maps (e.g., city select and topo), you need to turn city
select off to see the countours. Now go try to find where that is
done.
5. The buttons are really hard to push especially when you are
travelling. The thumb stick/rocker is much easier to use when your
driving. Its a shame that in most cases, on the screen pushing it in
does not do anything and they didn't allow you to assign that to one
of the buttons.
And now my favorite with has been reported for years and is a general
routing problem in any Garmin mapping device using city select. Here
in Houston we have roads that parallel the toll roads so if you are
cheap and don't mind slower speed limits or occasional light, you
drive the parallel road for free. Problem is the Garmin will
constantly tell you to enter to the toll road (hence that problem
above that kept erasing my work). If you tell it to avoid toll roads
it will avoid both roads.
Hope this helps,
Joel
| |
| emanon 2006-03-09, 5:48 pm |
|
"Joel" <askme@forit.com> wrote in message
news:rtru0290aavb47h
3qb710at0cmqt62m73h@
4ax.com...
One[color=darkred]
at[color=darkred]
out[color=darkred]
of[color=darkred]
it[color=darkred]
>
> This is by design behavior - I was on the phone with tech support on
> this a couple of weeks ago.
>
> Here is something even more irritating, suppose you are working on
> something in the menu and it needs to do an off route recalculation -
> it throws up the box to say it is doing it (on the ique off route
> calculation can be made silent) and then when its done - you go back
> to the main screen and lose anything you are working on in the menu. I
> regard that as a bug a let Garmin know so.
>
> Here are a few other things regarding the CX:
>
> 1. No way to turn the accuracy circle off like the models I own.
> 2. They explained autocalibrate for me and I am still not sure what
> exactly it does - not documented.
> 3. Fixed and moving locations for altimeter / baramoter appear to me
> to both do the exact same thing.
> 4. Many of the menu items are actually reachable by hitting the menu
> button in the menu - not very intuitive - for example, if you load up
> overlapping maps (e.g., city select and topo), you need to turn city
> select off to see the countours. Now go try to find where that is
> done.
> 5. The buttons are really hard to push especially when you are
> travelling. The thumb stick/rocker is much easier to use when your
> driving. Its a shame that in most cases, on the screen pushing it in
> does not do anything and they didn't allow you to assign that to one
> of the buttons.
>
> And now my favorite with has been reported for years and is a general
> routing problem in any Garmin mapping device using city select. Here
> in Houston we have roads that parallel the toll roads so if you are
> cheap and don't mind slower speed limits or occasional light, you
> drive the parallel road for free. Problem is the Garmin will
> constantly tell you to enter to the toll road (hence that problem
> above that kept erasing my work). If you tell it to avoid toll roads
> it will avoid both roads.
>
> Hope this helps,
> Joel
You are using a lot of functions, Joel, that I don't, so I've not run into
most of the problems you are mentioning.
What is this "Accuracy Circle" you mentioned? If this is the circle around
the planchette representing your position, this does not bother me, so it is
a non-issue for me. I can see the desirability to want to control the screen
display, though.
I have not found calibration to be a problem for me. Calibration is covered
on Page 73 of the manual that came with my Vista Cx. Seems clear to me.
I use my GPS primarily for Geocaching, so the altimeter function is accurate
enough for what I do. Maybe later this Spring when I attach the Vista Cx to
my bicycle I may see the altimeter complaint you mention. The same for your
Navigation issues.
I do not use my GPS for routing for my car trips. Just a personal
preference, but I've been using Streets and Trips 2002 for that. I'm not
really thrilled with the program, but I know the ins and outs of it so it
works for me. ST Does offer the ability to define your route choices and I
can plan a route the eliminates toll roads, but still makes use of major
highways. For the short car trips I've done, I've manually placed waypoints
on my MapSource that mark critical turns, then created a route from these
waypoints. I will probably acquire City Navigator soon as I'm planning on a
longer trip and need the additional street detail City Navigator offers.
Once I load City Navigator, I'll see for myself how well it blends with the
Topos and see if that is a problem for me.
| |
|
|
Joel wrote:
> 2. They explained autocalibrate for me and I am still not sure what
> exactly it does - not documented.
For a really good explanation of what it does and how it works, read
this page by Chris Malcolm.
<http://www.dai.ed.ac.uk/homes/cam/g.../altgraphs.html> It is
written about the eTrex Summit, but I have verified by experiment that
the 76cs works the same way, and it is unlikely that Garmin changed it
in the x models.
> 3. Fixed and moving locations for altimeter / baramoter appear to me
> to both do the exact same thing.
I assume you mean fixed and variable elevation modes. They don't do
the same thing. Fixed is for getting barometric readings. The unit
assumes your elevation is not changing, so any change in pressure is
attributed to changing barometric pressure and the barometric pressure
readout is adjusted accordingly. You might use this to watch
barometric pressure trends while camping or boating as a crude weather
forcasting device. Variable is for getting elevation readings. The
unit assumes that the barometric pressure is not changing, so any
change in pressure is attributed to a change in elevation and the
altitude readout is adjusted accordingly. This is what you want for
hiking or driving.
| |
|
| >
>Joel wrote:
>
>For a really good explanation of what it does and how it works, read
>this page by Chris Malcolm.
><http://www.dai.ed.ac.uk/homes/cam/g.../altgraphs.html> It is
>written about the eTrex Summit, but I have verified by experiment that
>the 76cs works the same way, and it is unlikely that Garmin changed it
>in the x models.
>
>
>I assume you mean fixed and variable elevation modes. They don't do
>the same thing. Fixed is for getting barometric readings. The unit
>assumes your elevation is not changing, so any change in pressure is
>attributed to changing barometric pressure and the barometric pressure
>readout is adjusted accordingly. You might use this to watch
>barometric pressure trends while camping or boating as a crude weather
>forcasting device. Variable is for getting elevation readings. The
>unit assumes that the barometric pressure is not changing, so any
>change in pressure is attributed to a change in elevation and the
>altitude readout is adjusted accordingly. This is what you want for
>hiking or driving.
That makes sense to me but when I set it to fixed and just leave it
next to the computer, the altitude still changes from the 65 foot
calibration I set it to.
As far as autocalibate, thanks for the reference but it is much too
much data. Is it saying that autocalibrate is based upon the GPS
altitude?
By the way, perhaps someday, Garmin devices could get really
intelligent and if you have a topo they support loaded, it could do an
approximation based upon where you are between two contours - heck
that is normally what I eyeball and calibrate it to anyway while I am
hiking (since I don't often pass by a known elevation).
| |
| budgie 2006-03-11, 2:48 am |
| On Fri, 10 Mar 2006 22:32:44 -0600, Joel <askme@forit.com> wrote:
(snip)
>By the way, perhaps someday, Garmin devices could get really
>intelligent and if you have a topo they support loaded, it could do an
>approximation based upon where you are between two contours - heck
>that is normally what I eyeball and calibrate it to anyway while I am
>hiking (since I don't often pass by a known elevation).
Crikey, that'd really stuff up recreational pilots, hot air ballooonists etc.
Bit presumptuous to conclude that ALL GPS users are on the ground.
| |
| emanon 2006-03-11, 5:48 pm |
|
"budgie" <me@privacy.net> wrote in message
news:qvm4125dfi0rjaf
18nq3r74060ptufdge3@
4ax.com...
> On Fri, 10 Mar 2006 22:32:44 -0600, Joel <askme@forit.com> wrote:
>
> (snip)
>
>
> Crikey, that'd really stuff up recreational pilots, hot air ballooonists
etc.
> Bit presumptuous to conclude that ALL GPS users are on the ground.
No to mention you'd be trusting the map information to be giving an accurate
reading to start with.
Seriously, if you're hiking, what kind of altitude accuracy are you after?
I'm happy to know I'm looking at a steep ascent up ahead or if an easier
pass is indicated on the topo. Ground subsidence, rises due to seismological
disturbances or trail erosion in a given spot could effect your altitude as
much as a few feet. And let's not forget: are you putting the GPS on the
ground to calibrate altitude according to the topo map, holding it at eye
level or waist level. . . and is you waist level the same as mine? All of
those will make a difference in the accuracy of your calibration.
Now avionics, I imagine that's another story altogether. I do not fly, but I
imagine their altitude accuracy would need to be greater than what a hiker
needs.
| |
|
| >
>"budgie" <me@privacy.net> wrote in message
> news:qvm4125dfi0rjaf
18nq3r74060ptufdge3@
4ax.com...
>etc.
>
>No to mention you'd be trusting the map information to be giving an accurate
>reading to start with.
>
>Seriously, if you're hiking, what kind of altitude accuracy are you after?
>I'm happy to know I'm looking at a steep ascent up ahead or if an easier
>pass is indicated on the topo. Ground subsidence, rises due to seismological
>disturbances or trail erosion in a given spot could effect your altitude as
>much as a few feet. And let's not forget: are you putting the GPS on the
>ground to calibrate altitude according to the topo map, holding it at eye
>level or waist level. . . and is you waist level the same as mine? All of
>those will make a difference in the accuracy of your calibration.
>
>Now avionics, I imagine that's another story altogether. I do not fly, but I
>imagine their altitude accuracy would need to be greater than what a hiker
>needs.
>
Both those comments make sense about not being on the ground and
relying on the accuracy of the topo map - but as a former
IT/technology/programmer person (I'm now a tv/film soundtrack
composer), all I am suggesting is make it an option since people are
probably doing it manually anyway. I do day hikes down forest service
and national park trails. If the altitude calibration is based upon
the satellites and otherwise based upon the barometer, then as I walk
and find a location on the topo (which is also on the garmin) that
suggests a more accurate height, I do a manual calibration. So all I
am suggesting is give those hikers who are manually calibrating
anyway, an automated option to do the same thing. If you do not like
this approach, its an option, so you wouldnt turn it on.
For us hikers who do day hikes on trails, keeping the Garmin on is
more of a past time than anything else since you really need a GPS if
you stay on a trail (but never hurts to have one just in case).
Joel
| |
| emanon 2006-03-13, 11:48 pm |
|
"Joel" <askme@forit.com> wrote in message
news:nubb12p5pdkd959
ee0vtdpgpfhqu3lgiso@
4ax.com...
ballooonists[color=d
arkred]
accurate[color=darkr
ed]
after?[color=darkred]
seismological[color=
darkred]
as[color=darkred]
of[color=darkred]
but I[color=darkred]
hiker[color=darkred]
>
> Both those comments make sense about not being on the ground and
> relying on the accuracy of the topo map - but as a former
> IT/technology/programmer person (I'm now a tv/film soundtrack
> composer), all I am suggesting is make it an option since people are
> probably doing it manually anyway. I do day hikes down forest service
> and national park trails. If the altitude calibration is based upon
> the satellites and otherwise based upon the barometer, then as I walk
> and find a location on the topo (which is also on the garmin) that
> suggests a more accurate height, I do a manual calibration. So all I
> am suggesting is give those hikers who are manually calibrating
> anyway, an automated option to do the same thing. If you do not like
> this approach, its an option, so you wouldnt turn it on.
>
> For us hikers who do day hikes on trails, keeping the Garmin on is
> more of a past time than anything else since you really need a GPS if
> you stay on a trail (but never hurts to have one just in case).
>
> Joel
I'm with you an that last part. I've started using my GPS for my lunch time
walks / urban caching more as a sophisticated pedometer than as a true GPS.
I mean, come on, how lost can I get wandering around the streets where I
work? But it is kind of neat to know that I walked 1.9 miles at an average
of 3 MPH with a total elevation gain of 175 feet. Yeah, I'm a geek and proud
of it ;-{)} I have found a couple of neat virtual caches, though, things I
would have passed right by had I not had a reason to be out looking for
them.
If you can't enjoy your toys, why buy 'em?
| |
|
| >
>"Joel" <askme@forit.com> wrote in message
> news:nubb12p5pdkd959
ee0vtdpgpfhqu3lgiso@
4ax.com...
>ballooonists
>accurate
>after?
>seismological
>as
>of
>but I
>hiker
>
>I'm with you an that last part. I've started using my GPS for my lunch time
>walks / urban caching more as a sophisticated pedometer than as a true GPS.
>I mean, come on, how lost can I get wandering around the streets where I
>work? But it is kind of neat to know that I walked 1.9 miles at an average
>of 3 MPH with a total elevation gain of 175 feet. Yeah, I'm a geek and proud
>of it ;-{)} I have found a couple of neat virtual caches, though, things I
>would have passed right by had I not had a reason to be out looking for
>them.
>
>If you can't enjoy your toys, why buy 'em?
>
And while this is slightly off topic, speeking of geek - its tough to
give up your toys, but I decided that there was no need to have
duplicate equipment with overlapping functions. So when I purchased
my Vista Cx for about $335, I decide to sell the overlapping equipment
on eBay. So far I have sold a Garmin III+ for about $83 profit and a
GPS 12 for about $52 profit. So far I have earned back $135 off the
purchase price. And I have one more to go - have a Suunto Vector
altimeter watch I purchased to use with the III+. I just saw one sell
used on eBay for about $95 profit. If I sell that as well (my testing
showed the only advantage of the Vector was a thermometer - the Vista
was actually more functional), my effective purchase cost of the Vista
would go down to $105. Not bad! Thank you eBay!
|
|
|
|
|