New Edge 1040 Series Public Beta 14.13 Now Available

Problem: Light network connectivity
Target device: Edge 1040

Still having issue connecting and establishing a light network with Varia RTL510 and UT800. In the light network under the sensors menu, the device keep on searching for both lights. Is it related to the ANT+ library implementation?

Radar of the RTL510 is working fine.

Dida 51km ride yesterday with RTL515 and UT800, no problems whatsoever connecting the light network. Also no other sensor disconnects. Using beta 14.13.

krazyeone said:

I will send you data fit file and also course tomorrow morning

Would love to see the course_fit file from your video, too

Yes, I’ve experienced similar behaviour with TrainerRoad workouts. They sync ok to the Connect calendar but don’t to the 1040.

Try powering off the 1040 - I found that triggers an update to the Training Plan on the unit. I think it should just require a sync to a phone or over Wi-Fi to do that.

I also tried adding bike workouts on the same day as the TR ones within Connect and they appeared on the 1040 and the TR ones vanished. It took a power off/on to update. I was also running a 1030+ in parallel and both the TR and Garmin-created workouts were visible on it. I notice there’s an arrow on the 1030+ that allows you to scroll between workouts in the Training Plan screen for a day. No sign of that on the 1040. Maybe only because I can’t seem to get more than one bike workout to appear.

Will put in a bug form.

CLIMB PRO:
Here the result of studying krazyeone 's course_fit file in reference to his video:

Conclusio:
Climb Pro endet at a section of (only) 4.9%, although the climb continues later with over 9%.

Would say: bad luck!
(or rather a not very intelligent Climb Pro, because thats no reason to end the climb)

Edit: there is another (very theoretical) explanation of failing Climb Pro: the GPS signal was off and wrong - very wrong. To check this I need the activity fit file)

Accuracy should be the best , as activity has Multi-GNSS multi band activated 

mcinner1 said:

Conclusio:
Climb Pro endet at a section of (only) 4.9%, although the climb continues later with over 9%.

I did another test to see if indeed the short section with less than 5% slope caused the "climb end":

We have seen that Climb Pro endet the climp at the appearance of less than 5%.

I modified the elevation graph of the course fit file, so that no grade below 5% happens in the section shown before.

And you can see - Climb Pro extends climb 4 by 100 m (4.6 km original course vs. 4.7 km after modification)

I have no Edge 1040 - all tests with Edge 1030 PLUS!

And that completes my testings.

CONCLUSIO:
@krazyeone 's course fit file is not to blame. 
It's rather the calculation by Climb Pro!

But this all has nothing to do with any delay  (of GPS, of elevation reading...)

PS: one more thing:

The GPS accuracy during this period of ride was perfect!!

yes , but it does not matter if you are dead , and still need to climb 100 m :) 

It has to do with logic behind climb pro, and how is defining the summit ,or the top

strange enough climb pro in climb 4 has 2.48 km and 168 M ascent ,AVG grade 7% (on my Edge 1040 , loaded from the course file) , and gradient is more refined, or micro spited  

Again strange If I am looking on the Overall map elevation there are some balloons on top of each climb , so I would aspect to have better climb pro behavior 

https://i.imgur.com/CbX0gkr.png

i.imgur.com/mkjL0zc.png

 So, you confirm this is not a new bug in the 1040?