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

Software Version 4.00 & Display SW 2.10

Finally big upgrade, but unfortunately, still no FW 4.00 for my Descent MK1. At the moment I only got the Display SW upgrade (from 2.00) to 2.10!
Does anyone know what's new at 2.10?

About SW 4.00: extensive upgrade and the corrections of errors. Hardly wait for this upgrade especially because at the end of August I leave for one week diving in Egypt.
  • Former Member
    0 Former Member over 6 years ago
    Anyone else having trouble updating to version 4.0? Can't update mine as well. Also unable to save the 'allow private messaging' setting on this forum despite multiple tries using multiple web browsers - it'll just untick itself and revert to default settings whenever I load another page (even after saving). Any tips?
  • atj777 As we talked about in the past, due to the version of your watch, the software takes a little bit more time to develop due to the regional language demands. Though the message you are getting when you look for the software version wants me to keep looking into this more. Since you already know my email address, could you reply to our email chain with your GarminDevice.xml file? (Garmin Device -> Garmin Folder)

    Sir_Nomad49 Since you are experiencing this too, I’m going to send you an email to the email address that is attached to your display name. In that email, I will be asking for a copy of your Garmin folder so I can look at some of the files and also test it from my computer here like I am planning on doing with atj777’s device.


    Hello Heath,

    my watch updated fine. I just wanted to help and ask if atj777 was already able to update.

  • I was doing Training Dives today at a quarry and the safety stop time never started on the watch after diving at a max depth of 27’. I tried at 20’ & 15’. Nothing...


    I dived today and the maximum depth of the dive was 8.71m (which is around 28.7') and the safety stop timer on my Descent Mk1 never started.
    https://connect.garmin.com/modern/activity/2971014248

    I also had my Shearwater Perdix AI. The safety stop timer on it never started.

    I also had my Oceanic Atom 3.0. The safety stop timer on it never started.

    I asked my 2 buddies after the dive. The safety stop timer on their dive computers never started.

    It appears to be consistent behaviour for dive computers.
  • Former Member
    0 Former Member over 6 years ago
    I have the same problem, "Sorry, we're having a problem communicating with our servers." - I am unable to update via the mobile app (can't even figure out how to do this) - everything is synching just fine, and I've never had trouble with any of the previous updates. Running Garmin Express for mac 6.7.0.0. I have tried re-installing, restarting, a different internet connection etc etc... ciq.forums.garmin.com/.../1396013.png
  • I have the same problem, "Sorry, we're having a problem communicating with our servers." - I am unable to update via the mobile app (can't even figure out how to do this) - everything is synching just fine, and I've never had trouble with any of the previous updates. Running Garmin Express for mac 6.7.0.0. I have tried re-installing, restarting, a different internet connection etc etc...


    You wouldn't be based in Asia Pacific would you? Apparently, it is a region based problem that is being worked on at the moment.
  • Former Member
    0 Former Member over 6 years ago
    You wouldn't be based in Asia Pacific would you? Apparently, it is a region based problem that is being worked on at the moment.


    Sure am.... New Zealand.... Wish they would communicate that it's an issue somewhere, rather than a couple of the moderators in the Garmin express section being super aggressive about it being everyone else's fault....
  • Sure am.... New Zealand.... Wish they would communicate that it's an issue somewhere, rather than a couple of the moderators in the Garmin express section being super aggressive about it being everyone else's fault....


    I think they only just found out about it. I sent Heath a file from my Mk1 last night and he responded this morning that Garmin can now reproduce our problem.

    It's fairly typical of support organisations to blame the users until it is proven that it's a product fault. It shouldn't be that way but they all seem to operate like that.
  • ARGGGGGH!

    Now, it's even worse. I can't sync at all. Neither with Garmin Connect Mobile or Garmin Express. Neither of them report any errors but no data is being synced.
  • ARGGGGGH!

    Now, it's even worse. I can't sync at all. Neither with Garmin Connect Mobile or Garmin Express. Neither of them report any errors but no data is being synced.


    It appears that when support used the file from my Mk1 to test why I couldn't update my firmware, it broke the connection between my Mk1 and my Garmin account. My data was syncing somewhere else.

    I managed to fix it by removing the Mk1 from Garmin Connect Mobile and adding it back.
  • I dived again today. This time the maximum depth was 10.1m (33.3').
    https://connect.garmin.com/modern/activity/2973604162

    As expected, because I'd gone deeper than 9m for more than 1 minute, my Oceanic Atom 3.0 started the safety stop timer once I ascended to 5.5m.

    Neither the Descent Mk1 nor the Shearwater Perdix AI displayed any safety stop timer - again as expected.