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

Vector 3 pedal data lag (20sec+) on 1040

Vector 3 data has a massive lag before displaying on screen. At least 20 secs to show increasing power / cadence and nearer 30 secs going down. Anyone else with this issue?

  • The averaging of values is as you correctly say just for the display.

    If you have time try the following. This maybe best done on a training.

    This is a lot to ask, but I think it would be the best way to get to the bottom of the problem.

    Put the 1, 3, and 30 second power data fields all on one way page so that you can see how they react. On the same page add the activity timer and cadence data fields.

    Video the following. Start the timer and start ride for 1 minute then coast until the power readings on all data fields are zero. Stop and save the activity.

    Send me PM and I will give you my email address and you can send me the activity file and the video.

  • Same here. Massive lag. What works (for a short time): if you go to the sensor page, deactivate the vector 3 and reactivate again works well. But just for a short time, then the lag is coming back unfortunately. 

  • I rode with a freind with Vector 3 + 1040 at the weekend and he was having no problems with lag at all. I can't verify his vector FW was up to date but the 1040 was running same as mine. Im still getting circa 30s lag on power and cadence readings. The later makes me think its not to do with 1, 3, 10, 30 sec avergaing as that doesnt average cadence. Literally I can start pedalling and 30 seconds later it starts to register... same when I stop pedaling... 30 secs before cadence gets to zero. If I pedal at a set cadence then suddenly stop... the readings shows the set cadence until 30 secs after I stop, when it the drops to zero. (I.e there is no slow averging out going on... it tracks fine just 30 secs adrift of reality.) 

  • What protocol are you paired to the pedals with ANT or BLE?

  • Sensor Information says ANT+

  • Same for me. Massive delay in the display of power data. Never had the problem with the 1030 (retired that 2 weeks ago) on same setup. Seems to help if I turn off the Garmin App on my phone while riding - not sure if they fight over the bluetooth connection or something...

  • SOLVED! OK I am not sure which of these solved the issue, but it has gone. Removed pedals from bike, removed batteries, let stand for a week (probabaly optional, but I was having a breif and torrid affir with speedplays), fit new batteries, fit pedals to bike.... and then from the Connect App on my phone (not Garmin head unit), I did a calibrate. It came up with some mad figure "-300" or something really out there. I just kept recalibrating from the app - and after five or six attepts, it suddenly started reading much more normal figures. Not sure what bit of all that did the trick... but 6 rides and 300km later... all is well and the delay has gone. :-) :-) :-) :-)

  • SOLVED - I had the same issue described above.

    what worked for me was:

    1. Remove the sensor from Edge 1040 (it got synchronized from my previous 830)

    2. Connect Vector 3 via Garmin app. Calibrate several times until showed consistently zero

    3. Add as new sensor to Edge 1040

    4. Calibrate from Edge 1040

    5. No more issues

  • Have the same issue, been frantically searching what the issue could be….? Thanks for this will try

  • Is it still working. I have the 30 second lag, so frustrating. Had did you connect from the app on the phone?