Suunto Nautic - will it be supported?

[Dietmar Flubacher]

Dear all,

my EON core just crashed and cannot be repaired. I am thinking about getting a Suunto Nautic. Are you planning to support it and if so, any idea when this will happen? Please don't misunderstand, just asking - I am VERY pleased with the work you all do

Dietmar

[Linus Torvalds]

On Sat, 29 Nov 2025 at 09:18, 'Dietmar Flubacher' via Subsurface
Divelog <subsurfac...@googlegroups.com> wrote:
>
> my EON core just crashed and cannot be repaired. I am thinking about getting a Suunto Nautic.
> Are you planning to support it and if so, any idea when this will happen?

The newer Suunto dive computers seem to all be based on the "sync with
Suunto cloud using the Suunto App only" model.

So I *assume* the Suunto Nautic is basically going to work the same
way as the Suunto Ocean: it will only sync to the Suunto App, and then
you can download a FIT file, and import that into subsurface.

And honestly, I have the Suunto Ocean somewhere, and I never use it,
because it was so flaky. It randomly simply didn't sync some dives at
all.

I had about a 10% failure rate, where one dive randomly would never
show up after the sync, even when other dives the same day did.

And I'm not talking about "randomly didn't sync into subsurface". I am
talking about the Suunto App itself randomly not seeing all the dives
that I could see on the dive computer itself, and no way to make it
sync properly, because it was all "automatic" and done for you.

Automatic but unreliable is not good.

In other words - as a Finn, I'm very sad to say that I cannot
recommend Suunto dive computers. They used to be really solid things
(although some of them were *much* too conservative in some
situations).

My reaction to the Suunto Ocean was "this is a running watch that
tries to do scuba diving instead".

Maybe that Nautic is better. Maybe Suunto has fixed the flaky sync
issue. I wouldn't know.

And if it does work, we *can* already import the FIT files in the
desktop app, but it's a multi-step process:

(1) sync the dive to the Suunto app - and hope that sync actually
happens, because if it doesn't, you can only see the dive on your dive
computer

(2) on the suunto app, do the "download fit file" thing

(3) move the file from your phone to your laptop (I used google
drive, but any file transfer thing works)

(4) import the FIT file into subsurface

end result: I still like and use my old Suunto EON Core, but the
Suunto Ocean is in some drawer somewhere gathering dust.

Too bad.

I can recommend Shearwater. Their bluetooth is slow and a bit flaky,
but they still put the diver first,

Linus

[Michael Keller]

Hi Dietmar.

On 30/11/2025 07:01, Linus Torvalds wrote:

I can recommend Shearwater. Their bluetooth is slow and a bit flaky,
but they still put the diver first,

Or, if you want a smartwatch that has a decent dive computer built in, go for a Garmin Descent. The drawback is that it requires an USB connection to download dives directly into Subsurface, but on the flip side it does all of the things you'd expect from a smartwatch.

Ngā mihi

  Michael Keller

[Dietma Flubacher]

Hi Michael, hi Linus

Thanks for the recommendation, but so far I was quite happy with my Suunto(s). And I have also Pods that work with Suunto and having the same for Shearwater becomes quite expensive. 

So, my question remains: what are the plans with the Suunto Nautic: will it be supported and if so, any idea how long will it take?

Dietmar

Am 29.11.2025 um 22:22 schrieb Michael Keller <mike...@042.ch>:



--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/86241db5-71bc-4aeb-ae47-cf95389a1cbd%40042.ch.

[Michael Keller]

Hi Dietmar.

On 30/11/25 21:12, 'Dietma Flubacher' via Subsurface Divelog wrote:

Hi Michael, hi Linus

Thanks for the recommendation, but so far I was quite happy with my Suunto(s). And I have also Pods that work with Suunto and having the same for Shearwater becomes quite expensive. 

So, my question remains: what are the plans with the Suunto Nautic: will it be supported and if so, any idea how long will it take?

As Linus stated in his post, from the looks of it the Suunto Nautic is already supported in Subsurface, in a laborious and unreliable way:

And if it does work, we *can* already import the FIT files in the
desktop app, but it's a multi-step process:

