So I bought two DG03s to use as bottom timers on deco dives.
Have these things happened to anyone else? Given that I'm in the middle of nowhere and it would be stupidly expensive/a lot of hassle to return the things I'm probably not going to pester Hollis over it, unless it's happening to loads of people.
One of them has decided that, despite the fact that I'm all of three feet above sea level as I sit here, it's at altitude setting 2 - sometimes even 3. This then gives me inaccurate readings at depth, which is mildly annoying as I then have to cross-check it with my other computer or bottom timer or do the maths to work out my actual depth.
More worryingly, I discovered last week, when using the other DG03 in computer mode on a deco dive, that there seems to be a serious bug in the programming. Approaching the end of my deco on a dive that V-Planner showed as using less than 50% of allowable CNS exposure, the computer decided I had exceeded pO2 limits and ordered me to the surface - despite the fact that it had, until that point, been showing 9 minutes of deco remaining. As soon as the pO2 warning went off, the deco immediately cleared.
I get that I was pushing the boundaries of what the computer was designed for (a 48metre dive with 52 minutes of decompression, calculated using VPM-B at +2), but it's a little scary that it just forgets a reasonable amount of deco time as soon as it - incorrectly - decides oxygen time has been exceeded.
Am I just unlucky, or is this a general issue?
Have these things happened to anyone else? Given that I'm in the middle of nowhere and it would be stupidly expensive/a lot of hassle to return the things I'm probably not going to pester Hollis over it, unless it's happening to loads of people.
One of them has decided that, despite the fact that I'm all of three feet above sea level as I sit here, it's at altitude setting 2 - sometimes even 3. This then gives me inaccurate readings at depth, which is mildly annoying as I then have to cross-check it with my other computer or bottom timer or do the maths to work out my actual depth.
More worryingly, I discovered last week, when using the other DG03 in computer mode on a deco dive, that there seems to be a serious bug in the programming. Approaching the end of my deco on a dive that V-Planner showed as using less than 50% of allowable CNS exposure, the computer decided I had exceeded pO2 limits and ordered me to the surface - despite the fact that it had, until that point, been showing 9 minutes of deco remaining. As soon as the pO2 warning went off, the deco immediately cleared.
I get that I was pushing the boundaries of what the computer was designed for (a 48metre dive with 52 minutes of decompression, calculated using VPM-B at +2), but it's a little scary that it just forgets a reasonable amount of deco time as soon as it - incorrectly - decides oxygen time has been exceeded.
Am I just unlucky, or is this a general issue?
