Mandatory Gas Time Alarm at beginning of the dive

[Nandodiver]

@l.sillsuunto Only did one diving ( sidemount with 2 x transmitters )

Neither the Nautic ou Nautic S gave me the Gas time alarm

[hhouter]

@Nandodiver Give it a few dives, all my budies have seen this alarm once or twice…You will get one also… It is something that needs to be fixed.

[MartinPadiPro]

@hhouter I use a metalsub flashlight
I send the logs to amilco Benelux and to Suunto.
They say to have a look. Friday I go diving again. Let’s see what is going to happen.

[MartinPadiPro]

@hhouter this needs to be fixed

[VoiGAS]

Yes, definitely a No-Go for a dive computer

[VoiGAS]

@MartinPadiPro Can you check the tank pressure in the app? Should be available as an overlay. It would be interesting if the pressure is reported wrong or the watch just went nuts

[hhouter]

@VoiGAS yes you can and I have checked… there is no dip in the pressure feed indicating a POD error. See first red notification at 33m, a gas time alarm. The pressure graph included. A good idea to overlay pressure a this doesn’t look like a POD issue but is leaning more to a sw bug calculating the mandatory gas time alarm at 5 min remaining in the tank

[MartinPadiPro]

@VoiGAS I checked it. Just when i got 195 stays there. It does not go crazy. I checked my gas time at the start that one is a bit nuts. 68 min then 4 5 6 7 back to 75. Normally i dive around 70 to 80 min with 200 bars 10 liters. But i hope Suunto comes with a update

[hhouter]

@MartinPadiPro @voigas Again I had the mandatory gas time alarm in the beginning of the dive. See included screenshots.

I had some initial issues getting the pressure on the display but that can be something that is non related… the tank was pressurized, i saw the pressure, but before my backroll I needed to check as pressure was “–”. But before he tank showed “201”. I’ve send the logs and an update of this case to Suunto support hoping they can find out what this causes. It is always during ascent and ofcourse correctly activated after a dive indicating the 5 Min alarm as is is supposed to do.

[MartinPadiPro]

@hhouter damn. I got a email from Suunto with standard answers. Check tank check pod i all did that. It is a wide problem under more Nautic users. Monday i go diving again if the problem is coming back i go send the data to Suunto and let you guys know

[MartinPadiPro]

MartinPadiPro said:

@hhouter damn. I got a email from Suunto with standard answers. Check tank check pod i all did that. It is a wide problem under more Nautic users. Monday i go diving again if the problem is coming back i go send the data to Suunto and let you guys know

Dear Martin,

Thank you for contacting Suunto Support and for sharing the detailed information about the issue you experienced during your dives.

We understand your concern, especially when the dive computer shows a low gas alarm despite having sufficient tank pressure. We will be happy to help you investigate this further.

When a Suunto dive computer triggers an unexpected low gas alarm or the Gas Time value resets despite having enough tank pressure, it is usually related to one of the following factors:

1. Tank Size Configuration

Gas time is calculated dynamically based on your current depth, tank pressure, and breathing rate (Surface Air Consumption / SAC).

Please check:

Go to Gases > Edit Gas

Confirm that the Tank Size (Volume) is correctly configured

If the tank size is incorrect or missing, the gas time calculation may become inaccurate.

2. Initial SAC Calculation Phase

During the first 5–10 minutes of a dive, the algorithm calculates your breathing rate. A higher breathing rate or sudden depth changes during descent may temporarily reduce the estimated gas time, which can trigger an alarm before the calculation stabilizes.

3. Gas Time / Pressure Alarm Settings

Please verify your alarm settings:

Go to Dive Settings > Alarms

Check your configured pressure and remaining gas time alarm thresholds

The default mandatory tank pressure alarm is set to 50 bar, but custom alarm values may affect when notifications appear.

4. Temporary Tank POD Signal Reconnection

If the wireless connection between the Tank POD and dive computer is interrupted temporarily, the pressure reading may briefly disappear and then update once the connection is restored. This recalculation can appear as a sudden reset of the Gas Time value.

Before your next dive, we recommend checking the following:

Connect both dive computers to the Suunto App and ensure they have the latest firmware installed.

Confirm the Tank POD is correctly paired and the pressure reading matches your mechanical pressure gauge before entering the water.

Ensure the Tank POD battery and connection are functioning correctly.

As a standard safety precaution, please continue relying on your mechanical pressure gauge if any wireless pressure readings appear inconsistent.

After your next dive, if the issue occurs again, please sync both devices with the Suunto App and provide us with:

Dive computer model(s)

Firmware version(s)

Approximate dive time when the alarm occurred

Any screenshots or dive logs available

We will review the information and assist you further.

Thank you for your cooperation.

Best regards,
Zack
Suunto Support Team

[MartinPadiPro]

https://photos.app.goo.gl/1o43GWsetjia3SfN9

https://photos.app.goo.gl/zhhZfuxBsEteLWo1A

This are mine screenshots

[hhouter]

@MartinPadiPro said:

During the first 5–10 minutes of a dive, the algorithm calculates your breathing rate. A higher breathing rate or sudden depth changes during descent may temporarily reduce the estimated gas time, which can trigger an alarm before the calculation stabilizes.

Interesting… but that is the issue with the full tank and in descent, this alarm in the beginning of the dive should never pop-up.

I have also submitted them the logs and model / Serial numbers etc… but didn’t hear back from them yet. The alarm in my last dive at 6m was not scary… the one I got at 33 meter was !!! I simply hope that I never get an alarm in the beginning of a dive which is relevant because now treat them all as irrelevant.

[hhouter]

@MartinPadiPro I have two buddies who also have a Nautic. This issue was seen by both, but they don’t bother to submit to Suunto. So it is definitively not a standalone problem…