dherbman:
I'll second that sentiment. In addition to issues posted
here, I was reviewing a dive from a couple of weeks ago with the DM software and it indicates that I blew off 7 minutes of deco. It also says I went several minutes at depth without my air pressure changing. It's possible that the download was corrupted. I'll look into it further and post what I discover.
The sample times of the computer are shorter than the sample times for storing your profile data to memory (for downloading later). The dive computer is calculating your tissue saturation based upon the actual profile data. SDM is attempting to simulate your Cobra's calculation based upon a much smaller and granular profile sample.
As a result, when you get
close (subjective definition) to NDL limits with the Cobra, the computer may calculate that you are within the limit, but SDM may show it as a deco obligation.
I have never been too concerned with the deco information generated by SDM as it is a simulation of the Cobra, not the Cobra itself. The primary feature of the software is that it allows me to log my dive and review my profile for 1) shape and 2) ascent rate violations. These are important to me as they are skills that I can develop as a diver, i.e. improve the profile of my dive and control my ascent rate to avoid "undeserved" (or whatever they are called these days) hits. I cannot convince SDM that I was a good boy on the dive, so I don't let it worry me too much
. Given that it is a simulation, the tissue saturation graph and deco information is
interesting, but not critical (to me, at least).
The issue with the air pressure is interesting. I will have a look at my profiles and see if I have had a similar issue. I am wondering, though, whether this information is calculated/interpolated from the download data or actually downloaded from the Cobra. I'll check it out.
Ok, I'm back (that was quick!). I checked out
this site for the protocol, and it appears that the air consumption is calculated (only starting pressure and end pressure is transferred). So it looks like it may be a bug in SDM. Maybe.
Cheers,
Andrew