DiverInSF
Registered
Hoping to get some input on a dive computer problem.
I have an Oceanic Veo 3.0 that's been with me for 200 dives and that's generally in good condition. I just came back from a LOB trip, where we were doing 4-5 dives/day on Nitrox 32. About half way through the trip, my computer started sounding the O2Sat alarm. By the end of dive 2 for that day, I was at 80%. This baffled me and the dive crew b/c I absolutely wasn't pushing the limit on depth or NDL and the EAN setting was confirmed (and reconfirmed) correct. Checked against computers of my dive buddies (similar profile, same Nitrox mix) and their O2 sat was in the 10-15% range. The general consensus is that my computer had gone a bit strange.
Anyone else have this experience? And any thoughts on what to do next? I don't want to toss a perfectly good computer, if the problem can be rectified, but I also want to be able to trust my computer on an extended dive trip.
I have an Oceanic Veo 3.0 that's been with me for 200 dives and that's generally in good condition. I just came back from a LOB trip, where we were doing 4-5 dives/day on Nitrox 32. About half way through the trip, my computer started sounding the O2Sat alarm. By the end of dive 2 for that day, I was at 80%. This baffled me and the dive crew b/c I absolutely wasn't pushing the limit on depth or NDL and the EAN setting was confirmed (and reconfirmed) correct. Checked against computers of my dive buddies (similar profile, same Nitrox mix) and their O2 sat was in the 10-15% range. The general consensus is that my computer had gone a bit strange.
Anyone else have this experience? And any thoughts on what to do next? I don't want to toss a perfectly good computer, if the problem can be rectified, but I also want to be able to trust my computer on an extended dive trip.