Garmin has just announced the new Edge 840, as well as Edge 540 units. And like last year, with the more expensive Edge 1040, both the 540 and 840 get Solar variants. However, the changes go far beyond just sunny-side-up or not. In fact, arguably, the solar piece is really the least important change. Instead, the huge bulk of the changes are software-focused, effectively matching that of the higher-end Edge 1040 series, bringing in tons of new functionality, including one entirely new-to-Garmin feature: Free-ride ClimbPro. You no longer have to be on a course/route to get up-ahead climb information.
Of course, it’s not just a buffet of software features, but also some hardware changes, including the switch to USB-C, as well as the addition of multi-band/dual-frequency GPS/GNSS. And for better or worse, the unit got a bit chubbier as well. Hey – you can’t win them all! Note that both new units are near-identical, but this review is focused purely on the Edge 840 model, which has a touchscreen that the Edge 540 lacks. It also has a few other differences outlined in the next section.
Garmin sent over media loaners to test out. As usual, this review is not sponsored (nor does any company get to preview anything I review), and I don’t take any advertiser money from any companies I review. Once this unit goes back, I’ll go out and buy my own for any future testing needs. If you found this review useful, you can use the links at the bottom, or consider becoming a DCR Supporter which makes the site ad-free, while also getting access to a mostly weekly video series behind the scenes of the DCR Cave. And, of course, it makes you awesome.
It’s been four years this month since the Edge 830 came out (alongside the Edge 530). During that time, the 530/830 received an astonishing number of feature updates, alongside the Edge 1030 and then Edge 1030 Plus. My goal in this ‘what’s new’ section isn’t to compare to the Edge 530/830 devices at release, but rather, to compare what’s new on the Edge 840 as of now. Meaning, taking into account all those firmware updates.
With that in mind, the vast majority of newness here software-wise has already been seen on the Edge 1040 since last summer. There’s really only a couple of features (freeride ClimbPro, ClimbPro Explorer, & to a lesser extent revamped daily suggested workouts for races) that are actually new-new here. And those are also coming to the Edge 1040 in a firmware update shortly. Here’s all the new things:
– Edge 840 has BOTH touchscreen and full button set (previously only had partial button set)
– Added multiband/dual-frequency GPS
– Added solar panels for Edge 540/840 Solar editions
– Added USB-C connection for charging/sync
– Made it slightly chubbier to accommodate solar panels (non-Solar edition is also same new dimensions)
– Completely revamped the user interface everywhere (matches Edge 1040)
– Added Power Guide race/training pacing feature
– Added ClimbPro Free-Ride mode, which automatically triggers ClimbPro without a route
– Added Climb Explorer dashboard for finding nearby climbs
– Added Connect IQ Widget Glances to Homepage/Dashboard
– Added Training Status 2.0
– Added full automatic race/event suggested workouts using a periodized/phased daily plan leading up to event, inclusive of any Garmin wearable data shifts (e.g., automatically reducing planned workout if you got no sleep on a redye flight)
– Added Course Demands to compare course features to ride needs
– Added Real-Time Stamina to show energy/distance/duration left during workout
– Added Location Search Widget
– Added ‘Recent Finds’ from navigation panel (so things you recently searched for)
– Added new ‘Bike Shops’ & ‘Water Stops’ categories for navigation search (and completely re-did other categories to mostly get rid of auto stuff)
– Added Post-Ride ClimbPro Splits on device
– Added re-scheduling of primary workouts
– Added support race/event driven Daily Suggested Workouts (expanded from initial Edge 1040 launch)
– Added paired sensor information to summary page (even for non-Garmin sensors)
– Added support for Shimano STEPS sensor type (eBike component)
– Added new consolidated post-ride Highlights screen with PRs
– Added estimated battery remaining when toggling Battery Saver mode
– Added manual WiFi sync all button (a ‘do it now’ option, but removed single-ride upload option)
– Added phone-based config of data fields/data pages
– Added ability to use phone for typing text on Edge
– Added ability to manually transfer sensors and device profiles to Edge from phone at any time (not just first setup)
– Added Garmin Connect IQ App Store on-device marketplace
– Added LiveTrack Spectator Messaging
– Changed nearby POI/Things search to be virtually instant
– Far faster route calculation/recalculation times
– Increased ClimbPro coloring to show more gradient definition
– Now automatically changes map popularity type to match activity (I.e., Road vs MTB)
– Changed screen background default from black to white for improved “readability”
– Removed horrifically unreliable duplicate Bluetooth pairing process for phones
– Removed Varia Vision sensor support
– Removed device transfer (sharing between units)
– Same 2.6” touchscreen size/resolution as before, however, Garmin says it has improved contrast ratio and color filters
– Weight is 90g for Edge 840 solar (up from 80g for Edge 830)
– Battery life up to 48 hours non-solar, 78 hours solar. Up to 34 hours with Multi-Band GPS mode with Solar (battery chart lower down)
– Simplified Bluetooth phone pairing to single connection (versus previous dual legacy BT and BT smart)
Additionally, while this is offered on the Edge units, it came much later, but it is still present on the newer units, and wanted to call it out:
– Paired sensor transfer from existing Garmin Edge units
– Activity Profile settings transfer from existing Garmin Edge units
In total, there are three SKUs/variants for both the Edge 540 & Edge 840, they are as follows (which include basically a $ 50+ price increase over the previous generation):
– Edge 540 base: $ 349/€399/£349
– Edge 540 Solar: $ 449/€499/£449
– Edge 540 Performance Bundle (which includes heart rate strap, speed sensor, cadence sensor): $ 449/€499/£449
– Edge 840 base: $ 449/€499/£449
– Edge 840 Solar: $ 549/€599/£549
– Edge 840 Performance Bundle (which includes heart rate strap, speed sensor, cadence sensor): $ 549/€599/£519
And the short version of how the Edge 540 vs 840 differs is actually surprisingly simple:
1) The Edge 840 has a touchscreen display, the 540 does not (both have full sets of buttons)
2) The Edge 840 has 32GB of storage versus 16GB on the Edge 540
3) The Edge 840 comes pre-loaded with two regions, the Edge 540 with one pre-loaded (but you can swap/download others after for free)
4) The Edge 840 can search on-device for specific street addresses and GPS coordinates, the Edge 540 cannot.
5) The Edge 840 has Trailforks maps pre-activated, versus with the Edge 540 you need to manually activate it once (also free)
6) The Edge 840 can manually build a multi-step structured workout on-device (using touch), the Edge 540 you need to send from app/3rd party/daily suggested workouts, or use interval builder on-device
7) The Edge 840 editions cost $ 100 more
(Side note: If you’re trying to build a complex multi-step workout on-device, something in your day/life/cycling world has gone horrifically wrong, you really don’t want to do this, even on the Edge 840. Trust me, nothing good comes from that rabbit hole.)
Honestly, the only two things that really matter in that above list besides price, for 99% of the people are the touch (and that’s a big deal here), and the bigger storage size if you frequently fly across the pond (any pond).
Phew, got all that? Good, let’s crack it open.
In the Box:
There are a couple of different bundles available of the Edge 840, but in my case, I’ve just got the simple Edge 840 Solar base unit kit. Other bundles include things like extra sensors or such.
Here’s everything unboxed on a table:
Inside you’ll find the Edge 840 itself, along with a lanyard in the event you don’t have full trust in the mount. While mounts do break, I’ve only ever seen that occur during a major crash, or if you’ve overloaded a 3rd party mount with too-heavy items (which doesn’t really apply here). There’s also a small hex wrench in case you need to remove the inside of the mount to add a Garmin battery pack/power bank.
Then we’ve got the included out-front mount. It’s plastic, but is a beefcake plastic, so it’s certainly gonna be pretty difficult to break. It comes with a few different collars, in case you have bigger/smaller handlebars.
Then there’s the rubber quarter-turn mounts that most people use. These have been standard on Garmin bike GPS units for almost 15 years now, and work great. Super quick and easy to switch around between bikes.
And finally, the USB-C charging cable – woot!
The weight of the Edge 540 Solar is 85g, 840 Solar is 90g, and 1040 Solar edition is 134g. Oh, and if you were to compare it to the Edge 530/830, you’ll see it chunked up a bit, presumably to fit the solar panels in there (Left: Edge 830, Edge 540 Solar, Edge 840 Solar, Edge 1040 Solar)
And for fun, here’s a lineup with a bunch of units: Wahoo BOLT V2, Edge 830, Edge 540 Solar, Edge 840 Solar, Wahoo ROAM V2, Hammerhead Karoo 2, Garmin Edge 1040 Solar.
Next is getting it all configured and covering some of the basic usability bits.
Basics and Configuration:
The biggest physical difference on the Edge 840 compared to the Edge 830 is that it’s got a full set of buttons. Previously, Garmin’s touchscreen devices always had fewer buttons than their untouchable counterparts. However, since Garmin started introducing touchscreens to their Fenix wearables last year, they’ve shifted to a model of ‘equality’ when it comes to touch vs buttons. Basically, you can choose whether you want to use buttons or touch, for virtually every operation. The only notable exception being you have to use a physical button to start/stop a ride.
You can see the 7 buttons on the Edge 840 below. Essentially the side buttons are for navigation/confirmation in menus, whereas the front/bottom ones are for stop/start/lap. Those bottom buttons are (never?) used in any menus at all, they are only ever for starting/stopping a ride.
Meanwhile, atop you’ve got a touchscreen for all the touching you want to do. I haven’t had any issues in either sunny/hot/sweaty conditions, or everyday Amsterdam rainy conditions using the touchscreen. Same goes for gloves – no problems there as you can see in some of my videos.
In fact, the Edge 840 is probably the first time I’m mostly switching my recommendation towards preferring the 840 vs the 540 (historically I’ve always kinda preferred the 510/520/530 series devices over the 810/820/830 devices), in part because I found the buttons faster. But as the reliability and ease of use of Garmin’s touchscreen has improved, I found it harder and harder to go back to a pure button setup on the Edge 540. Obviously, that’s partially because I’ve become accustomed to the good touchscreen on the 840/1040, but also because…it’s 2023 – touch for certain operations feels natural (like mapping, swiping data pages, or quickly changing data fields mid-ride).
The other major change is the USB-C charging port on the button. Sure, you’ve got solar panels up top for the Edge 540/840 Solar editions (more on that in the Solar section down below), but frankly those just don’t charge too much. Instead, you’re likely to plug it in, and you can do so here with any USB-C charger (such as your laptop).
The port has a little cover, but it’s also internally waterproofed to IPX7. That means you can crash into a shallow canal (up to 1 meter deep), and then you’ve got 30 minutes to fish it out. Note that like airline safety demonstrations, you should save yourself first from the canal, before saving your accessories.
Also, there’s a small lanyard hole next to the cover, in case that’s your kind of thing. It’s not my preference, but no judgements.
On the back of the unit there’s a standard Garmin quarter-turn mount that’s been used for the past 15 years. This mount is found on countless 3rd party mount accessories, and even a number of bikes have it built-in these days.
You’ll also notice the power pins there. Those are compatible with Garmin’s severely outdated battery pack, as well as their brand new Garmin Edge Power Mount from last summer (if your bike has power in it, and can power items forever). I’ve used it with the power mount and it worked just fine. When used with the power mount, it’ll disable solar charging. I presume the same for the battery pack.
Battery-wise, we’ll talk about those claims at the end of this section, and my test results.
Once you power it on (upper left button), you’ll see your ride profiles up top. By default this is Road/Mountain/Indoor, but you can customize each one, or create your own. They’ve all got their own colors, and within that, you can customize data pages/settings for each of them. This is handy when you want mountain bike metrics different from road cycling metrics, and then perhaps a more reduced set for indoor riding.
Below that you’ll find what is essentially a ‘What’s new’ panel. This shows you the last notable thing to sync to the device, or thing that you’ve done. For example, if you have a structured workout scheduled, it’ll show that. If you just sent a new course/route to the unit, it’ll show that. If you just completed a ride, it’ll show that, and so on.
Each one of these sections, as you scroll down, is both a menu item, but also a customizable widget. You can add widgets from both Garmin as well as 3rd parties onto it. For example, if you open up the ‘Navigation’ widget, you’ll see where you can load courses, browse the map, or navigate to saved locations. I cover navigation and mapping in the Navigation section down below.
You can customize this list at the bottom. For example, I added Acute Load, Training Status, and Load Focus to my list.
Next, you can swipe-down from the top to access a common set of menus whether doing a ride or not. This has controls like changing your ride profile, turning on/off GPS, the battery, screen brightness, sensors, and more. If you tap left/right, you’ll get additional control panels. For example, if you’re in a course, you can stop the course. Or inversely, you can route somewhere like back to home, from this panel. Same goes for stopping/starting a structured workout, or turning on/off bike lights if those are attached. There’s a notifications panel to see missed notifications, a weather page to see that it’s probably still raining outside in Amsterdam, and then both a Strava Segment explorer and a new Climb Explore feature (more on that in the ClimbPro section).
This is really one of the areas the Edge 840 with the touchscreen really shines compared to the Edge 540 with the buttons. It’s just more cumbersome to navigate these controls menus on the 540. Not hard, but just not dead-quick/easy/simple like on the 840/1040.
Next, back on the main page you’ll see that three-lined ‘hamburger’ menu option, which opens up the menu itself:
That dives into all the different settings areas, this includes tweaking your Activity Profiles, such as the data pages and data fields you want. But that’s also areas like how ClimbPro works, or how nutrition alerts work, and the gazillion different settings that Garmin offers.
However, all of these things can be configured from the phone now. Like the Edge 1040, you don’t have to do this on the unit itself, but can tweak these quickly from the Garmin Connect Mobile app.
In fact, if you had an older Edge device, then all of these would have migrated over as part of the Activity Profile migration setup process that’s offered when setting up a new device. And, even more notable is that new to the Edge 540/840 (and coming to the Edge 1040), is the ability to do both a sensor transfer and activity profile transfer whenever you want, not just during initial setup.
That same concept applies to sensors. You can manually set them up from the device itself, or you can have it migrate all your previously paired sensors from other Garmin Edge devices. From a sensor standpoint, the Edge 540/840 support:
– Heart Rate (ANT+/Bluetooth)
– Speed/cadence (ANT+/Bluetooth)
– Garmin VIRB Action Cam (ANT+)
– ANT+ Cycling Lights (front or rear)
– ANT+ Cycling Radar Sensors
– Power meters (ANT+/Bluetooth)
– Garmin inReach Satellite communicators
– Garmin Edge remote controls
– Shimano STEPS
– eBike (ANT+)
– ANT+ Shifting (Campagnolo/SRAM)
– Shimano Di2 (proprietary ANT)
– Garmin Tempe Sensor (ANT+ temperature sensor)
– ANT+ FE-C Cycling Smart Trainers/Bikes
– ANT+ Extended Display
Basically, it’s the same list as before. As with before, you can pair multiple types of the same sensor (e.g. three power meters on different bikes), each giving them your own names as you see fit.
I haven’t had any problems with any sensors during my usage, which has included multiple power meters (Stages LR, Garmin Rally, Garmin Vector 3), multiple heart rate sensors (Polar H10, Garmin HRM-PRO Plus), a few trainers/smart bikes (Wahoo KICKR Bike and Wahoo KIKR V6), and two different radar units (Garmin RVR-315 & Magene L508). All worked as expected.
Finally, there’s the incident detection and live tracking. You can set this up once, and then you don’t have to worry about it again, it’ll just automatically send an e-mail to your family/friends with a LiveTrack link in case you go missing (or just so they know when you’ll be home). In my case, I’ve set it up to automatically e-mail my wife each time I start a ride.
She’ll see both my current location as well as the planned route (if loaded). Also, she’ll see how much suffering I’m doing with sensor data like heart rate/cadence/power. I will give Garmin credit where credit is due. LiveTrack a few years ago used to be completely useless and full of connectivity issues and drops. These days, I find it generally quite dependable. Both myself and my wife use it on every ride, almost always without issue.
Tied in with that is incident detection, which will detect when you crash. Or, if some other big impact happens. The algorithm is basically using the accelerometers and gyros internally, in conjunction with looking at your speed. The idea being if there’s a big g-force impact and your speed goes to zero, you’ve probably crashed. Whereas inversely, if your speed is maintained after a big impact, then you’ve likely just been riding on normal Belgium pot-hole filled roads. Or, you were hit by a turnip truck and are now lying atop it and the truck is still moving.
I haven’t had any false-positives with the Edge 540/840 unit, though I do tend to average 1-2 per year, usually when I drop off a sidewalk edge or something and then immediately stop quickly at a light (such as to get around cars/traffic/construction blocking a bike lane). That tends to trip the conditions above. You’ve got 10-15 seconds to cancel the notification, before it sends a very dire text to your loved ones telling them things have gone poorly. It’ll continue tracking your location in the text it sends to them, in case you’re then brought to a hospital, they know where to find you.
Given that positive note, let’s head outside and start riding with it.
Riding with it:
The first order of business is simply quarter-turning it onto the mount and turning it on. From there, you’ll choose the ride profile by just tapping on it, or changing it by tapping the left/right arrows.
If you want to load up a course, now’s the time to do it via the ‘Navigation’ option, or if you just synced a course, it’ll show up on the ‘What’s New’ widget section. Same goes for any structured training, now’s the time to choose it. Generally speaking, I’ll load the course first, and then load the training, but it doesn’t really matter.
When loading a course, if you’re not at the course start point, it’ll offer to route you to the beginning of the course. I generally skip this option unless I’m actually not at the start and don’t know how to get there. Also, some of these images are a bit harder to see than I realized, the camera was off-angle. Apologies! In real-life, there’s no issues seeing off-angle like with cameras.
Once all that’s settled, you can press the start button and start riding. As noted earlier, the only way to start recording is to press that physical lower right button. This ensures any weird touchscreen things don’t impact the recording of your ride. By default, if you start riding but don’t press any buttons, it’ll notice you’re going somewhere and start chirping to press start. Inversely, auto-pause is on by default, which will pause the timer when you stop (such as at a stop-light). You can change that in the settings.
Once riding, you’ll see the data pages as configured. You can either swipe with your hand left/right, or press the up/down buttons on the left side to move from page to page. There’s a lot of pages by default on the Edge units, and some of them can become somewhat duplicates of others. For example, the elevation profile page is handy if you’re riding mostly casual rolling hills, but if you’ve got steeper climbs that trigger ClimbPro, then it’s just sorta in the way. Customization is easy via the app.
By default, the unit will use the new multi-band/dual-frequency GPS/GNSS. This means higher accuracy, but it also means lower battery life in that mode. This mode is best if you’re spending time in the mountains, cities, or spending time offroad in dense trees. If you’re mostly riding on farm roads or out in suburbia, you can just use the regular mode ‘Balanced’ GPS option to save a bunch of battery life (details in the charts in a second). You can always access this by just swiping down from the top, and remember it’s per-activity profile. So you can go to ‘Balanced’ for your road bike profile, but leave it on Multi-GNSS for your MTB profile.
If you’ve got any timers or alerts, those will appear as you ride. For example, you can set up nutrition/hydration alerts under the ‘Alerts & Prompts’ section, which lets you create independent reminders for both of those, as well as a bunch of other categories like power/cadence/time, and even a ‘Turn-Around’ reminder for a set distance.
These will then show up mid-ride based on how you’ve configured them. For eat/drink alerts, you can also have it be ‘smart’ alerts based on figuring out calories (food), as well as temperatures/intensity (hydration).
Meanwhile, if you trip a Strava Segment, it’ll automatically show you the Strava Live Segment page. Note that you can use Live Segments with courses, but it has to be a Strava Course, so that it bakes the segment into it.
In terms of display visibility, I’ve had no real issues in viewing the screen. As with the Edge 1040 Solar, the solar variants are slightly darker than the non-solar variants, due to the solar panel being overlaid atop the screen (across the entire screen at a 15% photovoltaic level). You can’t visually see it, but you do notice it’s slightly darker for the same backlight setting. In some conditions I found I needed to bump-up the backlight from the default ‘Auto’ setting to just a touch bit brighter. But nothing major.
Once your ride is done, you’ll get two sets of summary pages. The first is focused on training load related metrics, followed by some solar (if applicable) and then sensor pairing bits. After which there’s a second page that covers more of your ride details, including a course outline, total ride stats, and plenty more. No really, a disturbing amount of stats are below, the more you scroll. All the way at the bottom you’ve also got a summarization of your climbs too, for any triggered climbs (via ClimbPro).
Finally, all of this gets synced to Garmin Connect virtually instantly via Bluetooth or WiFi (or USB if needed), and then onwards to 3rd party apps like Strava/TrainingPeaks/etc. You can see an example of one of my rides here on Garmin Connect:
So – what about battery life? Well, let’s start with a quick look at the official charts for the Edge 540/840:
In my case, for rides where I wasn’t doing some sort of screen recording, it was generally burning at a rate of about 25-40 hours, inclusive of some solar activity, but not often a lot. In my case, I would generally fall between the ‘Mid’ and ‘Demanding’ on the chart above, where I had multiband enabled, 1-second recording, and 2 sensors (power/HR), plus sometimes either a structured workout or navigation. I generally did not hang out on the map page (as that burns faster). I also had LiveTrack enabled and Auto backlight usually on/stays on.
My results for both the Edge 540 & Edge 840 basically match what I saw with the Edge 1040 in relation to Garmin’s battery claims: They were conservative – in some cases, hugely so. Meaning, in every one of my tests my battery burn rate exceeded that of Garmin’s claims. Heck, even with screen recording enabled and heavy debug information enabled (in case something went wrong) it exceeded Garmin’s claims (just barely).
ClimbPro & New Free-Ride Mode:
Years ago Garmin introduced ClimbPro, first on their wearables (the Fenix 5 Plus in 2018), and then on the Garmin Edge cycling computers starting with the Edge 530/830/1030 series. The goal of ClimbPro was that if you had a course loaded, you’d be able to see the exact profile of the climb both before-hand, as well as during the ride. As you approached the climb it’d count-down, and then once riding on the actual climb it’d show you details like gradient remaining, ascent remaining, and plenty more.
It continues to be my favorite Garmin feature out of everything they do. It makes it exceptionally easy to see how much suffering you have left.
The problem though, is that up till now, that required a route/course be loaded, or be doing some sort of pre-planned navigation. Meaning, if you were just doing a regular ride without a course/route loaded, you didn’t get climb information. Last spring, their GPS competitor Hammerhead, took this concept further with their own free-ride mode, allowing you to just approach a climb on the Karoo 2 bike computer, and see the same climb stats as if you had pre-planned it.
With the Edge 540/840, Garmin is now joining that camp too. You no longer need to have a route/course loaded. Instead, it’ll automatically attempt to figure out your climb based on the road you’re on, and then show you that route profile. The Edge 1040 will shortly get a firmware update enabling that feature as well.
In my testing, I’ve been using the Edge 540/840 in free-style ClimbPro mode side-by-side with the Edge 1040 with a course loaded, all of this also side-by-side with the Hammerhead Karoo 2 and Wahoo ROAM 2, to see how they handle.
First though, a quick look at ClimbPro in regular route mode. Basically, when you load a course, it’ll automatically show you the climbs from that course. These climbs are determined based on them meeting specific criteria for what constitutes a climb, with the minimum threshold being:
“3% gradient and 500m length, with both needing to be satisfied.”
However, you can also configure ClimbPro (per activity profile) to ignore smaller climbs, and only show bigger ones.
You can see the total number of climbs, and the exact specifications for each climb. While riding, it’ll show you the distance until the next climb. Thus, while the free-ride ClimbPro is great, for longer routes with multiple climbs, it’s nice to know what lies ahead.
As you approach the climb, you’ll get a warning about 100 meters out, and then the distance will count-down. Once you cross the threshold of the start of the climb, it’ll automatically switch to the ClimbPro page, which includes stats about the climb itself, as seen below:
All of this worked just fine/as expected for me on both the 540 and 840 – matching exactly what I had on the Edge 1040 also concurrently operating. And in the case of all my climbs, ClimbPro ended at the top of each climb as expected (there’s currently an issue some people are seeing on some climbs on some routes on certain Edge units, seemingly tied to data from Strava, where the climbs can become offset – but for whatever reason, none of my climbs have triggered that).
So, that brings us to the newness, which are two pieces. The first is the new Climb Explorer drop-down menu, which lets you see nearby climbs. This menu shows you climbs sorted by nearness to you, upwards of 150 of them. It’s actually kinda astounding how many climbs are nearby some places I ride. Who knew?!?
You can then tap on any given one to see more details about it, showing you the normal per-climb ClimbPro page:
And then, from there, you can tap again to get directions to the base of that climb, ready for you to suffer.
Additionally, if you tap the upper right button, you can see the settings, allowing you to create some filters for this list:
Notably, this list populates pretty quickly. You can see this in my main review video. That’s because Garmin has substantially increased the size of their mapset (in GB) to pre-cache/create all of these climbs. It’s actually kinda mind-boggling when you think of it, but this ensures that the data is fast and responsive, versus much slower (compared to creating a ‘Round-Trip’ course/route on demand, which takes forever). However, one minor thing to note is that the minimum threshold here is slightly higher than the 3% for ClimbPro as a whole. At present, the minimum threshold is 3.5% for the Climb Explore feature. Garmin says that this threshold might change over the coming months, pending user feedback.
All of which eventually gets us to the main new feature of the Edge 540/840, which is the ClimbPro free-ride mode. This means you just ride, and it does its magic. As you’re just riding along it’ll show you a notification as you approach a climb, just like with the course mode:
And then, equally just like regular ClimbPro mode, it’ll show you the stats to the top of the climb:
Literally, it’s exactly the same…except when it’s not.
Which is to say that the key difference is that it doesn’t actually know where the top of your climb is. For example, I went riding last week in Belgium, up many of the famed cobbled classic climbs. In that case, those are very crispy start/finish climbs. There’s no ambiguity, and having a course loaded on an Edge 1040 vs the climbs in free-style mode on the 540/840, they matched identically.
However, the week before, when riding the climbs of Mallorca, it was a bit more mixed. In some cases, the climbs matched precisely, namely for climbs where again the top was crispy and clear. For example – climbing up Sa Calobra, the end is one known/clear spot with a sign and all. A few meters later, it goes downhill on the other side of the pass. That’s easy.
But getting to the backside of Sa Calobra from the flatlands? Well, that’s messier. There are multiple routes up, and most of them contain what is mostly regarded as one big climb, followed by some rolling flats for a while, before one more moderate climb. In this case, I saw differences for how it split this up. Coming via Lluc for example, in free-ride mode, it split the climb up at Lluc. I understand why it did this, because the road descends a bit first, then turns there and flattens out – before going back up. But that’s not the way most people define that climb. Most cyclists would say the top is up a bit higher near the road junction. Hammerhead’s free-style mode got this right (the screen recording for that died before I got to this section), as did Garmin’s course variant – but not Garmin’s free-ride ClimbPro.
But you can see below that the Edge 840 is about to end the climb in a few seconds, whereas the Edge 1040 with the known course knows that it’s another 3.38km to go after this brief downhill section. The Edge 840 assumes I’m taking a turn shortly thereafter.
A few times, it started a climb too early, for example, on some very flat sections that were only 1-2% in gradient, hundreds of meters (or even kilometers) before the actual climb. Sure, I was barely going up, so on a technicality this is correct, but not from an accepted cyclist’s perspective (which again, in ClimbPro course mode it detected all of these correctly).
Which isn’t to say it’s bad. Far from it. Again, the vast and overwhelming majority of the time it was spot-on. But at the moment, Hammerhead’s free-ride mode does a better job at detecting the specifics of the start/end points. Inversely, Hammerhead’s CLIMBER mode is far inferior when it comes to the gradient data inside the feature. Meaning, it’s very often wrong about the upcoming gradient – and severely so. A very long-term problem that’s been going on for years, due to bad underlying data. I guess a case of pick your poison.
Finally, I did have two notable ClimbPro free-ride failures. The first was a case where the road itself ended, and then there was a barrier, followed by a dirt road that went higher. In that case, the free-ride mode told me to keep going, as if I was only half-done with the climb (both Garmin ClimbPro course-mode and Hammerhead Karoo 2 CLIMBER correctly finished the climb). Garmin tracked down this error and it’s already fixed in a firmware update issued last week after my ride. The second error was at the top of Sa Calobra, when the unit started to rapidly increase the remaining gradient, eventually ending up at 105% gradient. Yes, for real. In fact, you can see a similar variant of this bug up to the on the (above/below) Edge 840 screenshot showing “19%” gradient remaining.
Garmin tracked this down to some bad data in the mapset itself, and has filed a bug to their map data team to fix this. Why this impacted only ClimbPro free-ride mode and not ClimbPro course-mode I don’t know, but hopefully nobody else gets 105% gradients.
Either way, overall I’m pretty happy with the free-ride mode, but it’s also clear it’s early days for it. Like with Hammerhead when they launched their free-ride mode, Garmin too says they expect to be tweaking it over the coming months as they get feedback from users. Which is actually exactly what they did when they launched ClimbPro the first time around years ago – over the first few months things changed a bit in terms of what triggered climbs and how they triggered.
So finally, what about reaction time of the gradient display itself? Meaning, set aside ClimbPro – and focus just on how fast the unit responds to gradient changes. To be really clear here (cause there’s a lot of confusion), this is *100% totally separate from ClimbPro* – the two have literally nothing to do with each other. ClimbPro is all about showing expected gradient based on known map data as you ride it. Whereas the internal sensors are responsible for showing the current gradient, and how fast it responds to situations.
A common complaint of the Edge 1040 is that it’s historically responded too slowly for some tastes, namely in sharper/steeper climbs. I actually did an entire video/post on it a year ago. In that video, I basically found that there are cases where it’s slower than their competitors, but also cases where the inverse was true. And further, as noted above, if you did take into account ClimbPro or Hammerhead’s CLIMBER, then those instant gradient differences were mostly moot when looking at ClimbPro.
Nonetheless, I’ve spent an inordinate amount of effort and time trying to document the differences between these units: Garmin Edge 540/840/1040, Hammerhead Karoo 2, and Wahoo ROAM V2. Basically, doing side-by-side rides of both long-term/slow climbs, but also fast/sharp/steep climbs, with cameras and screen recording going. You can see a tidbit of this in my main review video, with a longer breakout video to come.
The long and the short of it though is that the Edge 540/840 seem to act slightly faster than the Edge 1040 in some cases, but about the same in others. In relation to the Karoo 2 and ROAM 2, the Karoo 2 is by far the fastest responding gradient changer. In 90% of those cases, it gets it correct far faster, but every once in a while it’ll be suspectable to some wonky gradient response that doesn’t align to reality. The Wahoo ROAM V2 is sorta the middle-ground, generally neither super-fast nor super-slow. Just sorta middle-bear.
Then you’ve got the Edge units. In cases of more normal climbs, you’re almost never going to notice the differences between all of these units (compared to Karoo/Wahoo), they all slowly increase to match the slowly increasing gradient. However, in short/steep climbs where the road bucks upwards and you swear a bunch, you’ll typically see about 5-10 seconds of lag on the Garmin units. There’s some speculation that this is because Garmin has a 15-second weighted smoothing average in place, likely to reduce errors from things like vibrations or even wind (in fact, I saw some of this impact the Karoo 2’s and Wahoo ROAM’s normally faster responsiveness on a recent ride on cobblestones). This somewhat evens out in that as you flatten back out, it’s still showing higher gradients because of that lag.
But yeah, if you are frequently riding roads that are basically yelling FU at you, then you might carry that forward to the Garmin Edge series when it shows 0% and you’re actually at 20%. For better or worse, I don’t have any of those roads anywhere around me, perhaps not even in this entire country. I had to travel to Belgium and Mallorca over the past few weeks to find some of those. All of which is documented above.
Still, it’s important not to overthink some of these issues. While there are vocal critics of Garmin’s gradient responsiveness, the overwhelming majority of people don’t seem to notice/care. Make of that what you want. Would I like it to be faster? Of course. If I had to balance faster responsiveness for brief FU climb gradient changes (Karoo 2) versus more accurate ClimbPro data (Garmin), I’m going to choose the more accurate ClimbPro data every time, since that’s the thing I’m actually looking at for the next 15-75 minutes of climbing. But to each their own – maybe some day we’ll get both.
Navigation & Mapping:
This section is all about navigating with the Edge unit, and the built-in maps. To begin, the Edge 540/840/1040 all come with pre-loaded maps, as well as the ability to download cycle-specific maps for free. The main difference between those units is how much storage space you have, and if extra regions are pre-loaded. The Edge 540 comes with 16GB, the Edge 840 with 32GB, and the Edge 1040 with 64GB. But functionality-wise, all three units are identical map data-wise (except for address search I’ll talk about in a second).
Now, it’s important to note that with the Edge 540/840/1040 getting the new ClimbPro free-ride functionality, the map sizes have exploded. I mean, almost doubled in size. The real-world ramification of that is previously with a 16GB Edge device, you could fit both the US and some chunk of Europe on it. Now, it’s one or the other, hence why the 32GB of the Edge 840 is more useful if you frequently travel.
Just for context, here’s a look at the European map set sizes now (previously this was about 7-8GB):
- The core cycle map pieces: Roughly 7GB
- The ClimbPro pieces: Roughly 6GB for Europe Central+West
Plus atop that there’s a small map for Trailforks, of roughly another few hundred MB. I think it’s probably going to be time for Garmin to re-think how they do map downloads on the Edge series. First off, you still have to connect it to your computer. Whereas Wahoo & Hammerhead allow WiFi downloads of maps (Garmin allows WiFi downloads on their wearables for maps). Second, and most notable, Garmin only allows massive region downloads (e.g. all of North America), rather than per-country downloads.
I think having massive regions is great if you have the storage space, but practically speaking, it’s also a huge strain to download a map update that’s now 14GB in size. Or to download that last minute when travelling. Whereas the other companies allow you to pick a given country in most cases, or states in others. I get Garmin’s desire to sell-up a higher unit here with more storage, but with the new much larger map sizes, this starts to migrate from ‘annoying’ to ‘pain in the ass’, depending on how often you travel.
Map data aside, one minor but notable difference on the Edge 840/1040 compared to the Edge 540, is that it allows you to search for a specific street address. Garmin (probably rightly) assumes that it’s too much of a pain to type out a full address with buttons, so this feature isn’t offered on the Edge 540.
That said, frankly, outside of demonstrating how the feature works, I’ve simply never had a reason to type in an exact address on a bike computer. Like…ever. It’s just too cumbersome. However, one nifty feature here is that you can use your phone to type in things now. So if Garmin Connect is on your phone, it’ll prompt you to enter the text using your phone keyboard instead if you want, which is usually much faster for people. However, this seems kinda random as to when it appears. Sometimes it works, sometimes not.
As with the Edge 1040, Garmin revamped the POI database, making it easier to find bike-specific things now. So you’ll see stuff like bike shops, water stops, restrooms, coffee shops, and more. You can still search for all the other stuff like restaurants, hotels, transpiration, etc…. but Garmin has prioritized things you actually want to find on a ride.
You can also use this menu region to simply browse a map. For example, you decide to abandon your ride into the mountains and instead just want to go sit on a beach and eat ice cream. Sure, you could use the café/restaurant option to find an ice cream shop, but it’s just gonna be easier to look at the map and tap the beach and then choose to get directions to it.
In most cases though, you’re probably going to follow a course or pre-planned route. You can create courses umpteen number of ways, from on Garmin Connect itself (even on the unit itself), to 3rd party sites like Strava or Komoot, or by loading GPX/TCX/FIT files you downloaded somewhere. You can even re-ride past activities. The world is your oyster here, but that oyster eventually puts you on this menu where you choose a course:
Most of these are either Strava or Komoot courses, which automatically sync to Garmin Connect and then to the Edge 540/840 the second I hit save. It’s super efficient.
Once selected, you’ll see stats about the course, including an overview of the elevation and any climbs via ClimbPro:
At this point, you can tap to ride the course, which starts your navigating (once you press start on the activity). You’ll get notified as you approach a turn, no matter which data page you’re on:
Certainly, you can just stay on the map screen if you want to, but that limits your data field options, and also burns more battery. Instead, a mini-map will overlap over the top of the data page you’re on, with the turn information about 150m before the turn.
In the event you go off-course, you’ll get a banner offering you two basic options: Pause navigation, or Re-Route. If you ignore it, it’ll automatically re-route for you, rejoining the route where it makes sense. In cases where no obvious re-join exists, it’ll have you backtrack accordingly. You can actually change this behavior if you want. There’s a myriad of settings you never knew existed deep in the Activity Profiles > Profile > Navigation > Routing > Route Recalculation and Course Recalculation options.
I haven’t had any problems with any of this. As with the Edge 1040, this new layout just works a lot better, especially the pause navigation option. The idea being that if you’re just going a few hundred meters to that ice cream shack by the beach, you don’t need your bike GPS incessantly beeping at you that you’ve screwed up. Then, once you get back on course you can resume navigation. Easy-peasy.
You can literally see a great example of this here, of me actually taking a photo mid-ride slightly off-course, and it pausing by itself to see what I want to do:
In terms of the actual routing/re-routing, again, no issues with me going off-course in three different countries now, it all gracefully did what I expected. Even here in Amsterdam in one of the most bike-lane/road-dense locations on planet earth, it handles all of this without issue (something that can still challenge other companies, or some of Garmin’s older devices).
Same goes for initial route ‘Calculation’, or any immediate re-routing. That now happens pretty much instantly (like the Edge 1040), but that’s also a little bit of changing what’s displayed to you. On older Garmin devices, it’d actually calculate the entire route in front of you. You never had to wait for it, but people assumed you did. It calculates it in order of the route itself, so in reality you could never pedal faster than it could figure out the route – even if it took a few minutes to sort out a 100KM route. Now, most of that re-calculation happens behind the scenes (like their competitors do). There’s no reason to show you something that’s not going to come up until hours later in the ride.
Now, one area I’d like to see improved is just how courses are organized. I think across all companies, including Garmin, this is just getting messier and messier. With more and more services automatically pushing routes to your device, it becomes cluttered with routes (and copies of routes due to creating duplicates for things like PowerGuide or making a Strava route Public on Garmin Connect). I’d really like to see some attempt at a folder structure here, either automatic or one that I could manually create and is synced with Garmin Connect. I’m not saying I have a clear solution here, but I think it’s fair to say that simply sorting an ever-growing and duplicate course listing isn’t really cutting it anymore.
For example, I’d love to have it automatically folderize routes that start within 5KM of where I am now, and then by distance. Sure, you can sort by nearness to you, or by distance, but not both. Thus, I’ve got routes from Australia or South Africa showing up in the mix when I don’t care about those now.
But that’s a relatively minor nit in the grand scheme of things. Overall, Garmin is well known for their navigation, and the Edge 540/840 continues the trend the Edge 1040 set, making it the leader in terms of on-bike navigation options. While the Hammerhead Karoo 2 has a prettier display for said maps, Garmin’s feature set is far wider in terms of navigation features. As always, whether or not you use those features is a different question.
Structured Training & Power Guide:
Many of the new features to the Edge 540 & Edge 840 are within the realm of structured training, or at a minimum Training Load & Recovery. Some of these are center-stage, like Acute Load, and some of them are more tangential, like the ability to see a profile of you as a rider. Either way, I’m bundling them all into this section. Additionally, all of these things have previously launched on the Edge 1040, save the new Training Plan bits.
Beyond these, there are aspects like the new Power Guide (also launched on the Edge 1040), as well as the long-existing structured workouts option, including the ability to ride workouts from 3rd party entities like TrainingPeaks, TrainerRoad, and countless more.
First up are the newer stats pieces, which are all under the section called ‘My Stats’ on the unit. Alternatively, you can add them as widgets, like I have, for quick glancing. If you have a Garmin, these will (or should anyways), be in sync.
Next up is Training Status, which is comprised of both VO2Max and Acute Load. Of course, my VO2max has been solidly broken on the Garmin platform since last November, and hasn’t changed since then despite both a massive increase in volume since early January, and a substantial increase in FTP. Next is the Acute Load. This load is looking at your last 7 days of training volume, and will show non-cycling workouts on the Garmin platform as well (including ones from Zwift/TrainerRoad/Tacx).
The singular challenge with my VO2Max value being stuck/broken, is that since it’s not rising, it’s very challenging for me to get anything other than ‘Maintaining’ as my training status (such as ‘Productive’). On the flip side, I use Acute Load as arguably the single most important number I look at in terms of training load, as it allows me to roughly baseline my total volume. The green section is my normal training load, called the ‘Tunnel’.
Next there’s Exercise Load. This is basically a way of looking at the breakdown of your training load for the past 7 days, in terms of categorization:
Likewise you’ve got Load focus. This is simply looking at a 28-day variant of the previous 7-day Exercise Load chart.
After that, there’s Cycling Ability. This came with the Edge 1040, and gives you scores for each category. The idea here is that from there it can look at any course you load up (e.g., Alpe d’Huez) and tell you whether or not you’ll do well on that course. It’s effectively a way to match your skills to a given course.
You can see this here for the Sa Calobra course:
And, if you’re lucky enough to have gone somewhere warm (or high in altitude), you’ll get either heat or altitude acclimation:
There’s also a few other metrics shown, including Recovery Time. This is pretty self-explanatory. The reason this value is this high is I just did a beast of an interval (run) workout this morning, accompanied by a big week in training, as well as another ride this afternoon.
Finally, there’s FTP. In my case, I had set a manual FTP initially, but then let it auto-detect from there:
You can also see metrics like Fitness Age, Intensity Minutes, Stress Score, and more – all buried in the menus that you might not ever see. But, let’s move along to Power Guide.
Power Guide is basically going to define a specific power pacing plan, for a specific loaded course. It’s vaguely like Best Bike Split, except not nearly as advanced (BBS takes into account things like aerodynamic properties, wind, etc…). The idea though being you can essentially predict a specific finish time on a specific course, based on your chosen intensity level. The easiest way to start this process is by first having a course loaded in Garmin Connect, and then going into the Power Guide option and selecting said course. From there you can adjust the intensity slider, which changes the estimated finish time, as well as all of the split components seen down below.
Garmin divides up these sections based exclusively on gradient. Meaning, here in Amsterdam, when I use Power Guide, it’s basically useless because it’s one giant pancake and one giant segment. Versus using it in Belgium on that super hilly course, it’s constantly targeting different power values for both ups and downs, as well as the flats.
Once you’re on the bike, you’ll load up the course first, and then see the option for the Power Guide for that course. At which point you’ll see the targets for each section/split, as well as overall goal against targets. In my case I generally beat each split section, but my overall averages were impacted (lower) because of my desire to take photos of llamas, cobblestones, and pubs. Things I don’t usually do on a race itself.
It’s a cool concept, and is a good way for most people to pace using a power meter (which is required) without having to spend for a coach. Meaning, if you had a canned/semi-canned training plan, you might not actually have a good idea on the race side. This can fill that gap a bit by letting you adjust the slider pre-race to see estimated finish times. Additionally, if the race starts falling apart (or, you feel it’s waaaay too easy), you can adjust the slider/intensity mid-ride too.
Now, if you want to use Garmin for your entire training plan, the Edge 540/840 now have the ability to create an entire training plan for your specific race. The Edge 1040 gained this ability last fall to a degree, but it’s been more fully implemented over the last few months atop changes in Unified Training Status, accounting for things like sleep and other training load factors.
You’ll create your specific event on Garmin Connect, including uploading/specifying the exact course, date, and time. Using that information, it’ll create a specific training plan for that event.
The unit will create a periodized structure, including a base, build, peak, and taper phase.
Then each day it’ll give you a specific structured workout to do. If your sleep is too low, it’ll trigger a rest day or other easier workout instead. And you can adjust parameters like your long ride day as well.
Finally, you may alternatively be using structured training from either Garmin Connect or other 3rd party services/platforms (e.g., Today’s Plan, TrainerRoad, TrainingPeaks, etc…). All of those sync automatically to your Edge, and will show your planned workout on your Edge device.
Once I head outside, it’ll show me the steps for that as I go along. Here’s one from last week or so, with a set of intervals, showing me my power targets and current status for each of those intervals.
None of this has changed anytime in recent years, it’s all basically the same – and all works pretty well for both myself as well as plenty of others who have used this functionality over the years.
Now there are two versions of the Edge 840 – one with solar panels (Edge 840 Solar), and one without (Edge 840). This section is entirely focused on the solar variant, given the title you see just above the pretty picture. The general theory with the Edge 840 Solar is that it’s going to accumulate solar time while you’re riding, as well as just hanging out in the sun not-riding.
Starting with the solar panel itself, it’s divided into basically two portions. The first is the most obvious portion of the panel at the top/bottom of the screen (the reddish portions above). This is the visible portion, and has a photovoltaic level of 100%. In the most simplified explanation, 100% of the sun’s goodness that hits this portion of the panel gets converted to extra juice (there’s a lot of technical nuances to that, but again, simplicity here).
However, over the entire display is another solar panel that has a 15% photovoltaic level (a notable increase over the Fenix 7 & Forerunner 955 panels which are 7% photovoltaic levels). This main panel is obviously far larger than the upper/lower panels, but harvests less energy since it’s just 15% versus 100%. But, you can see through it, so it’s essentially invisible to you. That’s what Garmin calls ‘Solar Glass’, because it’s actually glass.
As one of the data pages while riding, you’ve got a dedicated page for monitoring your solar progress, showing time gained in minutes:seconds, plus a little graph of your solar power:
After you’re riding you’ll see the same thing in some of the summary screens, showing your ride totals. Here’s one from a 3 hour sunny ride in Belgium (below), which matched almost exactly the gains from a different 4hr 21min ride in Mallorca (in the sun) where I also gained 26 minutes.
And then inversely, here’s a dark/overcast late afternoon day in Amsterdam, where after riding for 1hr 40 mins, I gained a whopping 2 mins and 54 seconds:
This is also shown in Garmin Connect too, if you want to see total ride time gained during the day. One important thing to remember though, is that you’re still burning battery. Garmin’s solar battery claims are based on 75,000 lux conditions (a measure of brightness), which is another increase over their previous baseline claims of 50,000 lux conditions for their Fenix/Instinct/Forerunner units. This is actually a more useful change, because 50,000 lux conditions really aren’t that high. Even in the winter, on a sunny day in the Netherlands I can hit 70,000 lux. So it’s less about a hot day, and more just about direct sun.
So what happens when not riding? Well, let’s dig into that. If you tap the upper left button, you can choose to go to sleep or power off. When you press the sleep button, it shows the current solar intensity and current battery life. Here’s me putting it (and the other Solar units) to sleep in the Netherland’s April sun for a few hours.
I came back 3 hours later, in this case about 2 hours of that was mostly unbroken clouds (1:56pm till 4:59pm). The remaining hour was high/thin clouds. In total, here’s what it showed:
Garmin Edge 540 Solar: 39% to 42%
Garmin Edge 840 Solar: 79% to 79%
Garmin Edge 1040 Solar: 97% to 97%
Then again two days later, from 1:15PM till 4:08PM in strong direct afternoon sun – apparently gaining almost nothing. I have no idea why one unit above/below gains one day, and the other not. And vice versa. I would say having the Edge 1040 in the upper 90’s may impact charging, since most devices tend to slow-down charging rates above 90%, but I have no idea here.
Garmin Edge 540 Solar: 75% to 75%
Garmin Edge 840 Solar: 74% to 75%
Garmin Edge 1040 Solar: 89% to 89%
For the times where I’d I’d gain a couple percent, that does basically translate to about 1-2%/hour riding time. Meaning, if you leave it there an entire day, you could easily get a few hours of actual riding time.
Note that on the Edge 1040 Solar, there is/was a threshold where really hot days (like summer days), if you left it in the sun when not riding (e.g., on a table) it’d overheat and not solar charge anymore (to be excruciating clear: This only impacts solar charging when it overheats, not operation of the unit, further, this virtually never happens while riding due to the cooling effect of your bike speed). Unfortunately, being April right now, I haven’t had any of those hot days to test the 540 Solar or 840 Solar for the same thing.
The point being that in theory you could leave your Edge unit by the window in sleep mode and gain battery time the other 8-10 hours of the day it’s sunny out, and theoretically never have to charge your unit. In practice though, I’ve found that a bit tricky. Also, in reality, you could just plug it in for like 5 minutes and get the same as a day of solar. But hey, if you’re doing some crazy bike-across-Africa challenge, then sometimes every little bit matters.
Now, I’m gonna save you a bunch of time – GPS accuracy is basically perfect here. There’s literally nothing of concern in all the riding I’ve done, including in the mountains, through rock canyons, cities, and more. This mirrors what we’ve seen on the Edge 1040 since it launched last summer with multiband GNSS. Like that unit, both the Edge 540 & Edge 840 mirror it in performance, and also slightly best the competition – both the Hammerhead Karoo 2 (no multiband), and the Wahoo ROAM 2 (multiband). It’s usually very very minor differences, but you can see it here and there with just slight cutting of corners by Wahoo/Hammerhead on occasion.
Getting right into things, here’s my ride in Mallorca over Sa Calobra. This includes essentially a day of twisty/turny roads etched into the mountainsides. On the whole it’s a challenging, though not horrific, GPS environment. There are some horrifically challenging spots within it though.
As we look at some of the initial sections getting to Sa Calobra, you can see it’s exactly on the roadway, with only a tiny bit of offset activity by the Wahoo ROAM V2 here and there.
Even on this fast section of mountain switchbacks, virtually all the units remain on the roadway.
Here’s an aerial photo of this next section, to set the stage:
And then here’s the GPS tracks from that section, which are basically immaculate, including the loop.
And then later on, we’ve got this famed section where you slide between two rocks that are seemingly collapsing towards each other:
As you can see, the GPS is only different between the units by just a couple meters (note the scale):
Next, we’ve got a ride in Belgium as I bounced around the cobbled classics for a number of hours, this is relatively easy GPS conditions in the grand scheme of life, though, sometimes easy can still be challenging. However, I was actually more interested in the elevation accuracy here. More on that in a second. First, the GPS side of the house:
If we look at famed cobbled climbs like the Koppenburg, it’s identical across all units:
So then we try something more tricky, going under a railroad, to see if there’s any crazy wonk in the tunnel. Nope, essentially a wash (maybe a smidge bit of an extra meter or two on some tracks, but nothing to get upset about):
Even going around this roundabout in town, it correctly nailed the track – under a railroad mind you, where I took the inside curve:
As for elevation? All within +/- 3 meters of each other the entire time. The Karoo 2 oddly lost the plot about an hour in, for no clear reason. It was totally part of the gang, and then it became an offset outcast for the remainder of the time. I don’t remember seeing that elsewhere, so…ok. I guess I did something to offend it.
Next, we’ll wrap up with another boring iteration in the GPS plots. This time here in Amsterdam:
Starting off in a section with some tall buildings on both sides. No issues from the Garmin, though a slight blip from the Karoo 2:
But looking at various twists and turns, including in some towns showed no problems:
Or again out in the middle of nowhere:
Look, I could keep creating charts – and maybe I will when I’m sufficiently bored with nothing else to do. But all the charts and all the data plots I’ve looked at are virtually identical/perfect. We might finally be arriving at the point where for cycling GPS units, it’s going to be harder and harder to find GPS faults. Don’t worry though, running GPS still seems to be more challenging.
(Note: All of the charts in these accuracy sections were created using the DCR Analyzer tool. It allows you to compare power meters/trainers, heart rate, cadence, speed/pace, GPS tracks, and plenty more. You can use it as well, more details here.)
The Edge 840 delivers on what people want: An Edge 1040 in a smaller package. It’s got an identical feature-set to the larger-screened Edge 1040, and in fact, is arguably a more usable device, since it has the full complement of buttons the Edge 1040 lacks. The only differences between the two units are size/battery/screen. That’s it.
However, more critically, the Garmin Edge series finally delivers what many have been asking for: ClimbPro without a route/course loaded. On the whole, it’s very good. It correctly illustrates the climb as I approach it, and the calculates the pain and suffering till the top. Is it perfect? No, it doesn’t read your mind, yet. It generally gets it right, but every once in a while it just doesn’t guess right. I suspect we’ll see them continue to tweak some of these mind-reading gaps, based on user feedback.
The remainder of the features all are aimed at filling in the Garmin ecosystem. Things like Stamina to match the wearable side, and Training Status 2.0 to go along with that. Having Power Guide for pacing is legit useful. I could quite conceivably see using it for some races later this spring. And the rest of the core Garmin features you’ve had for years works as before, just a touch bit prettier now (and faster). Inversely, Garmin does need to sort out their map download situation. They’ve built a bit of a behemoth here with all the new map data in the unit, and for those that travel frequently (or even update the maps frequently), the annoyance will grow. I don’t think this is a ‘today’ problem, but a ‘by next year’ type of problem.
Up till now, I’ve long recommended people buy the cheaper of the two mainstream Edge units, meaning buy the Edge 510/520/530 series instead of the Edge 810/820/830 series. This was largely because the Edge 8xx series lacked the majority of the buttons when you wanted them, and also lacked a compelling use-case for a touch screen. But with the Edge 840, my recommendation is finally changing: Buy the Edge 840 over the Edge 540.
Now, this isn’t because the Edge 840 is magically more awesome than the Edge 540. But rather, because I’ve just found the button interaction on the Edge 540 oddly cumbersome with the new user interface. Specifically, when doing anything that requires diving back to the main/settings/features homepage menu mid-ride. On the Edge 840 it’s a split-second swipe-down or tap. On the Edge 540, it’s an entire set of dance steps of long-button presses, a bunch of ups/downs, changing button sides, and more. All while not trying to crash.
As for solar? Honestly, I wouldn’t spend the extra for it unless you ride in sunny weather all the time and need every last bit of juice. In most cases, you’d be able to charge the Edge 840 with the same amount of solar power from a 4-hour ride, in a mere 1-2 minutes via USB-C. I wouldn’t call it a gimmick, but rather, it’s just something only useful for a very small sliver of the population – at best. The good news is, that saves you money to spend on ice cream or something. And ultimately, at this point, the Edge 840 is clearly the cycling computer to try and beat. Well…minus the larger Edge 1040, of course.
With that – thanks for reading!