Thanks for the heads-up on rel. 2.3.

I got my 705 on July 5th and recently completed the first 500 miles with it, including the Seattle To Portland double century. I think it a great tool. :thumb: The integrated speed sensor is a great innovation. For several years I used a Garmin GPSMap 60cs for cycling.It has the mapping and track history functions but it would wander off when I stopped and it assumed that you were continuing in a straight line when the signal was lost. Then it would correct at 200 mph when the signal came back. This one never looses track. When signal is lost, it uses the internal compass and speed sensor to continue. It is accurate enough to tell which side of the street you were on in the track history. The elevation track is stable, no jumps or weird values.

The battery life is good, it was on and recording data for about 15 hours during STP. It would be nice to have replacable batteries. The other Garmin I have uses AA batteries which is nice because you can replace them any time. I'm going to try to make a waterproof version of the Mintyboost (http://ladyada.net/make/mintyboost/index.html) to extend the operating life for brevets.

Just did my first ride with release 2.3 in the 705. It was a century, and at mile 62 I once again had the autonomous shut-off failure noted in an earlier post. As in the other instances it looked OK when I first turned it back on--still had my mileage--but then I noticed that the average speed had gone way up. So the only way I can reconstruct my probable average speed is to go back and look at individual laps--if I had the foresight to press the lap button occasionally.

It also seems to still have the problem of not knowing what to do if you slightly deviate from the route, like pulling off for a rest stop. It starts asking you to make a U-turn and/or routing you off on side streets, not on the route. Perhaps this is asking too much. I have found that I can work around this problem by telling it to "Stop Navigating", riding a short distance back on the route, and then going to Where To, Saved Routes, selecting the route again and telling it to navigate. It will eventually figure out where I am on the route and start giving me correct turn-by-turn directions again. The turn-by-turn directions with their beeping warnings are a great heads-up to start looking for the Dan Henry symbols on a marked route.

I have my fingers crossed that a release 2.4 is not too far away and that it will address one or both of these problems.

Is the Auto shutoff a new issue or one you have had before? I haven't seen this yet on mine...but I also haven't updated to 2.3

Guys, I'm really not trying to be a smart@$$ when I say this but this thread would be a lot shorter if you all would read the owners manual.

I don't think the owners's manual (which I have read) mentions autonomous shut-offs, and no this is not the first time it has happened. This last time was maybe, about the 3rd or 4th, and in every case the average speed shoots way up; e.g. 576 mph.

Trick for converting larger files to GPX to import to MapSource:

