Lockdown setting suunto 9

[GingerBeardMan]

@isazi attempted this but got same results. did try excessive arm swinging though

[GingerBeardMan]

@NickK If only. we have the army enforcing lockdown, no cutting corners

[GingerBeardMan]

@Dimitrios-Kanellopoulos the fused track was much worse. I did 15km: 75x200m loops. My watch measured just over 9.5km and my trace was all over the neighborhood:)

[GingerBeardMan]

@Dimitrios-Kanellopoulos Sorry to be argumentative but the files exported from movescount show gaps of up to 8 seconds between data points I can’t imagine other manufacturers just fabricate 6 out of every 8 GPS points to achieve their advertised 1 second resolution. My Old Tomtom multisport is out performing my suunto 9. Is this just one of the costs of havin long battery life.

[Dimitrios Kanellopoulos]

@GingerBeardMan Hi please dont use GPX files (Why the obsession with that? ) . This is how GPS tracking works in all modern applications.

As an engineer on this subject with all the respect, because your Tomtom Did 1s interpolation doens’t mean that this is what happened neither what leading technology should do. I personally don’t like this type of argument. There are many reasons for that to happen on your old tom tom and mostly was not due to GPS but rather software extrapolation and interpolation on the export. (Yes I have worked on TomTom data )

Here is an example of loose records and how FIT files from Suunto app are generated. Movescount had many issues on this part and this functionality will go away

100:
timestamp: Sat Apr 04 2020 15:01:45 GMT+0200 (Central European Summer Time) {}
position_lat: 49.87775534391403
position_long: 14.683535909280181
distance: 379.5
heart_rate: 162
altitude: 404
speed: 4.031
activity_type: "running"
cadence: 89
power: 287
accumulated_power: 34748
stance_time: 224
stance_time_balance: 48.5
vertical_oscillation: 93
vertical_ratio: 6.5
step_length: 1310
__proto__: Object
101:
timestamp: Sat Apr 04 2020 15:01:46 GMT+0200 (Central European Summer Time) {}
position_lat: 49.87772106193006
position_long: 14.683511098846793
distance: 384
heart_rate: 163
altitude: 404
speed: 4.056
activity_type: "running"
cadence: 88
power: 283
accumulated_power: 35031
stance_time: 228
stance_time_balance: 47.2
vertical_oscillation: 91
vertical_ratio: 6
step_length: 1330
__proto__: Object
102:
timestamp: Sat Apr 04 2020 15:01:47 GMT+0200 (Central European Summer Time) {}
position_lat: 49.877690551802516
position_long: 14.683481510728598
distance: 388.5
heart_rate: 163
altitude: 404
speed: 4.056
activity_type: "running"
cadence: 87
power: 289
accumulated_power: 35320
stance_time: 234
stance_time_balance: 48
vertical_oscillation: 95
vertical_ratio: 6.5
step_length: 1340
__proto__: Object
103:
timestamp: Sat Apr 04 2020 15:01:48 GMT+0200 (Central European Summer Time) {}
position_lat: 49.87765618599951
position_long: 14.683452928438783
distance: 393
heart_rate: 162
altitude: 404
speed: 4.056
activity_type: "running"
cadence: 87
power: 295
accumulated_power: 35615
stance_time: 241
stance_time_balance: 48.8
vertical_oscillation: 100
vertical_ratio: 7
step_length: 1350
timestamp: Sat Apr 04 2020 15:01:49 GMT+0200 (Central European Summer Time) {}
position_lat: 49.87762190401554
position_long: 14.683426190167665
distance: 397
heart_rate: 163
altitude: 404
speed: 4.056
activity_type: "running"
cadence: 88
power: 294
accumulated_power: 35909
stance_time: 241
stance_time_balance: 47.3
vertical_oscillation: 101
vertical_ratio: 7.2
step_length: 1350
__proto__: Object
105:
timestamp: Sat Apr 04 2020 15:01:50 GMT+0200 (Central European Summer Time) {}
position_lat: 49.87758368253708
position_long: 14.6833985298872
distance: 401
heart_rate: 164
altitude: 404
speed: 4.056
activity_type: "running"
cadence: 90
power: 294
accumulated_power: 36203
stance_time: 242
stance_time_balance: 45.9
vertical_oscillation: 102
vertical_ratio: 7.5
step_length: 1350

With all the respect:

• GPS polling on the watch happens every 1second.
• Depending on the signal quality and other errors the distance is calculated every 1s if possible (also accounting accelerometer)
• GPX files cannot export non tree stuctures meaning that for each track record you need to interpolate or remove other track records if there are no data. For example if you miss coordinates but you have distance you cannot create a trackrecord as they dont support track records without coordinates.
• FIT files is what you should use.

Some side notes:

