Interesting question: For me (FR35) flatline was 97, and for that km 'lap' so was min/max/average
For me, as a Senior Systems Analyst, if this was happening in one of my systems, I would say there…
For me i is 100% watch as I see it whilst running - there am I, running up 1 km hill where HR should be 150+ but watch saying a steady 97 - I wish that were true!
HR seems to wear off, it was ok when a watch was new. Recently someone posted that cleaning the inside cable helped for HR of 235, but I haven't tested it yet. Seems possible, but probably I'll do it when something more happens with the watch which needs opening it, for now other things work fine.
A question for those of you who have this problem, and are using a model that records maximum heart rate for a run and possibly for each lap: How do the maximums stored in the watch compare with the flat line maximum?
Hey. My max is set at 193 bpm and my watch now flatlines at 155 bpm.
Interesting question: For me (FR35) flatline was 97, and for that km 'lap' so was min/max/average
For me, as a Senior Systems Analyst, if this was happening in one of my systems, I would say there is a logic loop issue.
The software would appear to be checking for a condition to be met, and until that condition is met it reports the previous 'good' reading - so it gets 'flatlined' at s specific value.
When this mysterious condition is met, things start again.
That's just my diagnosis based on many years trouble shooting software.
Thanks.
The reply from 3481042 supports the hypothesis the problem is in the watch, not the Garmin Connect app.
I was wondering if the problem was in the watch or in Connect because I discovered this thread when browsing the following:
Apps & Software Mobile Apps & Web Garmin Connect Web.