Jump to content
Sign in to follow this  
Followers 10
Trav'lin Two

New Garmin 62st

Recommended Posts

Can you disable the electronic barometer and let it use GPS data? This would be another test to pinpoint the issue, but sure doesn't excuse this finding.

Share this post


Link to post

Well I got my new 62st, and this one does not squeak.

 

I have however somewhat lost confidence that other problems with this unit will not pop up, seeing how this, in my opinion serious flaw, was allowed to get by quality controls.

 

I hope the company steps up to the plate and provides the kind of support for this unit that they have been famous for in the past.

Edited by gpscybr

Share this post


Link to post

Is there no pics of the ST build in maps? Really want to see details on the area where i live.

Share this post


Link to post

You can see the entire map through Garmin's interactive map web page. The link below is for the 100K scale product which is what is used for the new Garmin's that come with topo maps pre-loaded. If you search these forums you will notice that in some areas it appears the maps have slight differences but for the most part the 100K scale product and the pre-loaded topo's are the exact same.

 

Garmin Topo

Share this post


Link to post

Called Garmin this morning to talk to them about my replacement (second one) flimsy-sided, squeaky unit and the tech-rep said he received an e-mail this morning from engineering stating that the flimsyness and squeaking are NOT defects and will no longer be exchanged.

 

Hmm, some units squeak and some units side plastic pushes in and feels flimsy and others don't. This isn't a defect? This electronic equipment that I just paid top-dollar for shouldn't feel and sound like a cheap piece of $#!T in my hand. Just be aware as a consumer, if your considering this product, that the designers and engineers call this normal and don't plan on addressing it in any way. So buyer beware, you may get a flimsy squeaker or you may get a solid unit, flip a coin.

Edited by yogazoo

Share this post


Link to post

Poor business decision in my book:

 

Seems to me that if the case is flexing the plastic will potentially fatigue which will lead to failure at some point down the road.

 

Word to the wise purchase at a brick and mortar facility with a good return policy. If those stores start getting flooded with rejects perhaps they might flex their muscles and get the problem addressed.

 

Back in the day I returned two Colorados directly to Gary and Min. I doubt that they ever saw my missive, however, I had resolution to my issues in very short order.

Share this post


Link to post

Called Garmin this morning to talk to them about my replacement (second one) flimsy-sided, squeaky unit and the tech-rep said he received an e-mail this morning from engineering stating that the flimsyness and squeaking are NOT defects and will no longer be exchanged.

 

Hmm, some units squeak and some units side plastic pushes in and feels flimsy and others don't. This isn't a defect? This electronic equipment that I just paid top-dollar for shouldn't feel and sound like a cheap piece of $#!T in my hand. Just be aware as a consumer, if your considering this product, that the designers and engineers call this normal and don't plan on addressing it in any way. So buyer beware, you may get a flimsy squeaker or you may get a solid unit, flip a coin.

 

So did they replace your second squeaky unit?? I am still waiting on my third RMA'd unit to arrive for the squeaking problem. I am beginning to think that I should have learned my lesson about being an early adopter, my scars are still healing from the Colorado!!

Share this post


Link to post

Sadly, I can now confirm 100% that this is due to gripping the unit and pressing the buttons.

 

During my drive to work this morning I ran my 60csx, PN-40 and 62st. All were started at the same time, turned off at the same time, and sat in the passenger seat of the car in the same way. Periodically during the commute I reached over to each GPS in turn and pressed the "Page" button precisely five times. I always did the 60csx first, the PN-40 second and the 62st last. During one part of the trip I refrained from touching the units at all, to act as a control. And at one point in the trip I pressed the Page button five times, AND held the unit in my hands, squeezing the unit firmly repeatedly as one might do while holding it in regular use.

 

When I got to work, I used GPSBabel to export the tracks from each unit. I then used Perl and Excel and plotted the altitude data. The X axis is TIME; the Y axis is altitude.

 

normal_gpscomparison.jpg

 

You can clearly see the spikes from the 62st when the buttons were pushed. You can also clearly see the much longer period of instability when the unit was simply being gripped, no buttons pressed.

 

None of the other units show ANY sign of similar failure.

 

I will contact Garmin Support and send them this. Sadly I consider the unit badly flawed at this point. If anyone wants the raw GPX files and/or the Excel spreadsheet let me know.

 

...Sam

Share this post


Link to post

