Info Important Msg from Shearwater re Tern/Tern TX

Please register or login

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

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

Well that's a pretty f**king big fumble! Who's testing this software and I hope they're fired already!

The firmware update is out now btw TERN TX SUPPORT
LOL. Yeah, it would be nice if every product were perfect when released. At least Shearwater owned up to the error and fixed it, unlike some other dive computer manufacturers.
I'll bet that the majority of Tern/TernTX users were using Nitrox anyway.
 
Obviously all software contains bugs, but that's why we have QA/QC departments.

This strikes me as a regression bug introduced by the recent addition of Avelo capabilities (for all 10 of the Avelo divers worldwide). All I ask is that extremely fundamental functionality regarding gas settings, which should be perfect on day 1, remains perfect thanks to adequate QA/QC. Whoever let this slip by is simply not doing their job and should be replaced immediately.

I dive a Tern TX, and have done at least 12 dives locally in the 3 months that this bug was in the wild. I dive 50/90 and my Nitrox settings were 32% EAN left over from a vacation dive. Thankfully my local dives bottom out around 25m to 30m so any deco obligations thanks to the understated NDLs will have been minimal. Others might not be so fortunate.
 
I'm sorry you got caught by this, and I'm glad it did not hurt you.
 
I’m using a tern tx and a peregrine tx, never really noticed a difference but I run 40/85 so not really cutting it close.
 
Obviously all software contains bugs, but that's why we have QA/QC departments.

This strikes me as a regression bug introduced by the recent addition of Avelo capabilities (for those precious 10 Avelo divers worldwide). All I ask is that extremely fundamental functionality regarding gas settings, which should be perfect on day 1, remains perfect thanks to adequate QA/QC. Whoever let this slip by is simply not doing their job and should be replaced immediately.

I agree with much of what you say, EXCEPT for the assumed need to replace anyone. Having worked in software my entire adult life, I know firsthand that sometimes things happen that are not due to the negligence of any one person. Sometimes processes break or are not working as well as we believed they were. Shearwater needs to identify what caused this bug to be released without being identified (root cause analysis), fix the problem and ensure it is prevented in the future (CAPA ... corrective action/preventive action). IF it was due to someone being negligent, then by all means replace them. But if not, fix the process.
 
I’m using a tern tx and a peregrine tx, never really noticed a difference but I run 40/85 so not really cutting it close.
Are you diving air? Otherwise there would be nothing to notice....
 
I agree with much of what you say, EXCEPT for the assumed need to replace anyone. Having worked in software my entire adult life, I know firsthand that somethings things happen that are not due to the negligence of any one person. Sometimes processes break or are not working as well as we believed they were. Shearwater needs to identify what caused this bug to be released without being identified (root cause analysis), fix the problem and ensure it is prevented in the future (CAPA ... corrective action/preventive action). IF it was due to someone being negligent, then by all means replace them. But if not, fix the process.
That's fair, but these computers aren't far off being life-support systems, so I'd expect a much greater emphasis on correct function than for e.g. some webapp. Maybe a "brutally stern talking-to" would be more appropriate....

It _is_ though, nice to see Shearwater owning up and fixing the issue relatively promptly.
 
Back
Top Bottom