Constantin: monitor effort drift against your session average

[Łukasz Szmigiel]

Constantin 2.31

FYI: The update may not yet be public in the apizone.

Charts now use minute averages, expanding from a 5-minute to a 10-minute and then a 15-minute window. Nine vertical levels make the trends steadier, while a wider green line helps distinguish overlapping pace and heart-rate trends.

Charts refresh roughly every four seconds, with numeric values updating every two seconds. I also simplified the calculations and screen layout to reduce overhead.

Initial testing suggests the chart survives longer when used alongside route navigation. This is encouraging, though longer testing is still needed to confirm reliability.

Full details, the changelog and an interactive demo are available at constantin.szmigiel.design.

[Łukasz Szmigiel]

Constantin 2.32 fixes an unintended regression in 2.31: the chart’s endpoint was showing an averaged value rather than what was happening now.

The endpoint now represents the latest pace, NGP or speed delta and heart-rate delta, updating roughly every four seconds. The four earlier points remain averaged and cover consecutive intervals, giving 4, 8 or 12 minutes of history plus “now”.

Full details, the changelog and an updated interactive demo are available at constantin.szmigiel.design.

[Łukasz Szmigiel]

Good news everyone! It seems that I’ve finally found a way to have a history in main.js that survives the UI unload and no-crash experience. I’m currently testing this version.

[Łukasz Szmigiel]

Constantin 3.00 — the Carduelis release

Constantin 3.00 is out. The main change: you now decide what “steady” means, and that choice directly shapes the trend chart.

Where to set it. Open Constantin’s settings in the Suunto app. There are two sliders: Steady heart rate range (2–9 bpm, default 4) and Steady pace and speed range (1–10% of your average, default 3%). Changes apply the next time the Constantin screen loads, e.g. at the start of your next workout.

What it does to the chart: a minimum scale for steady running. The chart has nine levels, four above and four below your current drift. Your range sets the smallest step between levels, so the chart can never zoom in further than four ranges either way. With the default 4 bpm that’s ±16 bpm: a heart-rate point stays on the line within 0–3 bpm, moves one level at 4–7 bpm, two at 8–11 bpm, and so on. For pace at an average of 6:00/km, 3% is 11 s/km, so a point moves one level only once it’s 11 s/km away. This is what matters when you’re running steady: small fluctuations inside your range keep the line flat, and every step means a real change of at least that size.

Beyond that, the scale is still dynamic. Once any point drifts further than four ranges from now (more than 16 bpm with the default), the chart widens to fit the largest difference, and each step becomes bigger than your range. Example: with a 4 bpm range, a point 24 bpm away puts the scale at ±24 bpm, so one level is 6 bpm. So during intervals, hills or a big fade, you still see the whole shape on screen; the range only stops the chart from blowing up tiny changes when things are calm.

Same range for the status. The STABLE label uses the same numbers: a delta smaller than your range is STABLE; from the range upward it reads HIGH/LOW for heart rate or AHEAD/FADE for pace.

How to choose. Go tighter (e.g. 2–3 bpm, 2%) to see every small change on steady tempo runs or long easy efforts. Go wider (e.g. 6–9 bpm, 5%) if you only care about bigger shifts. Pace and speed use a percentage, so the setting means the same at any pace and in slower sports like hiking.

Also new in 3.0: the chart now survives screen changes. When route navigation starts or stops, or another SuuntoPlus app is switched, the full chart comes back in about 15 seconds, and history keeps collecting while Constantin is hidden.

[Łukasz Szmigiel]

Hi everyone,

Could someone with a Suunto Vertical 2 or Race 2 share the full filename of the latest firmware package stored on their watch? Ideally version 2.56.28.

I’m looking for the complete .sof filename, including the build number and the identifier at the end, rather than just the software version shown in About. I need it to find a direct download link and download the firmware to my computer.

To check the package name:

1. Open Settings → General → About.
2. Scroll down to Data privacy.
3. Press and hold the lower button until the service/debug menu appears. This may take around 12–20 seconds.
4. Open Select OTA pkg.
5. Take a photo of the package names or copy the full filename, and mention whether your watch is a Vertical 2 or Race 2.