Excellent data comparison and analysis sammydee! If only Garmin engineers were as on top of their product as you are. I can see MAYBE if you press the buttons you'd get the pressure shift but handling the unit as well? The case of the 62 flexes so much that it effects the pressure data by simply gripping it normally? Speaks to the poor, cheap, flimsy construction of the shell. This is a very troubling problem as well because it's a hardware issue. You can't fix the flimsy shell of the 62 with a firmware update.

 

ryan3295,

 

Garmin refuses to replace any more units due to the squeaking/flimsy case annoyance. I called again this afternoon hoping to get a different tech support person, which I did, who told me again about the email they all received this morning about the issue. Apparently there are alot of unhappy customers so they are going to play the "It's supposed to be like that" angle so they don't lose a bunch of money in replacing the defective units. Why I keep buying Garmin products is beyond me.

Edited by yogazoo

Share this post


Link to post

Garmin refuses to replace any more units due to the squeaking/flimsy case annoyance. I called again this afternoon hoping to get a different tech support person, which I did, who told me again about the email they all received this morning about the issue. Apparently there are alot of unhappy customers so they are going to play the "It's supposed to be like that" angle so they don't lose a bunch of money in replacing the defective units. Why I keep buying Garmin products is beyond me.

 

the rep i emailed said "it's the first i've heard of it", whatever.

 

so anyway, i just sent off the 3rd unit to gpscentral and they assured me they'll send a non-squeaker. we'll see. :P

Share this post


Link to post

Geeeeez,

 

Maybe the guy who designed the case / antenna interface for the gen.4 iPhone helped Garmin with the case design for the 62s.

 

That having been said, it seems that there may be some random quirks to the 62s case.

 

The issues revolving around altitude and how the case is held and when buttons are pushed is most distressing. If you haven't jumped on board this train it might be appropriate to sit on the sidelines for a while.

Share this post


Link to post

The raw data is available here:

 

http://spreadsheets.google.com/ccc?key=0As...uthkey=CJGmvZIJ

 

A higher resolution version of the chart is here:

 

http://www.flickr.com/photos/53807584@N00/4876879322/

 

You do not need to do a graph to see this. While at the altimeter page I pushed the enter button and could clearly see a spike/drop in the elevation every time I pressed the key. I tried the same procedure on my trusty 60CSx and NO spikes / drops !!!

 

Now what???

Edited by gpscybr

Share this post


Link to post

Anyone know what zoom levels custom POI are displayed?

 

Basically I want to know if it's like the Colorado/Oregon or like the Nuvi where it's limited to 80m or closer.

 

I think they start to disappear around 3mi but you can change it. It works like the Colorado/Oregon.

 

I found this bug.

On my 62s I have UTM as the position format.

When I hit Find/Coordinates and then on the enter location screen the last 2 digits of the Northing coordinate is

off the screen.

Anyone else have this?

This is fixed in 2.4

 

Now the bad news.

Very very difficult to read the 62s in the shade without the backlight on bright. Very hard to see the roads with the contour lines being so dark.

The 60csx is very easy to see without the backlight on.

I think the main problem is the colors they chose to use on the 62s.

It's unfortunate, because I like the new features on the 62s, but I'm going to return mine.

Tips on how to improve readability are here (I stole these from the Oregon wiki).

 

http://garmingpsmap.wikispaces.com/Miscellaneous#toc5

Is there a way to change the display colors of the roads and contour lines on the GPSr or in Mapsource before the maps are loaded??? ;)

Not without mucking with .typ files as suggested earlier.

 

On my 62st water is gray just like the roads. :P

 

You are in Marine mode. Setup>Marine>Marine Chart Mode>Off will fix this.

 

I've also seen the issue with jumpy elevation plots on my unit as well -- definitely related to squeezing the unit, pressing buttons, etc. As was posted on another thread you can see this by going to the elevation plot and watching the elevation change as you squeeze the unit, it fluctuates significantly.

 

I've asked Garmin about this but the response was that all units with waterproof altimeters do this (to some extent). Seems much worse on the 62s to me.

 

I'm assuming the 62 works the same way as all other Garmins and will record GPS elevation (vs. the bouncy altimeter elevation) in the track if you use this trick:

 

http://garminoregon.wikispaces.com/Altimeter#elevationtype

 

I'll try tonight to see if it "fixes" the issue as Timpat suggests.

Edited by g-o-cashers

Share this post


Link to post

I've asked Garmin about this but the response was that all units with waterproof altimeters do this (to some extent). Seems much worse on the 62s to me.

 

