Good point. I tend to forget about the ones that I (almost) never see in the wild...
You aren't wild enough. You need to get out of your shell more often.
Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.
Benefits of registering include
Good point. I tend to forget about the ones that I (almost) never see in the wild...
I respectfully disagree.@arkstorm Unfortunately, a poll on SB would be subject to selection bias and recall bias and not give me objective unbiased data. I'm sure it would be interesting, however.
I would propose to define a failure as any situation which caused the diver to be unable to ascertain their remaining tank pressure for the remainder of the dive. I realize that would include computer failure if using a transmitter but that is ok because that is one of the failure points when using hoseless ai.You also need to consider that the average age of SPGs on people's gear is likely older than the age of transmitters. Furthermore, do you consider a battery dying on a dive a failure? Or is it user error. What about a hp spool with a slight leak? What if a computer dies underwater? Do you count that?
I would propose to define a failure as any situation which caused the diver to be unable to ascertain their remaining tank pressure for the remainder of the dive. I realize that would include computer failure if using a transmitter but that is ok because that is one of the failure points when using hoseless ai.
Exactly. Makes no sense. I can understand alerting if the connection is lost, but to require intervention to display after connection is restored is useless. The log should record that the COMMS were lost at various points, so you’d be able to see if something was causing interference.That is a terrible feature.