Real world data

v.sacre

Tested Snap to route feature this afternoon.
Really nice feature if you want to realize accurate workouts on a known path or in urban/Forest environment. Or la f you get the official gpx from a race for example.

Else, I probably won’t use it for normal session

Theo Lakerveld

@fazel I’m typically doing around 60 min at ftp once a week. Usually devided as 4x15 or 3x20. This time I decided to go for the KOM.

Theo Lakerveld

Longer eazy run today. GPS was spot on, even underneath dense tree cover. OHR complied with perceived exertion: https://strava.app.link/cRDMubZKdhb

fazel

@theo-lakerveld Awesome.

ink357

@theo-lakerveld nice dog!

chrisc92

@isazi amazing bike trace this morning in GPS (+Glonass/Qzss) : in the wooden area the track overrides the route , almost like a snap to route :

I add to zoom to see the route :

ink357

Did somebody test the route tracking ? Any GPS losses ?

Mff73

@ink357 said in Real world data:

Did somebody test the route tracking ? Any GPS losses ?

maybe me
I was navigating a route while exercising, and a couple of times i was out of route, but it came back quickly. So i didn’t notice too much.
But once, i was looking at route screen, and GPS was lost at this time.
Is it what you mentionned ?

surfboomerang

@ink357 I did. Only once I noticed ETA was displayed as “–” and restored itself after a short time. I’m not sure if is because of a reception problem.

I did notice that the track was incredible close to the route so I don’t think accuracy is an issue in the open field. Didn’t try the forests yet.

ink357

@mff73 exactly. I use to trail on routes i don’t know and the route tracking is very important to me (i also take a map and my phone). In the last workout i made with my S9B, there were a lot of GPS losses. It could be boring…

Mff73

@pschenn said in Real world data:

Today I charged the S9P for the first time from 13% to 100% and it took only 52 minutes!

Up to 80% took only 25 minutes. After 90% things slowed down a little bit. In the last 2 minutes, it snapped suddenly from 95 to 100%, probably due to a recalibration of the battery since it was the first time…

I did the same test as you, but like a lazy guy
I let the watch register the data with a non GPS, non HR mode, and let QS show me the result

From 33% to 100% in 43min with same pattern
80% reached in 17min, wow !

Brad_Olwin

@ink357 I have had no losses and did an 11h run on Saturday.

ink357

@brad_olwin sounds good. What do you use ? GPS + ?? Or only GPS ?

pschenn

@mff73 That’s smart to do it like that!

Brad_Olwin

@ink357 said in Real world data:

@brad_olwin sounds good. What do you use ? GPS + ?? Or only GPS ?

Only GPS, I’ll post some data this evening, been busy.

chrisc92

@isazi today time to compare OHR with polar H10

Run OHR/Polar H10 comparison

Everything started well, but after 5 minutes OHR was continuously +40 over.
Maybe started to sweat ? incorrect placement ?
Not tightened enough ?

Dimitrios Kanellopoulos

@chrisc92 is this running ? Maybe sweat. Just in case next time try to clean the sensor of sweat.

Just saying. No clue though.

chrisc92

@dimitrios-kanellopoulos yes just easy running at Z2 , my Hr is 45-160, my Z2 stops at 130, tomorrow i will tighten the wristband and try the comparison again to understand, because the first minutes were so close.

wotus

The sensivity of autopause in openwater swimming is not as good as I remember from the Ambit3peak. During constant movement with higher speed in crawl it automatically stopped, but did not start again. I had to continue very often manually. In the end, about 300m was missing on a known distance of about 1600m. Gps was set in performance mode +Beidou.
I also miss a data field for the number of strokes. Unfortunatly the SA shows no swimming metrics like strokes or strokes per minute.

Mff73

I am really mixed with this S9P.
Really comfortable, quick charge, 24/7 HR is nice (i come from SSU without OHR )
GPS is not that exceptionnal in my area (tried GPS+Glonass, then GPS alone, then GPS+Beidou). It is good, but…
And fused alti is strange to me.
Latest run, GPS altitude vs recorded altitude

Start and end altitude are GPS OK (385m), but not recorded one (425m).
Max altitude is somehow correct (510m)