Instinct - 18.10 Public Release Candidate

Hello Instinct customers,

Please read the instructions below to update the software for your Instinct device. We've made some changes to how we deliver beta updates for our customers, so this forum post is now the primary resource for reading the change log notes – they are not available on another webpage. We look forward to your feedback!

18.10 Change Log Notes (changes since 18.01):

  • Additional improvements to altimeter performance.

New Software versions listed are in red.

  • System Software18.10
  • BLE/ANT/SNS: 1.60 

Instructions for updating software:

  • Download the .zip folder containing the update HERE
  • Connect the watch to your computer.
  • Unzip and copy the included gupdate.gcd file to the Garmin folder on your watch.
  • Disconnect the watch from the computer and it will prompt you to update software.

For any issues that you encounter, please send an email to [email protected]. In your email please include the software version, and a detailed description of your issue, along with any steps to reproduce. Please note that you may not get a response to the email unless we need more information on the issue you report.

  • Not sure what exactly you are referring to. Are we speaking about the altimeter, or not?

    No, i refer to the way too high intensity minutes.

    see my post here : 

    https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/instinct-solar/288781/instinct-solar---16-91-public-beta#pifragment-1292=2 

  • see my first post here : 

    Could you post a link directly to your message? I am lazy to search it in 5 pages long thread.

  • I'm sorry, since the problem has been dragging on for over 6 months, I haven't written just one post. If you are interested, the link above will take you to other threads (posts) about it.

  • I'm sorry, since the problem has been dragging on for over 6 months, I haven't written just one post. If you are interested, the link above will take you to other threads (posts) about it.

    OK, I have looked up some of your posts, but there is too little concrete data in them to make any conclusions. If you can reproduce the problem, comparing the IMs on the Tactix vs Instinct, please create a separate thread for the topic, so that we do not spam it here, and post screenshots of the daily HR graph for both watches for the same day (https://connect.garmin.com/modern/daily-summary/2022-09-21/heartRate and https://connect.garmin.com/modern/daily-summary/2022-09-21/intensityMinutes - change the date in the URL, if needed)

  • OK, I have looked up some of your posts, but there is too little concrete data in them to make any conclusions. If you can reproduce the problem, comparing the IMs on the Tactix vs Instinct, please create a separate thread for the topic,

    Considering that I already posted data about this in the relevant FW threads over 6 months ago, which Garmin-Chris found so meaningful that he replied "Thank you for the excellent data", and confirmed to forward the problem to the development department, there is no need for another thread. Also other developers have confirmed months ago here in the forum to work on the problem. It's sad that this obviously doesn't happen, or that there is no feedback anymore.

    That was over 6 months ago:

  • Considering that I already posted data about this in the relevant FW threads over 6 months ago, which Garmin-Chris found so meaningful that he replied "Thank you for the excellent data", and confirmed to forward the problem to the development department, there is no need for another thread. Also other developers have confirmed months ago here in the forum to work on the problem. It's sad that this obviously doesn't happen, or that there is no feedback anymore.

    Maybe they simply did not find any problem, which is very well possible, because it does not seem to be any general issue, and personally, I did not see any excess IM's on my Instincts. If you post the requested data, I can very likely tell you whether there is really a problem, or whether there is an easy explanation for it.

    The data you posted so far, miss the principal that is needed for the analysis - the HR data for given day. At least I did not find any.

  • Maybe they simply did not find any problem, which is very well possible, because it does not seem to be any general issue

    So we don't have to discuss this further here. Once again : Garmin Chris has directed the problem to development over 6 months ago. After that, Luke and others have confirmed on demand that there are more reports about this, and the problem is being worked on (also to be seen in the linked threads).

    So far there has been no solution to this. Who knows, maybe it is difficult to solve. Can be anything. But then there should be feedback on this. But unfortunately this does not happen. This does not contribute to customer loyalty.

  • I am not going to argue. I am just offering a helping hand, but if you do not want to post the requested data, I cannot do anything for you.

  • That is very nice. But I am not new to Garmin. About 20 years in total. I use the watches since 2016 (fenix 3 hr). So I know at least how to wear these devices, and that a watch on the left arm, and a watch on the right arm worn at the same time, should not have different data with factor 5. It's just absurd when after a firmware update the Instinct suddenly records 5x as high intensity minutes as before and compared to the Tactx Delta and Tactix 7.

    Only development can help here. They just do not. That is why I have deactivated the activity tracker. That's why I rarely wear the Instinct anymore.

    Incidentally, I have no problem with the barometer / altimeter.

  • So I know at least how to wear these devices, and that a watch on the left arm, and a watch on the right arm worn at the same time, should not have different data with factor 5.

    I did not tell anything about the way you wear the watch. What matters for IMs, is the ratio of the immediate HR, and the avg 7 day Resting HR. So if there is different RHR on both watches (which is quite likely), the detected IM's may differ very significantly. Besides that, there are some other details and settings, that may play a role, but if you think you know better, just let it.