Garmin Datarun Premium Fenix 5s Manuel - Page 7

Parcourez en ligne ou téléchargez le pdf Manuel pour {nom_de_la_catégorie} Garmin Datarun Premium Fenix 5s. Garmin Datarun Premium Fenix 5s 17 pages.

Remarks about the options

Altitude, elevation gain and elevation loss

Elevation gain and loss are Garmin's internal values that the watch calculates itself ànd come in feet

or meters depending on watch settings. Altitude is also in feet or meters depending on watch

settings.

These are not exact metrics! Garmin uses GPS for some devices for determining altitude, which is

definitely not precise, and a barometer. A barometer should be more precise, but in my experience it

is still not very good. On a really flat surface I see 30 meters of vertical gain after 500 meters...

Be sure to calibrate the barometer before you start a run (based on a known altitude); then you have

at least some precision for the altitude. The setting where the GPS is used to calibrate the barometer

at the start of an activity is the 2

forums (I always try to calibrate manually).

A nice read about the "truth" of elevation-data is available at the Runalyze website:

https://help.runalyze.com/en/latest/calculations/elevation.html

Race metrics

When you are in a race and striving for a certain finish time you need to be able to pace yourself. In

In my experience in the last part of a race, especially a marathon, it becomes harder to calculate your

estimated finish time or the pace required to meet a certain finish time. Therefore there are a few

possible metrics to help:

5. estimated finish time (in hours, minutes and seconds)

6. deviation from required finish time (in minutes and seconds)

7. required pace to meet a certain finish time

Also the colors green and red on the labels above or under the metrics indicate whether you are

within schedule, based on last lap pace or average pace, to be at the finish line at the required finish

time (only for FR645m, Fenix 5x, D2 Charlie/Delta and Fenix 5 plus series).

Depending of your way of racing ("flat" with almost no split, or with a significant split), you can

choose how the ETA-calculation is done; based on average pace of the pace of the last completed

lap. I expect that "based on elapsed time of the last lap" will work best for most people

When for the calculation of the estimated finish time (ETA) and for the deviation the pace from the

"last lap" is chosen, the values will be displayed after the first lap has been completed. If you have

autolap enabled in your profile-setting (for 1 mile or 1 km for instance), it will be visible after the first

mile or km. You can force it to update earlier by pressing the lap button and force a new lap.

When you have reached the required distance but choose to run on or haven't reached the finish

line, the ETA-time reverts to zero if it's based on last lap pace. The required pace disappears from the

screen. The "deviation" in time from the desired finish time stays alive however.

The distance of a race (for instance a marathon) can be entered alongside the desired finish time.

The ETA will be calculated for that distance. This needs to be in meters, or thousands of a mile. So for

the marathon in thousands of a mile the value must be 26219!

Be sure to use the right format (8 characters in total) for the desired finish time.

best option, is my conclusion based on discussions in the Garmin

M a n u a l D a t a r u n P r e m i u m , v e r s i o n 1 . 7 0

Pagina 7