About the Track Run Auto Lap Distance

While the track length may be unusual, most training plans have intervals set up in terms of 100m/200m/800m etc. Pace and times are also commonly thought of in these standard terms

So autolap should really be set based on these common intervals, rather than the number of "circuits" of the track.

If you really are trying to count in terms of the number of circuits, you could set up a structured workout with a lap duration of 360m. Noting of course that as soon as you leave the inside lane, then track length is no longer 360m.

Thanks for your reply! Will try it out soon

Did 2 runs with 10 laps each (should be 3600 meters if the information is correct). 1 run with "Track run" and 1 run with ordinary "Run" activity. Did not notice any big differences.

With Track Run activity:

Without Track Run activity:

You gave me some sort of hope mentioning structured workouts, see https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series/244053/track-run---how-to-get-benefit-from-it/1388117#1388117

A workout step in meters gave me two digits, so the max is 99m, I can give 24 m, for example.

Choosing kilometers I could type many decimals, like 0.524 km, but in a second later GC rounded it as 0.52 km. It is illogical ( I mean the resolution of m vs that of km) and a sort of nightmare, it seems that with a Fenix  one cannot get non-comventional circuit statistics with native tools.

Anyway thanks for mentioning the workouts, it is not your fault

Maybe some insight. One of my circuits is appr. 733 m long, rectangle like, two sides are more or less flat, one is an ascent of 19-20 m, and evidently there is the same descent.

My own training and motivation is to either find and keep up a pace/power in a way that I can complete as much laps I can with the same lap time, or just want to be always a bit faster than in my previous lap while I am more and more tired. 

I found that even if I was concentrating on pushing the lap button, time by time I forgot it, so this is why I needed auto lap. But what the hell I can do with an increment of 50 m on a lap with a  vertical profile/trajectory which is far from even? The real lap/circuit and the measured laps would be totally different in terms of ascents covered.

As I wrote in the other thread I found non-native solutions, but still dont understand what Garmin benefits from this sort of restriction in the field of lap distances? Some data bits? Maybe a byte? These restrictions make users go for non-native datafields and apps, and at the end they find themselves somewhere where there are more uncertainties. Your watch crashes? CIQ! Battery drain? CIQ! etc.

I still love my Fenix 6x, just to confirm it, but dislike the combination of elimination the lap by position feature on watches since 910XT and the increment of 50m in lap by distance feature. It is a sort of own-goal made by Garmin.

Many years ago I had used with great success a data field named hLapMonitor, currently Auto Lap Monitor. Check it out in the Garmin IQ

Thx, I did not use it, but knew it.

As I wrote I found a non-native solution for me, namely Lap+, but I cant use it together with my other two run-related ciq datafields.