This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Feedback for GPS 2.60

Hello,

Today I've updated GPS 2.60 on my FR945 (FW 3.30).

After a run, I noticed that the battery had dropped less than before the update of the GPS.
An activity is not very representative so I wanted to know if you notice the same thing on your side.

  • Nice looking track. What GPS settings? What country? What was the final distance recorded> How did that compare to the number of laps you ran?

  • It is run in Gouda, the Netherlands. 
    https://connect.garmin.com/modern/activity/4393599838

    prgram i ran was 800,1200, 1600, 1200, 800 meters with 200 mtr walking in between 

    Gps and Galileo. 

  • please make the run public :-) - i'm pretty curious having a closer look, but from your picture it tracked very well...

  • well, well- here's a snippet from the edge 530 beta fw: "Fixed an issue where GPS satellites were lost more often than they should be." my bet is that this will make to the 945 as well and potentially also sort some of the tracking / pace issues - as both devices share the same sony chipset. i

  • But interestingly it's on the Edge's side, not GPS chipset update? 

  • i think from a development perspective the architecture has been broken down into 2 layers - 1. gps core services, most probably a firmware written by sony and tweaked by garmin / polar or whoever is using the gps chipset 2. app layer that queries the gps chipset - and the improvement is done at this level - as said - just a guess - but as a developer myself, that how i suppose it is done.  the current change is done by garmin on the app level and what we'll get through the gps 2.50, 2.60 iterations is the fw supplied by sony. 

  • Yes, but as also an software developer (note, not embedded, nor gps), I would guess that tracking the satellites is done on the chipset firmware and they just report the location and some meta data from the chipset to the Garmin side. Then what normalization Garmin does to the data is done by them, but that code would not track the satellites itself.

    How the Garmin side would let the chipset lost satellites would be doing something with the chipset that causes it to do that. Some command that Garmin uses excessively for the Chipset and it makes something like that. Dunno.

    But is the implementation done either way, if that would be some problem that 945 is also having, it would great to get improvements as it's kind of annoying that your new device is less accurate than the old one :( 

  • That may explain my yesterdays track (the worst to date on some areas).

    After passing under a bridge, the track was all over the place for quite a long period. (Blue is the bridge - the most challenging place for gps - was tracked quite well , green my actual route after the bridge)

    https://connect.garmin.com/modern/activity/4428499007