@ or_watching: Should we use this thread also to make feature requests or only for bugs?
if only for bugs forget the next lines
Feature Request: Range alert on off course.
so the watch could inform you that you are off track...
@ or_watching: Should we use this thread also to make feature requests or only for bugs?
if only for bugs forget the next lines
Feature Request: Range alert on off course.
so the watch could inform you that you are off track...
I wrote a workaround script that fixes the GPX file. It requires knowledge of executing PERL scripts (and installing the necessary PERL libraries), though: https://forums.garmin.com/showthread...512#post148512
Last edited by shangrila73; September 29th, 2012 at 12:40.
(Warning: Do not try unless you really want to kill your Fenix)
I'm trying to get confirmation that anyone at all has connected to a Chirp device. In my tests, I can outright kill the Fenix in one shot if I turn on Chirp searching and pull the details from a Chirp. By kill, I mean, it won't turn on anymore nor respond in any way. I've reached out to Garmin, but given it's a Sunday - I'm curious if anyone else has successfully connected to a Chirp. If you haven't tried though, I wouldn't suggest now as the time to try yet.
Repro steps:
1) Enable Chirp search in the Geocaching Menu.
2) Have a Chirp nearby, perhaps one from your name tag - or just another (I have both).
3) Let the unit find the Chirp
4) It'll pull the Chirp details over, select 'Details'.
5) Unit shuts off immediately, doesn't turn back on again. Dead.
Thus far, two Fenix's, both dead - both 2.60.
It's easy if you are familiar with running scripts or programs from the command line?It's easy to install perl libraries in linux. It's slightly more difficult on a Mac (you need to install XCode first in order to install and build CPAN perl libraries). And I haven't run perl in Windows in ages, so I have no idea what's involved these days...
Ran with the fenix...
sat down to look at the Track details in the watch. Not there.
Looked at the FIT summary, it's there.
Checked the Save As... it's "GPX/FIT"
Back to to the track log... it's just not there. Plain and simple. No many how man times I scross through it.
On the PC, it's there to use in BC and GC.
FW 2.60
- Total distance recorded in FIT format is different from GPX format. In my test, FIT reported 42km while GPX reported 40km. When FIT format is import to other sites, e.g. Strava, 40km is reported, too. So I suspect the total distance calculated in FIT may be incorrect.
There are currently 1 users browsing this thread. (0 members and 1 guests)