MK3i support and Android version

[Stuart Sayre]

I'm waiting on my new Garmin MK3i to ship and I'm hoping to use Subsurface is support for the MK3 on the roadmap?

I migrated my data from the Aqualung i300c successfully.  On my Ubuntu notebook I couldn't get the bluetooth sync to work however.  It found the i300c and connected but the import failed.  So I downloaded the dives from their cloud but the import didn't bring the dive sites with.  So I manually entered them so we're good.

I found some posts suggesting to do bluetooth sync through the phone for better results but my Android version isn't supported by subsurface yet.  Any plans to support Android 14?

Without the mobile app would I use the cable to connect my MK3 to Subsurface?

Thank you and liking the app alot.

[Dirk Hohndel]

Garmin Descent Mk3i -- I haven't seen one myself, but I'm told it's compatible and should work. But ONLY with Subsurface on the desktop, NOT with the mobile version.

Generally Bluetooth does tend to work better on mobile devices. Android builds are available in our nightly releases for side-loading, e.g. here:

 https://github.com/subsurface/nightly-builds/releases 

Currently we are unable to build APKs/AABs that would qualify to be uploaded to the Google Play store.

/D

[Mike Dugan]

I know this is an "Android" thread, but it looks like the desktop App is being referenced so I'll ask here.  In the desktop App should we be seeing a MK3i option under Garmin?  I see MK1 and MK2/MK2i within Garmin but not MK3/MK3i.  I've tried selecting MK2/MK2i and pointing the mount point folder where the FIT files are from this MK3i and it fails to find anything.  

So basically has anybody figured out how to get dives from the MK3i into Subsurface?  

[Michael Keller]

Hi Mike.

On Fri, 19 Apr 2024 at 09:39, Mike Dugan <mrmp...@gmail.com> wrote:

I know this is an "Android" thread, but it looks like the desktop App is being referenced so I'll ask here.  In the desktop App should we be seeing a MK3i option under Garmin?  I see MK1 and MK2/MK2i within Garmin but not MK3/MK3i.  I've tried selecting MK2/MK2i and pointing the mount point folder where the FIT files are from this MK3i and it fails to find anything.  

So basically has anybody figured out how to get dives from the MK3i into Subsurface?  

Do you get any kind of error message when you try to download dives from the Mk3i to the desktop app by selecting 'Mk2/Mk2i'?

Also, what is the path (underneath the mountpoint) for the .FIT files on the Mk3i?

Cheers

  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+++

[Mike Dugan]

I stand corrected, the "point the desktop App to a folder with the FIT files in it" is working.  The only issue now is that they import as MK2i dives, not MK3i. So, progress, woot.

--
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/7Uo7A9YTGhg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/CACJC9LYZdw-bsQq2GtXgrt%3Dq%3DnpUyWRLZ%3Dg3qcwrYZR7p3Ge4Q%40mail.gmail.com.

[Michael Keller]

Hi Mike.

Thank you for the test files.

You will be able to identify this better than myself, as you were actually doing the dives, but does the data that is imported look correct to you, or are there things that are not correct in the logs?

Re the dives showing up as 'Mk2/Mk2i' dives, the pragmatic way to fix this will be to amend the dive computer name to be 'Mk2(i)/Mk3(i)'. I think for now this is the way to go, as there doesn't seem to be significant extra data in the files generated by the Mk3(i) that we want to add support for.

We can potentially add the extraction of the model information from the .FIT file, and add it into the 'Extra Info' tab.

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 on the web visit https://groups.google.com/d/msgid/subsurface-divelog/CAEET%2BW%2B%2BGpMa%3Da7azS1RfBh%2Bk0TUC7BgqfW85tX1%3Dndsg35mfA%40mail.gmail.com.

[Mike Dugan]

I thought I replied but I don't see it.  

Yes, most of the data is tracking with what's showing in the Garmin Dive Android App.  The SAC rate is a bit different (Subsurface showing be better by .5), but nothing else seems to off.  The good news is (and I'm asking Garmin) is that the sensor section of the Garmin App is sometimes telling me I'm ending dives with less than 100 psi when I'm not, and the Subsurface App nails it.  But that's something I'm working on with Garmin. 

Is the editing of the computer name to Mk3(i) something I do, or will it be part of a future release? 

Thanks for all your help..

[Michael Keller]

Hi Mike.

On Fri, 19 Apr 2024 at 15:29, Mike Dugan <mrmp...@gmail.com> wrote:

I thought I replied but I don't see it.  

I think your previous reply went to my email address and not to the group...

 

Yes, most of the data is tracking with what's showing in the Garmin Dive Android App.  The SAC rate is a bit different (Subsurface showing be better by .5), but nothing else seems to off.  The good news is (and I'm asking Garmin) is that the sensor section of the Garmin App is sometimes telling me I'm ending dives with less than 100 psi when I'm not, and the Subsurface App nails it.  But that's something I'm working on with Garmin. 

