Pool Mode

Yes, if there was a 10 sec delay after passing 1,5m (or 1,2 m as it is in the case of the Descent Mk1) would filter out when just jumping into a pool for a swim and not trigger dive mode.
But as it is today, the Descen Mk1 trigger dive mode immediately when it reaches 1,2 m, right?

Is 10 seconds long enough?

Is 10 seconds too long?

Here's what I would do if I was designing it:

Have a Start Dive Delay that is user configurable between 0 and 2 minutes. Perhaps: 0, 10s, 30s, 1 minute, 2 minutes.

As soon as the Mk1 descends below 1.2m it switches into dive mode (starts the timer, starts logging depth, temperature, NDL, etc.). If the Mk1 ascends above 1.2m before the Start Dive Delay ends, dive mode is cancelled and the logged information is discarded (but tissue loading should still be retained). Once the Start Dive Delay has passed, the Mk1 performs as it does now and any ascent above 1.2m is treated using the End Dive Delay processing.

The reason you want it to start immediately is so you don't lose the data from the start of the dive.

This should apply in all modes except if the watch is in pool mode or one of the Apnea modes.

Even if you put the Mk1 into dive mode already, it shouldn't keep the dive data until after the Start Dive Delay has passed. This would cover scenarios like: jumping off the back of the boat (or rocks on the shore) and going deeper than 1.2m but not actually starting the dive until all the group are ready; or duck diving from the surface to retrieves someone's lost mask.

One scenario that can't be handled is the person that puts the Mk1 into Apnea mode and then forgets to set it back before starting a dive, although a Start Dive Delay of 2 minutes might cover that so perhaps that's an alternative.

So my two cents on the Pool Mode after using it this weekend with a class I was teaching.
- You can toggle Pool Mode on and off manually
- If you do not turn off Pool Mode it ends automatically at midnight
- The Descent will still enter Dive Mode automatically if not other app is running
- Starting a timer, which sort of comes in handy on some of the skills, prevents the Descent from going into Dive Mode
- No dives were logged to Connect

All in all it resolves one issue. We could parse the fine details as to how we would do it differently all day, but does resolve the issues instructors ran into about having when working with classes. Some may be trying to stretch this into something it was not intended to be, I think most dive computers would start their dive mode automatically once you descended beneath the auto start depth. Is there some room to improve this, or course, but it is a feature that most dive computers do not have.

Great to get some experience on the pool mode.
Seems to me it is designed for instructors. But I guess that most of the customers of the Descent Mk1 are not instructors, but rather people like me who use the Mk1 diving fetures a few times per year on vacations. The rest of the time they use the watch on a day by day basis and other sports activities. As such I still would like to be able to turn the auto dive mode of during the 350 of the 365 days in a year, when I am not diving, and just activate it when on a diving trip. A bit like the wet mode on the Oceanic, so it does not go into dive mode when swiming during the summer season... Yes it is an improvement to have the pool mode, but it needs to be activated every day when on the beach during the summer. Or start an activity as before during every swim...
I am not complaining, it is fine. But it could be more conveniet for us more ”normal” users that do not dive every day.

I understand the concept of the “Pool Mode” because of the RN that you’re absorbing, even in a pool. What I don’t understand though is allowing another activity to run, thus overriding the Dive Mode to start.