- The pilots and instructor inside the cabin manipulate controls/switches/CBs/panels, sending signals to an bunch of interface cards.
- The interface cards convert voltages to values, and move them into a big chunk of shared memory on the host computer.
- The host computer recalculates the new state of the simulation, updating everything in the shared memory, 60 times a second.
- New values in the shared memory are sent to the interface cards.
- The interface cards convert values to voltages, driving the instruments, sound, visual and motion systems.
It all happens so fast that the pilots never sense the latency between their action and the effects in the cockpit. The host computer is the brain of the system, that's why a small bug there can be dangerous.
When they tried it in the sim, both of them were similarly thrown around and a terrified few seconds as neither were able to reach the panic button :-)
Most memorable event on the factory floor was when a hydraulic jack failed on a sim, and the resulting jet of fluid punched a hole through six layers of hand wire-wrapped PCBs on the sim next door.
I think it put them back six weeks. Luckily the penalty clause for lateness was only $50,000 per day. Gulp.
Here's what the simulators look like: http://blafsen.net/photos/simulator.jpg
I changed the code, and brought the simulator up on motion to test it... and the machine started bucking like a horse and tossing me around the cabin. I had the instructor console right in front of me, and for a while it was physically impossible to hit the freeze button - I was being tossed around too badly.
That day I learned a lesson about testing: first check it with motion OFF.