Fenix 6 Series - 17.73 Public Beta

Jeff_ODQA over 3 years ago

Hello Fenix 6 customers,

Our next beta version for the Fenix 6 series is now available!

Please ensure that you are downloading the correct beta software for your specific device.

Fenix 6s: www8.garmin.com/.../download_details.jsp
Fenix 6s Pro: www8.garmin.com/.../download_details.jsp
Fenix 6: www8.garmin.com/.../download_details.jsp
Fenix 6 Pro: www8.garmin.com/.../download_details.jsp
Fenix 6x Pro: www8.garmin.com/.../download_details.jsp

Instructions for installation are available below the change log on each of the above pages.

17.73 Change Log Notes:

Updated Battery Saver to automatically disable when device charged to at least 80%.
Fixed text truncation issues when calibrating altimeter or barometer for some languages.
Fixed crash when viewing Connect IQ apps in the widget list.

Current beta peripheral software version numbers below. New versions are indicated in red.

GPS: 5.30
Sensor Hub: 8.00
ANT/BLE/BT (Pro models): 6.11
ANT/BLE (non-Pro models): 2.11
Wi-Fi (Pro models only): 2.60

Please note, the beta updates released on these forums are not compatible for APAC region devices.

Please send all bug reports to [email protected], and indicate which model of the Fenix 6 Series you have in the subject line.

Top Replies

All Replies

0 6928399 over 3 years ago in reply to Jeff_ODQA

The pace and distance problem or something else, Jeff_ODQA

0 bluefish over 3 years ago in reply to AndersB

AndersB said:
I'm also wondering about what's happening with the Pace and Distance problems?

The too short distance comes from the FIT file.
The fenix 6 creates too short distances in the FIT file.

If you convert the FIT to a GPX, you will get the correct distance.
Really bad.

0 AndersB over 3 years ago in reply to bluefish

Yeah, I know. I have looked at those problems very much. Its algorithm problems.

0 Jeff_ODQA over 3 years ago in reply to 6928399

Responding to AndersB report regarding the Fenix 6X GPS version showing as 5.80 in the .zip file

0 Ɛpsilon over 3 years ago in reply to bluefish

Apologies both, as I'm just trying to understand.

Is this on the watch or when exporting them from GC? IE is what your saying that exporting a FIT from GC gives say distance 'x' but exporting to GPX gives "y" or is it the files actually on the watch?

0 AndersB over 3 years ago in reply to Ɛpsilon

The watch is using a "smart" algorithm which includes both GPS and the accelerometer to calculate Pace and Distance and records the data to the .FIT file. Often faulty. The watch also records the GPS semicircles (the GPS positions) to the .FIT file. And, when converting the file and use the GPS information (the semicircles) instead most of the distance problems are corrected. But, then its to late if you want correct data while training.

0 bluefish over 3 years ago in reply to Ɛpsilon

The watch shows a too short distance already during the run. This may also explain the poor pace.
When uploading the activity to Connect, Connect shows the same (too short) distance. If you then export a GPX file from Connect (e.g. save it on your computer) and import this GPX file back into Connect, you will get the correct distance.

0 6928399 over 3 years ago in reply to bluefish

Unfortunately not. Did that, got a few meters more distance but this has nearly no effect on pace. I was running a few roller-measured tracks, and might get a difference of 0:30min/km. Doing what you suggests only ads a few meters to the track and hence barely fixes the pace. What I see is that the problem is not linear. The first lap might have a modest deviation, the next might be more than twice that, and thus it builds up over time. Whenever I get anywhere near a single tree then the paces goes down big time, still goes down when I'm way past the tree and then finally comes up again. While I'm running a fairly constant pace.

0 Ɛpsilon over 3 years ago

Interesting.

I've just exported a 30.02KM run to GPX and it shows a distance of 30.1KM in GPX. The route I plotted was about 30.5KM but I admit I always overplot distance and then ensure I hot the target....

0 6928399 over 3 years ago in reply to bluefish

Plus what you suggest doesn't work with a Garmin Coach programme as that run won't be tied to the activity of the day anymore.And the GPX file seems to include no cadence data, but lots of odd artifacts. I downloaded two tracks and uploaded them again: both of them had odd spikes with a speed of over 200kmh and similar oddities.