I should note that in my test all three GPSes have barometric altimeters, and only the 62st demonstrates the problem. So I believe their claim is fairly simple to disprove.

 

I emailed the raw data and spreadsheet to Garmin Support as they requested this afternoon, but haven't heard anything back. I will update here when they report back.

 

...Sam

Share this post


Link to post

I've asked Garmin about this but the response was that all units with waterproof altimeters do this (to some extent). Seems much worse on the 62s to me.

 

I should note that in my test all three GPSes have barometric altimeters, and only the 62st demonstrates the problem. So I believe their claim is fairly simple to disprove.

 

I emailed the raw data and spreadsheet to Garmin Support as they requested this afternoon, but haven't heard anything back. I will update here when they report back.

 

...Sam

Share this post


Link to post

Can you disable the electronic barometer and let it use GPS data? This would be another test to pinpoint the issue, but sure doesn't excuse this finding.

 

Unless I'm mistaken, I think this is what the "Barometer Mode" setting does. If it's set to "Variable elevation," I believe it uses the barometric pressure to obtain elevation, whereas the "Fixed elevation" uses the GPS data.

 

I did some experimenting with the "Elevation over time" altimeter plot, which allows you to watch the elevation plot in real time by zooming way in on the x-axis. If I use the "Variable elevation" setting, I see a relatively smooth plot as long as I let the unit sit on a table. If I pick up the unit and/or press buttons, I suddenly see very obvious spikes in the plot. I then set the unit down, and the plot smooths out again.

 

I then switch to "Fixed elevation," and the plot stops showing the sharp spikes that I get with the "variable" mode. I still see some odd variations, but it's no longer "spiky." I'm not yet sure, but the variance in "fixed" mode may simply be caused by weak satellite signals since I did the experiment indoors. I'll try this outdoors next and report back.

 

My experiments so far appear to show that the "spiking" issue is specific to the "Variable elevation" setting, which uses pressure to determine elevation. UPDATE: Please see my followup post with new information on the effects of Fixed vs Variable elevation modes on the spiking: http://forums.Groundspeak.com/GC/index.php...t&p=4429657

The altimeter in this unit seems to be overly sensitive to handling, where lightly pressing a button can alter the reading significantly.

 

Something else, however, came up in my experiments, which is that the plot that's being drawn is sometimes distinctly different than the current reading indicates. By this I mean that when the unit was just sitting on the table and drawing the plot, the elevation consistently read around 890 ft. (using "fixed" mode.) The plot being drawn during this time, however, was up around 925 ft. In other words, even though the plot read a relatively consistent 890 ft., when I scrolled back over the plot it showed a consistent 925 ft. during the period I had just been watching (which, once again, read 890 ft. during this period.) The plot being drawn was NOT reflecting the current elevation being shown -- it was about 35 feet off. This just doesn't make sense to me, but it's definitely what I saw.

 

Larry

Edited by lalittle

Share this post


Link to post

I've asked Garmin about this but the response was that all units with waterproof altimeters do this (to some extent).

 

Bullcrap. My 60CSx fluctuates about +/- 15 or so feet in altitude when held and pressing buttons...SAME as it already does without being held. :P

Share this post


Link to post

Anyone know what zoom levels custom POI are displayed?

 

Basically I want to know if it's like the Colorado/Oregon or like the Nuvi where it's limited to 80m or closer.

 

I think they start to disappear around 3mi but you can change it. It works like the Colorado/Oregon.

 

I found this bug.

On my 62s I have UTM as the position format.

When I hit Find/Coordinates and then on the enter location screen the last 2 digits of the Northing coordinate is

off the screen.

Anyone else have this?

This is fixed in 2.4

 

Now the bad news.

Very very difficult to read the 62s in the shade without the backlight on bright. Very hard to see the roads with the contour lines being so dark.

The 60csx is very easy to see without the backlight on.

I think the main problem is the colors they chose to use on the 62s.

It's unfortunate, because I like the new features on the 62s, but I'm going to return mine.

Tips on how to improve readability are here (I stole these from the Oregon wiki).

 

http://garmingpsmap.wikispaces.com/Miscellaneous#toc5

Is there a way to change the display colors of the roads and contour lines on the GPSr or in Mapsource before the maps are loaded??? ;)

Not without mucking with .typ files as suggested earlier.

 

On my 62st water is gray just like the roads. :P

 

You are in Marine mode. Setup>Marine>Marine Chart Mode>Off will fix this.