(1) sync the dive to the Suunto app - and hope that sync actually
happens, because if it doesn't, you can only see the dive on your dive
computer

(2) on the suunto app, do the "download fit file" thing

(3) move the file from your phone to your laptop (I used google
drive, but any file transfer thing works)

(4) import the FIT file into subsurface

Not sure if this will ever improve - doubt Suunto will have much motivation to open up their watch to app protocol, and reverse engineering is likely going to be a lot more complex than other 'pure' dive computers, as these are smart wartches / sports watches with an added on dive computer mode, rather than devices that are only dive computers.

Ngā mihi

  Michael Keller

[dietmar....@gmx.net]

Hi Michael,

 

ok, after rcovering from a cold, I was finally able to really use my Suunto Nautic. Looking great so far.

 

One problem though during import to Subsurface: there is no import of the gas data, no way to see air consumption during the dive. I took a look to the JSON that you can export from the Suunto App and there you can see the data. Not sure if it part oft the .fit file.

 

It would be a shame if this info cannot be imported to ubsurface – any idea/proposal? How was this managed in the past?

 

Thanks

 

Dietmar

--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/CkeizSm0yXE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/5a162195-c8df-43a7-8a55-fe73cd29f348%40042.ch.

Virenfrei.www.norton.com

[Michael Keller]

Hi Dietmar.

On 28/12/2025 06:59, dietmar.flubacher via Subsurface Divelog wrote:

ok, after rcovering from a cold, I was finally able to really use my Suunto Nautic. Looking great so far. 

Glad to hear you're back to diving. 😃

One problem though during import to Subsurface: there is no import of the gas data, no way to see air consumption during the dive. I took a look to the JSON that you can export from the Suunto App and there you can see the data. Not sure if it part oft the .fit file. 

Yeah, I think this is a bit of a systemic issue with the use of FIT files for dive logs. The FIT data format was introduced by Garmin to support logs for fitness activities like running, biking, you name it. As such it has support for a lot of things that are not at all relevant for diving, like lap times, and no native support for diving specific things like tank pressures. When Garmin introduced their 'Descent' dive computer smart watches, they shoehorned support for these things into the FIT format by adding custom extensions.

As it looks now, other manufacturers have jumped onto the bandwagon and started to (ab-)use FIT for dive logs. And from the looks of it, sadly, they have not bothered to implement the same custom extensions that Garmin introduced for dive logs. 

So Suunto either does not include tank pressure information in their FIT files, or they do so, but in a different custom format.

It would be a shame if this info cannot be imported to ubsurface – any idea/proposal? How was this managed in the past?

I can see two ways:

- if you supply sample FIT files and accompanying dive logs in a format that can be analysed (can be a profile image showing the gas information), I can have a stab at finding the tank pressure information in it and see if it is possible to add support for it;

- there are other standardised formats that like UDDF that are intended for use for dive log files - does Suunto offer the export in any other format?

Ngā mihi

  Michael Keller

[Alon Dotan]

Yes,
Suunto offering an json export which is much richer and detailed then the FIT option,
I can supply an example if needed,
Thanks

[Linus Torvalds]

On Mon, 29 Dec 2025 at 11:31, Alon Dotan <alon1...@gmail.com> wrote:
>
> Yes,
> Suunto offering an json export which is much richer and detailed then the FIT option,
> I can supply an example if needed,

Yes, please send an example file - along with a screenshot of what the
dive looks like in the Suunto app (with things like air consumption
etc).

Maybe send it to me and Michael as emails, if you don't want to make
the data public (or maybe googlegroups might have issues with
attachments)

Linus

[Alon Dotan]

I have no issues with privacy,

I dont have air integration, ill ask from a friend to send me an example, I plan to go tech diving with the computer in the next 3-4 weeks ill provide a multi gas examples later on

[dietmar....@gmx.net]

Hi all,

 

please find attached the fit and json from my last dive using the Nautic, including 2 pods for sidemount configuration. The imported fit looks like this in Subsurfacce:

 

For this dive, I was also using a Garmin including air integration and this looks like this:

 

I am thinking about creating a python script that converts the json into ssrf format that can be used for import. Do you know if this is already out there or is this something completely new?

 

Dietmar

--

You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit

