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

Target time calculation of a Strava route since FW 12.00 even more unrealistic

Hello everybody,

 since the current firmware 12.00 I notice the following:

 I have a route on Strava with 45.23 km and a time of 1: 31h.

 When I load the route onto the Edge with the Strava IQ app, the time shown under routes is the same, i.e. 1:31 h.

 When I mark the route with a star, it is automatically displayed in the Garmin Connect app under Courses and then synchronized. On the Edge, 1: 48h is then displayed under Courses.

 But when I start the navigation, the target time is 2:44 hours in both cases.

 I usually drive a speed 28 to 32.

 With the 11.10, the Edge expected about 25kmh, now only with version 12.00, 19.4kmh.

 What can I do? Are there any solutions?

  • It should be possible to change the average course speed (including the course set by Edge) from the device. Unfortunately, there is no such thing, so even if the speed of the course set in, for example Connect, is good, the speed set in the device is constant at 25 km / h. And that sucks. Too low on the road, too high on MTB.
    Workaround? There is probably no way around this by using the standard Edge fields. But you can use CIQ fields.

    I recommend Distance + where you can configure what data will be available, additional fields may appear on the automatically scrolling screen or after touching the screen.
    The following are available:
    On Full Width Field (3 fields in one field): Distance, Distance to Next, Distance to Distination, Time at Destination, Time of Day, Time to Destination, Estimated Total Time, Estimated Total Distance, Elapsed Time, Timer Time.

    These fields can be selected in any order to be displayed in each of the three panes (with 3 fields in each pane) that roll based on your timer values.
    It would be even better if the slope of the route left to be taken into account, but good and what is.
    On a 1/2 wide field, there are 2 fewer fields to select / change.

    A field should be added to a map field - it will provide the most important navigation information (up to 9 fields in 3 data windows).

    Or use the SPH Graph field - the bottom line can contain heading data that computes data based on your current speed. I recommend.