Related
Options

Today’s suggestion on run is not using foot pod for pace

Palleplutt
over 3 years ago

tested on 17.74 but suspected all time since today’s suggestion was implemented.

today I made a video showing that on “T.S.” screen pace was - -:- - but when I changed to another page/screen it shows pace.

 I made this video sitting on my porch with the shoe with the FP on in my hand banging it in the porch ;) 

watch on other wrist with GPS and the phone between my knees.

  • 0 over 3 years ago

    video is made with iPhone so maybe there is a codec issue to view on other devices.

  • 0 over 3 years ago

    I can't access your video, but suffice to say that sitting on you porch banging your shoe in not a reasonable replica of real world running conditions.

    I'm pretty sure that the workout screens display lap average pace (even before TS), not instantaneous pace.

  • 0 over 3 years ago in reply to mcalista
    mcalista said:
    I'm pretty sure that the workout screens display lap average pace (even before TS), not instantaneous pace.

    This is correct. And average pace is always based on GPS (unless indoors).

  • 0 over 3 years ago in reply to mcalista

    Can you please explain why do you think that is correct?

    If I change “target type” to heart rate instead it showing my current heart rate not an average. 

    But heart rate is not working great when workout is intervals. 

    And todays suggestion is sprint intervals of 10 seconds and then an average pace is not working well either.

    so I need the watch to show me the pace I have right now, and Fenix is capable to do that in “normal” running with foot pod as an pace source so why should it not do that in “today’s suggestion” screen or any other workouts?

    when I do today’s suggestion in bike with a power meter connected I get momentarily power not an average (maybe smoothed 3sec)

    So why shall running workouts with pace target be different?

    You are correct my test is not replicating a normal situation it was done to clearly showing that when watch is stationary = GPS speed 0 it shows 0 speed despite that I have a foot pod giving speed that is known to give more precise momentarily speed than GPS. 

  • 0 over 3 years ago in reply to tmk2
    tmk2 said:
    And average pace is always based on GPS (unless indoors).

    I think that the correct is to say that average pace is based on elapsed distance vs elapsed time. If FP is used for distance that will be used.

    But you are right that average pace is not the average of all speed readings during the elapsed time.

  • 0 over 3 years ago in reply to TobiasLj
    Palleplutt said:
    Can you please explain why do you think that is correct?

    What I meant is that mcalista's statement about average pace is correct.

  • 0 over 3 years ago in reply to Palleplutt

    A foot pod should not give pace if you are banging the shoe up and down. If it does, it is nothing more than a step counter.

  • 0 over 3 years ago in reply to broyson

    It’s not the “banging that gives speed it’s the movement that affects the G-sensor that gives speed. 

    But the banging helps in my simulation because foot pod also uses the time a foot is stationary when in contact with ground during running.

    but I can repeat my test with same result without banging my shoe just move it back and forth but it is hard to “deliver the message” that I’m doing that out of picture therefore I used banging to deliver information via sound instead.

    but this is off topic, more like how a foot pod technology works 

  • 0 over 3 years ago in reply to tmk2

    tmk2 yes I thought that you did answer mcalista.

    My answer/question was directed to mcalista.

  • 0 over 3 years ago in reply to Palleplutt

    It measures the distance between two steps. At least, that is what Stryd does.