I should also note that after first noticing the problem, I've been using my trusty Geko 301 as a reference unit, packing the Geko in one shirt pocket and the Vista in the other.
TRACKSIFT 2 DOWNLLOAD SOFTWARE
On a couple of subsequent walks, I observed the same kinds of systematic positional errors that developed after the unit had been powered on for a while.Īfter reading some of the posts here, I downgraded the GPS chipset software to 2.50 (keeping the 2.70 unit software) and on at least one test walk (of only about 2 miles), the tracks seemed OK. On my first test walk of about 5 miles, the drift problem was horrible with portions of the track shifted more than 900 feet from where it should have been. I recently purchased a Vista HCx from that I immediately upgraded from 2.60/2.60 to 2.70/2.60. I am a hardcore backpacker and long-time GPS user, having owned several Garmin units over the years. But, I did not leave 2.8/2.6 on the gps - I reset it to 2.8/2.8 Edited Octoby jmundinger It worked the same way the the other backdates did. So, at the moment, I don't feel compelled to backdate the unit but I'm reasonably certain I could if I wanted to.Įdit: even though I had no compelling need, I did try the back date to chipset 2.60.
That one might not have been a good test of the odometer, however, because my pace was quick enough that I probably would not have experienced the odometer problem with the older configuration (I also think that the odometer problem was significantly less with 2.7/2.5). I've done one walk in my neighborhood and got a clean track that was reasonably consistent with the trip computer. I have upgraded to 2.80/2.80 and, although I have not tested it extensively, my initial impressions are favorable - quick lock up and onto more satellites with a lower estimated error rate than with previous configurations. That configuration seemed to be working reasonably well. Although, it then locked on when I restarted the unit, I wasn't happy with it. I had downgraded 2.70/2.60 to 2.70/2.30 and, when I first turned it on, the unit would not lock onto the satellites any better than an estimated error in excess of 150+ ft. I haven't tried it yet and probably won't because I am not impressed with chipset 2.60. Many of you have upgraded already, so you don't risk much by just trying out wheter downgrades are still possible.
img but something else) and the impossibility to downgrade Nuvis I'ld like to know if downgrade is still possible from 2.80. So John, could you just give it a try to downgrade back from 2.80 to something else? With the appearance of a new map format (CN Europe 2009 - only compatible with mapsource 6.14.1, no more.
0 kommentar(er)