I've also seen the issue with jumpy elevation plots on my unit as well -- definitely related to squeezing the unit, pressing buttons, etc. As was posted on another thread you can see this by going to the elevation plot and watching the elevation change as you squeeze the unit, it fluctuates significantly.

 

I've asked Garmin about this but the response was that all units with waterproof altimeters do this (to some extent). Seems much worse on the 62s to me.

 

I'm assuming the 62 works the same way as all other Garmins and will record GPS elevation (vs. the bouncy altimeter elevation) in the track if you use this trick:

 

http://garminoregon.wikispaces.com/Altimeter#elevationtype

 

I'll try tonight to see if it "fixes" the issue as Timpat suggests.

 

Excellent!! I now have BLUE water! Now.. how to adjust the volume?? :D

Edited by The Ravens

Share this post


Link to post

Far what it's worth, my 62s will get a lock on the satellites in my basement and the my 60csx will not.

The 62s also gets a lock on the satellites faster than my 60csx when outside.

 

Thanks for all the tips.

I upgraded to 2.40, it fixed the data entry field.

Turning off land cover and dem helped a lot. I still like the colors of the contours and roads used on the 60csx better.

I was going to send it back, but I think I'll keep it, squeaks and all!!

Share this post


Link to post

Regarding the elevation spikes when pressing buttons issue.

 

I'm no math genius but wouldn't it be easy enough to smooth the data from the barometer? Couldn't you write an algorithym that would smooth all unreasonable jumps in elevation? I'm probably not going to jump 80ft in less than a fraction of a second. Simple firmware fix could solve the issue.

Share this post


Link to post

I also was amazed when I got a lock in my basement!

Seems like it gets better reception than the 60CSx so far ...

Share this post


Link to post

I did another comparison on the way home tonight. Same as before ... ran all 3 GPSes on the passenger seat while I drove home. This time I left them mostly alone; three times on the trip I pressed the keys on each unit (15 times each).

 

Here are the results.

 

143303176-29ce7c2ed4015f0e06836fb64f36e156.4c60eae0-full.jpg

 

All three units seem to use different algorithms to calibrate their barometers. It takes them a while to do so, but once they do the curves all look very similar ... except for the three quite obvious spots where I touched the 62st and it went crazy. I don't see any similar artifacts on the 60csx or the PN-40.

 

I think that positively demonstrates that:

 

1. The glitches are due to pressing keys on the 62st.

 

2. This is NOT normal behavior for other GPSes with barometric altimeters. It's a bug in the 62st that needs to be fixed ASAP.

 

Again, spreadsheet and GPX files are available upon request.

 

I will post this to gba.net, geocaching.com and will send it to Garmin Support.

 

...Sam

Share this post


Link to post

Regarding the elevation spikes when pressing buttons issue.

 

I'm no math genius but wouldn't it be easy enough to smooth the data from the barometer? Couldn't you write an algorithym that would smooth all unreasonable jumps in elevation? I'm probably not going to jump 80ft in less than a fraction of a second. Simple firmware fix could solve the issue.

 

Agreed. Not sure if 'solve' is the right word ... 'hide' seems better. But yes, such a firmware filter would be better than recalling the units in the field ... and far better than ignoring the problem. I would be happy to help test such a fix.

Share this post


Link to post

Regarding the elevation spikes when pressing buttons issue.

 

I'm no math genius but wouldn't it be easy enough to smooth the data from the barometer? Couldn't you write an algorithym that would smooth all unreasonable jumps in elevation? I'm probably not going to jump 80ft in less than a fraction of a second. Simple firmware fix could solve the issue.

 

Agreed. Not sure if 'solve' is the right word ... 'hide' seems better. But yes, such a firmware filter would be better than recalling the units in the field ... and far better than ignoring the problem. I would be happy to help test such a fix.

Share this post


Link to post

 

I'm assuming the 62 works the same way as all other Garmins and will record GPS elevation (vs. the bouncy altimeter elevation) in the track if you use this trick:

 

http://garminoregon.wikispaces.com/Altimeter#elevationtype

 

I'll try tonight to see if it "fixes" the issue as Timpat suggests.

 

It doesn't appear to work on the 62. When I change to "Fixed Elevation" and press buttons while watching the elevation plot I still get spikes.

Share this post


Link to post

 

I'm assuming the 62 works the same way as all other Garmins and will record GPS elevation (vs. the bouncy altimeter elevation) in the track if you use this trick:

 

http://garminoregon.wikispaces.com/Altimeter#elevationtype

 

