New Edge 1040 Series Public Beta 14.13 Now Available

And are you aware that the beta is almost the same as the final releases? Read about the problems with the alpha releases. I have been observing Garmi software for several years and my conclusion is that the hardware assumptions are as future-proof as possible, while the software does not keep up with the hardware development. Primary school boys go to work !!! In any other company, if there were so many problems, you wouldn't be there anymore.

I've seen serval posts about ClimbPro lag. I've not been able to reproduce this. I've ridden the same course using an Edge 830 and 1040 and for me they track the same position on the elevation profile. If it is off it is off on both units. They don't appear to differ. The screens are different sizes and the grade coloring is different so it can be a bit tricky to align things unless you have a climb with a marked descent in it.

I would love to get some data from people that are seeing a difference in ClimbPro position between the 1040 and either the 1030 or 830. I would need the course file used on both units and the activity files from the same ride from both units and ideally screenshots of the difference. If you could drop a lap marker in the data the position you took the screenshot that would really help.

If you would be willing to share this data with me just send me PM.

Do you think everything was OK at 12.16? And do you use the E1040 with a multitude of sensors? And how much a day do you drive with the E1040 observation?

https://photos.app.goo.gl/TyypM9VwziWWufuQ8

1. I will send you data fit file and also course tomorrow morning
2. After the climb complete notification , i had at least 1 min to climb, I was dead so I cannot appreciate distance

ClimbPro can complete before you reach the physical top of climb depending on how the grade changes near the summit. Once the average grade left drops below 3% it considers the climb complete.

Clear , if it was 3% it will make sense, but the gradient was at least 6% after notification of segment end to end of summit( and I felt it like 8%) :) 

I had a very similar experience with a climb that I used to climb with 830 and for sure doesn't have 3% or less at the top. 830 was always spot on - same xlomby, same route, some cyclist. 1040 ends it much earlier and also keep delaying the internal changes in the grade (you can feel that you started to put much more power like 40 seconds ago and then you see go from Yellow to Red). So the whole thing is delayed - not just the finish...

Not sure if denial of the issue here is the best approach. We do have something really wrong with Climb Pro that we didn't have before (at least with 830 that I used to use).

I don't think anyone is denning the possibility of there being a problem. Just needing some data so that issue can be reproduced.

Can you follow the same climb but on the elevation screen to determine if problem is in climbpro or is the delay also on the elevation screen which points the finger at elevation reporting in general? I was watching the VELOGPS  1040 Navigation YouTube and at one point they are showing the elevation screen a clearly they have finished and going downhill while screen still shows not yet at top. (For those not familiar with VELoGPS videos they have a split screen showing the GPS device on left of screen and view of road on the right)

m.youtube.com/watch (hill starts at 4m20s, crest 5m10s)

PS: I have watched it again and the delay is pretty tiny, not what I would see as a problem so it might be climbpro issue