This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Edge 830 GPS signal acquired but not recording KM's

Former Member
Former Member over 5 years ago

Hey Guys,

Last week i upgraded to a new Edge 830 after 4 years using an Edge 520. Unfortunately i've had issues with my new 830 every ride i've used it. When i start my ride, everything is ok and the GPS signal is acquired quickly. Then, a few KM's into my ride, it will stop logging the KM's i'm covering, almost like it thinks i'm standing still. The weird thing is that while my KM's aren't being recorded, my GPS signal is showing 2-3m accuracy and 5 bars of strength.

Sometime later in he ride, it will start recording the KM's again like normal and my map will show my correct location. Sometimes this takes 10 or 20km's to start working again. When i get home i'm able to use Strava's distance correct feature to fix my ride up, but its annoying for a brand new unit to be having these problems consistently. I've upgraded the software to 5.44 BETA and that doesn't seem to have made a difference. I'm using the device on GPS + GLONASS. I've tried using just GPS and the same thing happens.

Any ideas on how to fix this issue? Or does it seem like a faulty head unit?

Thanks.

  • 0 over 4 years ago

    Have had an 830 for almost 2 years now, worked flawlessly up until the latest 8.10 firmware (thats the only thing i can think has changed) Lost Satellities popping up constantly on the device, km's not recording, ride going into pause mode. Nothing and i mean nothing else has changed on the device. Out for a ride this evening, it was 2k before the sats picked up, then said i was doing 63kph, down to 22kph and kept bouncing up and down speeds for the next 3 or 4 k. Stabilised for a while then started acting back up. Kept pausing and restarting mid ride. Getting very annoying, and am hoping this is a software issue that can be fixed. Any help appreciated.

    Padraic 

  • 0 over 4 years ago in reply to padraic.murphy

    Wow, that's far worse than mine. Alas, it all started after the firmware update for me as well. Wonder how long before they fix the issue.