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 - recommendation for datafields?

Original problem: The native fields for estimating a course finish are not very useful. For example, the ETA field is not based on e.g. the average speed of the current ride, but instead based on a fixed speed which is part of the course definition. Therefore, the prediction is mostly useless.

For quite some time i used the datafield „Distance Plus“ but apparently the developer is not working on it anymore (no response) and therefore the newer 840/540 devices are not part of the compatibility list: https://apps.garmin.com/en-US/apps/9136eae0-624e-4376-9b1f-3555bc29c544

I would appreciate any recommendation about alternatives. 

  • Since nobody replied, maybe i can modify the question: Did Garmin improve the native ETA datafield calculation and/or does somebody know how it's calculated?

    Maybe it's actually usable nowadays (i did not look into it for a few years).

  • This is not just a Edge 840 issue, I queried it for the Edge 830 that the Time to Destination and ETA is calculated wrong and could not find what it is calculated on.

    But, if you use an "App" from Connect IQ, it is calculated correctly to a "second" whether it uses average speed or current speed which I prefer.

    I never got an answer as to what the problem is, but I have learnt that Garmin will never reply if they do not have a clue what is wrong themselves or have an answer to the problem

  • Ok, so it seems the native field is still BS. I know of this connect IQ field which was updated to support Edge 840: https://apps.garmin.com/en-US/apps/5eaf1658-c951-47e0-96e1-99408f5ab4bb 


    The developer explained the current algorithm to me: "Time is calculated for 75% on your average speed and 25% on your current speed. If your current speed is 40% more than your average speed, I calculate 25% on your average speed and 75% current speed."

    For me, i would prefer it the other way around - more relying on average speed, less on curent speed (to have a more stable value).