F5 Cycling seems borked

I seriously do not know where to begin here. 40k bike ride, 140 bpm average HR, 15.5mph avg, 77 cadence, 942 cals TE for both 1.8, status started the day in recovery (Load 394) Currently after ride..still in recovery load 394.

Used my HRM-TRI and speed and cadence sensor. Anyone else getting nonsense results from bike rides?
  • 40k at 15.5mph - is nonsense :D



    Sigh, so can I get a person that isn't so high on their horse to actually take a stab at this. When looking at app, it looks like it wasn't counting movement...



    And copy of the workout.

    https://connect.garmin.com/modern/activity/1787467794


    FYI The ride had elevation climbs near 1000 feet, but sure I should be cranking out 20-30-40mph uphill all the time.
  • FYI The ride had elevation climbs near 1000 feet,

    Then there might be something wrong with the altimeter on your watch. Looking at the elevation profile the course seems rather flat. Or do you perhaps mean total/accumulated ascent for the ride?
  • 40k bike ride, 140 bpm average HR, 15.5mph avg, 77 cadence, 942 cals TE for both 1.8, status


    Cadence, speed and HR all seem quite low so at first glance. What is your max HR to get an idea of how hard you were working? Also, are you using a speed sensor or relying on the GPS?

    Looking in more detail at the activity, the speed, elevation, and HR plots are quite erratic and surprising.

    For example, at 1hr in you start climbing a small hill which lasts until 1:13:00 and initially your HR is 159. You seem to stop half way up (at a left turn junction), and after you resume, your HR increases again for a short while. However, by the top of the hill your HR is below 110, which is very surprising.

    I would have expected your heart rate to at least stay steady, but actually rise as you climb the hill, and also for it to stabilise as the workload increases, but it gradually decreases and continues to be erratic so it seems like you were not working very hard. Was there was a lot of traffic slowing you down?
  • I seriously do not know where to begin here. 40k bike ride, 140 bpm average HR, 15.5mph avg, 77 cadence, 942 cals TE for both 1.8, status started the day in recovery (Load 394) Currently after ride..still in recovery load 394.

    Used my HRM-TRI and speed and cadence sensor. Anyone else getting nonsense results from bike rides?


    Not sure what your max heart rate is but avg 140 doesn't seem that high, 40k not that bug a ride, reflected in TE of just 1.8. How many rides do you do a week, maybe do this daily and you will see improvement in straining load and status... just guessing
  • Cadence, speed and HR all seem quite low so at first glance. What is your max HR to get an idea of how hard you were working? Also, are you using a speed sensor or relying on the GPS?

    Looking in more detail at the activity, the speed, elevation, and HR plots are quite erratic and surprising.

    For example, at 1hr in you start climbing a small hill which lasts until 1:13:00 and initially your HR is 159. You seem to stop half way up (at a left turn junction), and after you resume, your HR increases again for a short while. However, by the top of the hill your HR is below 110, which is very surprising.

    I would have expected your heart rate to at least stay steady, but actually rise as you climb the hill, and also for it to stabilise as the workload increases, but it gradually decreases and continues to be erratic so it seems like you were not working very hard. Was there was a lot of traffic slowing you down?


    Max HR for me is 185, which apparently I didn't hit but...

    After thinking about this, I honestly think the HRM-Tri had to be winking out. Other than the big drops (two towards the end of the ride around 1:15 and 1:25 which were me waiting to cross traffic and coming down a fairly large drop) it must have been cutting out not getting a measurement or the OHRM was turning on because the Strap wasn't connected. I didn't considered the Strap to be an issue because I use the same strap when running and BARELY ever get drop. The cadence and speed sensors also "Reconnected" at least once which I noticed during the ride. I have few things set to vibrate on the watch during a ride that there might been more disconnects? This was the first ride also that I used Normal GPS for the ride and not GPS-Glonass.

    Not sure what your max heart rate is but avg 140 doesn't seem that high, 40k not that bug a ride, reflected in TE of just 1.8. How many rides do you do a week, maybe do this daily and you will see improvement in straining load and status... just guessing
    See HR above and my reasonings above.


    So just a few things to answer the second part of your question first, I ride perhaps 1-2 week, but work out 5/days a week. When the weather is nice here, Cardio stuff for the week turns into runs and cycling. I'm not training for anything, just bettering my health. This was a recovery week for me: I only did work 3 days (2 runs and the bike ride). My load at the start of the week was 784 and was unproductive (which in the span of one day, became maintaining and then productive, only after midnight rolling back into maintaining. by thursday my load was 394 and said I was in recovery and as of this writing still says this). I would say this is quasi-right but the zero movement in the load triggered the questioning of the results.
    Work is work, even if it is below pushing your limits, I would have figured the watch would get that "hey, you just rode your bike for an hour and half." Intensity minutes were recorded, as were active cals so the watch knows I was working, the rest just doesn't make sense to me.