Project Space Transportation System 2016

[MarkWatney2015]

I didn't know Discovery made a selfie during STS-64, which gives us a glimpse of its payload bay:

 

[gattispilot]

STS63 with the MIR

I ran into an issue. There is a default dock on the shuttle. I may need to add a NODOCK line. Even though this shuttle had no dock it still docks with the MIR. Or change the code if NO ODS then no dock?

MIR from the Imax camera in the AFT

 

[MarkWatney2015]

Yeah, the shuttles still has a ghost docking port even if ODS is not declared in the scenario. I actually used this advantage for my very old scenario (2020) for STS-88 with a static long ODS mesh long before it is encoded in the project's source code

 

[gattispilot]

Added nodock to the scenario. So no dock is present. So in the scenario. The shuttle can not dock with MIR.

I will put together another zip. I can't tell if the setup of the files in the zip are correct.

 

[gattispilot]

Sts 63 ODEACS released

I make them glow

 

[gattispilot]

RMS light. I think it is wrong but not sure. The camera position and direction is correct. The light seems to be off.

The blue lines seems to show the light direction. I think the red lines should be it.

arm_tip[4] = RMS_EE_LIGHT_POS;
spot_beacon[i].pos = &arm_tip[4];
spotlightRMS = (SpotLight*)AddSpotLight((arm_tip[4]), arm_tip[1] - arm_tip[0], 20, 0.25, 0.8, 0.001, 80.0 * RAD, 80.0 * 1.1 * RAD,diff, spec, amb);
void Atlantis::clbkPreStep(double simt, double simdt, double mjd) ... spot_beacon[8].pos = &arm_tip[4]; spotlightRMS->SetPosition(arm_tip[4]); spotlightRMS->SetDirection(arm_tip[1] - arm_tip[0]);

Beacon in the correct position. But not sure about direction. The code is similar to SSU

 

[gattispilot]

Fixed the RMS light. But found a mesh issue and code issue.

 

[gattispilot]

The image is from STS 63. Working out the details of it.

Here is the latest base shuttle.
STS2016 6.29

I made a Vanilla orbiter and unzipped into it:

open the folder and copied all folders into the main orbiter folder:

Opened a DG scenario and scenario Editor. See the shuttles are listed

Selected a shuttle and then created it

And there she is:

The only things I added was the sts2016 6.29 and MS2015.

For launch scenarios. 3 things are needed. 1 scenario, 2 ini to tell which boosters, shuttle, tank,.... and last guidance file.

In the scenario. You need the launch date and time. Set the MET to -30seconds of launch time. You need to know where it launched from.

Guidance file. -30.000 =orbit(246,274,40.3,-1) -6.0 =engine(0,100,6) 3.0 =engine(100,100,1.00) 30.0 =engine(100,72.00,5.00) 55.0 =engine(72.0,100,5.00) 521.0 =jettison()

This is what I had for STS1

Not sure if the Orbit info is correct.

I believe once the shuttle got launched OMS burns changed the orbit. I don't know if there is a MFD,.... that can do that or the pilot will need to do that?

 

[MarkWatney2015]

I believe once the shuttle got launched OMS burns changed the orbit. I don't know if there is a MFD,.... that can do that or the pilot will need to do that?

The shuttle pilots themselves make the final circularization burns so that the External Tanks doesn't become Skylab-sized space debris in orbit. I think the old GPC MFD from the original ShuttleFleet has an autopilot for this, but I'm not sure. Usually I just manually fire the engines until it matches the orbital parameters written on the Wiki or the SPACEFACTS website

The initial perigee upon MECO always range from 95-104 km in altitude

 

[gattispilot]

Thanks.
So what does the orbit value need to be on the guidance file? Attached is STS 1 flight info.

Now that makes me under how to denote that info maybe in the notes MFD? Like STS 1 final orbit should be 150/150 nm.

 

[MarkWatney2015]

The figure on OMS-1 is near the expected perigee value on MECO (57 miles = 91 km)

 

[gattispilot]

So really the orbit for sts 1 at MECO is 13/80 nm 24.076/148.16. So the orbit should be

-30.000 =orbit(24,148,40.3,-1)

And then somewhere the orbit final is mentioned.

 

[gattispilot]

does the STS 6/29 have the solshuttlehd?

yes.

From SHuttle fleet sts 1
OMS CALLOUT PROFILE 1 TGT_HEADING 90.000 228.0

TGT_HEADING Sets the target heading and apoapsis. is the target heading in degrees. is the target orbit apoapsis in kilometers

OMS When included, changes the thrust vector of the OMS engines such that the add-on “STS-Guidance” can accurately operate to provide rendezvous.

Not sure what the OMS vectors should be.

