Related

265 HR vertical Jump after about 10 minutes

gxgene1
13 days ago

I've had the 265 for less than a week and while I love the display and the esthetics of watch it may be going back.

I've done three gym activities, two treadmill shortish runs 3.25 and 4.5 miles and on both the HR at the start trends low in comparison to my Forerunner 245 and then somewhere in the general range around 10:00 minutes into the exercise takes a vertical leap into the area where I would consider it to be a historic norm as compared to the readings I get from my 245. On one of the days I did a long session on a stair climber after the tread mill run and it did not show the issue. Was it OK because it was changed to be a stair climbing activity instead of a treadmill run, or that it was the 2nd activity, I have no idea.

The frimware the watch came with is 19.18. I've hunted through the firmware change logs for releases since then and there is none that I find that mention this issue, though there seems to be a host of potential issues to introduce by doing the updates based on the forum.. 

I like the fluff that the 265 has vs the 245 but if it can't do HR right, that's a problem .

in the image below the red chart is the HR and the treadmill runs are the two outside images which look very similar and both show the vertical jump in HR.

The middle image is the stair climber done sequentially after the 1st treadmill run. The two dropouts in the stair climber were pauses to fuss with the equipment

  • 0 13 days ago

    So this is obviously not a new problem as today I found this "locked" for new comment thread.

    https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/388181/hr-stays-low-for-many-minutes-when-starting-an-exercise/1867651#1867651

    Your comment at the end of that thread is

    "Since we've released software version 21.19, I'd like you to test out a few more activities and create a new thread if you still see HR inaccuracies. Thank you!"

    Why the need to create a new thread? From my perspective, if folks do an update and report back in the original thread that the problem went away after an update that's a very useful chain for those of us with the problem to follow. It provides context and history about the problem.

    Above and beyond that, if the user reports that, while yes the HR issue was fixed but now my touch screen isn't working (for start/stop - that Garmin did on purpose), or my battery is draining at an alarming rate, or this exercise widget isn't working, we as users can make a better informed choice as whether to chance an update. 

    BTW, I'm not expecting my Garmin to provide medical grade readings for my heart rate, just a reliable, reasonable set of readings. I understand that the instantaneous response of the optical sensor is not as good as the chest strap but I had so many problems with drop outs and poor reliability from chest strap sensors that while the optical sensor of my 245 may miss some of the instantaneous peak values, it for me has been more reliable than the chest strap. I am certainly expecting the upgraded optical sensor of the 265 to provide at least as reliable data as my 245.

  • 0 12 days ago in reply to gxgene1

     I Took the 265 for it's 1st outdoor run today. Blissfully, thankfully the 265 did not wait for 10 minutes to start reading the right heart rate. It acted as would be expected, ramping up as I warmed up and then went more level. I did not do any of the funky things I had read elsewhere like wait 5 minutes after selecting the activity. I just selected run, the GPS acquired quickly and then it was out the door to start the run.

    This is a small sample size but if this only happens on indoor treadmill runs I'll live with it until Garmin gets a fix. Installing the fix, for what ever release that might come in, would be dependent on what other problems get reported with that release.

    The display on the 265 is so much easier to read during a run than the 245, the GPS seems more solid, and it has the barometric sensor.

    I'd throw in the graph if I could figure out how to get one into a reply message

  • 0 12 days ago in reply to gxgene1
    gxgene1 said:
    Why the need to create a new thread? From my perspective, if folks do an update and report back in the original thread that the problem went away after an update that's a very useful chain for those of us with the problem to follow. It provides context and history about the problem.

    You are 100% right!

    Garmin keeps closing HR topics in effort to hide this long-standing issue. Even their explanation does not make any sense - they closed thread about HR issues because new update was released although HR fix for particular issues discussed in the thread are not mentioned in the changelog of that software update. It is obvious that they are just trying to "clean up" bug report threads to make it look better. And they have done that before. 

  • 0 10 days ago in reply to gxgene1

     Sad to report than at 13:48 or 1.6 miles into a 10 mile run the Garmin jumped from a HR of 135 instantly to 155, so it's not limited to just indoor activities and it's not consistent in it's behavior and I don't know how the heck it is managing to present that inconsistency. The only difference between yesterday (where it worked OK) and today when it didn't, it probably took me a few more minutes to get out the door to start the run after selecting the activity and the GPS acquiring the signal.

    I'm no that's my job programmer but I have written enough code for a couple of process control systems that I have a reasonable idea of what goes into the effort (which is never as easy as someone who hasn't might think). But If the conditions are the same, the result of the code should be the same, or so I'd think. I guess maybe if you've put some kind of weird filter into the HR measurement that's reacting to something I'm not thinking about, like maybe the speed of the ramp of the HR? I don't really do a warm up, just start running but that is pretty consistent.

    What ever it is, it's a change from the 245 and it's very disappointing.

  • 0 10 days ago in reply to gxgene1

    This is obviously the same problem you logged and you mentioned it happened after you updated to 20.32, since I'm seeing the same problem at 19.18, I'm curious if you remember what version you were updating from where the HR worked OK?

    I'm also interested to know if updating to the latest software fixed the problem, that is of course if you decided to try the update. I'd ask in your thread but it's been closed by Garmin-Sierra.

  • 0 10 days ago in reply to gxgene1

    I was updating from 20.31 which was operating fine.  It was 20.32 that gave me these HR delay issues. I am now at 21.19 and so far so good.

    Weirdly the last run I did on 20.32 the issue was gone, then I updated to 21.19 and its still gone.  Not sure what to make of that, can other lower level software be updated in the background?  I'm specifically thinking the sensor hub, I'm currently on 32.24 and I don't know its update history to determine if that was indeed the issue.

  • 0 9 days ago in reply to 3809324

    The first outdoor run I did on the 265 did not show the problem but the 2nd run did, as did both of my treadmill runs. Since it's inconsistent, It would, at least from my viewpoint, be desirable get a few more in the bag before feeling really comfortable. 

  • 0 8 days ago

    You cannot depend on watch sensors these days for accurate HR, for me this watch is useful only for accurate GPS and battery backup. Thats it, never rely on their HR, get a hr strap from polar the H10, and make sure its connected before starting a workout.

  • 0 8 days ago in reply to Rohan Arora

    It's more about having a reasonable accuracy that at least lets you know what heart rate zone you are in rather than absolute precision accuracy.

    When spending £400+ on a watch that offers this as one of its core features, then it ought to be reasonably accurate without having to shell out more money on other expensive accessories.

  • 0 8 days ago in reply to 3809324

    I agree with you, the day I did my first run wearing 265 and then checked the forums, I knew I have bought a piece of crap when it comes to HR accuracy. Sadly, a friend bought it for me from overseas so I couldnt do much about it except getting an external HRM so that my workouts are not ruined.