Related
Options

Very slow pace change in the recent runs.

micro
over 2 years ago

Hey, I did couple of VO2 interval sessions in the last few days, and in both of them the pace change was veeeery slow. Like 30 seconds to adjust from 6:55 to 4:30 per km. The other way around the same issue. Anyone with the similar observations?

  • 0 over 2 years ago in reply to Etupes25

    yes, but I also have my HRM pro connected, set to indoors. 
    Up till this weekend I did not have a problem with the pace adjustments. They were almost instant. Now, like I said, 20-30 seconds. Watch is sent to the highest accuracy setting. 

  • 0 over 2 years ago

    Same issue for me. Also with HRM Pro set to pace for indoors.

  • 0 over 2 years ago
    micro said:
    Like 30 seconds to adjust from 6:55 to 4:30 per km

    Do you use lap pace instead of instant pace?

  • 0 over 2 years ago in reply to subra

    I use both on my watch face. But regardless on what is presented on it, the result is the same. And thank you for assuming I do not see the difference between instant and avg pace ;)

  • 0 over 2 years ago in reply to micro
    micro said:
     I do not see the difference between instant and avg pace ;)

    The lap pace is the average pace of the lap so far and the instant pace is the current pace. Due to smoothing, e.g. using the moving average method, there is a delay.

    So, the lap pace is equal to the current pace for a few seconds at the beginning of the lap. After that, however, for nonconstant pace it should deviate.

    You run at a pace of 6:55 and accelerate to 4:30. Is your acceleration time included in the 30s delay or how do you measure the 30s delay?

     

    micro said:
    Up till this weekend I did not have a problem with the pace adjustments. They were almost instant. Now, like I said, 20-30 seconds. Watch is sent to the highest accuracy setting. 

    The question seems to be: "What changed just before this weekend that is causing the delay?"

  • 0 over 2 years ago in reply to subra

    Mate, that was sarcasm, I obviously know the difference. What changed? Good question. Nothing I can pinpoint right now. 

  • 0 over 2 years ago in reply to micro
    micro said:
    What changed? Good question. Nothing I can pinpoint right now. 

    Then sync with GC and try a factory reset.

  • 0 over 2 years ago in reply to subra

    What a brilliant idea. No, I won’t factory reset the watch for the x time in the recent time. This is clearly latest firmware problem, as maybe at the beginning of the rollout I did not do any intervals to spot this. 

  • +1 over 2 years ago

    I was intrigued by the potential issue as I have been evaluating the HRM pro for pace.

    I went out to test in 3 scenarios

    - SatIQ GPS + HRM Pro set to indoors

    - SatiQ GPS only (HRM Pro disconnected)

    - Stryd set for pace and distance always

    I found that in all cases the pace gets updated about every second: 7 different values over 8sec. of acceleration, and 4 different values over 5 sec. of acceleration: pace is indeed "real-time".

    So I was not able to reproduce the issue.

    I brushed up my video editing skills and produced the attached video (there is a lot of movement as I found it was not easy to accelerate while holding the watch "steady" and recording with the phone with the other hand :-)