Features, readability, housing etc. may all be better or worse subjetiv, than its predecessor,
However, the device slips up in a discipline that is for me the most important: The accuracy!
Since October, the manufacturer aware of the problem and - it is hushed up. The 62er "shoots" in the track log
sometimes extremely over (thinks quasi points out) is extremely inaccurate in the slightest reception problems and thereby
compared to -Even älteren- Garmin devices for albsoluten no-go.
Now in winter, this problem may strike not great in nice weather and foliage-free forest, coniferous forest in the light one notices
today what the device can not cope with.
Garmin has this problem in his own public forum though "recognized" and said it is working on a solution - but at this
Status has now done much since 3 months.
Too Bad. For me personally, the suspicion arises that is no longer similar this "reception problem" with a new firmware to "solve" is, but the problem can not be solved because of the receiver chip - but that's speculation.
All the robust - relatively accurate - Garmin device search - remains the 60s!
Addendum 24/04/2011 Firmware 2.94
I am not reported last long for word - this time I wanted to test a lot of situations in peace - and did this as slowly completely the desire for the device verlohren. My feelings switches the disappointment - and now anger at Garmin. Because what the new firmware does - reminds me of "national verarsche" (sorry).
Well, now back on the factual level :-)
a) when operating the device, for example the bicycle handlebar on a dirt road - is nothing wrong with the track results. Therefore, I do not go on a well.
b) My Testzenarien: Mounted "to" a backpack - all-round visibility. Areas: Teutoburg Forest (mainly deciduous forest - not tight) and Rothaargebirge (coniferous forest).
I simply have no desire to detailed bug reports (I have dozens of Garmin sent directly - on request) I think it is here now short:
That what the device now dominates - and perfect - is DRIFTING. For the User
see the track on the display of clean and constant. But is often constant
up to 50 meters (extreme situations) next to it. For other devices, the poor reception (reflections, shadows, etc.) can be seen through a dirty track history. (Zig-zag course, slalom course to actual track etc). In the current
Firmware is Garmin taken a different approach: Here the position is now as long as "broken-expected" to result as a harmonized Route comes out -
but who has now times nothing to do with reality.
Accuracy Display: Maybe it's already noticed one or the other - in the basic display accuracy is pinned at 3 meters. This indicator has little to do now with the 50% rule - but rather with the statement: Ok, I receive enough satellites - and I should somehow hinbekommen sometimes 3-meter accuracy "Deep in the forest, the display was like 'stapled' and went rarely to 4 meters or more "up". 2 meter accuracy can only be achieved by the switched "ENGOS" correction data reception. But again, the accuracy indicator has nothing to do with reality.
Principle: It received + EGNOS = 2 meter accuracy more than 5 satellites
Principle 2: It received more than 5 satellites - Egnos = 3 meter accuracy
Principle 3: There is an accuracy> 3 meters displayed: Oops - what is wrong here!
Therefore my (added hard) judgment: Volksverasche. Here the user is a precision + Track History "fooled". Nothing else.
Example: JOSM + area / path / to (s) already tens of tracks uploaded = Reference.
Result: 62s (t) tracks are often extremely next to the real track - and constant! So "clean track course" but totally wrong.
And now comes the trouble: the users does not fall on the same error. Since way in JOSM / potlatch be registered in good faith that the own track but must be right because that looks so constant and clean. #Fail
Pity pity Garmin. We users are not stupid. And it falls to us when trying to present us "apparently-good" results a.
