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

Time to destination wrong with 5.00 firmware

Time to destination always wrong with 5.00.

Since beta 4.22 the time to destination when following a course made with Strava is always too long : the time is almost double

Top Replies

PeatFaerie over 3 years ago +1

I have the same issue and I can confirm it started with 4.22.

The strange thing is, when the navigation is not running (not started or paused) then the estimations are fine - they are calculated based…

All Replies

0 potourneur over 3 years ago in reply to aweatherall

exactly the same behaviour with another course I did this morning: It is like the time to destination is multiplied by 2 and the average speed divided by 2

aweatherall : did you take a look at my file?

thanks

0 Johneed over 3 years ago

Yep correct was good until the last round of Betas now way too long but suddenly corrects towards the end of the ride.

0 aweatherall over 3 years ago in reply to Johneed

The file does not appear to be correctly posted

0 potourneur over 3 years ago in reply to aweatherall

6052.Vaux_de_Cernay_2..._course.zip

is it ok now ?

0 aweatherall over 3 years ago in reply to potourneur

Thanks I will take a look later today

0 potourneur over 3 years ago in reply to aweatherall

Always the same problem with another course : time to destination is doubled

0 potourneur over 3 years ago in reply to potourneur

I wrote to the beta team about this problem but no answer

Garmin Matthew : can you do something ?

It is a very annoying problem

0 mcinner1 over 3 years ago in reply to potourneur

I know this doesn't solve the basic problem, but if "time to dest" and "est. time arr." are very important to you, you can use CIQ HM's DIY for that. Here both values are calculated continuously (and correctly) via the av. speed.
If it is too complicated for you, I can create the two config strings for you. (In this case send me a PM)

0 potourneur over 3 years ago in reply to mcinner1

Thank you mcinner1 I wrote to you a PM