• Running on a tarrace we dont measure the x,y you need to measure a circle by defining the radious.
• Running on a circle you will injure your self eventually if you dont change direction as one foot will push more than the other.
• GPS error is about ~5m in the best. If your tarrace is not >5m as of a radious I cannot imagine this can work with any equipemnt.
• Educate your self since you are on it about accuracy. Dual frequency antennas and what is possible. for 5m loops I am sorry but this is not possible. To get a kinda good GPS “circle” you need 5m + 5m = 10m radious at least! That is if you have the best GPS signal! In normal conditions it should be 7m + 7m = 14m radious.

Here is a site that can help you and here is the image of what I am talking about

https://fellrnr.com/wiki/GPS_Accuracy

Image of how accuracy works

P.S. I am sorry if this sounds a bit agressive but I got a bit on my nerves because I tend to think that you are trying to create a problem for something that it’s not naturally possible in a way. I understand that and sorry.
PS1.5 Please don’t focus on the 1s GPX export, that is not the reason for your issue.
P.S2: Will a A3P work better than your S9? Perhaps. Perhaps even your old tom tom due to the antenna being external and patch (always looking at the sky)

Here is the problem with circular antennas and how sony solved it:

https://www.sony-semicon.co.jp/e/products/lsi/gps/technology.html

Note this:

The targeted low-cost and low-power system design, along with the expected harsh operational environment, derived us to face exceptional GNSS signal reception conditions.

Sony Semiconductor Solutions GPS/GNSS receiver/processor chips use a proprietary positioning algorithm to enable accurate positioning in a challenging environment, such as the skyscrapers of Shinjuku (i.e., multi-path environment) and/or when running on an athletics track (i.e., body effect, such as arms swinging and swimming).

(I would google GNSS body effect if I was you )

Take it easy, be healthy and protect your self. I’ts more important to be healthy than to get perfect GPS on a tarrance.

[GingerBeardMan]

I’m sorry if I’m pissing you off. Let me me just shut up and be happy with what I have.

[Dimitrios Kanellopoulos]

@GingerBeardMan nah man. It’s all good. But just those comparisons like : Simpsons did it.

On the contrary you gave place for some good analysis for tarrace runners.

You didn’t piss me off per se, but rather step on nerves.

It’s all good and it was my mistake to get nerves. I am the d528head here

[GingerBeardMan]

I take my hat off to you and how you handle people like me on a daily basis. I see you dealing with it with admirable deplomacy.
I am running a backyard ultra on saturday(goal of 90km). Based on my averages so 474 laps of my 190m(80x20x80x20) loop turns into 549 laps if I want proof that I covered the distance.
Just looking for the best possible settings or maybe its a miracle I’m after;)
P.S. I’ve been stuck in my house since 19 march so please excuse my behaviour

[Mff73]

@GingerBeardMan

P.S. I’ve been stuck in my house since 19 march so please excuse my behaviour

we are all in the same boat (same planet ) .

I am running a backyard ultra on saturday(goal of 90km). Based on my averages so 474 laps of my 190m(80x20x80x20) loop turns into 549 laps if I want proof that I covered the distance.

I retire my words, we are not from the same planet

[Dimitrios Kanellopoulos]

@GingerBeardMan you could try some phone app and some armband. No joke.

Perhaps a footpod ? (Zwift pod is cheap)

I also don’t know what to advice here other than a pod.

A phone app I am suspecting that will over do the distance , due to offsets (or the GPS stars).

That should be better than less distance I think.

[Dimitrios Kanellopoulos]

@GingerBeardMan ok one thing to check.

If you use Strava, have you tried to press correct distance via the webinterface ?

Btw if you are good financialy , a pod will be something that will benefit you in general in running.

[GingerBeardMan]

@Dimitrios-Kanellopoulos said in Lockdown setting suunto 9:

a pod will be something that will benefit you in general in running

definitely going to look into it after lockdown

[GingerBeardMan]

@Mff73 said in Lockdown setting suunto 9:

I retire my words, we are not from the same planet

That’s the goal. was going to run comrades this year but it looks like this will be the closest i’ll get

[GingerBeardMan]

@Dimitrios-Kanellopoulos said in Lockdown setting suunto 9:

have you tried to press correct distance via the webinterface ?

Distance stayed the same but my pace went from 7min/km to 2:59/km

[Dimitrios Kanellopoulos]

@GingerBeardMan

[Mff73]

@GingerBeardMan
and others, does it exists any track analysis software that may count the laps you will do (assuming you will have a GPS track enough precise to define an area for the soft to decide “each time you pass into this area, one more lap” ?
i thought i have seen something somewhere, (maybe a plugin of sporttracks, but can’t be sure).

[GingerBeardMan]

@Mff73 not sure, I know “autolap by position” is a feature on some Garmin models. I’m not aware of any software that does it after upload.

[Bulkan]

This post made my day.

Maybe we need to talk about GPS from time to time to learn about it… or maybe just say “The Suunto doesn’t record 1s and I see it on my GPX file” and see what happens…