GPSrChive Discussion Forum

So I mentioned it somewhere before here in this forum, that I noticed once, that the 66sr had a fast satellite fix even with expired CPE.bin file after the Firmware 5.70 update. I didn't test it further and I just forgot about that. I also thought it was just a fluke.

Since I don't have my 66sr anymore, but instead the 67, I observed the same behavior yesterday. This time I tested it several times and turned the device on and off. The Status of the CPE.bin file was "expired". I tested it when the file expired exactly on the same day.

The fix was almost immediately for gps, galileo, glonass and beidou. Although if I looked at the map, my location was off around 50m at the beginning, the cursor brought closer to my "true location" really fast. So that after around 30second it was at my location. Many satellites were flashing at the beginning, but after 5min it stopped. I did not record the exact time, I just looked again after 5min.

The status stayed "expired", even when I used it for hours, but I always moved around.

I also recorded several tracks, but I did not analyze on a pc. I can only tell, that on the device itself they looked accurate enough , whatever accurate means for 67 and nothing catastrophically.

So can somebody share their observation, maybe also with the 66sr?

Also I did notice, that for my previous 66sr and now for the 67 the cpe.bin file expires exactly after 144h so exactly after 6 days. Is this the case for anybody else here too? Since garmin wrote on their website, that the file expires after 2-14days, I thought it should be random, but it seems to be fix the time.

Since version 5.70 on the 66sr, no more problem saving the CPE.BIN file as soon as it is expired. It's transparent, we see it immediately because the symbol at the top left which indicates whether the satellites are acquired, between the moment when I turn it on and the moment when the symbol turns black after updating the file c' is very fast, I go to see the satellites, in fact they do not blink but appear one after the other as they are acquired, it takes about 30 seconds and the position is immediately exact on the map.

Can someone check how long it takes for 67 to fully load the satellites, without the current CPE.BIN file.

When there is no CPE.BIN file in the device, WiFi is disabled.

Przekątny wrote: Wed May 03, 2023 10:03 am Can someone check how long it takes for 67 to fully load the satellites, without the current CPE.BIN file.

When there is no CPE.BIN file in the device, WiFi is disabled.

With the current bug you have to be away from your wifi, because it will load the CPE.Bin file automatical, even if wifi is turned off.

Gadwin wrote: Wed May 03, 2023 10:14 am

Przekątny wrote: Wed May 03, 2023 10:03 am Can someone check how long it takes for 67 to fully load the satellites, without the current CPE.BIN file.

When there is no CPE.BIN file in the device, WiFi is disabled.

With the current bug you have to be away from your wifi, because it will load the CPE.Bin file automatical, even if wifi is turned off.

Sure, but you can not share the network from your smartphone.

The CPE.BIN file can be loaded with Garmin Explore and or Garmin Connect I guess like with the 66sr, if you don't have WiFi.

mimichris wrote: Wed May 03, 2023 11:51 am The CPE.BIN file can be loaded with Garmin Explore and or Garmin Connect I guess like with the 66sr, if you don't have WiFi.

This topic has nothing to do with the CPE.bin file. I am interested, if somebodyelse observes, that the satellite fix is as fast even with a expired CPE.bin file. Normally you had to wait several minutes and you got only GPS and after 15min you got galileo, when the CPE.bin file was "expired".

Now it seems to be the case, that CPE.bin file is kinda obsolete.

Descriptions of satellite orbits are valid for a long time, after starting the device acquires only corrections (ephemeris), which are valid for up to 4 hours, but during this time, the device creates future ephemeris on the basis of tables, so when restarting, even after a longer time than 4 hours, full acquisition of satellites takes a short time if done in the same area.

So when I tested it 2 days ago, I moved approx. 600km and started it again and still the fix was pretty fast.

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.