> > > ---------- Forwarded message ---------- > From: micha <[email protected]> > To: [email protected] > Cc: > Bcc: > Date: Fri, 10 Nov 2023 08:29:05 +1000 > Subject: Shearwater imports - phantom cylinders when additional gas mixes > are configured > .....snip.... > > At the moment I'm diving Sidemount again, and again having issues with > spurious cylinders due to additional gasses being defined (although > disabled) on my Shearwater computer. Recreationally I dive with 2 > cylinders filled with the same gas mix (typically Air or EAN32), and > both cylinders have a transmitter. I leave my computer in "Tec" mode and > leave the common mixes I use during other dives disabled instead of > deleting them. >
[HH] I dive the same sidemount configuration, Shearwater Teric and Perdix AI set in tech mode, Sidemount AI feature enabled (you didn't mention if that's the case for you). I also dive with a 3rd cylinder (deco) without a transmitter. I define 2 gases for dives with 3 cylinders, so 2 gases are "ON", 1 gas is "ACTIVE". I do a gas switch if diving with 3 tanks near the end of the dive even with no deco obligations Upon import, I see a slightly different issue. Firstly, it assumes that only 1 of my two sidemount tanks has EAN32 (an example) and defaults the 2nd tank to air. That takes a minor edit on the equipment tab on subsurface The gas switch event on Subsurface is switching tank 1 to tank 2 (my 2nd sidemount tank). Using the desktop UI, I switch that to my 3rd deco tank. I do not get unexpected gas switches like you've described when only dive 2 tanks or choose not to switch to my deco bottle. I import my dives into Subsurface using an iPhone. This leads me to guess that the difference between your experience and mine is either the setup in your Shearwater, or the difference in the app you use to download into Subsurface (android for iOS). ......snip...... > I can manually fix the gas mix for Cylinders 1 & 2 using the UI. But > the only way to currently get rid of the phantom Cylinder 3 is by > manually editing the log files and deleting the initial gas change > event. > > > Now, I see several simple approaches to allow the user to fix this using > the Subsurface UI: > > 1. Don't generate the initial "gaschange" event, which is wrong anyway. > (At this stage I'm not entirely sure if this is being sent by the dive > computer, or generated by Subsurface during the import process; still > investigating). Subsurface doesn't seem to need an initial "gaschange" > event to render a dive correctly. > > ............ > I also contacted Shearwater about adding gas status (on/off) to their > protocol, but did not receive a reply. > > Thanks, > - Micha. > >
_______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
