Re: Garmin Mk2i - unlikely dive gas

2022-06-13 Thread Dirk Hohndel via subsurface
Yeah, it would be good to know how this is all done in a multi gas scenario.

For now I'd be tempted to add code that says "if there is only one gas mix, but 
more tanks, assume the same gas is in all tanks"

/D

> On Jun 13, 2022, at 2:19 PM, Mark wrote:
> 
> 
> Hi Dirk,
> 
>>> I have a Garmin Descent Mk2i myself and have done a fair number of air 
>>> dives with it, so I don't believe this is a general issue.
>>> But you may have set things up differently compared to the settings on mine 
>>> - so I'll poke at your .FIT file and find out :)
>> 
>> From your FIT file it seems that you have more than one tank pod connected 
>> to your Garmin, but only one gas mix defined. That confuses our code a bit 
>> and it thinks that the second pod is connected to a dive with undefined gas 
>> data - and then it defaults to air for that
>> 
>> Do you actually have more than one pod attached? Are you using both? How 
>> does this look in the on-watch settings?
> I was thinking about this in bed after I sent you my FIT last night, but 
> didn't have the brain power to work through it, or the desire to start wading 
> through the Garmin menus.  Yes, I do have two transmitters connected and for 
> all these dives only one gas mix.
> 
> The first transmitter is mine, and is set to be included in SAC calculations. 
> The second transmitter is on my partner's regs - she's only just started 
> diving, and I like to be able to keep an eye on her pressure at a glance. The 
> second transmitter is excluded from SAC calcs. I've had a look through the 
> dive setup on the watch, but it doesn't look like you assign a gas mix to a 
> transmitter, even in multi-gas mode. I've not done multi-gas dives with my 
> Garmin, so I don't know how it deals with matching mixes to cylinders (or 
> indeed if it does).
> 
> Next single gas dive I do, I could add a backup gas and see if it assigns the 
> backup gas to my second transmitter?
> 
> It'll probably be a while before I get out again, but I can experiment a bit 
> over the next few dives if you think that will help.
> 
> When I first import these dives with two transmitters, the graph shows both 
> cylinder pressures, but the SAC rate is blank until I delete the second 
> cylinder. I assume something in there is also confusing Subsurface's SAC 
> calcs?
> 
> Mark.

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface


Re: Garmin Mk2i - unlikely dive gas

2022-06-13 Thread Mark Stiebel via subsurface


Hi Dirk,

I have a Garmin Descent Mk2i myself and have done a fair number of air 
dives with it, so I don't believe this is a general issue.
But you may have set things up differently compared to the settings on 
mine - so I'll poke at your .FIT file and find out :)
From your FIT file it seems that you have more than one tank pod 
connected to your Garmin, but only one gas mix defined. That confuses 
our code a bit and it thinks that the second pod is connected to a dive 
with undefined gas data - and then it defaults to air for that


Do you actually have more than one pod attached? Are you using both? 
How does this look in the on-watch settings?
I was thinking about this in bed after I sent you my FIT last night, but 
didn't have the brain power to work through it, or the desire to start 
wading through the Garmin menus.  Yes, I do have two transmitters 
connected and for all these dives only one gas mix.


The first transmitter is mine, and is set to be included in SAC 
calculations. The second transmitter is on my partner's regs - she's 
only just started diving, and I like to be able to keep an eye on her 
pressure at a glance. The second transmitter is excluded from SAC calcs. 
I've had a look through the dive setup on the watch, but it doesn't look 
like you assign a gas mix to a transmitter, even in multi-gas mode. I've 
not done multi-gas dives with my Garmin, so I don't know how it deals 
with matching mixes to cylinders (or indeed if it does).


Next single gas dive I do, I could add a backup gas and see if it 
assigns the backup gas to my second transmitter?


It'll probably be a while before I get out again, but I can experiment a 
bit over the next few dives if you think that will help.


When I first import these dives with two transmitters, the graph shows 
both cylinder pressures, but the SAC rate is blank until I delete the 
second cylinder. I assume something in there is also confusing 
Subsurface's SAC calcs?


Mark.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface


Re: Garmin Mk2i - unlikely dive gas

2022-06-13 Thread Dirk Hohndel via subsurface


