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.

0 Milosherman over 6 years ago

So when will the Mk1 be triggered for a safety stop? At 10.7 m (35 feet) as stated by Garmin? Does it?

0 atj777 over 6 years ago

So when will the Mk1 be triggered for a safety stop? At 10.7 m (35 feet) as stated by Garmin? Does it?

I have no reason to believe it won't, but I haven't done any specific dives to test.

My next deepest dive after today was 12.2m a few weeks ago and I definitely had the safety stop timer for that dive. All the divers deeper than this (other than the one below) also had the safety stop timer.

In fact, the only dive deeper than 12m where I didn't have a safety stop timer was when I briefly went into deco and then my slow ascent cleared that. This incorrect behaviour is listed as fixed in 4.00.

0 Milosherman over 6 years ago

I have no reason to believe it won't, but I haven't done any specific dives to test.

My next deepest dive after today was 12.2m a few weeks ago and I definitely had the safety stop timer for that dive. All the divers deeper than this (other than the one below) also had the safety stop timer.

In fact, the only dive deeper than 12m where I didn't have a safety stop timer was when I briefly went into deco and then my slow ascent cleared that. This incorrect behaviour is listed as fixed in 4.00.

Thanks. Yes I believe it will. Looking in my log the most shallow dive, going below 10 m, is 14,4 m and that one triggered a safety stop.
Would be interesting to see if the limit 11 m is enough...

0 atj777 over 6 years ago

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.

FFS! Support did it again today. I lost all my data from around 5:30am until I realised around 4:30pm today.

0 Garmin-Heath over 6 years ago

atj777, epront0, GNEWNZ and anyone else that experienced the message 'Sorry, we're having a problem communicating with our servers.' with Garmin Express.

Can you please run Garmin Express and let me know if you are still getting the error message?

0 atj777 over 6 years ago

I already had Express running and didn't have the error. I quit and restarted Express and when I went into Descent Mk1 with error was back!

0 rolfsg over 6 years ago

I had this problem on Monday and Tuesday this week, it only affected the MK1 but not my Edge1030. Since yesterday the connection problem is gone on both units.