The first question is: How do you detect that a processor has failed? Next question will be: Hardware/Software? Does a reboot of that processor solve the problem and how do you detect if it functions again? How many times should the probe attempt that approach? What other actions can/should the probe take? What kind of messages should the probe send so mission control can determine the problem and possible solution? What if there's no connection with mission control? Should the probe attempt to run the program(s) of the failed processor in another (or a spare?) processor? What information can/should be extracted for a proper fault determination? In case of a faulty program, assigning that same program to another processor would only result in another processor failure. But such a decision would still be taken at mission control. throttling engines and orienting, life support systems, takeoff and return from Mun, etc.) if the processors that were originally supposed to perform them were destroyed or their program was faulty? minor inclination correction, landing leg damper control, light control) will be used to perform important tasks (e.g. You mean that processors that are used for unimportant tasks (e.g. I will be adding some modified parts as well (a universal container as kOS processor f.e.). I probably will remove (parts of those) mods when they're not used to save memory space. Mods which are not essential (but can provide eye candy or might be usefull):Īviationlights - lighting the probe and possibly also as "indicatorlights".Īgext / Modactions - For easy programming specific tasks like opening/closing solarpanels KSP 1.1.3 64 bits - The 64 bits 1.0.0 kOS version works correctly (the 0.21.1 version did not).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |