-
• #22477
I've started using an armband HR - Polar OH1+. Far prefer it. Chest strap always used to either fall down slightly or if tight enough to not fall down then I'd notice it on longer runs.
-
• #22478
Double posting error
-
• #22479
To be fair I get some wacky readings on my chest hr too, they're by no means perfect. I do have an irregular heartbeat though.
-
• #22480
Yeah, I guess I just want a second set of data for comparison.
I did a decent effort 5km the other day - I was definitely going near my limit, but my HR average was 132, with a max of 150. Even on steady runs my HR sits around 165, never mind when I'm trying to go fast. Same goes for when I've been doing kettlebell workouts - checking my pulse has it over 160, but the watch will be reading 70-90.
It seems to work totally fine 95% of the time, but really vigorous activity seems to throw it off. -
• #22481
Ah cheers.
-
• #22482
My watch seems to have me at 185 BPM all the time when running. Even on easy efforts. Did see it at 210 the other day on a hard segment effort which I don't think is likely.
-
• #22483
No I'm just paranoid my HR data is basically made up!
-
• #22484
Yeah, I guess I just want a second set of data for comparison.
I've considered carrying my garmin cycle computer with me for just that reason - optical with watch and chest with cycle computer. Strava used to be an option for a comparison but they removed sensor support I think.
-
• #22485
Re: hr my polar chest is regularly hitting 230bpm spikes at moderate intensity, my decathlon Bluetooth strap via phone recording gives me a steadier (more reliable) trace I can review after the session. /csb
-
• #22486
Strava used to be an option for a comparison but they removed sensor support I think.
A few weeks ago I was in a bind when I wanted to turbo, but my kids had hid my Garmin and so I needed an app which would work with a powermeter. Downloaded the Wahoo app. You could give that a go - It's pretty good, nice and clean.
-
• #22487
Oh thanks. Before I got my watch I'd use this janky app called ipbike for spin classes but I'd bet wahoo is a lot more usable
-
• #22488
I've ranted before about this but in order of reliability:-
- Garmin chest strap (but this one pinches and rubs just below the pec which is really annoying/painful, previous one - same model - didn't)
- Polar OH1+ (still manges to do several minute long periods of consistently 30-40bpm down on reality before jumping up)
- Forerunner 935 wrist based HR (similar to Polar OH1+ but longer and more frequent - also nigh on useless for interval type running where there are big sudden changes in HR)
I tend to use my Garmin HR Tri chest strap unless the welt it causes is too painful and then it's the Polar OH1+. If I forget to keep that charged, or I just leave the house for a run without bringing an HRM then I'll fall back on the wrist based HR. (I can never be arsed to go back in to get an HRM as I'll be more likely to just bail on the run, especially if the weather is shit.)
[ Bought the Polar OH1+ for swimming (as can attach to the goggle strap meaning no HRM-Swim chest strap) but using it for running now too. Haven't had time, despite lockdown, to write the code to merge the HR trace from the OH1+ with the .fit swim file from my Forerunner 935. ]
- Garmin chest strap (but this one pinches and rubs just below the pec which is really annoying/painful, previous one - same model - didn't)
-
• #22490
245 for comparison. Dressed down with a NATO strap makes it look and feel a bit less rubbery running watch.
2 Attachments
-
• #22491
This looks really good!
-
• #22492
I have a Garmin forerunner 35 and it seemed to be recording just fine this evening. When I tried to sync it, lots of general data went across to garmin connect but not the actual run, and when I tried to upload it manually it said the file was corrupted. I think I had maxed out the memory on the watch as now only the last 2 days activities are saved, I've cleared all those and hopefully it won't happen again. Annoying but at least I didn't lose the data of a race or anything (that would have pissed me off no end).
-
• #22493
sometimes you can rescue an activity by shoving the broken .fit file through one of the tools at https://www.fitfiletools.com/#/top
I sometimes use the 'Corrupt Time Fixer' to resurrect something that GC tells me is corrupt. It sometimes strips off other data but I assume that's just some of the data that was broken.
FWIW I never delete activities from my 935 and rely on it to do its own management and cull the oldest ones if it starts to run out of space. In the two years I've been using it (665 activities) I've only got 4 that have _FIXED in the name in my archives. Likewise I'm lucky that none have been activities I really wouldn't want to have lost.
-
• #22494
I did my usual run but used Strava and Nike Run Club. Distance and average speeds are different on both. Strava makes it look like I ran further and faster, Nike went the other way.
-
• #22495
Went out to do some slow hill reps, 1km~ each way. Bit odd that my HR would stabilise at 165~ but then go all over. My cadence is pretty consistent at 165-167, which makes me wonder if it’s just picking that up instead.
1 Attachment
-
• #22496
I tried fixing it to no avail - when I looked at the file manually almost every row had an error. Bit weird really.
-
• #22497
delete the Nike app.
-
• #22498
Whats the stank factor like on that? I like the look but rubber is just so practical
-
• #22499
Strava uses moving time but has a generous cut off for what is "moving" and also doesn't interpret the data from most GPSes well at all. If there's any GPS dropout during the run (say for 5 seconds or so) Strava will claim that as stopped time despite there being cadence/HR/running-dynamics data there for that period and the subsequent GPS point appearing 15m down the road in line with running at 12kph for 5 seconds.
As for distance, that's just the whim of the GPS data and the smoothing algorithms that get applied. Again, Strava tends to be more generous and doesn't smooth things out as much. Others will get rid of obvious glitches (like suddenly moving 400 yards NE for a few seconds before instantly moving back - Strava counts it, others don't).
-
• #22500
Just gone through my runs for April, surprised to see I managed 131km. Shame my pace has dropped off a cliff - massively. Did 10km PB last weekend (for 2020) of 50:49 - really thought I was gunning it and thought I was closing in on 15km, but sadly not. Some way off my 39:46 - 3 years ago....
Any tips for increasing both speed and distance? I'm not doing as much HIIT in the gym, perferring instead bigger compound moves. Weight has remained fairly consistant, at a lardy 90kgs.
I might have one. Let me check.