CDU Self-Test Failed
-
First post-SU3 flight in the Starship. High ground temperatures at Ashgabat made it very hot in the cabin (140F!) until I got the engines and AC going. It was so hot that both engines went into the red briefly on startup but surprisingly suffered no damage. All was good until about 25 minutes into the flight when the co-pilot CDU suddenly displayed "Self-Test Failed". No faults indicated on the tablet or the avionics status page on the MFD. Temps at the time were 95F in the avionics bay, 90 behind the panel, and 76 in the cabin. Cycling the copilot avionics switch cleared it up, and there were no issues for the remainder of the flight.
-
@Black-Square any thoughts on what might cause the CDU to report a self-test failure during flight?
-
Looking at the code, the only condition that is intended to cause a self-test-failed screen after everything is powered up is a loss of power to the copilot's FMS computer. Beyond that... I guess just let me know if it happens again. There was a bug early on that could have caused this on startup if the pilot's CDU didn't initialize first, but I think that was fixed before v1.0.
-
I think I had this once when I was running up with an ambient temperature above 40ºC (104ºF). After the avionics bay overheated, the message was shown. After shutting the avionics down for some minutes, it cooled enough to resume operations and get airborne.