I'll try tonight to see if it "fixes" the issue as Timpat suggests.

 

It doesn't appear to work on the 62. When I change to "Fixed Elevation" and press buttons while watching the elevation plot I still get spikes.

 

This is interesting because I am definitely seeing different behavior when I use "fixed elevation" mode on my 62st. I don't know if you saw it, but I posted about this above:

 

Post describing Variable vs Fixed Elevation mode behavior on my 62st

 

When I change to "Fixed Elevation" the spikes in the plot definitely disappear. HOWEVER, I did some more testing and things got even more interesting.

 

What I found was that while the PLOT smoothed out after switching to "Fixed elevation," the "current elevation" reading and the "elevation gain" continued to record the spikes. In other words, if I did not touch the unit, the elevation stayed between 832 and 834 feet where I was testing -- i.e. VERY stable readings. If I picked up the unit and started pressing buttons, I saw the current elevation reading start fluctuating between about 800 and 900 feet. The "total ascent" reading (which I have on the altimeter page) also reflected these spikes, meaning that as I pressed buttons, I watched the total ascent climb by about 30 or 40 feet over 20 or thirty seconds of button pressing.

 

I could also see the spikes on the far right edge of the plot, BUT the plot did not actually RECORD these spikes. Rather, the recorded plot continued to show a smooth line. In other words, the unit appeared to be smoothing the plot as it was being drawn. Even though I saw violent spikes on the right edge as was being drawn, these spikes did not show up in the actual "finished" graph.

 

Yogazoo -- I'm wondering if you were just watching the far right edge of the plot, or if you actually waited to see how the graph looked after a few minutes of drawing.

 

My latest observations are that the unit continues to "see" spikes even in "Fixed elevation" mode, but that the elevation graph either does not "record" them, or that it smooths them out. The end result is that even in Fixed Elevation mode, the "current elevation" and "total ascent" values are still subject to the spikes.

 

Larry

Edited by lalittle

Share this post


Link to post

 

I'm assuming the 62 works the same way as all other Garmins and will record GPS elevation (vs. the bouncy altimeter elevation) in the track if you use this trick:

 

http://garminoregon.wikispaces.com/Altimeter#elevationtype

 

I'll try tonight to see if it "fixes" the issue as Timpat suggests.

 

It doesn't appear to work on the 62. When I change to "Fixed Elevation" and press buttons while watching the elevation plot I still get spikes.

 

I don't know which '62' you have, but unless its a '62s*', then it doesn't have barometric altimeter, so that setting isn't going to make a difference for a '62'. If you are seeing spikes in a '62', then it could be because you are changing the orientation of the '62' and it's getting difference satellite data.

 

--Marky

Share this post


Link to post

I did another head-to-head test on my commute today...the PN-40 with the barometer vs. the 62st in "Fixed" mode (allegedly disabling the barometer and reporting GPS elevation).

 

The GPX results are indeed much smoother, and don't show any sign of spiking when buttons are pressed. (I didn't look at the 62st's on-device altitude track, so I don't know if it made a difference there or not. I would hope so.)

 

HOWEVER the results vary dramatically from the other runs. In other runs comparing the 60csx, PN-40 and 62st the 3 GPSes altitude solutions would typically match to within a couple of meters (once the units all finished calibrating, which could take a while). However, comparing the PN-40 barometer track and the 62st non-barometer track the altitude solutions were often off by 10 meters or more.

 

So while turning off the barometer makes the button interference problem "go away" in the GPX track, naturally taking out the barometer subjects the user to the whims of GPS altitude calculations, which are known to be dodgy ... and are the reason why folks put barometers in GPSes in the first place.

 

Garmin either needs to fix the mechanicals of the 62s[t] so pushing the buttons doesn't impact the altimeter (as they had successfully done in the "gold standard" 60csx), or at minimum filter the results in software. The GPS knows when the buttons are pressed, after all, and could easily throw away the altitude readings for several hundred milliseconds before and a second or two after any button press. That would probably hide most of the problem, though a true fix would involve fixing the mechanical separation between the barometer and the buttons. As was done successfully in the 60csx and PN-40.

 

Note that on the PN-40 and the "gold standard" 60csx not only is the case quite rigid, but the buttons only travel a very short distance when pressed. On the 62st the button travel is dramatically greater, thus increasing the amount of air being pushed around.

 

Still waiting for comment from Garmin Support. They didn't give me a case number, just asked me to email data to someone.

 

...Sam

