Mandatory Gas Time Alarm at beginning of the dive

[Nandodiver]

@hhouter do you have the problem in :

Sunnto Tank POD (new version)

Or the

Suunto wireless tank pressure transmitter (old version)

[hhouter]

@Nandodiver I have the tank POD, i believe the transmitter only works with the older computers like Vyper and the D Range of dive watches.
I bought the POD in the beginning of this year and i’m not aware that there is a new version available.

[Nandodiver]

This morning i had 2 x Mandatory gas alarm with both dive computers connect to the same transmitter and completely diferent times

1x Nautic (right arm) (battery 45% )
1x Nautica S (left arm) (battery 18% )
1x transmitter on right side (backmount)

and from my findings i believe is related with bad communication between transmitter and dive computer

Ps: its the first time im using the configuration single gas tank, my normal configuration is multiple gas (even if both tanks are air ) Could be related or not with the alert/bad communication.

pps: this was the dive i had most dropouts (no idea why)

NAUTIC S

Mandatory gas alarm 7m26s
Air consumption 100L/Minute 7m31s
Dropouts time on Nautic S 8m41s + 9m.28s + 26m49s + 27m21s + 29.26s

Theres was some Dropouts that i didn’t record, not sure if was at same time has the Mandatoy gas alarm

NAUTIC

Mandatoy gas alarm 26m28s
Air consumption 100L/Minute 26m28s
Dropouts time on Nautic 9m19s + 26m43s + 27m20s + 29m24s.

[Nandodiver]

More prints

[Nandodiver]

more prints

[Nandodiver]

Here the Nautic S had dropout and i move the arm closer to the transmitter to re-connect

[Nandodiver]

here Nautic & Nautical S had dropout at same time, and i was able to check the air consumption in Nautic

[Nandodiver]

Another dropout Nautic & Nautical S

[Nandodiver]

The following air consumption is not making sense on the Nautic S
Tank 12 L x 197 bar = 2364 bar

start 197 Bar
end 43 Bar
154 Bar x 12L =1848
2.70 ATM x 44 minutes = 118

1848L / 118 =15,6L minute

[hhouter]

@Nandodiver This is why I think, the POD does not have anything to do with it, somewhere in the Ventilation and GasTime calculation as seen by @mikenizm something goes crazy, it is corrected after some time but this is a serious issue to be solved asap!!!

[Nandodiver]

@hhouter the air consumption is definitely a bug (starting new topic about it)

[hhouter]

@Nandodiver Correct, but might also be related to the Ventilation issue…

[l.sillsuunto]

Since Suunto still shows no meaningful response and reports of Nautic issues keep piling up, I have now reported the Nautic through the European product safety system as a potentially dangerous product.

Given the false mandatory gas-time alarms and other incorrect dive data, I think an independent safety review is overdue.

I’ll keep you updated.

[jozzz999]

@hhouter I had the same issue this morning on my Ocean. Freaked me out a bit. I was 17.5m down, shortly after starting the dive. Interestingly looking at my gas consumption graph in the app, it spiked through the roof momentarily when the Mandatory Gas Time alarm fired. Definitely a bug

[Nandodiver]

Since my latest findings, im starting to get a conclusion based on what I’ve observed (some of you might not be on the same opinion)

Nautic - No dropouts > No issues (air consumption or alerts)
Nautic - With dropouts > issues air consumption & alerts

Nautic S - No dropouts (sidemount ) NO ISSUES watch & transmitter are close by
Nautic S - with dropouts (backmount ) ISSUES since the watch is opposite side of transmitter

[Nandodiver]

So did 2 dives this morning (maximum depth 11m)

Nautic - new firmware 2.55.46
Nautic S - 2.54.12
transmiter on Right Side

Air consumption seems to be correct in Nautic & Nautic S

1st dive Nautic S had no dropouts or alerts (Left arm)
1st dive Nautic no droputs or alerts (right arm)

2st dive Nautic S no dropouts or alerts ( right arm)
2st dive Nautic no dropouts or alerts (right arm)

In more and more convinced the issues some people have are due transmitter bad connection with their computer, and is more noticeable at great depths

[Nandodiver]

One more dive without dropouts and the Time gas alarm is nowhere to be seen

My findings and observations for that Time gas alarm at beginning of the dive is due the dropouts and bad connection between dive computer and the transmitter…

Doing sidemount never had issues or bugs, with backmount i use both computers on the same wrist…

Even the air consumption was very similar in Nautic /Nautic S

[Nandodiver]

This tips comes from several dive computers manufactures to avoid Dropouts…

When a dive light causes a wireless tank transmitter to drop its signal or fail underwater, it is usually due to electromagnetic interference (EMI) or radio frequency interference (RFI) emitted by the light’s internal LED driver circuit, or a shared power drop if batteries are critically low.

TIPS

Increase Distance: Keep your primary dive light mounted on your Goodman handle or hand, well away from the tank transmitter on your first stage or the computer on your wrist.

Check Batteries: Swap or fully charge the batteries in both the dive light and the transmitter. Low voltage changes the operating frequency and output power of electronic circuits, making them much more susceptible to noise and drops.

Use a HP Hose Extension: Move the transmitter off the direct port of the first stage using a short high-pressure hose extension. This clears physical and electronic blind spots.

Upgrade Gear: Switch to a high-quality, name-brand dive light with certified electromagnetic compatibility (EMC) shielding, or service/replace an aging transmitter.

My dive lights usually are:
2x Divevolk LS50 ( video lights mounted on Gopro) away from transmitter.
1x Wurkkos LS05 ( torch bolt snap attached to Nautic Bungee cord)
1x Prozhaozhu ( strobe beacon bolt snap attached to Nautic Bungee cord)

Curious: coincidence or not, when i stop using cheap TDS DZENOT backup light the dropouts stop

[hhouter]

@jozzz999 I did a comparison of two similair dives with the Nautic different firmwares (Claude AI). Location, depth anf time are moreless the same.

Comparing the two logs (same device, firmware upgraded from 2.49.32 on Aug 9 to 2.55.46 on Aug 23):

Structure is the same — both nest Ventilation inside each Cylinders[] entry, mixed in with Pressure, on the gas-0 (main tank) samples. No schema change there.

But the logging pattern changed noticeably:

	Aug 9 (fw 2.49.32)	Aug 23 (fw 2.55.46)
Gas-0 samples	474	473
Both Pressure & Ventilation in same sample	465 (98%)	421 (89%)
Pressure logged, Ventilation null	5	42
Ventilation logged, Pressure null	4	10
Zero-ventilation readings	5	10
Value range (nonzero)	0.000137–0.000554	0.00014–0.000529

Key differences:

1. Co-logging dropped off. On the older firmware, pressure and ventilation were almost always reported together in the same sample. On the newer firmware, they’re split apart much more often — 52 samples (11%) carry only one of the two fields, versus 9 samples (2%) on the older version. The measurement range itself didn’t change, just how consistently both values land in the same record.

2. Twice as many zero-dropouts, despite nearly identical sample counts (474 vs 473). That suggests the newer firmware either drops more ventilation samples or is more prone to zero readings at depth.

3. Dropout clustering differs. Aug 9 has one back-to-back double-dropout (two zeros 2 seconds apart at 29 m — the deepest point of that dive). Aug 23 has no back-to-back zeros, but its 10 dropouts are spread more broadly across the whole dive, including two right at the surface near the start (depth ~1.2 m, where a zero reading is plausible rather than a fault).

Takeaway: the underlying ventilation calculation looks stable (same value range, same warm-up delay before the first reading appears), but the newer firmware is logging it less reliably alongside pressure and dropping to zero roughly twice as often — worth flagging as a possible regression if you’re tracking data completeness across firmware versions.

[hhouter]

This is the log comparison for the Nautic and the EON Core on the same dive this morning 23/08/2026 +/- 9 AM. I didn’t sync the EON Core before the dive, that explains the hour difference as last dive was in the winter.

NOTE:

• 1 Single POD (Left on my 1st Stage)
• Nautic (New Firmware) on my Left Arm
• EON Core on my right arm

That’s the real story here — these two logs are from two entirely different dive computers, not the same device on different dives. That changes what “logging accuracy” comparison actually means.

Device identification:

	09:01:45 file	08:01:49 file
Device	“Vaasa” (Suunto-style), SW 2.55.46	“EON Core”, SW 4.0.1131
Serial	254610001470	1953100087
Schema	Nested — Ventilation inside Cylinders[], alternating with Pressure	Flat — Ventilation as its own top-level sample field

Ventilation logging accuracy:

Metric	Vaasa (09:01)	EON Core (08:01)
Ventilation coverage	431/473 (91.1%)	422/446 (94.6%)
Pressure & Ventilation co-logged in same sample	89.0%	94.4%
Zero-value (likely dropout) readings	10 (2.3% of present)	0 (0.0%)
Sample interval consistency	0–10.2s (one 0.0s duplicate)	9.8–10.0s, very tight
Timestamp gaps >15s	0	0
Nonzero value range	0.000140–0.000529	0.000133–0.000555

Assessment:

• The EON Core log is more accurate/reliable: higher ventilation coverage, tighter and more consistent co-logging of pressure with ventilation, zero dropout events, and a cleaner sample cadence.
• The Vaasa log has real data-quality issues: 10 zero-ventilation dropouts mid-dive at depth (physiologically implausible), a lower field-coverage rate, and a stray 0.0-second duplicate timestamp — all consistent with the sensor/logging quirks flagged in the earlier Vaasa-only analyses.
• Both devices measure ventilation on the same order of magnitude and unit scale, so the underlying sensor readings are comparable — the difference is purely in how completely and cleanly each device logs the field, not in what it’s measuring.

Bottom line: if you’re trusting ventilation data for analysis, the EON Core’s log is the more accurate/complete of the two; the Vaasa log needs the dropout samples filtered or interpolated before use.