The SAC is calculated from depth and tank pressure information, but there are different ways of doing it (integrating over all samples vs. based on total consumption / average depth, are you considered to be breathing from the tank when at the surface or not), so this is not an exact science and there is room for differences.

Is the editing of the computer name to Mk3(i) something I do, or will it be part of a future release? 

I'll be looking into this.

[Mike Dugan]

Sounds good, thank you again.

[Dirk Hohndel]

On Apr 18, 2024, at 20:41, Michael Keller wrote:

 

Yes, most of the data is tracking with what's showing in the Garmin Dive Android App.  The SAC rate is a bit different (Subsurface showing be better by .5), but nothing else seems to off.  The good news is (and I'm asking Garmin) is that the sensor section of the Garmin App is sometimes telling me I'm ending dives with less than 100 psi when I'm not, and the Subsurface App nails it.  But that's something I'm working on with Garmin. 

The SAC is calculated from depth and tank pressure information, but there are different ways of doing it (integrating over all samples vs. based on total consumption / average depth, are you considered to be breathing from the tank when at the surface or not), so this is not an exact science and there is room for differences.

Almost always these discrepancies are explained by Subsurface taking the compressibility of gases into account and some other apps don't.

The ideal gas law is nice and easy to implement. It also isn't how actual gasses work.

/D

[Mike Dugan]

Totally agree. 

[S Asmus]

Hello, I still have problems to import the dives into Subsurface. I put the .fit file in a folder on the desktop. After importing the file to Subsurface, I see some informations (dive time, gps location, max. depth), but I can't see the dive profile and the average depth. The calculation of the SAC rate isn't working.

I have the latest update (16.25) on my Garmin mk3i.

Has anyone the same problem?

Thanks!

[Michael Keller]

Hi S.

Thank you for reporting this.

On 25/04/24 07:02, S Asmus wrote:
> Hello, I still have problems to import the dives into Subsurface. I
> put the .fit file in a folder on the desktop. After importing the file
> to Subsurface, I see some informations (dive time, gps location, max.
> depth), but I can't see the dive profile and the average depth. The
> calculation of the SAC rate isn't working.
> I have the latest update (16.25) on my Garmin mk3i.

Would you be willing to share one or more sample .fit log files showing
this problem with me, so that I can have a look into figuring out what
is going wrong here?


Ngā mihi

  Michael Keller

[S Asmus]

Sure, here you go:

Thank you!

Sven

[Michael Keller]

Hi Sven.

On 25/04/24 16:18, S Asmus wrote:

Sure, here you go:

Thank you for the log files.

It does indeed look like Garmin has changed the format of the log files somewhere between firmware 15.62 (top) and 16.25 (bottom):

As the format of the CSV output isn't strictly relating to the format of the binary files, getting support for the new format added will probably take a fair whack of trial and error to guess the field positions in the binary file. Oh the fun!

Cheers

  Michael Keller

[S Asmus]

Hello Michael,

thank you for the quick response. I hope you can fix the issue and Garmin won't change the log file with every update.

Best regards

Sven

[Michael Keller]

Hi Sven.

On 28/04/24 18:08, S Asmus wrote:
> thank you for the quick response. I hope you can fix the issue and
> Garmin won't change the log file with every update.

Their format seems to be pretty stable, and to be fair to them the
problems were caused by a change that had been in the protocol for a
long time, but had never been used. And they gave a long warning before
making the change - it's just that nobody in Subsurface is actively
following their announcements.

Anyhow, if you try a version
from https://subsurface-divelog.org/latest-release/ Garmin Descent
models with firmware >= 16.22 should be supported now.


Cheers

  Michael Keller

[walt...@gmail.com]

Seems I have the same issue! After the update of my MK3i to 16.25 I'm not able to import data. I tried 6.0.5151 with the new dive. So far Subsurface crashes when I import the latest dive.

[Michael Keller]

Hi Walt.

Are you able to supply me with one or more of the .fit files that result in the crash with 6.0.5151?

Crashing was certainly not intended when I made these changes, and the limited number of .fit files from 16.25 that I have available at the moment are importing just fine.

Cheers

  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 on the web visit https://groups.google.com/d/msgid/subsurface-divelog/9d3413d7-ff1e-4bc3-891a-3482494871dcn%40googlegroups.com.

[Michael Keller]

Hi Walter.


On 29/04/24 18:34, Walter Hirschle wrote:
>
> Seems that the data was imported correctly. But again, as soon as I
> click on Subsurface it immediately crashes. I see the same behavior
> when I select a singe 15.62 dive. Also I tested native English and
> German as the interface language. No difference!
>
> Attached my FIT file with the 16.25 dive.


Thank you for sharing the file. I tried opening it with 6.0.5151, both
alone and together with other Descent Mk3 .fit files, but I was not able
to reproduce the crash. What operating system are you using?

Btw, looks like lake Zurich is plenty cold at the moment. ;-)