Right now they are:
th_oms[0] = CreateThruster(THRUSTREF_OMSL, THRUSTDIR_OMSL, ORBITER_OMS_THRUST, ph_oms, ORBITER_OMS_ISP0, ORBITER_OMS_ISP1); th_oms[1] = CreateThruster(THRUSTREF_OMSR, THRUSTDIR_OMSR, ORBITER_OMS_THRUST, ph_oms, ORBITER_OMS_ISP0, ORBITER_OMS_ISP1); // we don't yet define a thruster group for the OMS engines // They will be assigned to the MAIN group as soon as the ET is jettisoned
const VECTOR3 THRUSTDIR_OMSL = { 0.10, -0.23, 0.97 }
// -------------------------------------------------------------- // Enable/disable Orbital Maneuvering System // -------------------------------------------------------------- void Atlantis::EnableOMS(bool enable) { PROPELLANT_HANDLE hProp = (enable ? ph_oms : NULL); for (DWORD i = 0; i < 2; i++) SetThrusterResource(th_oms[i], hProp); if (enable) { if (GetGroupThrusterCount(THGROUP_MAIN) > 2) { // switch MAIN group to OMS DelThrusterGroup(THGROUP_MAIN); thg_main = CreateThrusterGroup(th_oms, 2, THGROUP_MAIN); } SetDefaultPropellantResource(ph_oms); } }
EnableSSME(status < 3); EnableRCS(status == 3); EnableOMS(status == 3);
What I can tell the status value changed based off if ET/SRB were attached. Since using MS2015 status is always 3
CONFIGURATION 3

I can't tell what then switches from SSME to OMS


STS-Guidance looks like it was able to switch orbit automatically

 

[gattispilot]

yes.

From SHuttle fleet sts 1
OMS CALLOUT PROFILE 1 TGT_HEADING 90.000 228.0

TGT_HEADING Sets the target heading and apoapsis. is the target heading in degrees. is the target orbit apoapsis in kilometers

OMS When included, changes the thrust vector of the OMS engines such that the add-on “STS-Guidance” can accurately operate to provide rendezvous.

Not sure what the OMS vectors should be.

Right now they are:
th_oms[0] = CreateThruster(THRUSTREF_OMSL, THRUSTDIR_OMSL, ORBITER_OMS_THRUST, ph_oms, ORBITER_OMS_ISP0, ORBITER_OMS_ISP1); th_oms[1] = CreateThruster(THRUSTREF_OMSR, THRUSTDIR_OMSR, ORBITER_OMS_THRUST, ph_oms, ORBITER_OMS_ISP0, ORBITER_OMS_ISP1); // we don't yet define a thruster group for the OMS engines // They will be assigned to the MAIN group as soon as the ET is jettisoned
const VECTOR3 THRUSTDIR_OMSL = { 0.10, -0.23, 0.97 }
// -------------------------------------------------------------- // Enable/disable Orbital Maneuvering System // -------------------------------------------------------------- void Atlantis::EnableOMS(bool enable) { PROPELLANT_HANDLE hProp = (enable ? ph_oms : NULL); for (DWORD i = 0; i < 2; i++) SetThrusterResource(th_oms[i], hProp); if (enable) { if (GetGroupThrusterCount(THGROUP_MAIN) > 2) { // switch MAIN group to OMS DelThrusterGroup(THGROUP_MAIN); thg_main = CreateThrusterGroup(th_oms, 2, THGROUP_MAIN); } SetDefaultPropellantResource(ph_oms); } }
EnableSSME(status < 3); EnableRCS(status == 3); EnableOMS(status == 3);
What I can tell the status value changed based off if ET/SRB were attached. Since using MS2015 status is always 3
CONFIGURATION 3

I can't tell what then switches from SSME to OMS

But In space only the OMS fire. I guess one uses RCS to point the shuttle and fire OMS. I know the OMS were vectored. so they could fire up/down/left/right,.....

STS-Guidance looks like it was able to switch orbit automatically

STS-guidance doesn't really work in 2016 and maybe with other than SF

 

[MarkWatney2015]

In later Shuttle-ISS missions, the OMS also acted as booster engines for about 2-4 minutes which begin right after SRB separation. But yeah, on all occasions, the OMS were only fired in space as it is ineffective below the Earth's atmosphere

 

[gattispilot]

Thanks. I would be nice if the STS-guidance worked. Code is there.

On the in orbit scenarios. I am using the TLE info and set the time and MET.

The launch ones I just need to know what to put in the guidance.

I need to make an IUS vessel. So that the attachment point will work. Then press a Key and the 2nd stage plus separate. I will attach the 2nd stage as a vessel to the first. then the TDRS scenarios can be done,......

 

[gattispilot]

Writing notes for sts 57
This is the start: EURECA is grappled

Then move it to the Bay

Because of issues the Antenna on the EURECA could not be moved in. I moved the attachment point above it.

Next is to move the rms to get the EVA guy and position over the EURECA and the EVA guy secured the antennas

 

[gattispilot]

Done with EVA and Eureca capture and dock. My biggest dislike is the darkness.

This is what I have for the start of the mission.
STS-57:Shuttle2016BEarly STATUS Orbiting Earth RPOS -5677463.328 -3781016.225 635803.380 RVEL -2319.8769 2308.4931 -6875.0482 AROT -89.470 16.775 -35.520
Date MJD 49162.665185

That should be
GRAPPLE 03/02:50:00

3 days 2 hrs 50 minutes from launch:

Launch date	21 June 1993, 13:07 UTC

So June 24 15:57 UTC


I positioned the shuttle so the most light

By the time I get to the EVA it is dark in the shuttle

Not sure if the orbit is right. Attached is the TLE for sts 57

 

[gattispilot]

UUGGHH

I made a vessel of the IUS. and the same issue. I think it is how the rotation is done.

I think I will use a modified ASE. BUt not all the detail as the gauge. The gauge was based off the real rotational point. But since it is offset,....

 

[gattispilot]

sts 44

Thanks to Gargantua2024 to the Vessel builder version of IUS and DSP1. Solar panels and silver foil are reflective

I can't get the animation of the TDRS to work in VB