Wind Field. Cannot imagine riding life without this one
PowerSlider
Battery Burn Rate (just for curiosity)
Make sure in data screens you add the Stamina Screen. I ported over my old screens and didn’t even know this one existed. And try it in night mode. And keep the firmware updated, the first couple of revs had some rough edges.
I updated the Garmin Screens Excel file that @ratz originally created for the Edge 530 for the Edge 1040 - sharing here via DropBox
This lets you figure out screen layout on your computer before setting them up on your Edge 1040.
If you find any bugs let me know and I will try and fix them.
Note: I just uploaded an updated version - let me know if this breaks the link - that includes the ability to list ConnectIQ Data Fields you’ve downloaded. To be able to select these, go to the “Data Fields” worksheet, and add in your Connect IQ data fields in the ConnectIQ_DataFields column - Column B. Delete WindField if you don’t have that installed.
The battery life is amazing - 6 hr ride time / 7:30 total time (multiple coffee stops) - and I only burned ~12% of the battery
I’d forgotten how much I hate hate hate the implementation of Strava Live Segments. I wish there was an option where it would only signal segments when you are actually on them. I got too many “off course” warnings when I passed by a segment that I had no intention on doing
The GPS (even multi-band) is still challenged by Bay Area tree covered canyon roads / climbs. I know @dcrainmaker and others get good / very good GPS tracks, but I consistently have issues - see these shots
I just used ClimbPro for the first time yesterday, and it is a cluster. The lag was so bad that I was on the downhill and ClimbPro thought I still had more to climb. I don’t see how Garmin did any internal testing and thought “gee, this lag is okay”
I guess these don’t have accelerometers in them so it has to rely on prediction and analysis. With a course it’s relatively easy to predict where on an incline included in course data. Just riding with CP, it’s a trade off of sensitivity “am I really on an incline” and for how long. Sensitivity could improve if connected to the phone that could then provide additional altitude data based on position and direction but that’s a lot of data to pack into a stand alone device. I think they could do better on the detection though, like you said going down a hill after cresting and still seeing a positive grade is kinda poor
I think they probably don’t have something to measure incline.
They have accelerometers, that’s how they collect all of the MTB metrics like flow and jumps and air time.
Would be smart to set up an incline measurement the same way they estimate wheel diameter with speed sensors - calibrate it over time based on routes, elevation, etc….
Hmm, you’d think it would be fairly easy then with a 6-axis accelerometer.Maybe something in stats like a rolling window like average power, 5,10,20s.
I guess that Garmin concluded that the value of the feature was in concert with courses rather than a free ride. For me, I ride a set course maybe 10% of the time so it limits the usefulness of ClimbPro
I’ve got a 530 and the latest firmware (9.5 on 530) has a bug, same for 1040. The first 3 climbs were fine, the lag bug started on the 4th and 5th climbs.
Since you have to be riding a course for ClimbPro to pop-up, I don’t understand the lag. ClimbPro has to be using the course to pre-calculate climbs as it thinks it know where climbs are and how long they are. So especially with the 1040 with its dual-band GPS, you’d think it would nail climbs exactly.
So I’m hoping this is a bug that Garmin can easily fix
It’s a bug, nothing more to understand. I’ve done climbs with the 530 single-band gps and it worked well until the current 9.5 release. I posted some screenshots in this or another thread.