COROS has begun rolling out a new firmware update today that adds in more exacting time splits for certain sports, as well as a new waypoints-like feature for outdoor route navigation. In addition, the running track mode now supports structured workouts.
These updates are available for the COROS VERTIX, APEX Pro, and PACE 2, with the APEX coming a bit later this week. Note that while the rollouts began this morning, they are typically staged, which means it won’t necessarily show up on your device instantly – but may take a few hours/days. Also, you’ll need the latest COROS smartphone app to both update and utilize these features.
Here’s the full list of what’s in this update:
- Adds 0.01s to Run, Track Run, Bike, Pool Swim, and Rowing
- Adds checkpoint feature that allows users to record a point before, or during the outdoor workout under route navigation [Not for COROS Pace 2, as it doesn’t support navigation]
- Workout program supports track run
- App workout details include weather info: temperature, humidity, and wind
- New map layer options in the app from Mapbox: outdoor terrain, winter, and dark
Got all that? Good. Essentially all COROS watches get this update save the original COROS Pace, which is great! COROS is still mostly early enough in their existence as a company that it’s relatively easy for them to support all watches for firmware updates. But as we saw with the original COROS Pace, eventually it becomes challenging to plan hardware wise for things years down the road. While that’s easier on high powered devices like a phone (or an Apple Watch), it’s far more challenging on endurance wearables that are designed to eke out every little bit of battery performance (at the expense of system capacity).
New Navigation Bits:
I wanted to briefly talk about the new routing/navigation features related to so-called ‘Checkpoints’. Ultimately, these ‘checkpoints’ are actually just called waypoints by all other apps/platforms/standards, though, the actual nuance of how they are implemented is different than what other platforms do.
In talking to COROS about it over the last few days, they see this as a starting point for deeper features around navigation and waypoints.
First though, let’s establish the core new features here to begin with, bullet-point style:
A) Ability to view checkpoints in the COROS smartphone app atop an existing GPX route within the COROS app
B) Can then transfer that route/course to your watch, inclusive of the checkpoints
C) On the watch you’ll see the distance and elevation remaining to the next checkpoint
D) You’ll also see the checkpoints listed on the breadcrumb and elevation profile pages
E) While out on the trail you can then save a new waypoint/checkpoint at any time
F) That waypoint is then added to the file and synced back to the smartphone app
Now, before I show this – the big-ticket item that’s *NOT* here though is the ability to navigate to a newly saved checkpoint on your watch, such as using the compass. Meaning, if you save a waypoint next to a given spot, you can’t then later on navigate back to that spot. There’s no menu for navigating to a new checkpoint on the watch. But COROS says that type of functionality is in the queue to implement.
To get started you’ll need a GPX file *WITH WAYPOINTS* defined in it. Unfortunately this isn’t something you can create in the app (either the route or the waypoints in the route). So you will need to use a 3rd party app to do that.
Side note: This turned out to be a solid pain in the ass to do purely web-based. Strava doesn’t create waypoints, and while Komoot creates waypoints, they don’t export them in the GPX file. Next, Garmin Connect allows waypoint creation, but doesn’t actually put them in the .GPX file upon export. Google Maps only allows KML/KMZ export. Easy Route, which I typically use, can’t create waypoints. Other apps I tried could create waypoints, but then sucked creating routes because they didn’t leverage auto-trail following. Ultimately, ended up using Suunto Movescount. #NotKidding.
(Another side note: According to this page, I’ve got a mere one week left till Movescount wouldn’t allow me to do this either. Shame. Long Live Movescount!)
Ok, with that file created, I e-mailed it to myself and told my phone to open it using the COROS app. From there I could see the route, and it even shows me the waypoints (thank god, given how long I spent trying to get to this point). Also, each time you click on a waypoint it’ll show how long between points and the elevation.
In this case, while there is actually a mere 15m of elevation gain to the top of the hill – Suunto Movescount doesn’t quite show it, thus, COROS doesn’t show it. Look, by this point in the post you’re lucky you’re getting any example data at all given how much time I burned trying to create a functional file.
You can edit the waypoints, handy since you’ll have noticed I managed to spell ‘Hill’ wrong earlier. So I fixed that down below. Then, I sent it off to the watch to sync to the Vertix:
After that’s done, load up your route on the COROS watch of choice, and you’ll see the waypoints showing up as little orange icons:
There’s also a new menu item called ‘Sections’, which lists the sections between each waypoint. This is pretty handy to be able to break-up the course, showing the same sections as seen earlier on the app:
And if you look in the elevation field, you’d likely see the elevation profiles of each one. But as discussed earlier, my file produced null elevation data and it’s Monday and lunch should have been three hours ago. Maybe on a Wednesday I might have tried harder.
Next, as I start, it’ll show me the segments and how much distance to each segment. This is pretty darn cool – I like it!
And you’ll also get a notification upon each checkpoint/waypoint you arrive at – ‘Reach Check Point 2’ – as seen below. After that, though not immediately, it’ll update to show the next checkpoint. It seemed to wait about 100-150m after I left the checkpoint before it triggered showing details to the next checkpoint.
There isn’t any way to navigate to an existing checkpoint after you’ve gone past it. So you can’t pull open checkpoint #2 after you’ve gone to #4. Which in some ways hints at how COROS sees this feature used: Race checkpoints. They outlined a scenario where a race director posts a .GPX file of the race with the various aide stations or – literally – checkpoints in the file. Hence the rebranding of waypoints to checkpoints.
As I mentioned earlier you can save waypoints at any time, and even see them on the map mid-route too once saved:
However, these are not accessible to route to within this section. Instead, they’re accessible afterwards on the COROS smartphone app in your completed activity, you’ll see the little icon added to the screen (#1 below), and then if you save that specific route it’ll save that checkpoint for your next workout. However, it won’t convey over any of the existing checkpoints from that previous run/ride/whatever. Meaning, the checkpoints that I defined from the earlier GPX file aren’t carried through to the new route if I add a new checkpoint.
Note that it’s not possible at this time to do both a structured workout and navigation at the same time.
And with that, you know everything there is to know about checkpoints on COROS watches.
Overall, it’s good to see COROS expanding their navigational aspects here. And it’s clear they’re starting to build the foundation for more features, as they themselves noted in my chat with them. I really like the segmenting of chunks between checkpoints, that makes a lot of sense – and fills in the two core metrics most people care about (distance to next point and elevation gain to next point).
Given this is their first slice at this, it won’t have anywhere near the depth of features of watches that have been around a decade. And I think if one looks at my feedback to COROS over the last year, I’ve been pretty consistent that they need to focus on polish on the app/platform side. To that end, we have been seeing that. Aside from the super-well executed COROS Pace 2 this past fall, almost everything else has been updates for existing watches – which is great. However, I think my attempt to write this post inadvertently exemplifies some of the opportunities COROS has to simplify the platform side further. In my ideal world I’d simply have authenticated my COROS account to Strava or Komoot or whomever, pulled in the route I created there, and then added any waypoints quickly using the COROS app. No messy files to create, e-mail to myself, edit, and so on.
But ultimately, no vendor boils the ocean overnight – and COROS has shown they can keep heating up the water each month. As always, looking forward to seeing what they add next.
With that – thanks for reading!