End Dive Delay

There's a setting called End Dive Delay.

This is what the manual says: End Dive Delay: Allows you to set the length of time before the device ends and saves a dive after surfacing.

The idea makes sense as perhaps you surfaced mid dive and then descended again. The problem is it adds the time to the dive. Instead of the watch working out that the dive actually ended when the depth first got to zero, the dive is still going until the end of the delay time.

The default is a minute so that the profile data show a whole minute of 0 depths at the end of the dive. The exit coordinates are also recorded at the end of the minute so for my dive yesterday I was already walking back to the car!

Do any other dive computers do this? None of mine do.

0 atj777 over 6 years ago

This is how the watch should work, in my opinion...

As soon as the watch registers a depth of 0 it stops accumulating dive time, but continues to record all the data it has been recording. It should immediately start trying to get a GPS signal and as soon as it has a reliable signal record the GPS location.

Once the End Dive Delay (time since the first 0 depth reading) has been reached and the depth is still 0, the watch saves the dive based on the first 0 depth reading in the line of 0 depth readings and calculates all the averages (depth, temperature, etc.) based on all the readings from the start of the dive until the first 0 depth reading (that was only followed by 0 depth readings). It also records the first accurate GPS reading it took after the first 0 depth.

If the depth goes to 0 but then goes non-zero before the End Dive Delay, the dive is continuing and everything keeps recording, although the dive time should exclude any time at zero depth, and all the averages should also exclude any time at zero depth.

My dive time yesterday should have been recorded as 79:39 instead of 80:29. I suspect my averages are wrong, too.

0 Mark_H20 over 6 years ago

This is a known issues and Garmin says they are working on it, though no idea when this will be corrected

0 atj777 over 6 years ago

I've set it to 20 seconds for now which seems to work OK - but my dives are "longer" on the MK1 than my other computers/watches.

0 Mark_H20 over 6 years ago

The actual dive time during the dive seems to track very closely with my Shearwater Perdix, but Garmin adds the end of dive delay time into the dive time which will make it longer than pretty much any other dive computer. They claim this is a known issue and will be corrected, but so far I have seen little action to address the issues with the Descent.

0 Odie21 over 6 years ago

The actual dive time during the dive seems to track very closely with my Shearwater Perdix, but Garmin adds the end of dive delay time into the dive time which will make it longer than pretty much any other dive computer. They claim this is a known issue and will be corrected, but so far I have seen little action to address the issues with the Descent.

.

There are still a ton of issues yet no response/resolution from Garmin. Silence isn’t golden in this case.

Here’s something to chat about...let’s see who the first person to notice the issue (hint...my Residual Nitrogen is on the left side)...the DM’s and/Instructors should see this quickly.

ciq.forums.garmin.com/.../1329636.jpg

0 atj777 over 6 years ago

.
let’s see who the first person to notice the issue

The only issue I see is the photo is too small to see any detail... one of the most common issues in my day job.

0 Odie21 over 6 years ago

The only issue I see is the photo is too small to see any detail... one of the most common issues in my day job.

Yes, unfortunately the way the picture transferred over via Garmin destroyed the image quality.

That picture was taken on my 4th dive (same day with 3 hours). I had a very high amount of Residual Nitrogen from the previous dives and even at 31’ it showed —:—. Meanwhile, my standard console computer showed what my adjusted time based on my Nitrogen from previous dives. I should have “some” NDL at the depth I was at based on my previous dives. That IMO is a very bad issue.

0 atj777 over 6 years ago

For single dives the NDL on my Descent tracks very closely to the NDL on my Perdix (with the same conservatism). I have only done single dives so I can't comment on the second or third dive in a day.

0 Mark_H20 over 6 years ago

I am really not thrilled with the NDL implementation, and I get that Garmin has "dive professionals" assisting them with features and testing.

- NDL should NEVER be blank. Display Hours:Minutes, display 99:59, but display something
- NDL needs to change slowly and smoothly, not jump around quickly as it did recently on a 85 foot dive.

And for God's sake improve the tech support, it is atrocious right now.

0 atj777 over 6 years ago

I don't have a huge problem with it displaying --:-- to indicate it is greater than 99:59. It can't mean anything else and once you know it, you're set.

I do have a problem with screen real estate being wasted with seconds. None of my previous or current dive computers display the seconds component of the NDL. It is unnecessary detail and if the seconds are significant, you're too close to going into deco. It would be better to just display 3 digits of minutes.

NDL will change just as quickly as it changes. I don't see that as a fault of the watch. It is just showing the current NDL based on the current depth and pressure history. It will appear to jump more quickly because of the seconds but I see the NDL on all of my computers bounce around if my depth is changing. That's how it is mean to be.

Garmin Tech support is non-existent. Even basic support is terrible. I'm still waiting for them to get back to me after 2 weeks!

To contrast, I had a problem with the compass on my Shearwater Perdix AI. The calibration went out. I emailed them and Tech Support got back to me in under 24 hours.