Software Version 4.00 & Display SW 2.10

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 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...

Is a safety stop even required from a maximum depth of 27'? You never got to 10m so the pressure never doubled and DCS would not be an issue.

I'm pretty sure my Perdix doesn't require a safety stop until I go deeper than 10m for at least a few minutes.

Is a safety stop even required from a maximum depth of 27'? You never got to 10m so the pressure never doubled and DCS would not be an issue.

I'm pretty sure my Perdix doesn't require a safety stop until I go deeper than 10m for at least a few minutes.

Does it matter? It worked on the previous software version. The answer to your question is no BUT when you’re teaching students, you teach them to get into a habit of doing a “precautionary safety stop” for all dives that don’t require a mandatory safety stop.

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...

The Descent Mk1 will not trigger a safety stop until the device reaches 35ft and the software update has not changed that feature.

I also have this problem, when jumpinh into water for a swim, the Mk1 starts a diving activity.
@Garmin-Heath: If a swim activity is started, then the Mk1 will not go into a diving activity when jumping into water even if the watch goes below 1,2 meters?
If so, does it have to be a swim activity to disable the watch from enter diving mode, or will any actvity do?

If you start any activity, such as swim, running…, it will disable the Descent from going into Dive Mode. So, if you swim under the water like you stated, it still will not start due to the depth.

The Descent Mk1 will not trigger a safety stop until the device reaches 35ft and the software update has not changed that feature.



If you start any activity, such as swim, running…, it will disable the Descent from going into Dive Mode. So, if you swim under the water like you stated, it still will not start due to the depth.

Heath, I’ve been diving in my local quarry since April where the max depth is 30’. My watch has always hit the 3 min, 15’ safety stop as I do that with students on Day #2 of their Training Dives. That also wouldn’t be “technically” correct as at least with NAUI, all dives less than 40’ are still considered 40’ dives under the NAUI dive tables...hence the practice of doing a “precautionary safety stop” at 15’ for 3 minutes.

Odie21 Due to some questions, I am going to email you directly so we can get this figured out.

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.

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)

Heath, I have sent you the requested file. I don't understand how it could be relevant as I get the error shown above even when the Descent Mk1 is not connected. In fact, the first time I got the error was without the device connected. Further, as shown by the other screen shot, when connected, my Mk1 syncs fine (and obviously connects to the servers) when it is connected.

Does it matter? It worked on the previous software version. The answer to your question is no BUT when you’re teaching students, you teach them to get into a habit of doing a “precautionary safety stop” for all dives that don’t require a mandatory safety stop.

As I already stated, my Shearwater Perdix will not ask for a safety stop unless you dive deeper than 10 metres. It appears all Shearwater dive computers since at least the Petrel work in this way.

My Oceanic Atom 3.0 will not ask for a safety stop unless you dive deeper than 9 metres. I suspect all other Oceanic dive computers behave in this way.

I looked online at manuals for Suunto, Mares and Scubapro dive computers and they all behave this way, i.e. no safety stop unless you dive deeper than 10 metres.

As Heath says, the Descent Mk1 also behaves in this way (even before the latest update).

There is absolutely nothing to stop your students from doing a "precautionary safety stop" even if their computer doesn't tell them to do one.