3 ms·
For stuff like positional and airspeed information, it would not be difficult to design a connection that is physically limited to one-way communication. It wo
by sjwright 12y ago
For stuff like positional and airspeed information, it would not be difficult to design a connection that is physically limited to one-way communication.
It would also seem sensible that any interaction the pilots might want to perform on the cabin computer systems could be done by giving them a terminal on that network.
- com2kid 12y agoFor some stuff that did have data sharing there was a very tightly controlled pipe. Oddly enough it was Linux on one side and Windows on the other. The level of scrutiny that IPC (inter-processor communication) channel got was insane. It is probably one of the safest IPC channels in existence! Unfortunately I didn't fully grasp what systems it was connecting, aviation is full of its own parallel set of jagon that I didn't fully learn in my short time at Boeing!
- sjwright 12y ago> Oddly enough it was Linux on one side and Windows on the other. Doesn't sound at all odd -- quite sensible actually. Though I would probably have suggested a pairing more along the lines of OpenBSD/x64 and Linux/ARM or some-such. It depends on what the remainder of the systems is using. This is a perfect example of where ecosystem diversity is a Good Thing.