I have had a couple of long rides that exceeded the 3 meg file limit for GPS Visualizer (http://www.gpsvisualizer.com/convert) conversion from tcx format to gpx for importing to MapSource. I wrote an awk script that strips out the heart rate and cadence data, reducing the file size by about 30%.

File strip_tcx.awk:

# Usage: awk -f strip_tcx.awk input_name.tcx > output_name.tcx

/HeartRateInBeatsPerMinute_t/ { for (i=1; i<4; i++ ) getline }
/\<Cadence\>/ { getline }
/./ { print $0 }

Been holding off on updating to 2.3. Hoping to hear that some of the more adventurous folks here would be giving full thumbs up (or maybe the opposite) on the upgrade? I'm planning on my first Century with the 705 this weekend and would rather not suffer the autonomus shut off that Oroluk got at the 62 mile mark or find that the speed is way off again as I experienced with version 2.2 before finding the manual setting technique for wheel circumference here on this forum.

I did a 65 miler on Saturday with no issue (still on version 2.2). Anyone else having the 62 mile point shutoff with version 2.3?

Is the automatic wheel size calibration working correctly now with 2.3 or do we stay with the manual setting to get an accurate speed reading?

Any other 'hiccups' to be aware of?

Thanks in advance

Ok, Maybe I'm missing something, or maybe it's because I didn't purchase detailed maps yet, but here goes. I just got my edge 705, and I'm loving it so far, I had the 305 for two years, so I am familiar with most of the menus.

Here is the catch, I have the 2.30 software, and I'm trying to find by address, and it doesn't give me that option, when I do find I get "favorites" and "cities" and that's it. Anyone have any suggestions?

Joe

Ok, Maybe I'm missing something, or maybe it's because I didn't purchase detailed maps yet, but here goes. I just got my edge 705, and I'm loving it so far, I had the 305 for two years, so I am familiar with most of the menus.

Here is the catch, I have the 2.30 software, and I'm trying to find by address, and it doesn't give me that option, when I do find I get "favorites" and "cities" and that's it. Anyone have any suggestions?

Joe

You do need the detailed maps in order to use the address and some of the other functions. City Nav NT on DVD is your best bet. I think Amazon has it for about $70. Then you can load them into the onboard memory of the Edge or put in a 2gb (no bigger) SD card and load most of the USA into it.

You do need the detailed maps in order to use the address and some of the other functions. City Nav NT on DVD is your best bet. I think Amazon has it for about $70. Then you can load them into the onboard memory of the Edge or put in a 2gb (no bigger) SD card and load most of the USA into it.

Ok, that's cool, I planned to get that anyway, at some point. Thanks!

Joe

Been holding off on updating to 2.3. Hoping to hear that some of the more adventurous folks here would be giving full thumbs up (or maybe the opposite) on the upgrade? I'm planning on my first Century with the 705 this weekend and would rather not suffer the autonomus shut off that Oroluk got at the 62 mile mark or find that the speed is way off again as I experienced with version 2.2 before finding the manual setting technique for wheel circumference here on this forum.

I did a 65 miler on Saturday with no issue (still on version 2.2). Anyone else having the 62 mile point shutoff with version 2.3?

Is the automatic wheel size calibration working correctly now with 2.3 or do we stay with the manual setting to get an accurate speed reading?

Any other 'hiccups' to be aware of?

Thanks in advance


I have been running 2.3 since the day it was released. I have had no issues with 2.3 then again my 705 has never had an issue. :thumb:

The auto wheel size issue has been fixed. The only new confirmed bug I know about occurs if you use the start/stop button mid ride. This can cause a lap with no data to be logged into your file. This may cause issues with downloading to Training Center or other programs.

That is about it.

I have been running 2.3 since the day it was released. I have had no issues with 2.3 then again my 705 has never had an issue. :thumb:

The auto wheel size issue has been fixed. The only new confirmed bug I know about occurs if you use the start/stop button mid ride. This can cause a lap with no data to be logged into your file. This may cause issues with downloading to Training Center or other programs.

That is about it.

Thanks Luv2climb. Guess I'll take the chance and go to 2.3. and test the auto wheel size thing tonight. Still scratching head to understand why a GPS based speed calculating method would be affected by the wheel size (except during GPS signal loss moments) calibration. Here's hoping I don't run into the 62 mile recording stop.

Still scratching head to understand why a GPS based speed calculating method would be affected by the wheel size (except during GPS signal loss moments) calibration.


The 705 uses the sensor as the primary input for the speed. It uses the GPS to back it up. This is a change from the 305 which was the other way around.

The 705 uses the sensor as the primary input for the speed. It uses the GPS to back it up. This is a change from the 305 which was the other way around.

Ah, so that's it. Thanks for the clarification

I seem to have one issue with the 2.3 on the 705. I just installed the maps last night, thanks to luv2climb, that did fix my no "address" option, and wow, what a load of poi's. But here is the odd thing, in real time my unit is not showing elevation, or elevation data, additionally, when I pull my ride data, I get the error "There was a problem downloading your profile data, do you still want to download your ride data?" I say yes, and my rides come down fine. When I look at the data from the ride, it shows elevation, but on the unit I don't have real time elevation, nor do I show total climb while I'm riding even though this is a setting I have selected to show. Any advice on this?

Joe

I seem to have one issue with the 2.3 on the 705. I just installed the maps last night, thanks to luv2climb, that did fix my no "address" option, and wow, what a load of poi's. But here is the odd thing, in real time my unit is not showing elevation, or elevation data, additionally, when I pull my ride data, I get the error "There was a problem downloading your profile data, do you still want to download your ride data?" I say yes, and my rides come down fine. When I look at the data from the ride, it shows elevation, but on the unit I don't have real time elevation, nor do I show total climb while I'm riding even though this is a setting I have selected to show. Any advice on this?
Joe

Interesting. You have successfully stumbled upon two of the current bugs that the Edge has at one time! :thumb:

Fortunate for you the fix for both is the same, a hard reset of the Edge. The reset will not erase your maps so dont worry about them. Here are the instructions:
1) Make note of all the fileds you display on the various screens and all your profile settings (user and bike) as you will need these later on in step 9
2) Plug Edge into computer
3) Go to the profile folder on the Edge
4) Delete the contents of this folder
5) Unplug Edge
6) Turn Edge off it not off already
7) Press and hold Mode and Power at the same time
8 ) When prompted to erase all user data select yes
9) Rebuild all your screens, user profile, and bike profiles based on step 1 above


