Dive gases not properly recorded

[Sol Chrom]

Comrades: Just did a half hour dive on EANx32. Why does the log say I was on air?

I had the Shearwater Perdix AI set to 32%. I had a couple of other gases improperly activated, but air wasn't one of the options.

   

[Michael Keller]

Hi Sol

On Thu, 21 May 2026 at 16:05, Sol Chrom <sol....@gmail.com> wrote:

Comrades: Just did a half hour dive on EANx32. Why does the log say I was on air?

I had the Shearwater Perdix AI set to 32%. I had a couple of other gases improperly activated, but air wasn't one of the options.

 

This is very odd.

What version of Subsurface were you using?

And what firmware version is running on the dive computer?

Have you tried downloading this log in the Shearwater app, and does it show the correct gas?

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

[Sol Chrom]

Hi Michael:

Sorry, I should have included that.

Macbook running Tahoe 26.4.1

Subsurface 6.0.5597-CICD-release

Shearwater FW 102/BT13

Shearwater Cloud records it as EANx32.

--
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/TtKIPt_kXK0/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/CACJC9LY_Nq6uKU94wAPozk9WCMXUcJZknZw3X72abRAHjsAeGQ%40mail.gmail.com.

[Michael Keller]

Hi Sol.

On 21/05/2026 22:55, Sol Chrom wrote:

Sorry, I should have included that.

Macbook running Tahoe 26.4.1

Subsurface 6.0.5597-CICD-release

Shearwater FW 102/BT13

Shearwater Cloud records it as EANx32.

Hmm, this is really odd - I can't really explain how Subsurface should get the gas mix wrong on import.

Are you able to share the Subsurface log file just in the form that it was imported in with me?

Ngā mihi

  Michael Keller

[Sol Chrom]

I’d be delighted to. What do you need me to do?

Sent from my iPhone via Gmail Mobile

--

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/TtKIPt_kXK0/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/74cdd336-16ee-4f59-8d4a-9ed4585c7d0b%40042.ch.

[Sol Chrom]

Hi Michael:

I took a flyer and exported it as Subsurface XML. If this isn't what you need, please let me know. 

Sol

[Michael Keller]

Hi Sol.

On 24/05/2026 12:30, Sol Chrom wrote:
> Hi Michael:
>
> I took a flyer and exported it as Subsurface XML. If this isn't what
> you need, please let me know.

Thanks, that was what I was looking for. Unfortunately this looks
exactly like you'd expect a log to look like after importing from a
Shearwater dive computer, with nothing pointing in the direction of
where this is going wrong, like an incorrect tank sensor mapping.


Next step will be to generate a libdivecomputer log file, by importing
the dive with 'Save libdivecomputer logfile' checked, and sending this
log file.


Ngā mihi

  Michael Keller

[Sol Chrom]

Hi Michael:

Hopefully this does the trick.  

S

--
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/TtKIPt_kXK0/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/77c0248c-cd66-4033-bdc2-f75fcff79aeb%40042.ch.

[Jef Driesen]

On 25/05/2026 02:47, Sol Chrom wrote:
> Hopefully this does the trick.

The log file is empty, which means you either didn't try to download from the
dive computer at all, or there was already a problem establishing the bluetooth
connection. If you already download the problematic dive before, you may also
need to enable the "Force download of all dives". You can cancel after the dive
has been downloaded, and exit without re-importing the dive.

Jef

[Sol Chrom]

Hi Jef:

I was saving the download to a different location so I didn't overwrite the main log file on my hard drive. Could that be the problem?

I can give the "force download of all dives" option a try, but I'd want to make sure not to overwrite. 

Sol

[Sol Chrom]

OK, how about now? 

[Jef Driesen]

On 25/05/2026 17:51, Sol Chrom wrote:
> OK, how about now?

This log looks good!

I quickly checked your latest dives and they are all correctly parsed as dives
with EAN32. No idea where or how subsurface changes that into air.

Jef

[Sol Chrom]

Curse of the gas gods?