Please only view the list. Don’t select a package to install, and don’t use “Delete OTA pkgs”, as it removes the cached firmware packages. Once you have the filename, leave the menu.

A photo is fine if the filename is too long to copy.

Thanks!

[Mff73]

@Łukasz-Szmigiel
I just have 2.56.18,sorry
https://firmware.geo.movescount.com/production/Xiamen-fw_2.56.18.31896-V-a8f49e99.sof

[Łukasz Szmigiel]

@Mff73 thanks, It’ll be helpful!

[Lazar Dimitrov]

@Łukasz-Szmigiel
Here’s the one for Race 2 - 2.56.28

https://firmware.geo.movescount.com/production/Wismar-fw_2.56.28.33260-U-5bfd6226.sof

[Łukasz Szmigiel]

3.10 is out. What changed since 3.00:

Chart

• History: 30 minutes instead of 12. Groups (oldest → newest): 1-1-1-1, then 4-2-1-1, 8-4-2-1 and 16-8-4-2 minutes (imagine as dots from the left side of the screen, where the rightmost is “now”).
• Each point is now that period’s mean vs. your current value. In 3.00, minutes were stored as deltas against the running average: steady drift showed at about half its size, and a lasting slowdown could look like a recovery.
• Fixed scale: one step = one steady range (4 bpm / 3% by default), max ±4 steps. In 3.00 the farthest point stretched the scale, so a warm-up could turn one step into 8–12 bpm and hide later drift.

Warm-up (new setting: 0–20 min, default 10)

• During the warm-up, the Pace and HR views show WARMUP instead of a status.
• After it, delta, status and the on-screen average compare with your average since the end of the warm-up, not the whole workout. In 3.00, HR read HIGH for most of a shorter run just because the first minutes were slow.
• Wider chart groups start only after the warm-up (default: at 18, 25 and 40 min), so the warm-up never comes back into the oldest point.
• 0 = 3.00 behaviour.

Summary

• Pace/HR AVG: unchanged (watch averages).
• VAR: measured against the post-warm-up average, so values are lower than in 3.00.

Full changelog: https://constantin.szmigiel.design

[Mich Tom]

@Łukasz-Szmigiel Hi, here a little feedback. Of course many thanks for the app and the efforts you are putting in the dev and the updates. Keep it up!

It’s by far the s+ app I have used the most yet with my ~ 2 months old Race S.

Unfortunately the 3.00 and 3.10 updates make the watch systematic freezes and resets if a s+ guide is simultaneously active. When activated alone or with another sport app everything seems to work just fine.

For 2 weeks, with 3.00 of course, I experienced once another issue, the app couldn’t any display data. I was using the navigation and maybe another app as well, no guide.
I have to test this configuration again, especially since there is a new update.

[Łukasz Szmigiel]

@Mich-Tom thanks a lot for the report.

To be fair - I’ve never tested the app alongside any guide being active as I’ve never used guides. The app is heavy and it’s already pushed to the limits of what the S+ platform can handle (untill I find a way to further optimise it), so in certain circumstances it may fail. However, normally the watch should unload any S+ apps in order to regain the memory. Freezes and reboots happen when it cannot do so.

I’ll do some digging into the compatibility with guides.

As for the issue you’re describing with no data - did you see a black screen or just no graph? were “–” present where the data should have been?

[Łukasz Szmigiel]

@Mich-Tom can we dig a little bit into your experience? It would be helpful if you could answer those questions:

1. Which guide was it? A structured workout created in the Suunto app, or a guide from a partner service (TrainingPeaks, Humango, etc.)? If you can share the name or a screenshot of the guide, even better.
2. When does the freeze happen: right after pressing start, at the first step change, or at a random step later on?
3. Was route navigation active at the same time?
4. Which other sport app worked fine together with Constantin, so I can compare its size?
5. Which firmware version is on your Race S (Settings → General → About)?
6. Did you ever use the same guide together with Constantin 2.x without problems, or did you start using guides only recently?
7. Rough length of the workout before the freeze, and whether it was running, trail running or another sport.