> On Jun 13, 2022, at 8:41 AM, Dirk wrote:
> 
>> On Jun 13, 2022, at 5:31 AM, Mark wrote:
>>> 
>>> Ideally we'd figure out which one it is and have you send us just send that 
>>> one file, but that puts the onus on you, if you don't mind sharing the data 
>>> privately, you could simply put ALL of the .FIT files under Garmin/Activity 
>>> on your Mk2i into a .zip file and send it off list to me and then I can 
>>> figure this out here.
>> It's all dives, not just particular ones. Well, all air dives anyway. Have 
>> not confirmed nitrox.  Without having looked into it at all, I'm 
>> hypothesizing something like the Garmin using a flag for air/not-air, and 
>> assigning the O2% a nonsensical value (null/zero) for air dives.
> 
> I have a Garmin Descent Mk2i myself and have done a fair number of air dives 
> with it, so I don't believe this is a general issue.
> But you may have set things up differently compared to the settings on mine - 
> so I'll poke at your .FIT file and find out :)

From your FIT file it seems that you have more than one tank pod connected to 
your Garmin, but only one gas mix defined. That confuses our code a bit and it 
thinks that the second pod is connected to a dive with undefined gas data - and 
then it defaults to air for that.

Do you actually have more than one pod attached? Are you using both? How does 
this look in the on-watch settings?

I'm trying to figure out how to parse this correctly, but since I only have one 
pod, this isn't something I can experiment with here...

/D___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface


Re: Garmin Mk2i - unlikely dive gas

2022-06-13 Thread Dirk Hohndel via subsurface


> On Jun 13, 2022, at 5:31 AM, Mark wrote:
>> 
>> Ideally we'd figure out which one it is and have you send us just send that 
>> one file, but that puts the onus on you, if you don't mind sharing the data 
>> privately, you could simply put ALL of the .FIT files under Garmin/Activity 
>> on your Mk2i into a .zip file and send it off list to me and then I can 
>> figure this out here.
> It's all dives, not just particular ones. Well, all air dives anyway. Have 
> not confirmed nitrox.  Without having looked into it at all, I'm 
> hypothesizing something like the Garmin using a flag for air/not-air, and 
> assigning the O2% a nonsensical value (null/zero) for air dives.

I have a Garmin Descent Mk2i myself and have done a fair number of air dives 
with it, so I don't believe this is a general issue.
But you may have set things up differently compared to the settings on mine - 
so I'll poke at your .FIT file and find out :)

> Was a little bit of a hassle. Mainly from distraction. I've just come back 
> from a dive trip, where I was downloading the FITs onto my laptop and 
> importing them. Now I'm back home I plugged my Garmin into my desktop and 
> started fighting with Garmin USB. On my desktop I've installed drivers using 
> Zadig to import directly into Subsurface, but now Subsurface is the only 
> thing that works - I can no longer connect to my Garmin using MTP or via 
> Garmin Express. Argh, Why can't Garmin make things that play nice? 

This is more a combination of the libraries that I chose to use for MTP 
communication - since we build across Linux, macOS, and Windows, I went for 
something that supports all three OSs to simplify life - and that one requires 
a different driver on Windows. So it seems a wee bit unfair to blame Garmin. 
That's more a Subsurface issue, to be honest.

/D

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface


Re: Garmin Mk2i - unlikely dive gas

2022-06-13 Thread Mark Stiebel via subsurface
When importing from my Garmin Mk2i, I always get a red error bar on 
the bottom of the Subsurface window:

"unlikely dive gas data from libdivecomputer: o2 = 0 he = 0"


And O2 value of 0 is, admittedly, fairly unlikely, wouldn't you say?

O2 value of zero definitely not going to result in a good dive.

It happens after hitting the "Download" button. In all cases the dive 
computer has been set to Air.  Have not dived nitrox since I've bought 
the Garmin. Have thought about setting to 22% and see what happens, 
but have not go around to that yet.


So this is almost certainly a .FIT file on your device that confuses 
our parser.