Cheers

  Michael Keller

[Walter Hirschle]

Hi Michael

Windows 11 with latest updates. The UI freezes and as soon as I click into the window Subsurface crashes if it is still alive. No issues with 6.0.5112! I switched several times to 5151 and back to 5112 again! Always the same!

The first few meters will get warmer the next few weeks! Below 10 to 12m it's always cold! It's ok with a dry suit!

Thanks

Walter

--
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/7Uo7A9YTGhg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/99ec90c0-c4fe-4de8-9dee-bc156354e63d%40042.ch.

[walt...@gmail.com]

Hi Michael

I just set up Subsurface on Fedora 40 (VirtualBox). Seems to work with 6.0.5151. So the crash must be related to Windows. Also I set locales to German (Switzerland). No issue with my MK3i files.

Thanks

Walter

[Mike Dugan]

I have found the same thing, 5151 crashes of Win10 when starting (perhaps because the dive it opens when opening is one from a Garmin Mk3i (???)), and going back to 5112 allows Subsurface to open, but the dive displays no real data outside of what's in the dive selector window.  I've attach the two FIT file and a screen shot of what I'm seeing.

[Michael Keller]

Hi Walter and Mike.

Thank you for testing!

Would you mind giving this a go with 5145 (https://github.com/subsurface/nightly-builds/releases/tag/v6.0.5145-CICD-release) and 5144 (https://github.com/subsurface/nightly-builds/releases/tag/v6.0.5144-CICD-release) as well?

My suspicion is that this was introduced by https://github.com/subsurface/subsurface/pull/4126.

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 on the web visit https://groups.google.com/d/msgid/subsurface-divelog/f9a2e87f-73fe-431a-bc65-82f7d46a87b6n%40googlegroups.com.

[Mike Dugan]

5144 opened but the screens were blank.  5155 crashed upon opening (so no screenshot).  On Win10.

I'll try going back to 5144, deleting the most recent dive (from a Garmin Mk3I), saving it, then going back to 5155 and see if it's the Garmin dive causing the issue, or the build...

[Mike Dugan]

OK, 5144 will open no matter what, 5145 won't open on Win10 without crashing, even if the most resent dive is from a Mk3i.  not sure if that helps, but I'll leave 5144 installed for now and keep diving with my ScubaPro Mantis 2 as my backup because it loads and shows data.

[walt...@gmail.com]

Hi

I can confirm: 5145 crashes always and does not load MK3i 16.25 data!

[Mike Dugan]

Sorry, this was meant to have "not" in it:

OK, 5144 will open no matter what, 5145 won't open on Win10 without crashing, even if the most resent dive is NOT from a Mk3i - deleted my last dive, a Mk3i dive, while I had 5144 loaded, so that meant Subsurface opened displaying a ScubaPro Mantis 2 dive.  I'm not sure if that helps, but I'll leave 5144 installed for now and keep diving with my ScubaPro Mantis 2 as my backup because it loads and shows data.

[walt...@gmail.com]

And 5153 crashes under Windows 11 even without having loaded new dives!

[Michael Keller]

Hi Mike and Walter.


Thanks for testing these versions.

This has helped identify the problem, and it should now be fixed in the
latest version available at
https://www.subsurface-divelog.org/latest-release/?lang=en.


Ngā mihi

  Michael Keller

[walt...@gmail.com]

Hi Michael

Actually I ran a test with my Suunto D5 using Subsurface 5153 on Windows. Seems Subsurface uploads the data. When the upload has been completed Subsurface 5153 crashes within seconds. With 5153 on Fedora 40 (VirtualBox) I'm able to load MK3i data without any issues. The logfile then can be used with 5112 on Windows!

Btw, I've noticed that you now support events? Just perfect! Thank you!

Regards

Walter

[Michael Keller]

Hi Walter.

On 1/05/24 21:32, walt...@gmail.com wrote:
> Actually I ran a test with my Suunto D5 using Subsurface 5153 on
> Windows. Seems Subsurface uploads the data. When the upload has been
> completed Subsurface 5153 crashes within seconds. With 5153 on Fedora
> 40 (VirtualBox) I'm able to load MK3i data without any issues. The
> logfile then can be used with 5112 on Windows!

Try 5154.

> Btw, I've noticed that you now support events? Just perfect! Thank you!

We've supported events for a long time - but we've added the translation
of more 'interesting' data points coming from the dive computer into events.


Cheers

  Michael Keller

[walt...@gmail.com]

Hi Michael

Perfect! Seems to work now! I've uploaded old and new MK3i files and also tested Suunto D5 import. All data was correctly uploaded! Thank you for your support!

Cheers

Walter

[Mike Dugan]

Confirmed, after loading the new 5154 build, deleting the old dives that weren't displaying correctly, downloading them again, all works as expected.  And the new build shows that it came from a Mk2i/Mk3i - I like that...  

[S Asmus]

It also works on the Mac. Thanks a lot Michael!