https://groups.google.com/d/topic/subsurface-divelog/CkeizSm0yXE/unsubscribe.

To unsubscribe from this group and all its topics, send an email to

subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/CALqEfON%3DYPMH%2BxJXKF2S16Cw4poCWDqL8sthS5HKksCxq7EYzQ%40mail.gmail.com.

Virenfrei.www.norton.com

[Michael Keller]

Hello Dietmar and Alon.

Dietmar: Unfortunately it looks like the attached files did not make it all the way - can you try it again please?

Alon: Thanks for the JSON. 

The JSON looks interesting and rich in data. But unfortunately it also looks like Suunto 'invented' a new format instead of leveraging an existing format like UDDF - so it will need a reasonable amount of work to implement a converter / importer for Subsurface.

The mechanism to import proprietary formats into Subsurface that is currently best supported is to convert them into the native Subsurface XML format through an XSLT transformation - see the xslt/ directory in the repository for examples of existing importers / exporters. Adding an importer that is implemented in this way into Subsurface will be straightforward. For a python based importer this might be considerably harder, as it will require to bundle python with Subsurface, or get the Subsurface installer to install python on Windows / macOS / linux...

Ngā mihi

  Michael Keller

You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/001201dc790f%24ba447070%242ecd5150%24%40gmx.net.

[dietmar....@gmx.net]

Hi Michael

 

First of all: Happy New year.

 

Apologies for the delayed response, I was on a business trip and could not answer earlier. I combined the json and fit in a zip file, hoping that with this, they go through. Please let me know if you need more

 

Dietmar

To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/054f94c9-6445-4aac-858e-508fc0cc8e2d%40042.ch.

[Le TNZ]

Hi everyone,

I come back from my N3 / CMAS confirmation with 2 dives around 40m. It was the first time I use my Nautic.

The computer during dive is great, you have the expected information regarding the dive phase ... just magic and readable for other fellows with you during the dive.

