- News
- Reviews
- Bikes
- Accessories
- Accessories - misc
- Computer mounts
- Bags
- Bar ends
- Bike bags & cases
- Bottle cages
- Bottles
- Cameras
- Car racks
- Child seats
- Computers
- Glasses
- GPS units
- Helmets
- Lights - front
- Lights - rear
- Lights - sets
- Locks
- Mirrors
- Mudguards
- Racks
- Pumps & CO2 inflators
- Puncture kits
- Reflectives
- Smart watches
- Stands and racks
- Trailers
- Clothing
- Components
- Bar tape & grips
- Bottom brackets
- Brake & gear cables
- Brake & STI levers
- Brake pads & spares
- Brakes
- Cassettes & freewheels
- Chains
- Chainsets & chainrings
- Derailleurs - front
- Derailleurs - rear
- Forks
- Gear levers & shifters
- Groupsets
- Handlebars & extensions
- Headsets
- Hubs
- Inner tubes
- Pedals
- Quick releases & skewers
- Saddles
- Seatposts
- Stems
- Wheels
- Tyres
- Health, fitness and nutrition
- Tools and workshop
- Miscellaneous
- Cross country mountain bikes
- Tubeless valves
- Buyers Guides
- Features
- Forum
- Recommends
- Podcast
Add new comment
2 comments
Did you cycle a course or planned route? If so may be when you planned your route there was no underlying elevation data available for part of your route. Either that or you used Garmin Connect to plan your route and this often fails to download the elevation data even though Garmin Connect shows that it exists in the elevation profile. I have had this happen many times, although only for the entire route not jus part of it.
Anyway it's a Garmin device so you should expect a few bugs and unpredictable behaviour.
Over the summer mine seemed to get conflicted between GPS speed and the speed sensor, so displayed nothing. The trace was fine, like yours. I took the speed sensor off and haven't had a problem since. That doesn't help you, except to say others have glitches, too.