Share this post


Link to post

I called Garmin Support for an update.

 

They did their own in-house testing in Support and verified that, sure enough, pressing the buttons on the 62st causes disruption to the altitude data that the GPS records.

 

They passed the information on to Engineering, and have not yet heard back.

 

Support noted that the 62st has the barometer in a different internal location than the 60csx, which they think is part of the reason for the poorer behavior of the 62st vs. the 60csx.

 

Reasonably enough, they could not commit today to whether there would be a fix or not, nor to when we might expect a reply from Engineering.

 

I made it clear that the acceptable outcomes to me are either a software fix, a hardware fix, or a complete refund on the unit. The support engineer understood, but reasonably enough could not commit to anything today.

 

The support engineer agreed to contact me when he hears from Engineering. If I haven't heard from him in 7 days I will contact him again, and will let you know what I find out.

 

...Sam

Share this post


Link to post

Makes sense. The altimiter works by sensing air pressure. If the case flexes enough to change the volume of the case faster than the external vent thingy will let it equalize, it's going to change the air pressure.

 

That doesn't mean it's right...

Share this post


Link to post

They did their own in-house testing in Support and verified that, sure enough, pressing the buttons on the 62st causes disruption to the altitude data that the GPS records.

 

They passed the information on to Engineering, and have not yet heard back.

 

I don't know why but I just started laughing when I read this. It's as if the engineering doesn't even see the unit until afer it's released to the public. Everything seems to be a surprise to them. It's as though they don't take an interest in playing with the products they engineer as much as most of the people in these forums.

 

Man, if we could all just get togther and design a GPS it would be the end-all be-all. Or if a company would sit us all down in a room for a few hours they would have the market-cornering outdoor/geocaching GPS.

 

I digress.

Share this post


Link to post

 

I don't know why but I just started laughing when I read this. It's as if the engineering doesn't even see the unit until afer it's released to the public. Everything seems to be a surprise to them. It's as though they don't take an interest in playing with the products they engineer as much as most of the people in these forums.

 

Man, if we could all just get togther and design a GPS it would be the end-all be-all. Or if a company would sit us all down in a room for a few hours they would have the market-cornering outdoor/geocaching GPS.

 

I digress.

 

