Shuttle FDO MFD

New release:

-Extensive internal reorganization of the Orbital Maneuver Processor. Not a lot of new features, but implementing some stuff that will make it possible to add the remaining features (e.g. taking drag into account).
-More user friendly inputs and displays of the OMP. It should be a lot nicer now to add and modify inputs on the Maneuver Contraints Table.
-Updated manual and small bug fixes. Especially the OMP walkthrough was a bit outdated for the actual workflow in the MFD.

Orbiter 2024: https://github.com/indy91/Shuttle-F...6.0-alpha-O2024/ShuttleFDOMFD_O2024_0.6.0.zip
 
  • Hailprobe
Reactions: GLS
Is a mission file required for the FDOMFD to work with the SSV?
 
Is a mission file required for the FDOMFD to work with the SSV?
In the FDOMFD you need to create a configuration file, so it can save the launch time, target name, rendezvous profile, etc, but that has no relationship to the SSV mission files.
 
New release:

The main new feature is "Supersighter", a display the flight controllers could use in the MOCR for various attitude and pointing calculations. The FDO Console Handbook has procedures that make use of it for IUS and PAM deployments, among other things.

1777989197021.png

Also added are a few displays in support of Supersighter, like lnstrument definitions, and the Checkout Monitor, another display used as part of calculations for deploying an upper stage.

 
Couple of general questions.

What are some reasons one of the early NC burns will put the chaser higher than the target, then calculate a later large retrograde phasing burn?

What are some reasons the calculated NPC burn doesn't fully correct the rINC between the chaser and the target?
 
What are some reasons one of the early NC burns will put the chaser higher than the target, then calculate a later large retrograde phasing burn?

Then the rendezvous plan doesn't really work out for the specific orbits and phase angle. Either have to use a different plan or it needs some adjustments (e.g. number of orbits between some maneuvers).

What are some reasons the calculated NPC burn doesn't fully correct the rINC between the chaser and the target?

If you are using spherical gravity then they should be the same. With non-spherical gravity it's partially the required difference in LAN that I talked about in the SSV thread. The NPC burn still needs to target that as well. But it's also that the orbital elements of both Shuttle and target are constantly wobbling around from the non-spherical gravity. Only at position match (if the target was directly above the Shuttle in its orbit) would that difference be zero. So hopefully orbital mechanics are taking over after NPC and are nulling the RInc on its own. After NPC got deleted from the plan, you can tell by the DVY components of TI and MC4 if the orbits are properly aligned or not.
 
Then the rendezvous plan doesn't really work out for the specific orbits and phase angle. Either have to use a different plan or it needs some adjustments (e.g. number of orbits between some maneuvers).
By plan, do you mean the generic plans A thru D?
If you are using spherical gravity then they should be the same. With non-spherical gravity it's partially the required difference in LAN that I talked about in the SSV thread. The NPC burn still needs to target that as well. But it's also that the orbital elements of both Shuttle and target are constantly wobbling around from the non-spherical gravity. Only at position match (if the target was directly above the Shuttle in its orbit) would that difference be zero. So hopefully orbital mechanics are taking over after NPC and are nulling the RInc on its own. After NPC got deleted from the plan, you can tell by the DVY components of TI and MC4 if the orbits are properly aligned or not.
Based on a previous question I had asked, I'm now using non-spherical gravity for both the sim and the FDOMFD. Great explanation about the RInc. I'll have to digest that for a bit and think it through. Appreciate the answers. o7
 
Back
Top