paulraymaekers
Active Member
yes, I'll give that presentation at A.I.R Bali
paul
paul
I see no reason to not check your cells at 6 meters at the beginning of a dive in addition to later in the dive. If they fail at the beginning, the dive needs to be aborted regardless of any cell reaction later during the dive. In other words, if they fail at any point during the dive, it's time to abort the dive and replace the cells. I understand Paul's reasoning in wanting to check the cells at later points throughout the dive, but feel that it is also important to verify functionality at the beginning as well.
You've already calibrated, so you already know your cells read 1.0 PPO at some given mv.
AFAIK, the only way you could get a reading of 1.6 and a real PPO of 2.2, would be some sort of horrifically non linear cell performance past 1.0 that wouldn't show as current limited. I'll have to leave that possibility to the experts on sensors. And that would also assume all 3 sensors failed the same non linear way, so I wouldn't have some idea something wanky was going on.
Now I do know that sometimes a cell will flare high before failing (My instructor had this happen to him), but that's the opposite where PPO was lower, and cell read high.
Ken,I think the bigger problem that Josh may have been getting at is that adding O2 just to spike cells without knowing the exact gas in the loop doesn't really tell you much about cell health other than they might be able to reach 1.6. But maybe they are reading 1.6 when the actual loop is actually at a very dangerous 3.0. Pumping in O2 just to get a high cell reading isn't smart. Cells are batteries and can act funny. Current limiting doesn't necessarily mean it is impossible to get a 1.6 reading; only that it won't get that reading at 1.6. And even if your cell turns out to be so limited that it won't reach 1.6, how do you know you haven't increased your pO2 to a dangerous level trying to spike it?
iPhone. iTypo. iApologize.
our experience is that sensors with different dive history, age, heat exposure, pressure cycling etc, react in a different way to sudden 'events.But there you're assuming that, by cycling cells, they won't fail simultaneously. Which is fine for normal deterioration but, if an event of some kind (heat, drowning, prolonged exposure to pure O2 etc) affects all cells to the point where two or more fail simultaneously? The whole "Rotate cells and you'll be fine" approach has lulled you into an assumption that everything's fine because the cells all read the same.
Most of the time, a good approach. But not necessarily the best of "habits" to get into, perhaps.
I think the bigger problem that Josh may have been getting at is that adding O2 just to spike cells without knowing the exact gas in the loop doesn't really tell you much about cell health other than they might be able to reach 1.6. But maybe they are reading 1.6 when the actual loop is actually at a very dangerous 3.0. Pumping in O2 just to get a high cell reading isn't smart. Cells are batteries and can act funny. Current limiting doesn't necessarily mean it is impossible to get a 1.6 reading; only that it won't get that reading at 1.6. And even if your cell turns out to be so limited that it won't reach 1.6, how do you know you haven't increased your pO2 to a dangerous level trying to spike it?
our experience is that sensors with different dive history, age, heat exposure, pressure cycling etc, react in a different way to sudden 'events.
an event that is so dramatic that it will change the behaviour of 4 / 5 sensors that have all different history, in exactly the same way... is unlikely not to be noticed before that dive, during the predive / prejump check
.....but I think simply relying on a change interval to the exclusion of everything else is asking for trouble.
I have and have played with a cell-checker - it's perhaps the most non-useful piece of kit I have - I've tried known knackered cells that pass a "quick test" and I've tested cells that work fine that show non-linearity (due to the completely inadequate pressure gauge on the one I have). Folks swear by them, I'd rather check my cells in a pond.
Matt.
After any break from diving I go to a pond and check them at the end of the dive, 8m, 1.6+. I've found that cells under 18 months from manufacture that show 0.21 with the lid off, have the same end-cal-value (Inspo) as previous and can reach 1.6+ at the end of the dive do not give trouble. Any variation is to be watched during the dive. Matt.
That's what I do, but there are many alternatives. I have and have played with a cell-checker - it's perhaps the most non-useful piece of kit I have - I've tried known knackered cells that pass a "quick test" and I've tested cells that work fine that show non-linearity (due to the completely inadequate pressure gauge on the one I have). Folks swear by them, I'd rather check my cells in a pond.
Matt.
Your lucky a mate of mine is yet to get out the pond with 3 cells still working, they were brand new when he got in ! Guess who's
I have one & I use it occasionally but by no means swear by it, it is a small tool in a big locker. I have 8 cells in total to worry about so am not going to throw any away needlessly !
Not really - it doesn't provide any information other than at the start of the dive they read over 1.6 which has no impact later in the dive so it lures you into a false sense of security that the cells must be OK as I tested them at start of dive. All of these spikes and pots do nothing except verify cell function at time (and conditions / duration) and not the most important time, ie on the dive, you'd be much better off just throwing cells away 1 year after manufacture.
I see no reason to not check your cells at 6 meters at the beginning of a dive in addition to later in the dive. If they fail at the beginning, the dive needs to be aborted regardless of any cell reaction later during the dive. In other words, if they fail at any point during the dive, it's time to abort the dive and replace the cells. I understand Paul's reasoning in wanting to check the cells at later points throughout the dive, but feel that it is also important to verify functionality at the beginning as well.
Randy can you confirm or deny if this is supposed to be part of Hammerhead user training?
Thanks.