If you have any more questions feel free to post them.

Hmm, I did the hard reset, and it appears to have resolved the profile issue, however the altimiter is still reading _ _ _ _ when I go to that screen. Odd, I'll play with it and see how it goes, worst case scenario I'll wait for 2.4 and see if that resolves it, or give Garmin support a shout. I've been waiting for this thing since march, so I'm fine with having a glitch or two, I'm just happy to have it in hand. I love the mapping, haven't had a chance to really try it out, but the wife and daughter are gone two weekends from now, so it WILL be getting a workout!

Joe

Power the Edge on by pressing Power and Enter at the same time. Wait for the beep. The 3rd line from the bottom of the screen is altitute, you may have to wait 30 seconds. Does it give you the correct elevation?

First a clarification about my autonomous shut-off events. They don't happen at exactly 62 miles. That just happened to be the mileage the last time it happened before that particular post. This problem, as far as I can tell, happens only when I am navigating a Saved Ride. I don't recall it happening when I am just riding a random route. Second, it only seems to happen well into a longer route; e.g. 50, 60, miles, centuries, etc. I am NOT getting a low battery warning so I don't think that's it. When I restart the unit it is still navigating the route, but my average speed always jumps way up.

If I'm the only 705 owner that is having this problem (luv2climbsays it's not one of the known bugs), then perhaps I have a defective unit that needs to be exchanged or repaired.

So, my question is, AM I the only 705 owner on this forum thread that has had this problem?

First a clarification about my autonomous shut-off events. They don't happen at exactly 62 miles. That just happened to be the mileage the last time it happened before that particular post. This problem, as far as I can tell, happens only when I am navigating a Saved Ride. I don't recall it happening when I am just riding a random route. Second, it only seems to happen well into a longer route; e.g. 50, 60, miles, centuries, etc. I am NOT getting a low battery warning so I don't think that's it. When I restart the unit it is still navigating the route, but my average speed always jumps way up.

If I'm the only 705 owner that is having this problem (luv2climbsays it's not one of the known bugs), then perhaps I have a defective unit that needs to be exchanged or repaired.

So, my question is, AM I the only 705 owner on this forum thread that has had this problem?

I dont think so. There are a few people that have had it happen over on the Motion Based foums but no one can determine if it was an software issue or an issue with their route.

