• AnarchoSnowPlow
    link
    fedilink
    arrow-up
    34
    ·
    5 months ago

    These should be USB sticks, but otherwise this is preferable to something like wifi.

    You do not want to stop requiring physical access to avionics for updates and reprogramming.

    The fewer surfaces for entry into the avionics systems the better and if that means an engineer schlepping a database update on a thumb drive to the cockpit that’s what you want.

    I spent the better part of a decade on avionics, and while this as a headline sounds bad it’s one of the few things Boeing shouldn’t be mocked for right now.

    • cmnybo@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      14
      ·
      5 months ago

      Boeing could supply virtual floppy drives that take USB drives or SD cards if they wanted to. I’m sure they don’t want to spend the money getting one certified until they are forced to though.

      Floppy disks will continue working fine until the supply of new old stock disks runs out or becomes unreliable.

      • AnarchoSnowPlow
        link
        fedilink
        arrow-up
        6
        ·
        5 months ago

        Certification is expensive. But updated dbs are pretty huge and seem to only get bigger over time. Stuff like radio firmware tends to be in the hundreds of KBs though, so for that it really wouldn’t be a big deal either way.

      • AnarchoSnowPlow
        link
        fedilink
        arrow-up
        11
        ·
        5 months ago

        It doesn’t, that’s just a very common reaction to these types of articles. I recall having some very intense discussions around stuff like iPads in cockpits. I’m on the “not a fan” side, but I’m also not making avionics software anymore either.

          • AnarchoSnowPlow
            link
            fedilink
            arrow-up
            4
            ·
            5 months ago

            It’s not the iPads themselves, it’s the addition of Bluetooth and/or wifi to support them. I agree that they can alleviate a lot in terms of paperwork reduction etc. My issue is the additional exposed surface.

            • deranger@sh.itjust.works
              link
              fedilink
              arrow-up
              2
              ·
              edit-2
              5 months ago

              Wireless isn’t a requirement and connectivity seems slow to be adopted anyhow according to this source.

              https://www.aircraftit.com/articles/data-connectivity-for-efbs-part-2/

              If we agree that connectivity is a good thing, why has the adoption rate been so slow?

              The first required piece is an actual connection between the device and the airplane. This connection can be wired or wireless. It’s now possible to have a wireless access point that’s dedicated to the crew. A wireless connection will need to include security capabilities so users can prove their identity to the wireless network. Let’s not forget that security must also be practical for in-service use. A wired connection is generally seen as more secure, since there has to be physical access from the flight deck, which is considered a secure domain.