Software update 2.55.46 (17th. August 2026)

[hhouter]

@gorhabb Good work Suunto to make the Nautic even better and provide more features to technical divers. Way back in November 2025, CCR was announced as a future feature so it is good to see it is catching up its promise.

Still missing as these were not promised;

1. Improved flexibility configurable field options
2. Both pressure and compass in one screen
3. 1/2 Field compass widget
4. Stop clear compass bearing after power save screen jumps in
5. Solve Mandatory Gas Time Alarm at start of dive
6. Clear and improve SAC calculation algorithm
7. Improve ascent alarm to allow deflator function without alarm.
8. Fix screensaver with time and %. Only uses top left screen area
9. Others will follow

[Ldive]

@hhouter
hello. I can’t wait to test the ccr mode in 10 days!
taking a quick look, the dive profiles seem to have disappeared…

[Hugues78fr]

@hhouter I would resume:
P1 — High Priority

1. Safety / ascent-rate alarms
   Improve the ascent-rate detection algorithm to eliminate false ascent-rate alerts caused by normal wrist/arm movements, particularly when raising an arm to operate or vent a drysuit.
2. Ergonomics / full screen customization
   Provide much greater flexibility in configurable fields and screen layouts, including:
   the ability to display Compass + Tank Pressure + Depth + TTS simultaneously;
   a ½-screen compass widget;
   greater freedom to select and position essential dive information.
3. Compass / bearing persistence
   Do not automatically clear the compass bearing when the power-save screen activates or when switching between screens. A manually selected bearing should remain active until the diver explicitly clears or changes it.
4. Technical diving — Runtime / Dive Plan
   Provide a true Runtime / Dive Plan that can be prepared before the dive and then executed and followed underwater, including:
   planned depth/time segments;
   ascent schedule;
   decompression stops;
   planned gas switches;
   comparison between planned and actual runtime.
   P2 — Medium Priority
5. Numerical ascent rate
   Provide a configurable numerical ascent-rate display in m/min or ft/min, making it much more useful for precise and controlled ascents.
6. Gas Time alarm
   Resolve the mandatory Gas Time alarm at the start of a dive and provide greater user control over whether and how this alarm is displayed.
7. SAC / RMV and gas-consumption analysis
   Clarify and improve the SAC calculation algorithm and provide much more advanced SAC/RMV monitoring and gas-consumption statistics, both during the dive and in post-dive analysis.
8. App / dive data
   Provide one or more of the following:
   significantly improved diving functionality within Suunto App;
   development of a dedicated Suunto Dive app;
   or open access/integration with Subsurface or other third-party diving software;
   with full access to the detailed dive data recorded by the Nautic.

[hhouter]

@Hugues78fr

[Nandodiver]

Keeping both computers on same side of the dive transmitter seems to improve the dropouts and alerts

The issue/bug is why 2 x computers connect to the same transmitter give us different air consumption

Even more weird the log of Nautic S dive dont show up in the suunto app/Mac, even after new pairing

[hhouter]

@Nandodiver For the SAC Calculation Suunto uses a very complex formula which includes a Compressibility / Temperature factor. See here: https://www.suunto.com/Support/Product-support/suunto_nautic/suunto_nautic/wireless-tank-pressure-support-/gas-consumption/. So it might be different from a calculations which does not take these variables into account.

I agree it is strange that the Nautic S and Nautic have different outcomes of SAC by using the same Tank / POD.

This weekend I will take my EON Core with me and do the same. I will report back…

[ccrhenrik]

How do you switch setpoint from low to high and vice versa? No shortcut och quick commando?

Why is there only two setpoints? No alternative or bailout setpoints.

[Migsey]

@hhouter Can one pod broadcast info to more than one computer at any given time?

[hhouter]

@Migsey Yes, the POD transmits a signal that is individually picked up by each computer which registered the POD and is within 1.5 m. I have done multiple dives with one POD and my 2 Computers Nautic and EON Core.

[Migsey]

@hhouter Excellent!

Shame I just sold my EON Core!

Today, during the first dive I did with the brand-new software, the SAC rate was nowhere to be seen — just dashes on the computer display and no data in the iOS app.

The POD was definitely sending data, as I could see the cylinder pressure being displayed correctly.

Looking through the documentation, I think I’ve found a way of downgrading to the previous software version, where at least everything related to diving was working reasonably well!

[hhouter]

@Migsey That is strange… you didn’t get the SAC Rate in the dive log? And you did see the tank pressure declining as SAC is calculated in the Nautic and doesn’t have anything to do with the POD other then tank pressure. I will dive tomorrow with both and implemented the SAC / consumption switch window… I will report back…

[Nandodiver]

@Migsey nothing to due with new firmware or old firmware.

I had no SAC calculation twice in old firmware versions (NAUTIC)
In latest firmware FW 2.55.46 happened on the first dive and in the following dives everything is normal… (NAUTIC)

[erik.eddn]

Hi,

Since my Nautic doesn’t run very smoothly—quite the opposite, actually :/—I always carry my EON Steel Black with me as well. The SAC deviation is significantly lower for me—I think that’s probably due to the variables used in the calculation and the time range covered—for example, yesterday:

