Delays in speed and pace makes it impossible to follow suggested sprint workout with Fenix 6X Pro Solar version 12.10 RC

I have posted some other threads about the delays in speed and pace on my Fenix 6X Pro Solar (software version is now 12.10 RC).

Today I tried to follow the suggested workout which was a Sprint workout called "3x3x0:[email protected]/h 55:00". Se picture:

The estimated benefit was like this:

I followed the instructions on the watch and ended up with this training effect result which I thought was strange... I noticed that the speedometer had really long delays while running.

  

I logged in to Garmin Connect on the web to look at the training and especially the pace diagram which shows targeted pace vs the watch pace. And there it is, the delays are there and mess up the interval training. The gray is targeted speed and the blue line is the pace that the watch shows. Several seconds delays. See this picture:

And if we look at the statistics for each interval we can see that the pace is totally wrong...

Garmin, please fix this...

  • My lactate threshold is automatically configured to 158 (by garmins guided lactate test) so im gaining anaerobic points below that.

    And also i have run with higher bpm than 158 without receiving anaerobic points.

    So the speed/pace is a very important factor for the garmin anaerobic points.

  • Based on my results in ~2 months its clear that my training helps very much. VO2 Max is now 50. Age still 45...

    But im also very interested in statistics, numbers and technical devices. When I look at the data in the .FIT files its very clear that something fishy happening. The numbers (especially those regarding speed and distance) are messed up. With bad data its hard to solve the problems related to that data.

  • First of all I thought that Training Effect was based on two metrics, time and HR, not speed/pace but I might be wrong... 

    speed/pace is not affected more than the effect of elevation differences (3D speed).

    Just to verify, you don't have 3D speed enabled, do you?

  • My lactate threshold is automatically configured to 158 (by garmins guided lactate test) so im gaining anaerobic points below that.

    But not enough points, this is why you complain. So, run faster and rise your HR above 158 and look what happens.

  • , the Anaerobic points for short sprints is not so much about HR values. I will show todays test results in a moment. Yes, I have 3D speed and distance enabled. Shouldn't I?

  • @subra, no, my original post in this thread was about delays in speed/pace which made the suggested workout impossible to follow. Then the thread went towards Training effect and Training load.

    I have done some more tests today and will soon show proof that high HR values is not necessary to gain the anaerobic points.

  • Yes, I have 3D speed and distance enabled. Shouldn't I?

    No. I've done some tests with it and it makes the precision worse. It will add at least one more parameter to the algorithm which also needs filtering to get rid of outliers and missing data. Unless you are running tracks with a lot of elevation the change in elevation will have a minor impact on distance (and speed).

  • This post does not have not so much with the original post of this thread (delay issues). Its more about the Anaerobic training effect points by shorter sprints vs heart rate.

    Today I ran/jogged 10,63 km in very slow pace (mostly pulse zone 2). I did two 15 seconds sprint intervals during this slow jog. Before the intervals I took a standing rest for ~3 minutes and after the intervals I took another short standing rest. The rests before the intervals was to get down the heart rate to pulse zone 1 before starting the intervals.

    I got Training effect "Base", 3.1 in Aerobic, 1.6 in Anaerobic and 109 in Load. Interval 1 gave 1.0 in anaerobic score and interval 2 gave 0.6 in anaerobic score. Total of 1.6 by doing these two intervals.

    Here is a screenshot of the pace with HR overlay for the complete run.

    Zoomed in on interval 1 (heart rate reached 153).

    Zoomed in on interval 2 (heart rate reached 148).

    Time in the different heart rate zones (no time in zone 5 as you can see).

    So, Anaerobic points can be achieved without having the heart rate in zone 5. 

  • @TobiasLj, hmm, interesting! That extra calculations needed for 3D Speed and distance shouldn't take much performance of the unit. My usual running tracks have rather much elevation (158 meters on a 10,63 km track for example) so I think that I always have those settings enabled. I can try to disable them and see what's happening with the delays.

    Can you explain some more about which kind of problem you had when it was enabled? Did you see unusual long delays etc?

  • That extra calculations needed for 3D Speed and distance shouldn't take much performance of the unit.
    My usual running tracks have rather much elevation (158 meters on a 10,63 km track for example)

    Pythagoras: SQRT(158**2 + 10630**2) = 10631.17m

    So the difference is 1,17m. What do you expect from 3D? OK, elevation gain and loss for a round course is 2*1,17m=2,34m