• State Not Answered
  • Replies 17 replies
  • Subscribers 2 subscribers
  • Views 3948 views
  • Users 0 members are here
Options
Related

pace field not working in solar Instinct

ozzz
over 2 years ago

I have issue in my Instinct Solar that the Pace in data field doesn’t show any whether any activity used. I’m doing the normal way waiting to GPS ticked in to my watch before i do any activity but still pace data field don’t work. I also did reset the watch but it is still the same. The weird thing is the lap pace field is working and even when i sync my watch to Garmin connect will have pace details. Anyone knows to solve this?

  • 0 over 2 years ago in reply to ozzz

    I do not know about any source of the APAC firmware packages. There are no APAC betas, so it would be only possible if someone owning the APAC watch, copied the firmware from the watch before it was installed.

    If you could post links to another two activities, I could try to find out whether I can detect the APAC status, and when it changed (if it did). Please post a link to an old activity, when the pace was still all right, and another one to an activity where it was already wrong, but still with original firmware (not the one you installed manually).

    Also check whether the pace disappeared when the firmware version changed - the version is listed at each activity, so it is not too difficult.

  • 0 over 2 years ago in reply to trux

    this is the working activity in previous firmware. 

    https://connect.garmin.com/modern/activity/9954751911/share/1?lang=en&t=1668698805

    this is the not working activity (previous firmware):

    connect.garmin.com/.../1

  • 0 over 2 years ago in reply to ozzz

    Ah, that's interesting - the same firmware version at both of them! In that case the APAC/ROW firmware conflict seems improbable. I'll try whether I can see some clues in the JSON data, but it may take a while. 

  • 0 over 2 years ago in reply to ozzz

    OK, so I compared these two activities. I did not find any information about the APAC or ROW version in the data. However, I found some other problems - not sure whether you noticed them too:

    1. The oldest activity - although the pace is being recorded and shown correctly, there is no elevation data - 17m all along, without any deviation. At an 11km track, it normally never happens, even if the terrain is completely flat.

    2. The newer activity (same firmware) - elevation OK, and pace missing (as you know). Strangely though, despite the elevation profile being all right, the Stats show the Total Ascent and Total Descent 0 m. 
       
    3. The same activity is also completely missing the temperature data

    The missing temperature and zero total ascent/descent are also at the newest activity with the latest firmware.

    Since the change happened without changing the firmware version, I am afraid there is a serious issue with your watch - possibly a hardware problem. I am afraid you'll have to contact the Support and have your Instinct replaced.

    If the watch is no more under warranty, and Garmin does not offer you any good deal for a new watch, then you can try checking the storage for errors over the USB cable, with a flash drive repair tool. And you can also try downgrading the firmware including the sensor hub. Frankly told, I do not give it a lot of chance for success. I am sorry for the bad news.

  • 0 over 2 years ago in reply to trux

    thanks for checking this out. i’ve checked my older activities for the ascent data and it seems the elevation data was gone after the 18.10 upgrade happened. in 17.50, i still have these data.

  • 0 over 2 years ago in reply to ozzz

    Well, I do not have the time now to dig in the JSON data again - it is quite time-consuming, but looking at the screens, I see that besides no elevation changes, and zero total ascent/descent, there is a very high temperature, at the second activity. It shows 55°C the whole time. That's pretty hot, and you would feel it. More likely the sensor started to fail. And at the later activities, it was already completely disconnected.