Space Shuttle Avionics: Difference between revisions

Jump to navigation Jump to search
Line 253: Line 253:


Many options are at least semi-quantitatively implemented in FG, i.e. filters will show residuals which allow to gauge their quality and can be used to update the state vectors, but there's no real simulation of the filter matrix done, the simulation just assigns a filter quality measuring how close to the true state of the craft a filter leads.
Many options are at least semi-quantitatively implemented in FG, i.e. filters will show residuals which allow to gauge their quality and can be used to update the state vectors, but there's no real simulation of the filter matrix done, the simulation just assigns a filter quality measuring how close to the true state of the craft a filter leads.
=== ORBIT TGT (SPEC 34) ===
[[File:Shuttle avionics spec34.jpg|600px|ORBIT TGT display of the Space Shuttle]]
While usually mission control would perform such tasks and uplink the results, the Shuttle has an on-board computer for calculating burn sequences to reach orbital targets. This functionality is controlled via SPEC 34.
The display allows to compute a sequence of two OMS burns (T1 and T2) that will bring the Shuttle close to a target such that rendezvous navigation (SPEC 33) can be used (the difference being that SPEC 34 assumes you are far from the target and orbital mechanics effects are important to reach it, while SPEC 33 assumes you are so close to the target that translational RCS burns are all that is needed).
As of June 2016, the implementation in FG supports a quasi-Hohmann transfer computation. From a lower, reasonably circular orbit, item 28 calls a numerical trajectory solver which fits burn parameters to reach the target. The results are stored as PEG-7 targets and can directly be used in the MNVR display. Most other options to tweak the T1 and T2 targets are currently not supported.


=== HORIZ SIT (SPEC 50) ===
=== HORIZ SIT (SPEC 50) ===
1,360

edits

Navigation menu