Software update 2.55.46 (17th. August 2026)
-
@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) -
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 -
@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/
-
@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). -
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…
-
@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.
-
@erik.eddn what problems & outages ?
-
@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.
-
@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
-
@hhouter Hey
I think the slight discrepancies in my case were because the Nautic measured a residual pressure of 81 bar and the Eon only 79 bar—at least that makes sense mathematically. I think the two just ended the dive slightly differently. Otherwise, the SAC is actually pretty much the same. In short: unlike the Nautic S and Nautic mentioned above, it seems to be working well for me (single-tank pod configuration). -
@erik.eddn if the Nautic reboots, return it asap for inspection / warranty. / replacement.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login