Nope, no altitude ever shows up on that line. :( Odd.

Nope, no altitude ever shows up on that line. :( Odd.

What happens when you press menu, Save Location, Avg? Does it show elevation on that screen?

First a clarification about my autonomous shut-off events. They don't happen at exactly 62 miles. That just happened to be the mileage the last time it happened before that particular post. This problem, as far as I can tell, happens only when I am navigating a Saved Ride. I don't recall it happening when I am just riding a random route. Second, it only seems to happen well into a longer route; e.g. 50, 60, miles, centuries, etc. I am NOT getting a low battery warning so I don't think that's it. When I restart the unit it is still navigating the route, but my average speed always jumps way up.

If I'm the only 705 owner that is having this problem (luv2climbsays it's not one of the known bugs), then perhaps I have a defective unit that needs to be exchanged or repaired.

So, my question is, AM I the only 705 owner on this forum thread that has had this problem?

Thanks for the clarification on the autonomous shut off events. I've updated to 2.3 now & haven't had that issue either with 2.2 or 2.3 and have had > 65 mile rides with both, although I don't use navigation of a saved ride at all (yet). Will keep fingers crossed that it doesn't happen when I get around to using that feature.

What happens when you press menu, Save Location, Avg? Does it show elevation on that screen?

Yes, on that screen it does show it, but still not on the other one.

Joe

Yes, on that screen it does show it, but still not on the other one.

Joe

Well that is a good sign, I think.......

Digging for straws here.

When you did the full reset did you delete your profile first?

How accurate is your satelite?

Are you outside?

How long did you let it sit before you checked the elevation?

Well that is a good sign, I think.......

Digging for straws here.

When you did the full reset did you delete your profile first?

How accurate is your satelite?

Are you outside?

How long did you let it sit before you checked the elevation?

Yes, deleted profile first.

Sat acc about 14 feet on average

Yes, I have been both outside, and inside with 5 sats locked on.

Let it sit about 2 min, and then checked.

Joe

I'm running 2.3 and just saw some really bizarre behaviour wrt elevation and grade display:

http://www.dim.com/~ryoder/gldngtcyn.png

Note the start/finish is at the upper right, and the turnaround point is at the lower left. The return trip retraced the outbound trip, so the righthand side of the elevation *should* be the mirror image of the lefthand side. But looks what happened between mile 44 and mile 66. At mile 66 it suddenly regained it's senses at the point where it appears I rode over a 1500' cliff. On the descent, I first noticed the grade reading wasn't corresponding at all to reality, then as I descended further I saw that familiar locations were being indicated as being much higher than they were on the way up. Now one more piece of data;

Just a 1/2 mile from the top of the ride, I was caught in a downpour, resulting in me taking refuge in the office of a campground, where I spent 2 hours waiting for the rain to stop as I ran my clothes through a dryer to stave off hypothermia. (Thank goodness for that campground!!!) The entire descent was on rainsoaked roads with light drizzle. I didn't see a dry road again until I began the Northbound leg. Note how this corresponds to the portion of the ride where the elevation data was wacked out. Could it be that being wet causes the 705 to lose it's ability to track altitude?

I'm running 2.3 and just saw some really bizarre behaviour wrt elevation and grade display:

http://www.dim.com/~ryoder/gldngtcyn.png

Note the start/finish is at the upper right, and the turnaround point is at the lower left. The return trip retraced the outbound trip, so the righthand side of the elevation *should* be the mirror image of the lefthand side. But looks what happened between mile 44 and mile 66. At mile 66 it suddenly regained it's senses at the point where it appears I rode over a 1500' cliff. On the descent, I first noticed the grade reading wasn't corresponding at all to reality, then as I descended further I saw that familiar locations were being indicated as being much higher than they were on the way up. Now one more piece of data;

Just a 1/2 mile from the top of the ride, I was caught in a downpour, resulting in me taking refuge in the office of a campground, where I spent 2 hours waiting for the rain to stop as I ran my clothes through a dryer to stave off hypothermia. (Thank goodness for that campground!!!) The entire descent was on rainsoaked roads with light drizzle. I didn't see a dry road again until I began the Northbound leg. Note how this corresponds to the portion of the ride where the elevation data was wacked out. Could it be that being wet causes the 705 to lose it's ability to track altitude?

Actually I do think I know what caused your issue, the 705 like the 305 uses a barometric altimiter to track your altitude, along with the GPS, as a result, you end up having oddness if the weather changes mid ride. Mine however just isn't working at all, the altimiter always reads _ _ _ _ _ Ft. I may try another reset too see if that fixes it.

Joe

Well, back to the drawing board, second reset and still have the issue. Strange, perhaps my barometric sensor is bad in the unit?

Actually I do think I know what caused your issue, the 705 like the 305 uses a barometric altimiter to track your altitude, along with the GPS, as a result, you end up having oddness if the weather changes mid ride. Mine however just isn't working at all, the altimiter always reads _ _ _ _ _ Ft. I may try another reset too see if that fixes it.

Joe

Sorry, but I can't buy that it was atmospheric pressure change.

The storm came in just before I reached the peak at 9000'.
I spent two hours sitting in a campground office waiting for it to blow over.

As I descended, it ABRUPTLY went goofy, with the grade wandering around -1 to +1 while I was descending a 6% grade. You can see the dogleg in the elevation data at 44-45 miles where it suddenly flattens out. From that point until 66 miles, there were two steep climbs during which the grade never registered that I was climbing, but claimed I was still slowly descending.

Then at 66 miles, it ABRUPTLY corrected itself and worked normally the rest of the way home.

My suspicion is that riding the wet road back down the mountain, (on a road bike w/o fenders), caused water to be thrown up against the underside of the unit where those two sets of holes are. Since the air pressure was increasing to descending, this could cause water to be pushed in the holes. The Northbound leg of the ride was dry, and it was soon after turning North that the unit regained normal function.

Indeed, that does seem extreme to be atmospheric pressure. Looks like perhaps the 2.3 has some flaky issues with the altimiter? The good news is it does come with a 1 year warranty, so I'll wait a bit and see if the next fix takes care of it. I don't generally use elevation data during a ride, and it does seem to import it ok after the fact.

Joe

The 705 uses barometric pressure and temperature to measure elevation changes. This info is fed to the sensor via the holes in the bottom of your Edge. I am wondering if when you were rained on a light film of water covered these holes. This seams plausable as when they water layer you saw the 1,500' cliff.

The elevation scale on the elevation page did not scale to match the profile of the ride like the 305 does (IMAGE_010). However about 1/3 of the way through the ride it was scaling just fine (IMAGE_006).


Can you explain this a little more? I'm not sure what you mean by "scale". I guess I'm just not clear on what the elevation page is showing me, is it just what I've done or does it show what climbs are coming up? Are there options about how I can set this page up?

The 705 uses barometric pressure and temperature to measure elevation changes. This info is fed to the sensor via the holes in the bottom of your Edge. I am wondering if when you were rained on a light film of water covered these holes. This seams plausable as when they water layer you saw the 1,500' cliff.

You know, funny thing here, when I look at the diagnostic page, guess what other field is blank? The Temp field. Bad sensor perhaps?

Joe

Can you explain this a little more? I'm not sure what you mean by "scale". I guess I'm just not clear on what the elevation page is showing me, is it just what I've done or does it show what climbs are coming up? Are there options about how I can set this page up?

The 305 only let you scale the horizontal and it would automatically scale the vertical. The 705 allows you to scale both of them. You do this using the thumb stick, up/down for vertical and left/right for horizontal.

You know, funny thing here, when I look at the diagnostic page, guess what other field is blank? The Temp field. Bad sensor perhaps?

Joe

I think at this point you may be right. Call Garmin direct and my guess is that you will be getting a new unit.

Oh happy day!!!
I retured my 605 and got ALL of my money back.
Now I can ride my bike the way it was built to be ridden --for the FUN of it.
What a piece of cr@p Garmin has foisted upon us!

Man I love my 705. I did an 85mi ride last week and a 55mi ride today. I love just getting lost and returning via GPS -- marking every cool hill on the way. I loved the 305 for this reason, too. But now I know what city or major roads I'm on.

I'm in the process of loading the north america 2009 mapsource maps onto my microSD card. It's taking about 20min, but I'm excited to finally use this feature so I can look at all the really small roads I take. I'm liking Madison more and more.

Can't wait for my sponsor, Saris, to come out with ANT+ for the powertap.

Talked to Garmin, they say it's most likely a bad sensor, so I gotta get my proof of purchase and send it to them so I can get it replaced. I'm gonna hold off for a bit, as I want to keep using it, but it's good to know I'm not crazy.

Joe

Oh happy day!!!
I retured my 605 and got ALL of my money back.
Now I can ride my bike the way it was built to be ridden --for the FUN of it.
What a piece of cr@p Garmin has foisted upon us!

Dude, to each his own, but I LOVE my 705. I love just putting it on the map page and glancing down to see what roads I'm zipping past. I love being able to see what I'm close to that I could never see with the naked eye (like I never knew there was this large body of water right near where I pedal past, I'm going to take the time to check that out too). This thing rocks. Heck, turn off all the numbers and just use the map to find eats when you do a century and the thing is worth it's weight in gold. I love it!

Joe

Just a quick question- I am wondering why in bicycle mode, when I select where to and type(key in) an address and select go to; the edge is trying to have me get on an express way. Is there a work around for this other than to just ignore it and continue that portion of the route another way and then allow the edge to recalculate the route from that point? In my case I used goggle maps to calculate a walking route and then tried to have the edge do the same for the bicycle. I have marked avoid major streets and then done the same with that check mark removed. I also tried to place the edge in car mode and selected avoid highways and it still tried to route me onto the ramp and then get off at the next exit and then ride on normal streets or road's that I would be okay riding.
Thx Mike

I got this idea from reading the forum on motionbased...but has anyone tried using the Route and Course function at the same time? It was suggested this would allow you to still get the prompts from the Route and that Course will make sure you are going the way you want to go (it will help if the 705 tries to re-route you).

Just a quick question- I am wondering why in bicycle mode, when I select where to and type(key in) an address and select go to; the edge is trying to have me get on an express way. Is there a work around for this other than to just ignore it and continue that portion of the route another way and then allow the edge to recalculate the route from that point? In my case I used goggle maps to calculate a walking route and then tried to have the edge do the same for the bicycle. I have marked avoid major streets and then done the same with that check mark removed. I also tried to place the edge in car mode and selected avoid highways and it still tried to route me onto the ramp and then get off at the next exit and then ride on normal streets or road's that I would be okay riding.
Thx Mike

I also use Google maps to plan my rides. Once I have determined the route I want to take, I use this website to create a route:

http://www.marengo-ltd.com/map/

I make a waypoint at every turn to ensure the 705 has no logical alternative to the route I want.
Then:
- Hit the "GPX" button to get the XML text box.
- Copy/paste the XML into <filename>.gpx.
- Connect the 705 to your computer, and copy the file into the 705's GPX directory.

Now just bring "Where To?" -> "Saved Rides", and it will appear in the list.

Just a quick question- I am wondering why in bicycle mode, when I select where to and type(key in) an address and select go to; the edge is trying to have me get on an express way. Is there a work around for this other than to just ignore it and continue that portion of the route another way and then allow the edge to recalculate the route from that point? In my case I used goggle maps to calculate a walking route and then tried to have the edge do the same for the bicycle. I have marked avoid major streets and then done the same with that check mark removed. I also tried to place the edge in car mode and selected avoid highways and it still tried to route me onto the ramp and then get off at the next exit and then ride on normal streets or road's that I would be okay riding.
Thx Mike

What mapset do you have loaded?

Are they turned on in the Settings/Maps screen?

What country do you live in?

Here in California bikes are allowed on some express ways so it may come down to how the roads are categorized within the mapset. If this is the case though one would expect the avoid major roads function to route you around it UNLESS the alternative takes you way out of the way.

What mapset do you have loaded?

Are they turned on in the Settings/Maps screen?

What country do you live in?

Here in California bikes are allowed on some express ways so it may come down to how the roads are categorized within the mapset. If this is the case though one would expect the avoid major roads function to route you around it UNLESS the alternative takes you way out of the way.

The card- 2009.
Yes that is what I have selected for it to use.
USA

I do not think that a bicycle is permitted on the watterson 264 in Louisville, KY and even if it were, I would not chose to ride one on it.
Routing- that could be the case as, the edge tried to take me on a 120 mile jurney to get across the river that should have been a 20 mile ride a few days earlier.

Still, I like this device.
Will try my luck with the course feature on todays commute home.

Regarding history on the 705, I cleared history, selected history menu selected the unit returns, "no history saved",
So I was surprised when connected to the computer the history folder was full, a file for each ride. I expected it would be empty. What am I missing here?

Has anybody seen this problem? I find the Edge 705 elevation varies wildly. For example, I live in California at about 110 feet above sea level. Yesterday when I woke up and switched on the Edge, it showed i was at about minus 10 feet. I did a 10 mile ride and when I returned home--still around minus 10. Then this morning I switched it on and put it outside so it could commune with the satellites. It showed 108. That's right! Then I went for a ride up into the Santa Cruz Mtns but when i got home 2 hrs later it showed 350 feet!! Weird! It's especially weird because in the Garmin FAQs then say it calculates elevation from the GPS coordinates, not from barometric pressure which can vary over time. They also claim it's more accurate than barometric pressure! Anybody else seen this and have any idea what to do about it?
Thanks.

Regarding history on the 705, I cleared history, selected history menu selected the unit returns, "no history saved",
So I was surprised when connected to the computer the history folder was full, a file for each ride. I expected it would be empty. What am I missing here?

What software version is on your Edge. I think this was an issue that 2.3 fixed but 3 am not positive. Regardless the fix is to delete the files from your computer.

Has anybody seen this problem? I find the Edge 705 elevation varies wildly. For example, I live in California at about 110 feet above sea level. Yesterday when I woke up and switched on the Edge, it showed i was at about minus 10 feet. I did a 10 mile ride and when I returned home--still around minus 10. Then this morning I switched it on and put it outside so it could commune with the satellites. It showed 108. That's right! Then I went for a ride up into the Santa Cruz Mtns but when i got home 2 hrs later it showed 350 feet!! Weird! It's especially weird because in the Garmin FAQs then say it calculates elevation from the GPS coordinates, not from barometric pressure which can vary over time. They also claim it's more accurate than barometric pressure! Anybody else seen this and have any idea what to do about it?
Thanks.


The 705 actually uses barometric presure and temp to calculate elevation. It really likes to aclimate itself pre-ride just like you did on the one ride you did. It does however have some issues in calculating elevation. You should report your issues to Garmin. Many of us have already asked to have the ability to manualy set the current elevation.