you would thing they would have some sort of beta testing team. get 100 people to use the units months in advance, work out all the glitches and problems, then release it. :(

Share this post


Link to post

 

I don't know why but I just started laughing when I read this. It's as if the engineering doesn't even see the unit until afer it's released to the public. Everything seems to be a surprise to them. It's as though they don't take an interest in playing with the products they engineer as much as most of the people in these forums.

 

Man, if we could all just get togther and design a GPS it would be the end-all be-all. Or if a company would sit us all down in a room for a few hours they would have the market-cornering outdoor/geocaching GPS.

 

I digress.

 

you would thing they would have some sort of beta testing team. get 100 people to use the units months in advance, work out all the glitches and problems, then release it. :(

 

Why do it when they know there are guys like us, early adopters (a.k.a. guinea pigs) that will pay $500+ to do it for them LOL :lol::lol:

 

Seriously what do we do - return the units to the store we bought them while there is still time to do so or have faith in Garmin to recall the units / quickly fix these seemingly major hardware flaws?

 

I am torn, because other that this confirmed serious altimeter issue and hit and miss squeaky case issue (geeze, do i need more "other thans"?), I like my new 62ST.

Share this post


Link to post

Called Garmin this morning to talk to them about my replacement (second one) flimsy-sided, squeaky unit and the tech-rep said he received an e-mail this morning from engineering stating that the flimsyness and squeaking are NOT defects and will no longer be exchanged.

 

Hmm, some units squeak and some units side plastic pushes in and feels flimsy and others don't. This isn't a defect? This electronic equipment that I just paid top-dollar for shouldn't feel and sound like a cheap piece of $#!T in my hand. Just be aware as a consumer, if your considering this product, that the designers and engineers call this normal and don't plan on addressing it in any way. So buyer beware, you may get a flimsy squeaker or you may get a solid unit, flip a coin.

 

I am going to side with Garmin on this instead of trigger happy technoids. Without taking it apart and analyzing the true cause - I strongly suspect that the squeak is a result of the two layers of the case. The rubberized outer layer and the inner hard plastic. The glue (if there is any) that keeps them together has dried out so when you press on the outer rubber it rubs against the inner plastic. The rubberized outer layer is there for water proofness as it seals the unit better than the hard shell of the 60 series. When I first looked at the unit itself, I remarked at how robust the battery compartment was and that it appeared to be better at keeping out moisture than the 60.

 

That's my story and I'm sticking to it! :(:lol::lol:

 

Seriously though, I have no idea why it squeaks and unless this issue is anything more than cosmetic I am going to keep my little squeaker and keep on caching.

 

Anybody got the guts to actually put the unit to a submerged water test? :(

Share this post


Link to post

Got my little squeaker (more like creaker) today. I'm in the camp that doesn't much care about the noise. I probably wouldn't have given it a second thought if it hadn't been mentioned here.

 

There are plenty of things I'm going to like about this unit, and some I don't care too much for. I'm moving from a 60csx, and I LOVE the compass on the 62. The electronic compass was a waste of money for me on the 60, and it was always off.

 

I wish the 62 could handle a zipped gpz file, but I'll probably be loading it from GSAK most of the time anyway. Can't wait to give it a good workout!

Share this post


Link to post

until now product.support@garmin.com (just got an email) does NOT confirm that there is any altimeter bug which has to be fixed.

 

If they cannot confirm this bug, they never might have started to solve that bug :(

What's going on with that company.

Share this post


Link to post

Seriously what do we do - return the units to the store we bought them while there is still time to do so or have faith in Garmin to recall the units / quickly fix these seemingly major hardware flaws?

 

I am torn, because other that this confirmed serious altimeter issue and hit and miss squeaky case issue (geeze, do i need more "other thans"?), I like my new 62ST.

 

Everyone has the same tough choice to make. The safe thing to do, of course, is to return your unit and buy another later if/when a fix comes out. Assuming you can get a full refund, of course. But that's not a very satisfying thing to do, since the 62st is so cool in most ways - but with one major flaw.

 

If your retailer won't give a refund - like mine - then it's more complicated. But I expect Garmin to do the right thing, so it'll all work out. !?

Share this post


Link to post

until now product.support@garmin.com (just got an email) does NOT confirm that there is any altimeter bug which has to be fixed.

 

Sure, that's to be expected. At this point just one support engineer has seen my data, has shown it to one help desk person, who has forwarded it to one engineer - who hasn't yet looked at it. Nobody else knows even this much is going on. Patience is a virtue at this point. Let's give them a few days to digest the situation and decide what to do next.

 

Of course, the clock is ticking and lots of folks are watching. A point I made to them firmly, by pointing out that i'm posting the info here and elsewhere. If I don't hear positive feedback in 7 - now 6 - days, we should go postal on them. But for now let's let them investigate and ponder for a few days.

 

If you want to call or email to let them know you are concerned about the issue that's super, but I wouldn't be surprised if the low level rep you talk to doesn't know anything about the issue yet.

Edited by sammydee

Share this post


Link to post

until now product.support@garmin.com (just got an email) does NOT confirm that there is any altimeter bug which has to be fixed.

 

Sure, that's to be expected. At this point just one support engineer has seen my data, has shown it to one help desk person, who has forwarded it to one engineer - who hasn't yet looked at it. Nobody else knows even this much is going on. Patience is a virtue at this point. Let's give them a few days to digest the situation and decide what to do next.

 

Of course, the clock is ticking and lots of folks are watching. A point I made to them firmly, by pointing out that i'm posting the info here and elsewhere. If I don't hear positive feedback in 7 - now 6 - days, we should go postal on them. But for now let's let them investigate and ponder for a few days.

 

If you want to call or email to let them know you are concerned about the issue that's super, but I wouldn't be surprised if the low level rep you talk to doesn't know anything about the issue yet.

 

I'm sure I'm going to feel like an idiot for asking once I see the reply to my question, but why is a momentary spike with a button press an important issue? If just holding the unit in a normal manner interferes with the reading, I can see that being more serious, but even that - why is that so important to a geocacher?

Share this post


Link to post
It's as if the engineering doesn't even see the unit until afer it's released to the public. Everything seems to be a surprise to them. It's as though they don't take an interest in playing with the products they engineer as much as most of the people in these forums.

 

Or, so it would *seem*...

 

This is pretty much EXACTLY what happened with the iPhone 4 release. Apple acted like there was nothing wrong with the antenna design, but when the "uneducated, unwashed masses", i.e. CUSTOMERS, figured out calls were dropping on the FIRST day of release? And, then they had these rubber phone condom things all stocked up and ready to go because they would *fix* the problem...with a rubber band...literally?

 

You cannot tell me those Apple engineers didn't know about this problem if they'd just USED the damned thing like a phone. They knew about the signal strength loss and dropped calls...and did NOTHING about it until after release because they knew their good little fanboys would lap up their crap anyway. :(

 

These companies are really pushing/abusing the limits of their customer patience. :lol:

Share this post


Link to post

I'm sure I'm going to feel like an idiot for asking once I see the reply to my question, but why is a momentary spike with a button press an important issue? If just holding the unit in a normal manner interferes with the reading, I can see that being more serious, but even that - why is that so important to a geocacher?

 

Personally I like recording my tracks so I can tell how many miles I have hiked and how many feet I have climbed. (340 miles and 78000 feet so far this year.) My first hike with the 62st came in at 8000 vertical feet, when my hiking partners logged 2000. For me this is a fatal flaw. But sure, you can certainly find caches without looking at altitude at all. If you don't care about altitude tracking buy a 60 (not s or st) and save $200.

 

I think we all want the 62st to be a deserving successor to the 60csx. With this flaw it does not deserve that title. With a fix for this I suspect it will. That's why I expect Garmin to fix the issue asap.

Share this post


Link to post

Makes sense. The altimiter works by sensing air pressure. If the case flexes enough to change the volume of the case faster than the external vent thingy will let it equalize, it's going to change the air pressure.

The old etrex models with barometric altimeter did this as well, but to a lesser degree. I noticed a glitch like this every time I took it out of the holder and squeezed the case a little. I don't think it was so extreme that it produced a glitch every time I pressed a button though, that's very poor. My current GPS, and Oregon 550t, doesn't suffer from this at all, but has a very solid sturdy case which would explain it.

Share this post


Link to post
I'm sure I'm going to feel like an idiot for asking once I see the reply to my question, but why is a momentary spike with a button press an important issue? If just holding the unit in a normal manner interferes with the reading, I can see that being more serious, but even that - why is that so important to a geocacher?

 

In its current form, the "total ascent" reading is absolutely useless on the 62s and st. Simply handling the unit and checking things like the elevation, trip computer, compass, etc. for a few moments will add 30 or 40 ft to the total. After a few hours of hiking, this can really add up. I personally don't do geocaching -- my GPS is used for navigation, and for stats on the hiking/biking I've done. The elevation stats, which is one of the more important things I look at, is useless because of these elevation spikes.

 

It should be reiterated that even though the "Fixed Elevation" smooths out the elevation plot, and apparently the track recording as well, it does NOT fix the problem with the "total ascent" or even the current elevation reading. This is just not acceptable in what Garmin themselves refers to as a "top of the line" GPS.

 

Larry

Share this post


Link to post

I've always found the Total Ascent field to be much more reliable than tracklog derived elevation data.

 

FWIW, my 60CSx has always been the best for getting a true reading of elevation gain. In reviewing my testing figures, it looks like there has been a fix applied in the most recent 62 series firmware. My early readings were way off (2x the 60CSx), while they were very close to each other in my last test -- close enough that I can't tell which is more accurate.

 

The best test would be a hill climb with no ups and downs -- well, just ups! Compare it to known elevation. Benchmarks would be ideal, but a topo map will get you pretty close. Its always possible that some smoothing may be happening in the background.

Share this post


Link to post

I'm sure I'm going to feel like an idiot for asking once I see the reply to my question, but why is a momentary spike with a button press an important issue? If just holding the unit in a normal manner interferes with the reading, I can see that being more serious, but even that - why is that so important to a geocacher?

 

Personally I like recording my tracks so I can tell how many miles I have hiked and how many feet I have climbed. (340 miles and 78000 feet so far this year.) My first hike with the 62st came in at 8000 vertical feet, when my hiking partners logged 2000. For me this is a fatal flaw. But sure, you can certainly find caches without looking at altitude at all. If you don't care about altitude tracking buy a 60 (not s or st) and save $200.

 

I think we all want the 62st to be a deserving successor to the 60csx. With this flaw it does not deserve that title. With a fix for this I suspect it will. That's why I expect Garmin to fix the issue asap.

 

Gotcha! I couldn't care less about the altimeter, but I think I'm going to love the 3 axis compass (coming from a 60csx). Can't wait to try it out. I also want the micro sd slot, so there are other reasons to choose the 62s and st over the 62.

 

Anyway, I hope the altimeter issue gets resolved! That IS serious! Thanks for the reply.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  
Followers 10

×
×
  • Create New...