Suunto ZoneSense

Adrian.S

@The_77 Heart rate zones for cycling are usually 8-10 beats lower than for running, according to statistical studies of thousands of athletes.

When training for a triathlon, people do separate zone tests for running and cycling.

I regularly do running tests 1-2 times a year. The person who does this told me this, and I believe him because he does this professionally

I have set my zones 8 points lower than for running, and this more or less corresponds to how I feel at the same HR, for example 142 while in Z1 running and 142 while cycling are different feelings.

thanasis

I still get some hard to justify measurements
Eg today on a trail run , going uphill , HR exceeded 180bpm for over 2minutes and zonesense was still on the green part

timecode

@thanasis this happened to me just now. My HR was 176, Zonesense shows a huge drop. Not sure how to read that.

Brad_Olwin

@timecode ZS needs minutes to adjust. What you saw is normal. Your HR dropped a lot before it rapidly elevated at the end of your graph. ZS appropriately dropped then started rising. You were not long enough at a high HR! This has been stated many, many times here.

timecode

This keeps happening when using Zonesense a lot. I am able to see data on my watch during an activity, but in the app the graph looks like this. HR strap is connected, HR data is there. Any idea why this is happening?

Brad_Olwin

@timecode Is this true for all exercises? Do you have old ones with a strap prior to ZS release? Those will show ZS as well.

timecode

@Brad_Olwin it’s not every exercise, sometimes it’s like this - there’s a chunk missing at the end of the excercise or some drops:

Today I was checking Zonesense quite often on my watch during the excercise and I saw data. It’s just missing in the app.

brechtvb

@timecode sometimes I have the impression by opening the big graph or swapping the data in the display for other measurements, more data (complete) pops up, odd, and a bug in the end.

SamuelP

@timecode it happened me the first time a few weeks ago. I didnt wet the belt before my run. I guess the connection was good enough for HR but not the r-r data. After a while probably my sweat made the connection better or something?

isazi

@SamuelP indeed, if the data is too noisy it is not used for ZoneSense, data needs to be quite clean to be used.

timecode

@SamuelP good hint, thanks. I will try it again tomorrow and keep this in mind.

SamuelP

@isazi would be nice if suunto app could tell the quality of the data(like runalyze), would help with all the confusion

Brad_Olwin

@timecode If the HR belt dries and/or you have a tech shirt and dry belt it can cause problems. I thoroughly wet my belt before I run and I typically sweat enough that the belt stays wet. If you stop and dry out it could also be an issue.

timecode

@Brad_Olwin thanks. I also always wet the belt and sweat a lot, like A LOT. But it of course can happen that it dries out - today was quite cold, so it’s possible. I’ll try again tomorrow.

Brad_Olwin

@timecode said in Suunto ZoneSense:

@Brad_Olwin thanks. I also always wet the belt and sweat a lot, like A LOT. But it of course can happen that it dries out - today was quite cold, so it’s possible. I’ll try again tomorrow.

I rarely have loss of data from ZS but it has occurred. The last time this happened my belt battery was about done. I finally remembered to check it.

timecode

@Brad_Olwin just fyi, today I ran again with the HR strap and as you can see time spent in each zone on the watch is different as in the app. There’s again a gap at the end. I am sure it’s not an issue with the strap, it’s wet, fairly new and a brand new battery.

Brad_Olwin

@timecode the watch is real time and the app calculates from synced data. Those are very similar IMHO 30s ± for VO2M does not seem like much.
Don’t know about the end, perhaps R-R data is noisy from strap drying or static from tech shirt, don’t know. I have not seen this in my experience.

timecode

@Brad_Olwin ah ok, I thought data in watch == data in SA. Good to know, thanks. Will “investigate” further.

Stefano M64

The past week a made a short easy run (I’m not a runner) primarily to check if the VO2max estimation I got by walking (46.1-46.2) was similar to the one I would obtain by running. Since it resulted to be 45.5, the answer is yes, they are pretty close, ok.
The part on which I would like to have an opinion from someone more expert on the argument is relative to the ZoneSense: I walked for 10 minutes with a cadence of 55/60 then increased to about 70, the HR increased from about 100, to 150-160. For most of the time DDFA index was in the aerobic green zone, with two period in the yellow zone, which started at about 150 bpm the first time and at 160 the second time. Previously, I got 3 estimations of the aerobic threshold (134-136-137) while training at the gymn. For my age (61) the usual formula gives an HRmax of 159 pbm, another one I found (213-0.65*age) gives 173 pbm, from which I should have the aerobic threshold at about 134, in line with the previous estimation. So, I was quite surprised to see the transition from ZS green to yellow zones at 150 pbm or even at 160 pbm. By following this forum, I learned that HR zones based on age are just a vague indication, however I’m bit scared to be pushed to training to hard, what I want is just to keep fit (but I like to experiment and understand). Any comment is welcome!

GiPFELKiND

@Stefano-M64 i never would use zone sense as training indication or as reason to train harder as you feel. Go to an medical doctor and make a lactat running Test. There you got your right and personal heart rate and Training zones. Good Option here is to do this with Spiroergometrie system.