Software update 2.55.46 (17th. August 2026)

Migsey

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.