This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

FR235 HRM and Sleep Data Comparison

Hi,

I have received my FR235 yesterday and am currently in the process of comparing its HR data and sleep data to other products I have been using so far.

HR: Compared vs Polar H7 chest strap recorded by Polar Beat iOS app. I am using mygpsfiles.com to compare.
Sleep data: Compared to iOS Sleep Cycle Alarm app.

I thought I might share this here in a thread.... so here you go :) I will add new comparison-results once I have completed them.


GPS Run 02 Dec 2015, Beta 3.13



Blue: FR235
Orange: H7

My first ever run with the FR235, I was trying different paces including walking to see how it would react. Over all I am satisfied with accuracy.
- at around 14:00 I slowed down for the first time and the FR235 lagged behind with dropping HR again.
- at 25:00 I did a sprint... the FR235 was suprisingly accurate with this one
- at 33:00 it was a little more inaccurate, maybe because at that point I was slowing down again
- From about 52:00 I was just sitting down... there the FR235 was jumping a lot more up and down than the H7
  • Cadence looks like the "old style" full cycle 0-100 type values - i.e. half the single foot ones now in use.

    The FIT file actually stores cadence in two fields - the full cycle field then a fractional 0 or 0.5 value. So the programs needs to add these together and then double the result.

    TCX I think outputs the full cycle values as it is quite an old protocol. Garmin started doing the single step values when the 620 came out and the HRM-Run could record odd or even values.




    Thanks. Someone in the GC forum suggested it would count "revolutions", guess thats why the units in the fit file says rpm instead of spm.

    I suppose the fraction of 0.5 means, the full cycle field value is only "half the truth", so I have to multiply by 2 which shouldn't be overly hard to do in excel ;) Just good to know it has to be handled that way!
  • Here is an extract of the updated chart from my previous run. As you can see we have cadence lock in action several times, actually every time i was climbing a hill and my HR increased...

    albeit I would't consider this a deal breaker and the longest one (in the beginning of the run) was something under 2 minutes. Maybe this could be important if one is doing intervals based on HR zones...


    Also interesting: why did my HR from the FR spike from 130 to 180 before I even started to run again (at the end of the graph, was having a chat with a friend I met).


  • Former Member
    0 Former Member over 9 years ago
    Here is an extract of the updated chart from my previous run. As you can see we have cadence lock in action several times, actually every time i was climbing a hill and my HR increased...

    albeit I would't consider this a deal breaker and the longest one (in the beginning of the run) was something under 2 minutes. Maybe this could be important if one is doing intervals based on HR zones...


    Also interesting: why did my HR from the FR spike from 130 to 180 before I even started to run again (at the end of the graph, was having a chat with a friend I met).




    I have noticed this as well just looking at the watch while running. When I start a climb my heart rate does not show a real increment until some seconds later, between 8-10 seconds, then it rises quickly and maintains what I think is the right HR. Maybe this is a consequence of the smart data recording, next time I go running I will check again with the "every second" mode.
  • I have noticed this as well just looking at the watch while running. When I start a climb my heart rate does not show a real increment until some seconds later, between 8-10 seconds, then it rises quickly and maintains what I think is the right HR. Maybe this is a consequence of the smart data recording, next time I go running I will check again with the "every second" mode.


    I have 1-sec recording enabled. And yours sounds more like a short cadence lock, or maybe rather an effect of the smoothing that is applied as it's very short. 8-10 seconds could just be the lag produced by the smoothing.

    You could also try to export your run and open it in excel (I exported TCX and then opened as xml in excel). Apparently you have to multiply the cadence with 2 and then you have a nice chart!
  • Here's another run... this time with some speedy intervals up some hills.

    As you can see in the steady beginning there was some cadence lock.

    On the speedy hill runs the result is mixed, sometimes the FR235 just seemed to lag behind, sometimes there seemed to be a cadence lock for a short time.

    nevertheless I am still happy with the result again. Overall the FR235 is tracking my run HR pretty well.








  • Former Member
    0 Former Member over 9 years ago
    Hello

    I wanting to compare my activities between the Optical heart rate monitor vs my Edge and chest strap, What are you using to create these comparisons?

    Many thanks
  • Hello

    I wanting to compare my activities between the Optical heart rate monitor vs my Edge and chest strap, What are you using to create these comparisons?

    Many thanks


    see here https://forums.garmin.com/showthread.php?336443-FR235-HRM-and-Sleep-Data-Comparison&p=774634#post774634
  • Another Run with 3.30/2.40.

    It's actually better than I preceived during the run. Cadence seemed to be a lot the same as HR whenever I looked at the watch, but in the analysis I can't see much of cadence lock. Maybe till 13:44 it was locked somehow... Otherwise the HR again is quite close to what my chest strap recorded.

    Still happy :)





  • Former Member
    0 Former Member over 9 years ago
    Yeah that looks great! My last run was similarly good, with the 235 flawless (both HR and GPS accuracy) and the 220+Mio combo actually struggling a bit. Usually both have some minor issues, but nothing i'm too worried about.