Now, the sync ... 2 dives & only one available in suunto app :(

@Linus : sync issues are still on the air. I'll tell you after FIT export / subsurface import.

TNZ

[Phil Robinson]

Hello,

I'm a new diver (obtained my PADI Open-Water in the UK last December), and spent a week in January diving in Martinique with the Suunto Nautic.

I haven't experienced any of the sync issues reported by others on this thread - so far, every dive is shown in the Suunto app as soon as the sync is complete.

I would be interested in helping bring support for the Nautic to Subsurface. It would appear that the new JSON export format that Suunto provide for the Nautic provides a great level of detail, but may not be straightforward to integrate with Subsurface. 

Is anyone aware of any other dive computers that use a JSON format that are already supported by Subsurface (I don't want to reinvent the wheel....)?

Thanks, 

Phil

[Michael Keller]

Hi Phil.

On Tue, 24 Feb 2026 at 03:35, Phil Robinson <philip.r...@gmail.com> wrote:

I would be interested in helping bring support for the Nautic to Subsurface. It would appear that the new JSON export format that Suunto provide for the Nautic provides a great level of detail, but may not be straightforward to integrate with Subsurface. 

Is anyone aware of any other dive computers that use a JSON format that are already supported by Subsurface (I don't want to reinvent the wheel....)?

No, there currently isn't anything that imports JSON into Subsurface. There are quite a few dive log formats that use XML, and we use XSLT transformation to convert from / to these.

Unfortunately the XSLT library we are using only supports XSLT 1.0, so it does not have the capability to directly handle JSON that was added in XSLT 3.0.

But you should be able to get something going with a custom XSLT that directly handles the particular JSON format that Suunto emits.

Ngā mihi

  Michael Keller

--

GCS$/CC/E/IT d- s+ a C++ UL+++/S++ P L++ E-
W++ N o? K? w O(++) M-- V+ PS+ PE+ Y? PGP+ t
5? X R tv b++ DI++ D++ G e+++ h---- r+++ y+++

[Phil Robinson]

Hi Michael,

Thanks for your message.

Please to confirm I now have a working proof of concept that allows me to import JSON files exported from a Suunto Nautic into Subsurface. The data imported is currently similar to when using a FIT file, so still missing consumption info etc..

As the Nautic is my only DC, I don't have any comparitive exports from other "working" DCs to help me progress further - is there a set of files that are regularly tested against that I could use for this purpose? (I can't find anything on subsurface's github).

If not, @Dietmar - would you be willing to share the export from your Garmin that matches what you shared on 26th January for the Nautic?

Thanks,

Phil

[Dietma Flubacher]

Hi Phil,

Here we go. Let me know if you more examples for checking

Dietmar

[Dietma Flubacher]

Hi Phil and all others 

that are interested in getting data from a Nautic or Ocean into Subsurface. I reached out to Suunto Support and raised a ticket that the .fit is incompletely implemented. It might be helpful if more of us push for this

Dietmar

__________________________

Dietmar Flubacher

Im Bühl 2a

79189 Bad Krozingen

Germany

 

phone: +49 (0)7633 923 10 90

mobile: +49 (0)176 326 922 81

Am 25.02.2026 um 20:53 schrieb Dietma Flubacher <dietmar....@gmx.net>:



Hi Phil,

Here we go. Let me know if you more examples for checking

Dietmar

<Example_DF.zip>

Am 25.02.2026 um 18:35 schrieb Phil Robinson <philip.r...@gmail.com>:

Hi Michael,

--

You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/927e86c6-6193-4304-b8c1-9e9c2ecb4120n%40googlegroups.com.

[Wayne Heming]

Phil

I use a Suunto EON Steel and can provide some export files from that if you need them. I am looking at buying a Nautic.
How do you want the data exported?

Regards,

Wayne Heming
0428 436 638
wayne....@hemnet.com.au
http://dive.hemnet.com.au

--

[Phil Robinson]

Status - I now have gas consumption working, including for 2 tank setups. Working on location info now.

-----

Dietmar - many thanks for sharing. I was actually looking for the data from your Garmin for that dive to allow me to check I've correctly mapped all of the data - is it possible to share that? 

I agree it would be good to push Suunto to complete their FIT implementation. 

That said, Suunto's JSON export from the Nautic is very data-rich, including all of the inertial guidance information which allows for 3D mapping of the dive route. I don't believe the FIT protocol provisions for this (though I haven't had time to look in detail), and therefore suggest we push for continued support of the JSON export format as well as FIT.

There are some oddities in the current JSON export that I will try to confirm on the latest firmware before raising with Suunto support.

-----

Wayne - thanks for your offer, I have a few EON Core files, but it would be good to have more references to work with. Exporting both FIT and JSON files from the Suunto app, then placing in a ZIP before adding here seems to work best.

Thanks,

Phil

[Wayne Heming]

Phil

Here is 2 sets of files. Sorry couldn’t zip them

From Eon Steel Black, with tank Pod. 

To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/936c6757-31dc-4293-ae44-39fb2ddd0848n%40googlegroups.com.

[Wayne Heming]

Well that didn't work.

Try again (Zipped)

Regards,

Wayne Heming
0428 436 638
wayne....@hemnet.com.au
http://dive.hemnet.com.au

To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/A60AF3E6-AF6D-4E97-AEDD-A164FE656F78.goodhumans%40hemnet.com.au.

[Jasper van Eeuwijk]

I've been working on importing Suunto .json exports into Subsurface. It is working with all the .json files that have been posted in this discussion, and I tested with a few exports from my EON Core, but there is also a lot that is untested. 

 Tested configurations:
 Model          Air   Nitrox   Trimix   No AI   Multi cyl   Multi gas
 -----------    ---   ------   ------   -----   ---------   ---------
 Nautic         yes   no       no       yes     yes         no
 Nautic S       no    no       no       no      no          no
 Ocean          no    no       no       no      no          no
 EON Core       yes   yes      no       no      no          no
 EON Steel      no    yes      no       no      no          no
 D5             no    no       no       no      no          no

What is the best way to contribute to Subsurface?

The JSON structure is different between the Ocean/Nautic and the D5/EON exports, but there is some overlap.

I have combined the import logic for the EON/D5 and the Ocean/Nautic into one import-suunto-json.cpp file, is that the right approach?

The Nautic logs that were posted here don't have tank sizes in the json (that I could find). The SAC per sample is imported from the JSON,  What puzzles me is that the tank size must be known by the computer for it to calculate the SAC in the first place.

I have resorted to calculating the average SAC of the dive by averaging these values.  Is this an acceptable way?

Any other suggestions I should take into consideration?

[Dirk Hohndel]

Hi Jasper,

Thanks for working on this.

The best approach to integrating this into Subsurface depends on a number of factors, the biggest on likely how the user gets access to that .json file. What's the workflow?

Assuming that they need to manually download / extract this file and it ends up in the file system, the best approach is likely to add this as another import filter.

Looking at the json, I see this:

        "Gases": [

          {

            "EndPressure": 5648438,

            "Helium": 0,

            "Oxygen": 0.32,

            "PO2": 160000,

            "StartPressure": 23329688,

            "State": "Primary",

            "TankFillPressure": 20000000,

            "TankSize": 0.012,

            "TransmitterEndBatteryCharge": 0.51,

            "TransmitterID": "2251100336",

            "TransmitterStartBatteryCharge": 0.54

          }

        ],

So I'm guessing that was a 12l tank? Because it makes total sense to provide that size in... umm... cubic meters? Especially when giving the PO2 and TankFillPressure in Pascal.

That's what happens when people are told to use SI units and subsequently turn off their brain?

Anyway, I think I found your tank size. And once you import that, Subsurface will calculate the SAC rate for you.

/D

[Jasper van Eeuwijk]

Hi Dirk,

Thanks for assisting me in finding the tank size, I've been trying to find the JSON snippet you shared and I was able to find it in the EON Steel Black JSON export:

699f9c153fc6eb6cc349c4d0.json (from EonSteelBlackTankPod.zip) - posted by Wayne Heming on Feb 28, 2026, 10:37:01 PM

The files that contain data from Nautic computers in this thread are:

ScubaDiving_2025-12-21T12_22_19.json - posted by Alon Dotan on Dec 29, 2025, 9:24:06 PM

694ffe4cffc876413c2dd975.json (from Example_DF.zip) - posted by dietmar....@gmx.net on Jan 25, 2026, 12:44:43 PM

My import code recognises the tank size on EON (and hopefully D5) computers, exactly from that section of JSON. My problem is with the Nautic logs, I was unable to find tank size anywhere inside those.

[Dirk Hohndel]

Yes, very few dive computers ask the user to set a tank size. The Suuntos are kinda unusual in this.

So my guess is that the Nautic computers just don't do that. Which means that the user needs to set the tank size manually after the import - just as they have to do for many other dive computesr

/D

[Jasper van Eeuwijk]

In the Nautic manual, chapter 5.1, it shows the option to set tank size:

"In the Edit gas menu you can also set your tank size. The default value is 12 liters / 80 cu ft. Make sure you set your correct tank size to ensure correct gas consumption calculations when diving with Suunto Tank POD."

What I'd like to find out is if I should assume 12 liters if there is no record of it in the JSON. If anyone could share a Nautic dive log in JSON format with a tank size set to anything but 12 liters I could determine if the tank size does get listed if it was explicitly set by the user.

I also noticed this in chapter 6.3:

"You can see your average gas consumption after the dive in the dive summary. The value shows the average gas consumption value, calculated from all the gas consumption values during the dive."

So for now I'll keep the code that averages all SAC rates in the samples to calculate the SAC-rate for the entire dive.

With that information and the pressure drop from the tank(s) I could back-calculate the tank size. From the manual it seems there is a fixed list of tank sizes and I could match to the closest one. 

Then again that feels really hacky and I'm not sure where to draw the line between data completeness and just importing the raw data from the dive computer as it is offered.

[Jasper van Eeuwijk]

I'm getting closer to completing the import module. 

One thing I'm coming up against is the automatic generation of SupportedDivecomputers.html and SupportedDivecomputers.txt.

These are automatically generated from libdivecomputers and have Seabaer and Uemis injected in parse-descriptor.pl.

First question, do we want to add the Suunto Nautic and Ocean to the supported dive computer list when what I intend to add is a JSON import and not a direct import from the dive computer?

If so, should I add to the parse-descriptor Perl script and hardcode these models in? That would require different logic than the current way  Seabaer and Uemisare are handled, these brands are not in libdivecomputer at all. I would need to add some merge logic to insert the Nautic and Ocean in alphabetical order into the Suunto list. My suggestion would be to push them onto @descriptors before sorting.

Or is it a better idea to separate out these Suunto models as well as the Seabaer and Uemis into a separate file that gets read after libdivecomputer's descriptor.c (and then also push them onto @descriptors)?

[Michael Keller]

Hi Jasper.

On Wed, 8 Apr 2026 at 09:33, Jasper van Eeuwijk <glew...@gmail.com> wrote:

One thing I'm coming up against is the automatic generation of SupportedDivecomputers.html and SupportedDivecomputers.txt.

These are automatically generated from libdivecomputers and have Seabaer and Uemis injected in parse-descriptor.pl.

First question, do we want to add the Suunto Nautic and Ocean to the supported dive computer list when what I intend to add is a JSON import and not a direct import from the dive computer?

If so, should I add to the parse-descriptor Perl script and hardcode these models in? That would require different logic than the current way  Seabaer and Uemisare are handled, these brands are not in libdivecomputer at all. I would need to add some merge logic to insert the Nautic and Ocean in alphabetical order into the Suunto list. My suggestion would be to push them onto @descriptors before sorting.

Or is it a better idea to separate out these Suunto models as well as the Seabaer and Uemis into a separate file that gets read after libdivecomputer's descriptor.c (and then also push them onto @descriptors)?

Don't get too hung up on the dive computer list; this is really just window dressing. The import functionality is what gives value to the users.

But I think it might make sense to rethink the structure of the 'supported dive computer list,' separating it into 'direct import' (generated from libdivecomputer) and 'file based import' (which is static), and then add your importer to the file based section. This will hopefully reduce support requests from users who can't find the importer for their model because they are looking in the wrong place.

Ngā mihi

  Michael Keller 

[Jasper van Eeuwijk]

Hi Dietmar,

Would you mind if I included the .json export you shared in the automated test for the Suunto Nautic importer I'm developing?

That would mean it gets bundled with the subsurface code and will be visible to anyone interested on github.com, the file is likely to remain there for as long as Subsurface exists, and be copied to other places outside your, my and the Subsurface maintainers' control. With your permission I will change the serial number from the dive log, I don't think there is any other data that could be linked back to you.

kind regards,

Jasper van Eeuwijk

[Dietma Flubacher]

Good morning Jasper,

So if I understand correctly, you are asking whether my files can also be used by the community to develop the json important therefore the are accessible for everyone. If this is the case, it is absolutely fine for me and I am glad I can be of some help! Please feel free to use them and thanks for asking.

Dietmar

Am 09.04.2026 um 00:05 schrieb Jasper van Eeuwijk <glew...@gmail.com>:



You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/CkeizSm0yXE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/9d944fe3-b15a-4d28-8600-bccd4a612cfdn%40googlegroups.com.

[Dietmar Flubacher]

Hi Jasper, hi Dirk,

based on your list I saw that you have no examples for the Ocean - a friend of mine has mone and he shared with me 5 files which I attached to this mail. It is fine for him to share them so that the import can be developped.

2 dives are with Nitrox.

Ealry May, I am planning 2 dives in a sidemount config with the Nautic, so can get examples for this as well.

Dietmar

[Dietmar Flubacher]

Sorry, there was a problem with the upload of files, here are the files now in a zip-file

[Jasper van Eeuwijk]

Hi Dietmar,

Thank your friend for me, these are really useful. I believe one of the files you sent is actually one of your dives (the sidemount dive you shared earlier), but the other four are plenty for now.

From a quick look the Suunto Ocean has a different structure again from both the Eon and the Nautic, so far the import succeeds but the tank pressure data is not recognized by the importer. I hope that this weekend I'll have some time to add support for the Ocean and submit a pull request, no promises though!

Your dive with the Nautic

One of the dives your friend submitted, without pressure data for now.

Thanks again,

Jasper van Eeuwijk

[Jasper van Eeuwijk]

Pull request submitted: Import: Support Suunto app exports (JSON parser, .json/.fit filters) #4767