Ideally we'd figure out which one it is and have you send us just send 
that one file, but that puts the onus on you, if you don't mind sharing 
the data privately, you could simply put ALL of the .FIT files under 
Garmin/Activity on your Mk2i into a .zip file and send it off list to 
me and then I can figure this out here.
It's all dives, not just particular ones. Well, all air dives anyway. 
Have not confirmed nitrox.  Without having looked into it at all, I'm 
hypothesizing something like the Garmin using a flag for air/not-air, 
and assigning the O2% a nonsensical value (null/zero) for air dives.


Obviously there is a risk that some sort of personal data might be 
included in those .FIT files (I seriously don't know exactly what is 
and isn't included in those... they contain the wildest stuff...), but 
I doubt it will be anything more than information about where you did 
exercises (and what exercises you did) and I really don't care about 
any of those things... but likely this will help us figure out what 
causes that annoying error above.
I'll send you a FIT that I've confirmed raises the error (well, warning) 
off list.


Let me know if you need help how to do this (or if you'd rather figure 
out which .FIT file it is and then only send me that... I'm somewhat 
hopeful that I could walk you through how to do that as well)
Was a little bit of a hassle. Mainly from distraction. I've just come 
back from a dive trip, where I was downloading the FITs onto my laptop 
and importing them. Now I'm back home I plugged my Garmin into my 
desktop and started fighting with Garmin USB. On my desktop I've 
installed drivers using Zadig to import directly into Subsurface, but 
now Subsurface is the only thing that works - I can no longer connect to 
my Garmin using MTP or via Garmin Express. Argh, Why can't Garmin make 
things that play nice?


Mark.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface


Re: Garmin Mk2i - unlikely dive gas

2022-06-12 Thread Dirk Hohndel via subsurface
Hi Mark!

> On Jun 12, 2022, at 3:52 PM, Mark wrote:
> 
> 
> This email has been triggered by your email encouraging users not to ignore 
> or work around errors, but to make them known. So here's one that I've been 
> ignoring for a while.

YAY! Thank you!

> When importing from my Garmin Mk2i, I always get a red error bar on the 
> bottom of the Subsurface window:
> "unlikely dive gas data from libdivecomputer: o2 = 0 he = 0"

And O2 value of 0 is, admittedly, fairly unlikely, wouldn't you say?

> Yes, realise strictly this is libdivecomputer and not subsurface.

No, in this case this is the right place to report it, the Garmin code still 
hasn't been merged upstream in libdivecomputer and is only available via our 
own branch... so this is a Subsurface thing.


> It happens after hitting the "Download" button. In all cases the dive 
> computer has been set to Air.  Have not dived nitrox since I've bought the 
> Garmin. Have thought about setting to 22% and see what happens, but have not 
> go around to that yet.

So this is almost certainly a .FIT file on your device that confuses our parser.

Ideally we'd figure out which one it is and have you send us just send that one 
file, but that puts the onus on you, if you don't mind sharing the data 
privately, you could simply put ALL of the .FIT files under Garmin/Activity on 
your Mk2i into a .zip file and send it off list to me and then I can figure 
this out here.

Obviously there is a risk that some sort of personal data might be included in 
those .FIT files (I seriously don't know exactly what is and isn't included in 
those... they contain the wildest stuff...), but I doubt it will be anything 
more than information about where you did exercises (and what exercises you 
did) and I really don't care about any of those things... but likely this will 
help us figure out what causes that annoying error above.

Let me know if you need help how to do this (or if you'd rather figure out 
which .FIT file it is and then only send me that... I'm somewhat hopeful that I 
could walk you through how to do that as well)

Thanks again for bringing this up!

/D___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface


Garmin Mk2i - unlikely dive gas

2022-06-12 Thread Mark Stiebel via subsurface


Hi Dirk,

This email has been triggered by your email encouraging users not to 
ignore or work around errors, but to make them known. So here's one that 
I've been ignoring for a while.


When importing from my Garmin Mk2i, I always get a red error bar on the 
bottom of the Subsurface window:

"unlikely dive gas data from libdivecomputer: o2 = 0 he = 0"

Yes, realise strictly this is libdivecomputer and not subsurface.

It happens after hitting the "Download" button. In all cases the dive 
computer has been set to Air.  Have not dived nitrox since I've bought 
the Garmin. Have thought about setting to 22% and see what happens, but 
have not go around to that yet.


___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface