GPSMAP 66 Firmware 6.00
-
- Posts: 30
- Joined: Tue Aug 20, 2019 3:28 pm
Re: GPSMAP 66 Firmware 6.00
Hello,
your approach, Recording Menu - halt - discard, has also been my favourite work around. Worth metioning, I had Auto Calibration set to Continuous. I will alter the setting to Once instead. Anyway, this is a remedy. With clear vision of the sky GPS-altitude is suficiently accurate for calibration. GARMIN's documentation leaves quite a bit to be wanted for. Good things are worth waiting for ..... and come in tiny boxes.
Stay negative and safe
your approach, Recording Menu - halt - discard, has also been my favourite work around. Worth metioning, I had Auto Calibration set to Continuous. I will alter the setting to Once instead. Anyway, this is a remedy. With clear vision of the sky GPS-altitude is suficiently accurate for calibration. GARMIN's documentation leaves quite a bit to be wanted for. Good things are worth waiting for ..... and come in tiny boxes.
Stay negative and safe
- GPSrChive
- Site Admin
- Posts: 3952
- Joined: Fri Jan 20, 2017 11:29 pm
Re: GPSMAP 66 Firmware 6.00
Please see the post above by 987.
If you are certain of the elevation value for a given location, manually calibrate the device at that location and configure the 'Calibration = Once' option in the GPSr Altimeter Setup menu.
In the US, it is recommended to do this at a survey 'Benchmark' with a known elevation. I believe the UK have something similar called 'Trigs'.
-
- Posts: 65
- Joined: Thu Apr 04, 2019 9:35 am
Re: GPSMAP 66 Firmware 6.00
Yes you are right! In the UK the Ordnance Survey triangulation pillars are called trig points - short for trigonometrical points - see http://trigpointing.uk/wiki/Types
The list of trig points has given rise to the sport of trig-bagging, with the usual images and blogs!
-
- Posts: 7
- Joined: Fri Jan 01, 2021 9:12 pm
Re: GPSMAP 66 Firmware 6.00
I remember that with version 4.80 going to the satellite page (just going, and then back to map) would cause the baro nav to calibrate to GNSS having it set to continuously calibrate.
Now I'm running 6.00 and I can confirm (after a hike) that the feature does not work, even with significant height changes.
Let's hope Garmin fixes it!
Now I'm running 6.00 and I can confirm (after a hike) that the feature does not work, even with significant height changes.
Let's hope Garmin fixes it!
- GPSrChive
- Site Admin
- Posts: 3952
- Joined: Fri Jan 20, 2017 11:29 pm
Re: GPSMAP 66 Firmware 6.00
Is that a 'documented feature'? Can you share a source of the documentation if yes?Skinoku wrote: ↑Tue Jan 26, 2021 7:21 pm I remember that with version 4.80 going to the satellite page (just going, and then back to map) would cause the baro nav to calibrate to GNSS having it set to continuously calibrate.
Now I'm running 6.00 and I can confirm (after a hike) that the feature does not work, even with significant height changes.
Let's hope Garmin fixes it!
-
- Posts: 7
- Joined: Fri Jan 01, 2021 9:12 pm
Re: GPSMAP 66 Firmware 6.00
I dont think it is (was) a documented (or even desired) feature, I discovered it casually when using the 4.80.
I took advantage of it until updating to 6.00
Maybe some bug fixes modified software behavior and now the calibration routine is no longer invoked when switching to satellite page.
Anyway I feel SBAS acquire time is faster on new firmware.
In about 10 minutes or less after cold start EGNOS is operating.
I took advantage of it until updating to 6.00
Maybe some bug fixes modified software behavior and now the calibration routine is no longer invoked when switching to satellite page.
Anyway I feel SBAS acquire time is faster on new firmware.
In about 10 minutes or less after cold start EGNOS is operating.
- GPSrChive
- Site Admin
- Posts: 3952
- Joined: Fri Jan 20, 2017 11:29 pm
Re: GPSMAP 66 Firmware 6.00
Ahh, OK, thank you.
I thought maybe I missed this one!
Likely it was actually a bug that was corrected, but I may have to install an older firmware on a test unit for observation.
I thought maybe I missed this one!
Likely it was actually a bug that was corrected, but I may have to install an older firmware on a test unit for observation.
-
- Posts: 7
- Joined: Fri Jan 01, 2021 9:12 pm
Re: GPSMAP 66 Firmware 6.00
If you want to experiment, I was shifting to the satellite page (from map) via the quick menù by pressing PAGE or QUIT.
I do not remember if this happened also accessing the page via the normal menù.
- GPSrChive
- Site Admin
- Posts: 3952
- Joined: Fri Jan 20, 2017 11:29 pm
Re: GPSMAP 66 Firmware 6.00 [Bug 101]
Still Present in 9.60?masaki wrote: ↑Mon Dec 07, 2020 3:09 pmThe track point date would jump to the future at one point and then corrects itself. Here's an example:
When this happens, the incorrectly dated <trkpt> usually lasts for several seconds before correcting itself.GPX
<trkpt lat="xxx" lon="xxx"><ele>876.26</ele><time>2019-09-28T23:12:00Z</time><extensions><gpxtpx:TrackPointExtension><gpxtpx:atemp>20.1</gpxtpx:atemp></gpxtpx:TrackPointExtension></extensions></trkpt>
<trkpt lat="xxx" lon="xxx"><ele>876.19</ele><time>2019-09-28T23:12:01Z</time><extensions><gpxtpx:TrackPointExtension><gpxtpx:atemp>20.1</gpxtpx:atemp></gpxtpx:TrackPointExtension></extensions></trkpt>
<trkpt lat="xxx" lon="xxx"><ele>876.10</ele><time>2019-09-28T23:12:02Z</time><extensions><gpxtpx:TrackPointExtension><gpxtpx:atemp>20.1</gpxtpx:atemp></gpxtpx:TrackPointExtension></extensions></trkpt>
<trkpt lat="xxx" lon="xxx"><ele>875.95</ele><time>2019-09-28T23:12:03Z</time><extensions><gpxtpx:TrackPointExtension><gpxtpx:atemp>20.1</gpxtpx:atemp></gpxtpx:TrackPointExtension></extensions></trkpt>
<trkpt lat="xxx" lon="xxx"><ele>875.75</ele><time>2025-12-27T23:12:04Z</time><extensions><gpxtpx:TrackPointExtension><gpxtpx:atemp>20.1</gpxtpx:atemp></gpxtpx:TrackPointExtension></extensions></trkpt>
<trkpt lat="xxx" lon="xxx"><ele>875.38</ele><time>2025-12-27T23:12:06Z</time><extensions><gpxtpx:TrackPointExtension><gpxtpx:atemp>20.1</gpxtpx:atemp></gpxtpx:TrackPointExtension></extensions></trkpt>
<trkpt lat="xxx" lon="xxx"><ele>875.19</ele><time>2025-12-27T23:12:07Z</time><extensions><gpxtpx:TrackPointExtension><gpxtpx:atemp>20.1</gpxtpx:atemp></gpxtpx:TrackPointExtension></extensions></trkpt>
<trkpt lat="xxx" lon="xxx"><ele>874.99</ele><time>2025-12-27T23:12:08Z</time><extensions><gpxtpx:TrackPointExtension><gpxtpx:atemp>20.1</gpxtpx:atemp></gpxtpx:TrackPointExtension></extensions></trkpt>
<trkpt lat="xxx" lon="xxx"><ele>874.67</ele><time>2025-12-27T23:12:09Z</time><extensions><gpxtpx:TrackPointExtension><gpxtpx:atemp>20.1</gpxtpx:atemp></gpxtpx:TrackPointExtension></extensions></trkpt>
<trkpt lat="xxx" lon="xxx"><ele>874.51</ele><time>2019-09-28T23:12:10Z</time><extensions><gpxtpx:TrackPointExtension><gpxtpx:atemp>20.1</gpxtpx:atemp></gpxtpx:TrackPointExtension></extensions></trkpt>
According to Garmin Product Support, this was something they had never heard of in the email reply on 2019-08-15.
Correction: This issue actually started on 2019-08-12.
I last provided more details (data and requested files on 66s) on 2020-01-31 and have not heard from Garmin since.
- GPSrChive
- Site Admin
- Posts: 3952
- Joined: Fri Jan 20, 2017 11:29 pm
Re: GPSMAP 66 Firmware 6.00 [Bug 101]
Still present in 9.60?AndyJ wrote: ↑Fri Dec 04, 2020 8:54 pm I'll have to keep an eye on this... on my first longer bike ride after updating to 6.00, the date in the FIT recording suddenly jumped forward nearly 2 years for 2 points, and then went back to the correct date. It was only the date that was wrong; the time was actually correct. For example, here's the timestamps:
Fri, 04 Dec 2020 15:30:41 GMT
Fri, 04 Dec 2020 15:30:49 GMT
Fri, 21 Oct 2022 15:30:58 GMT
Fri, 21 Oct 2022 15:31:09 GMT
Fri, 04 Dec 2020 15:31:17 GMT