66sr/67 fast fix with expired CPE.bin file

[Gadwin]

If the device has current ephemeris, the time of full acquisition of satellites is counted in seconds,
after the expiration of ephemeris, in tens of seconds, when changing the area, the time may be longer,
it can be counted in minutes, not tens of minutes.

I wouldn't classify the automatic update of the CPE.bin file as a bug, I don't think Garmin will change it.

Ok, if I understood it correctly, the fix will be still pretty fast so long the CPE.bin is not expired for a long time. I guess, they fixed something like that with 5.70 on the 66sr, because even when the CPE.bin file was one hour expired, the time for first fix was really really long. Since firmware 5.70, what I only tested once, the fix was still pretty fast even with a fresh expired CPE.bin file.

[mimichris]

If the device has current ephemeris, the time of full acquisition of satellites is counted in seconds,
after the expiration of ephemeris, in tens of seconds, when changing the area, the time may be longer,
it can be counted in minutes, not tens of minutes.

I wouldn't classify the automatic update of the CPE.bin file as a bug, I don't think Garmin will change it.

Ok, if I understood it correctly, the fix will be still pretty fast so long the CPE.bin is not expired for a long time. I guess, they fixed something like that with 5.70 on the 66sr, because even when the CPE.bin file was one hour expired, the time for first fix was really really long. Since firmware 5.70, what I only tested once, the fix was still pretty fast even with a fresh expired CPE.bin file.

On the 66sr, the CPE.BIN file is updated even if not expired if you are connected to WiFi, I saw it, I had an unexpired file, I turned on the 66sr at home, the CPE updated, I connected the 66sr to the PC and saw that the CPE file had today's date. I hope the 67 works the same way. In any case it is much better than before version 5.70.

[Przekątny]

If the device has current ephemeris, the time of full acquisition of satellites is counted in seconds,
after the expiration of ephemeris, in tens of seconds, when changing the area, the time may be longer,
it can be counted in minutes, not tens of minutes.

I wouldn't classify the automatic update of the CPE.bin file as a bug, I don't think Garmin will change it.

Ok, if I understood it correctly, the fix will be still pretty fast so long the CPE.bin is not expired for a long time. I guess, they fixed something like that with 5.70 on the 66sr, ......

The device's memory includes clock synchronization, current and future ephemeris and an almanac (description of satellite orbits). The data is stored in the device even after the device is turned off, but the satellite constellation is constantly moving, after 20 minutes from turning off the clock synchronization becomes out of date, after 4 hours the ephemeris becomes out of date. An almanac is up to date the longest, an outdated almanac causes the longest wait for a full fix, so updating the CPE.bin file is important.