Related
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

Edge 1030 Time to Destination / ETA at Destination totally wrong

Former Member
Former Member over 6 years ago
Hello, I do not understand why ETA at destination is totally wrong. I rode 100km on race bike, Time to destination indicated more than 10h! , thats to say 10km/h average speed! Do you have the same problem?
Yann
  • Former Member
    0 Former Member over 5 years ago

    I am having a similar problem, except the ETA appears to be calculated using an average speed of 25 km/h when my actual average speed is much lower than that.

  • 0 over 5 years ago

    When you create your course, do you set the pace field in Garmin Connect (website course editor). That is what sets the ETA usually and you may be running off a default value. You can set a target speed and the ETA will be calculated with it.

  • Former Member
    0 Former Member over 5 years ago in reply to Martin868

    I have done that, but I also have the problem when I just "Navigate" without creating a course.  So, I'm out and I decide to go some place.  I choose Navigate and select my destination.  The ETA calculations then assume 25 km/h and does not appear to use my actual average speed (always much lower than 25 km/h) in its calculations.

  • 0 over 5 years ago in reply to Former Member

    I don't think it ever used the average speed but always used the course speed, which might default to 25km/h. I might be mistaken. I always use ETA in conjunction with a course, not navigation.

  • 0 over 5 years ago

    i'll revive this old thread. I faced exactly this problem some days ago on a bike tour with an Edge 530.
    It seems the behavior didn't change at all in the meantime. I don't understand why this is not recalculated on the fly.
    Maybe there is an alternative, e.g. a connect IQ datafield which does reasonable ETA calculations?

  • 0 over 5 years ago in reply to Martin868

    great find. i'll check it out. Also i asked the developer if he could add time to destination as well. Then we could consider the matter as closed. Of course this could be made even fancier like taking into account wind direction or ascent/descent. But average is perfectly fine and more meaningful as the garmin version.

  • 0 over 4 years ago in reply to Heikoo

    Update: I was in contact with the developer and he modified the field "Distance +" to include time to destination and did some other minor improvements. 
    https://apps.garmin.com/en-US/apps/9136eae0-624e-4376-9b1f-3555bc29c544

    This field is a suitable replacement for the built-in-navigation metrics and is strictly based on average speed.
    Also, it can autoscroll between different metrics (distance, ETA etc.) so i don't need a dedicated page anymore for this stuff.

  • 0 over 4 years ago

    I have the same problem and you figure after 3 years it would be solved.  I'd prefer not add another IQ data screen because I'd like to limit the number of screens on my Edge and prefer to keep this info on my Map screen when navigating.  Obviously I don't need it if not navigating.  I already have SPH Graph - SPHGraWH that shows a better time to destination but it has other limitations.  I have no idea why my IQ app would provide a better time estimate than the imbedded Garmin data field.  I assume, but must be wrong, that the IQ app uses the Garmin data field.

    Also, I removed my speed and cadence sensor when I put a power meter on my bike.  The cadence from the power is ok but the speed is not accurate when Sat. signal is poor.  The average speed seems less effected by this.  I'm wondering is this could be part of my problem?  If so why is my IQ app working ok?