Treadmill Distance Accuracy

[Spree]

@Stas-Varazhbit I agree with the battery, it’s not great. I didn’t have connectivity problems though.

[Andi Buzer]

I received my Runn Sensor on Friday and did two runs with it over the last two days. It’s stunningly accurate, no big differences and kilometer vibration of the watch matches with display of the treadmill.

[pilleus]

@Andi-Buzer Did you increase the sensitivity of the Runn to obtain a correct cadence?

[Andi Buzer]

@pilleus no not yet. I did the speed and incline calibration with the configurEZ app and nothing else.
I just compared it to the trackings before installing the runn sensor and it appears to have almost doubled for the same speed. 79 before installing to 155 after installing.

[pilleus]

@Andi-Buzer It’s another value. There is SPM and cadence. If I sync the activity to Strava I get the double value of the SPM, which is the (cadence * 4) …

And if you use the Runn without calibration, you will get the real speed and distance, which may differ from your treadmill. I just calibrated the incline and use the speed settings without calibration.

[Andi Buzer]

@pilleus so just to make sure I got it right. Cadence is one leg, SPM both legs. And Strava misinterprets the value delivered by the runn and doubles it ?

I guess I should reset the runn to factory calibration then

And now on German to eliminate the chances of me messing up translation:
Also es ist ein Datenfeld, aber die Uhr berechnet den Wert anders als der Runn ? Und Strava geht von der Art und Weise aus wie die Uhr es berechnet und nimmt den Wert Mal 2 ?

[pilleus]

@Andi-Buzer Garmin macht es korrekt, das Datenfeld stimmt, die Angaben auch.

Suunto App zeigt z. B. 176 spm, Strava macht daraus beim Synchronisieren 352 S/min.

Warum auch immer.

For all: Garmin is okay, the data field is correct, the data too.

Suunto app shows e. g. 176 spm, after the sync to Strava I get there 352 S/min.

No idea why.

[Andi Buzer]

Today I ran into a new problem. After having to reset my s9p because workouts weren’t synced to it anymore. I obviously had to pair my runn to my watch again, and now my watch does not use the pace values delivered by the runn. Do I have to do some outdoor runs to get the calibration off the watch to work and then accept the values of the runn “footpod” ?

The problems which occur with my s9p in the last few weeks makes me really want to leave suunto…

[pilleus]

@Andi-Buzer

Did you pair the Runn as foot pod? The blue LED is on, when connected to the watch? And the Runn configuration is okay? The on/off switch is configurable to switch off both, BLE and ANT+. Just to be sure …

[Andi Buzer]

@pilleus yeah it’s paired as footpod and I double checked configuration. It’s also displayed as connected when I start the workout.

[pilleus]

@Andi-Buzer

Okay, you can try to change the data field from pace to speed to check if this is the problem. The sticks on the treadmill floor are okay? Does the app Configurez show the speed and incline?

[Andi Buzer]

@pilleus yeah the ConfigurEZ app shows the values spot on.
Gonna test the change for the data field tomorrow, although I haven’t had it changed in the treadmill mode before the soft reset.

[Andi Buzer]

So it turns out I’m just dumb. The watch connected to the Garmin HRM pro plus which was in near vicinity and acts as a footpod as well. After moving it to another room and trying the pairing again everything worked fine. Nonetheless it wasn’t helpful neither being able to choose between sensors to connect nor see the name of the connected sensor on the watch.

[isazi]

@Andi-Buzer said in Treadmill Distance Accuracy:

Nonetheless it wasn’t helpful neither being able to choose between sensors to connect nor see the name of the connected sensor on the watch.

Agree, sensor management should improve.