• Saik0A
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days ago

    Well duh? I’ve read the reports. I mean that maybe they went too deep because the controller died. Eg, dude holds button that tells controllers to go deeper. Controller dies… Sub just takes last input and keeps going deeper until it hits the catastrophic depth.

    Guy was an idiot for sure, I just wonder if the controller played ANY role at all.

    • theneverfox@pawb.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 days ago

      It seems unlikely… The vessel wasn’t up to the challenge of anywhere near that depth, and they intended to go that deep from the get go.

      I mean, it could be, but Bluetooth shouldn’t work like that - it’s a digital signal with a bunch of failure modes in the spec. You’d have to code it particularly stupidly to have that kind of problem - it’s a very time-synched protocol, even a sudden disconnect with no disconnect signal is something a coder would have to confront explicitly if they were using off the shelf components

      I’m not one to bet against bad code, but the decompression seemed to be pretty much instant and within the planned trip, it just seems like it doesn’t survive oscams razor

    • bstix@feddit.dk
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      The plan was to go to the Titanic, which is on the bottom of the sea. Controller malfunction or not, the hull was the issue.