Some time ago, we bought an Edge 1030 as a replacement for our Edge 1000. After using it for a while, the GPS reception went bad. Before, the GPS track was always on the road, with a small deviation of at most 10 meters. Now we got a deviation of up to a few hundred meters and the GPS signal is lost very often. We always keep our Edge 1030 up to date with new firmware releases as they published.
After contact with the reseller, we swapped the Edge 1030 for a new one. But after a few days, the same happened. Frequently Lost GPS reception and a large deviation. So the Edge was swapped for the second time.
When we were riding last week, the same problem turned up again. We looked a little bit further: we studied the err_log.txt and found a few very alarming error messages, which indicate that there are internal software errors, of which one can directly be linked to a 10-minute long lost of GPS reception. This is the error message of line 255. We have also included a map, on which the track of the Edge 1030 is drawn in red, and the track of the GPSMap 62st, which we took with us, is drawn in blue. The mouse arrows indicates there the error of line 255 occurred. GPX files of both tracks are included.
We have also included err_log.txt, we found 6 error messages in it:
Line 2:
Unit 4294967295 = 0xFFFF, on 14-7-2018 (M-D-Y), the unit was not in our possession yet. Maybe at factory setup?
Line 36: Error message: "Data abort, system r0-15 + cpsr".
This suggests an internal software error. This occurred near to the end of a ride.
Line 109: Error message: "......TSKtsk_ntfctn.c 104, Can't destroy notification. List not empty. p_list = 0x0245ba6c, p_first = 0x01d9c0a0"
This suggests an internal software error, occurring at inter-process communication.
Line 161: Error message: "Semaphore already released, r0=task ID, r1=smphr, r2=rtrn"
This suggests an internal software error, occurring when using concurrent programming, with multiple simultaneous threads, where one of the threads made an error with releasing semaphores.
Line 255: Same error as in line 2. This time, this was during a ride. The minutes before and after this error, the GPS reception was lost or fluttering. At the moment of the error, there was GPS reception, which soon after the error was lost for about 10 minutes in the open field.
Line 289: Error message same as line 109. This was generated while the Edge was at home, not during a ride. Probably the Edge was connected Garmin Connect using an iPhone.
When we found this information, we think that firmware issues are the cause of our problems, and that the hardware may be OK. Swapping the Edge for a third time for a new one may not solve the problem. We have tried a lot of things to get better GPS reception, but nothing seems to help. We tried disabling bluetooth, disabling all sort of options that may cost processing power, setting GPS mode to GPS instead of GPS/GLONASS, and a lot more. Attached to the Edge are all the sensors from the Edge 1030 Bundle plus a set of Garmin Vector 3 pedals and a Shimano DI2 set.
For Garmin..
We ask you to investigate this and let us know in a short term what we should do. Is it indeed a firmware issue, or would it help to swap the Edge again? And when it is a firmware issue, when can we expect that it will be fixed?
Below we have included a list of the 3 devices we have had.
Greetings,
Marcel van Kooten Niekerk PhD
31-8-2018
Productnaam: EdgeÆ 1030
Serienummer: 576112310
Eenheid-id: 3975032280
28-08-2018
Productnaam: EdgeÆ 1030
Serienummer: 576119668
Eenheid-id: 3977008406
20-01-2018
Productnaam: EdgeÆ 1030
Serienummer: 576043608
Eenheid-id: 3956994221 ciq.forums.garmin.com/.../1405756.png
