This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Power target change

KomivesG
over 3 years ago

Hi,

I use Edge 530 to control my Vortex, but i measure power with Assioma Duo. My problem is that if i have a workout interval for 5 minutes and 200 watts for example. beacuse of the Vortex is inaccurate the interval average canbe 195 or 200 too. On the Edge there is a lap average power field and i can adjust power target to make it close to the target 200 watts. And here comes my problem, if i got to change power target ( interval target is 200) it sometimes drop down to a previous and a so much lower target and it take too much time to push back from 140w to 200w.

So why i power target value is not the actual power targer value when i try to change it? After a few intervals it sometimes change to 200w, so i dont know what value Garmin is using, maybe the first interval, maybe the last interval target when i changed target.

Example workout.

5 min 100w

5 min 200 w ( i try to change target and it drops down to 100 w )

1 min 100 w

5min 200 w ( i try to change target and it drops down to 100 w )

5 min 100

It is a bug or is there any logic behind this?

  • 0 over 3 years ago

    Now  I am sure it is clearly a Garmin bug. I made a WO in Connect and problem is the same.

    Workout:

    1min 100w

    1min 150w

    1min 200w

    The result is totally the same, you can check the video, i changed the language to English so you can understand the layout on the Edge.
    I think the problem is with the Edge Target Power change menu, Garmin should fix that.
  • 0 over 3 years ago in reply to KomivesG

    530 has this problem for years. Looks like power target default value is from first step of whole WO or from first step of previous repeat.

    I have created fake very short 2-steps repeats right before important interval. Power default is so set to power of first step of this fake repeat, probably on high enough power.

  • 0 over 3 years ago in reply to RainoE

    Thanks for this, it makes sense. It was strange that sometimes it was high power durin "over unders", but i couldnt figure the logic behind that. I hope they will fix this and dont need this workaround.

  • 0 over 3 years ago

    Yeah, it's an annoying bug.

    520 plus did not have it , but is reproducible on 530.

  • 0 over 3 years ago

    I took and sent logs from my device to Garmin on February 8. Yesterday i tried to escalate it:

    Garmin answer:

    "With the information you last provided, we have already escalated this ticket to our engineering team. I have asked them to provide me with any updates, but if it is truly a bug, it is not one that has been widely reported.

    I am able to confirm that we are working on reproducing this issue internally."

    1. I reproduces it, provided logs. They didn't even reproduce it yet.

    2. "but if it is truly a bug, it is not one that has been widely reported." So it is a bug who cares? I was test engineer, it is very annoying behavior handling this way. Users made free testing for them and they dont want to correct it? It should be in the basic test cases and in regression testing.

    3. It can cause serious injuries also when 300 w drops to 67. Or 67 goes up to 350 in one second.

    4. A simple solution is: power target should only turn active when you confirm the changed value.

    This is a shame of Garmin. 

  • 0 over 3 years ago in reply to KomivesG

    "it is not one that has been widely reported."

    If you have the same issue please report to Garmin maybe they will correct it sometime: support.garmin.com/.../

  • +1 over 3 years ago in reply to KomivesG

    Got a new answer today:

    "Thanks for following up on this matter. I have received information from out engineering team that this issue will be specifically addressed in a software update, but I do not have a planned release date for this software update at this time."

  • +1 over 2 years ago

    In the latest Edge SW it is resolved, during written workout when i go into power target menu the target is always the actual interval target, so it works fine now.