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

ETA and Time to destination calculation is completely wrong since version 8.00

Uwe_DD
over 3 years ago

When I load a course with turn guidance on, then the calculated time to destination and the ETA always corresponds to an average speed of about 11-15 km/h. That doesn't change even after I've been driving for a while (with 25-28 km/h).

The courses were created with Garmin Connect and have an average speed set at 25 km/h and were downloaded to the device as .fit files.

With version 7.10 this definitely still worked as expected, i.e. the times corresponded approximately to the given average speed and were also adjusted to the real average speed while cycling.

Garmin, can you please fix this bug, the ETA calculation is a very important feature for me.

Uwe Höhna, Dresden, Germany

  • 0 over 3 years ago

    Never tested this with < 8.00, but on 8.00 and I also think 8.10 it's completely off. I once had ~15km left and the suggested left time was 9 minutes. Another time I had still some 38km, the suggested left time was nearly 5 hours. Really not sure how this ETA is calculated.

  • 0 over 3 years ago

    I wholeheartedly agree.  ETA has always been bad for me with the 830.  With the latest update it's moved to awful.  On a recent ride with a mile to go I believe it was telling me it would take 30 minutes.....and adjusted to something reasonable only right as the ride was about to end.  

  • 0 over 3 years ago

    Just a suggestion - try my IQ app Distance +  I have ETA and Time to destination based on your average speed.

  • 0 over 2 years ago

    Hello Uwe, 

    I have the same issue as you. My Garmin Edge 830 is now in v9.50. But I have get it for 2 years ans the ETA has never been correct.

    Did you get a feedback from Garmin about that point ? Do you have still the issue ?

    Christophe, Rennes, France

  • 0 over 2 years ago

    A short while ago I ran a similar thread in the 530 forum with no success at finding an answer for this problem.

    I cannot work out the logic Garmin is using to calculate timings.

    But if you use a 3rd part app from Connect IQ, they will give you the correct timings to a second.

    Basically, Edge devices using Garmin data fields are incapable of doing a simple time and distance calculation which is very poor for a device that is used for navigation.

  • 0 over 2 years ago

    I have the same problem with my edge explore 2 just updated 8.xx and it is showing the estimated time based on 0.15kPH rather than 20kph which was st when I created the course. Very annoying!

  • 0 over 1 year ago

    This is s shame. No reaction or fix from Garmin for several yeras. Next time I will use Wahoo