Suunto SHRB2 Firmware 3.2.6.8 Update

[isazi]

Forwarded this discussion to the product manager at Suunto

[snow*]

tried this morning the new fw (don’t pay attention to the noisy part—I was fiddling with my running vest)

thanks @łukasz-szmigiel for this handy tool

that said I keep trying with ESD tape/bags (not used in the above run)…

[atoponce]

@snow I’m about to test the same. I chopped up an ESD bag hard drives come in, wrapped it around the module, and taped it to the back careful to not short the snaps. About to head out on a run with it now and see how it performed.

[ggrego]

Hello little have returned to the previous version that version is meh the flight times no longer work 45 ms the previous outputs were at 290 ms thank you

[snow*]

@ggrego said:

the flight times no longer work 45 ms the previous outputs were at 290

they’ve probably changed the FT (FT = Duration of a single step - GCT) calculation and imo it’s not wrong when viewed in the context of the other data e.g. see @atoponce math (well, there’s still something that needs to be fixed, since @inge-nallsson’s FT value is 0…)

[atoponce]

About on par for me when it’s not shielded. Although 0.0% anomalies, which is different. This was a trail run with friends.

[matram]

A bit more input from my side. A run today of mixed-pace short intervals. Data with 3.2.6.8 FW and compared to Stryd Duo.

The overall run

Metric	Suunto	Stryd
Step Cadence	150	151
GCT	435	457
FT	1	N/A
GCT:FT	2419.1%	N/A
GCT * Step Cadence / 60 (= Duty Factor)	1.09	1.15

The formula for Duty Factor (DF) assumes that GCT is per individual foot. Which in this case means I am mostly walking, GCT > Step time.

Let us compare some intervals at a higher pace to see how they differ. I am using only Suunto numbers here. I can provide Stryd if it is of interest.

Interval Pace	Cadence	GCT	DF	Note
4:10	208	297	1.02	This is a 30s interval for me
5:15	176	347	1.02	This is about VO2max pace for me

Full disclosure, I am 70+ years old. Not especially fast. My running style is fairly flat. I have run mostly half marathons and full marathons during my 25 years of running.

My current absolute max pace is 3:30. But based on the duty factor numbers it looks like I would still be walking

[ggrego]

I reset the belt and tried again over 10 minutes and the flight time returned to normal 245 ms suunto updates are deplorable forced to reset everything after each update show included

[snow*]

@matram interesting.

Your GCT is 435 mS, while the step duration is 400 mS. It seems that when the GCT is greater than the step duration, the FT becomes 0 or so as if to tell you that you are “always” in contact with the ground.

same applies to @inge-nallsson e.g.

GCT 337mS
Step cadence 180 so step duration is 333mS

Again GCT > SD

Does that make sense?

[matram]

@ggrego
Just to clarify. I did a factory reset after the update of the FW and had to re-pair the belt with my iPhone and Watch. This took several attempts.

My old Polar H10 updated FW more easily and cleanly.

[matram]

@snow
Maybe, I could buy that for a very slow recovery run at 7 - 8 min pace.

But 4:10 pace is very close to my absolute limit and it sure does not feel like I am speed walking.

But it seems like I am in good company with other walkers

It comes back to, if GCT is for one foot per step or for both feet per stride, the rest follows mathematically. I guess Suunto should provide an authorative answer to clear up the confusion.