Related
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

Hitting a wall with an Edge 130

Captain_Debugger
over 7 years ago
I bought an Edge 130 as a future replacement to my Edge 510 which I am anticipating die off me soon (rubber covering of power button gone, covered with duct tape only yet still working)

I immediately noticed something weird with the 130 when I am going up slope. Its not responsive at the start, then will suddenly shoot up to percentages beyond Zoncolan then just as quickly goes down to normalize

I did a video showing differences between the FIT files of 130 vs the 510, Fenix 3, and the Virb X, and it shows as if I am hitting a wall on the 130. Maybe I need to bring a ladder next time.





https://youtu.be/VnLPqdOv0PM
  • 0 over 6 years ago
    update

    so the above issue turned me off and laid off the device for a while. only this week i decided to use my edge 130 again. i plugged it to my laptop and checked on Garmin Express. sure enough
    ??there's firmware update.

    went out for a spin on my brompton and purposely routed through some rolling terrain. I'm happy to share that the elevation profile looks normal now for my entire ride. here's the segment with the ups and downs

    https://youtu.be/N8lrtMLXKQY
  • 0 over 6 years ago
    Could you please repeat the same ride and compare the elevation metrics with the previous ride? The elevation of the same place differs by 50 meters on the same ride on two different days for me. Just wondering if you come accross something similar. Version 3.00 of course.
  • 0 over 6 years ago

    that's probably more related to the starting elevation of your ride. after the above video, my next ride was more of a loop near my place. for some reason the starting elevation was almost 200m and i ended at 45m after 18km, so the profile is like a continuous downhill when it really isn't. seems to be one of the issues in the other threads here. though i only had that 1 ride so far with this issue over 4 rides.