Even though I have run seven times outdoors since my last LT reading with a 5X and a HRM-Tri I am not getting lactate threshold readings anymore. Connect says that I haven't any eligible data. I haven't changed anything as far as I know but have always had LT data. Can anyone help?
I've just done the LT test and got a read out which is one BPM less than that which was previously shown on the watch. Which makes me wonder even more why I haven't been able to get an updated LT reading since March.
Well why would the watch give you an update if the LT point hasn't changed? In other words it sounds like the results from the canned test were statistically indistinguishable from the previous reading back in March, so I'm not sure I would have expected the watch to post up an update since there was no material change (and maybe no change at all from the watch's firmware point of view.)
August through to November I had regular updates (weekly) during which the BPM didn't change at all, the pace changed by as little as 4 seconds, then December through to February the LT went a bit haywire and in March settled down again but since then I've not had any update where before I was getting weekly ones. I've never had to do the "LT Test" to get a readout before, but happy that I have one now.
I'm officially "out of purgatory" and since I have a properly-working strap it will be interesting to see if I get an update this week during my usual workout schedule.
The pattern you had is pretty-much the same one I had, and then my strap went haywire enough (and a new one stopped it instantly) that it's now established that was the cause of the haywire stuff. Whether the LT computation on the watch from activity (without doing an actual guided test) is also borked in 8.x I guess we'll see if I do (or don't) get an update over the next week or so. It was pretty-common for me to get one every week or so before it all went crazy.
Tough 5 mile run just completed, the LT update popped up after it was complete. The heart rate is ridiculously wrong but climbing (a lot) from the former ridiculously wrong value (which was 46!) so I assume it's integrating and will fix itself in the next few readings. Unfortunately I don't know of any way to clear that out of Connect.... The pace where it flagged it, however, is approximately correct.
So yeah, it was the strap, and it DID prevent getting LT readings -- and they DO work on V8 firmware.
I may be missing something (or not doing something) but I don't have a LT Reading at all. I have a 935 rather than Fenix but I believe they are very similar. I have had the watch 8 months - I haven't run the specific test but I do have my HR zones set reasonably realistically and have VO2 max regularly calculated. Do I regularly need to run near the top of zone 4 to get a value?
sorry for the dumb question (i am quite new to the whole measure thing), but why is there no lactate threshold measurement for (indoor) bike training? it seems as if lactate threshold on the fenix is for runners only...
as far as i understand, lactate threshold normally can be measured for biking as well (at least apps for indoor cycling with smart trainers can do this)?
If you have any sort of issue with the strap returning garbage data (e.g. double-count heart rate, etc) then it's odds-on that the strap is sending bad data often enough to screw up the LT computation.
I was unwilling to pin it there for quite a while since the problem showed up at the same time the 8.x firmware did, but ultimately bought a new strap and not only did the bad data immediately disappear (e.g. the double counting) but in addition as soon as I had served out my purgatory (I reset the watch so as to prevent bad data in it from being responsible as well) I got an LT update during a workout. The flagged heart rate is still wrong (don't let the watch update HR zones with it until it's right!) but strongly trending the right way (about halfway between the former bogus number and where I know it generally is) but the pace it posted up is pretty-much bang-on with my experience.
