Space Shuttle Avionics: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 5: Line 5:
The avionics of the [[Space Shuttle]] is designed to provide Guidance, Navigation and Control (GNC) through all phases of a mission as well as Systems Management (SM) functions. Like all systems aboard, it is designed with substantial redundancy in mind.
The avionics of the [[Space Shuttle]] is designed to provide Guidance, Navigation and Control (GNC) through all phases of a mission as well as Systems Management (SM) functions. Like all systems aboard, it is designed with substantial redundancy in mind.


At the core of the avionics is the Data Processing System (DPS). In interaction with the DPS, the crew can monitor the status of systems aboard, enter maneuvering targets for the autopilot, re-configure the Digital Autopilots, control mechanical systems such as the payload bay door and perform similar tasks.
At the core of the avionics is the Data Processing System (DPS)<ref>http://history.nasa.gov/computers/Ch4-6.html</ref>. In interaction with the DPS, the crew can monitor the status of systems aboard, enter maneuvering targets for the autopilot, re-configure the Digital Autopilots, control mechanical systems such as the payload bay door and perform similar tasks.


The front-end is primarily implemented using [[Nasal]] and the [[Canvas]] system for 2D rendering purposes. Most of the code can be found in [http://sourceforge.net/p/fgspaceshuttledev/code/ci/development/tree/Nasal/PFD/ Nasal/PFD]. The display is using the MFD framework from the F15 (link).
The front-end is primarily implemented using [[Nasal]] and the [[Canvas]] system for 2D rendering purposes. Most of the code can be found in [http://sourceforge.net/p/fgspaceshuttledev/code/ci/development/tree/Nasal/PFD/ Nasal/PFD]. The display is using the MFD framework from the F15 (link).

Navigation menu