10L, 41min, ~6.3m avg
Nautic (latest firmware): 18.9 l/min (start/end pressure 195 bar / 81 bar)
EON: 19.2 l/min (start/end pressure 195 bar / 79 bar)

Both are on the same tank pod, with the Nautic on the opposite side from the transmitter and the EON on the transmitter side/arm. For me, at least, it seems to be working as it “should”.

Of course, my own calculation differs from this (but that could just be due to the formula used—more detailed information would be helpful, of course):

Nautic: ((195 - 81) × 10) / (41 × 1.63) = ~17.1 L/min
EON: ((195 - 79) × 10) / (41 × 1.63) = ~17.4 l/min

[hhouter]

@erik.eddn you forget to take additional variables into account: Temperature and Pressure (Compressibility). See formula used by the Nautic here: https://www.suunto.com/Support/Product-support/suunto_nautic/suunto_nautic/wireless-tank-pressure-support-/gas-consumption/

[erik.eddn]

@hhouter That was the “more detailed” information—thank you very much. But what I also wanted to point out is that the discrepancies between my EON SB and the Nautic are pretty much negligible (or rather, they’re due to slightly different data/variables)—in stark contrast to the discrepancy with Nanodiver (Nautic/Nautic S).

[Nandodiver]

@erik.eddn

the Nautic on the opposite side from the transmitter

My advice is to run the Nautic on right wrist, the Antenna will be in line of sight with transmitter also on the right side…

Using the Nautic on left wrist the antenna will be face forward to the hand…

[erik.eddn]

@Nandodiver Hi, thanks. But I actually don’t have any connection issues at all, no matter which side I have it on. I actually had it on the side where the transmitter is, but since I’ve been having a lot of other problems and outages with the Nautic, I only carry it now to collect data or to somehow make errors reproducible for support (I don’t want to give up on it yet—I think the basic concept is great :)). On the “right” side, I now have my EON back as my primary computer.

[Nandodiver]

@erik.eddn what problems & outages ?

[hhouter]

@erik.eddn I did a dive with my EON Core and Nautic this weekend. And the SAC was identical. So if you are using the same setup (Single POD) it is strange you have different readings as I assume the formula Suunto uses is the same for both models (Not sure if the EON Steel /Black use the same FW as the EON Core…). Are you sure you are leveled during the dive as that is the only thing of what I can think of that can make slightly different readings.

You can upload the json files and ask Claude AI to look at the pressure and ventilation differences of both computers, maybe it will find the issue why the difference is significantly.

[erik.eddn]

@Nandodiver There are many minor software issues; sometimes the times are incorrect, or the GPS waypoints are strange. Here and there, a configuration setting is missing (though I’m not 100% sure if I had confirmed that setting) or a no-fly time of 40–50 hours after four very short and shallow dives. With the latest firmware version, there’s also the issue that in the German translation, the information and warning messages in the top-right corner are slightly offset to the far right, extending beyond the curve of the display—at least that’s what I think I observed over the weekend.

The biggest problem, however, is reliability; at least my Nautic reboots for no apparent reason, and I haven’t yet been able to observe or replicate a consistent pattern. If you look around a bit, though, I’m not the only one with this problem—on the other hand, there are apparently plenty of owners who don’t experience this behavior.

It does this on the surface, during or after a dive, regardless of settings, temperatures, environmental variables, dive mode, etc., at completely irregular intervals. Of course, this comes with the associated algorithm deviation. Since it resets all values to 0 after the reboot, it’s not even useful as a bottom timer anymore. The compass also needs to be recalibrated afterward, etc. In short: total failure.

Since then, I’ve been in contact with support; unfortunately, for a very long time, it felt like going in circles—always the same questions and requests for data / diag logs inkl timestamp etc etc, or requests that are no longer even possible (such as generating a link to the dives in the Suunto app—it simply doesn’t work on iOS anymore; there are only generated images to share—never mind, “pretty unsatisfying” sums it up quite well, unfortunately). In the meantime, we’ve managed to establish some communication via email; they first recommended that I perform a soft reset (which I’d already done several times on the boat) and, if that didn’t help, to perform a factory reset.

It did reboot once while I was reconfiguring it—but I hoped that might just be some kind of initialization process and ignored it. The weekend before last, I took it on four dives again, and it didn’t exhibit that behavior.
For me, though, that wasn’t enough testing time, so I hadn’t yet reported taht back to support. Last weekend, I did five more dives, and on the second dive, it started happening again—a reboot just before or after surfacing. Data gone, 0m -273C …

The only similarity I could find is that this behavior occurs after the first time I actively sync with the iOS app. In Egypt, I did that after the first dive when it was brand new, and here, after the first dive last weekend (I hadn’t synced it the weekend before that), it was the first sync after the factory reset.

Even though Suunto hasn’t considered this possibility yet, I’m really hoping it’s a hardware defect (and I think it is somehow) - it would be much much worse for me if these problems were somehow software-related - in that case, I think that would be the end of the story between me and the Nautic.

Basically, I actually think the Nautic and its overall concept are great - I haven’t given up on it yet
But of course, reliability is the be-all and end-all with this kind of device, and anyone who rolls out software in this state is, for me personally, definitely no longer a serious option. Depending on the type of dive, it’s just not fun anymore—redundancy or not.

Sorry for the long bla bla