SSU Space Launch Complex 6 development

[SiameseCat]

I'll take a look.

---------- Post added at 08:39 PM ---------- Previous post was at 04:50 PM ----------

Autopilot should be fixed now. BTW, the texture used in the STS-62A mission file hasn't been checked in - the shuttle is untextured.

 

[DaveS]

I'll take a look.

---------- Post added at 08:39 PM ---------- Previous post was at 04:50 PM ----------

Autopilot should be fixed now. BTW, the texture used in the STS-62A mission file hasn't been checked in - the shuttle is untextured.

The texture has been checked in. And thanks for fixing the autopilot.

---------- Post added at 01:41 PM ---------- Previous post was at 08:25 AM ----------

Could the PCR, MAS and MST be made part of the main SLC-6 vessel? Here's the code for animation of the MAS rear panels:

[ANIM_COMP_0]
;Door panel#7
SEQ=0
GROUPS=9
TYPE=TRANSLATE
RANGE=(0,1)
SHIFT=(0,52.3,0)

[ANIM_COMP_1]
;Door panel#6
SEQ=0
GROUPS=10
TYPE=TRANSLATE
RANGE=(0.142,1)
SHIFT=(0,44.83,0)

[ANIM_COMP_2]
;Door panel#5
SEQ=0
GROUPS=11
TYPE=TRANSLATE
RANGE=(0.284,1)
SHIFT=(0,37.36,0)

[ANIM_COMP_3]
;Door panel#4
SEQ=0
GROUPS=12
TYPE=TRANSLATE
RANGE=(0.426,1)
SHIFT=(0,29.88,0)

[ANIM_COMP_4]
;Door panel#3
SEQ=0
GROUPS=13
TYPE=TRANSLATE
RANGE=(0.568,1)
SHIFT=(0,22.41,0)

[ANIM_COMP_5]
;Door panel#2
SEQ=0
GROUPS=14
TYPE=TRANSLATE
RANGE=(0.71,1)
SHIFT=(0,14.94,0)

[ANIM_COMP_6]
;Door panel#1
SEQ=0
GROUPS=15
TYPE=TRANSLATE
RANGE=(0.852,1)
SHIFT=(0,7.47,0)

Here's photo that shows the MST in the stacking position around the Launch Mount:

 

[SiameseCat]

I'll do this when I have the time.

 

[SiameseCat]

DaveS, I just noticed the changes you made to the SLC6 project file. Are these actually needed? On my computer, the stdafx.h file isn't included at all, and I don't get any compile errors.

 

[DaveS]

Just checking here: Is any body besides me not having any manual rotation RCS control of the orbiter following ET sep in the SLC-6 test scenario? Translational controls work fine, but the rotational controls are dead.

 

[SiameseCat]

The texture has been checked in. And thanks for fixing the autopilot.

---------- Post added at 01:41 PM ---------- Previous post was at 08:25 AM ----------

Could the PCR, MAS and MST be made part of the main SLC-6 vessel? Here's the code for animation of the MAS rear panels:

[ANIM_COMP_0]
;Door panel#7
SEQ=0
GROUPS=9
TYPE=TRANSLATE
RANGE=(0,1)
SHIFT=(0,52.3,0)

[ANIM_COMP_1]
;Door panel#6
SEQ=0
GROUPS=10
TYPE=TRANSLATE
RANGE=(0.142,1)
SHIFT=(0,44.83,0)

[ANIM_COMP_2]
;Door panel#5
SEQ=0
GROUPS=11
TYPE=TRANSLATE
RANGE=(0.284,1)
SHIFT=(0,37.36,0)

[ANIM_COMP_3]
;Door panel#4
SEQ=0
GROUPS=12
TYPE=TRANSLATE
RANGE=(0.426,1)
SHIFT=(0,29.88,0)

[ANIM_COMP_4]
;Door panel#3
SEQ=0
GROUPS=13
TYPE=TRANSLATE
RANGE=(0.568,1)
SHIFT=(0,22.41,0)

[ANIM_COMP_5]
;Door panel#2
SEQ=0
GROUPS=14
TYPE=TRANSLATE
RANGE=(0.71,1)
SHIFT=(0,14.94,0)

[ANIM_COMP_6]
;Door panel#1
SEQ=0
GROUPS=15
TYPE=TRANSLATE
RANGE=(0.852,1)
SHIFT=(0,7.47,0)

Here's photo that shows the MST in the stacking position around the Launch Mount:

Done.

I'm not sure how long each element takes to move, so you might want to change the SLC6_XXX_TRANSLATE_RATE values in SLC6.h.

 

[DaveS]

Done.

I'm not sure how long each element takes to move, so you might want to change the SLC6_XXX_TRANSLATE_RATE values in SLC6.h.

Thanks for adding this. Could change the texture used for the ROFIs on both KSC LC-39 MLP and the SLC-6 LM? The default contrail2.dds texture is more appropriate instead of the current white one.

 

[DaveS]

Just checking here: Is any body besides me not having any manual rotation RCS control of the orbiter following ET sep in the SLC-6 test scenario? Translational controls work fine, but the rotational controls are dead.

Just bumping this one. Also, I think there's something wrong with the FWC code. It seems the performance is really low, keep hitting Low-Level Cut-Offs(LLCOs) instead of guidance commanded cut-offs and that is with no payload whatsoever.

Checked in a updated STS-62A mission file which has the correct inclination(72.5°).

 

[DaveS]

I have done some research and according to the STS News Reference Manual, the payload to a 201 kmX201 kmX68° orbit from Vandenberg is 22,230 kg.

So there really is a performance problem with SSU from Vandenberg AFB.

 

[Urwumpe]

I have done some research and according to the STS News Reference Manual, the payload to a 201 kmX201 kmX68° orbit from Vandenberg is 219336 kg.

Even in lb, this number would be an outstanding performance of the Space Shuttle. Is there a digit duplicated or the decimal missing?

 

[DaveS]

Even in lb, this number would be an outstanding performance of the Space Shuttle. Is there a digit duplicated or the decimal missing?

It's supposed to be 22,230 kg. I used the wrong pound for the calculation(lbf vs lbs). Thanks for catching it for me.

 

[SiameseCat]

I have done some research and according to the STS News Reference Manual, the payload to a 201 kmX201 kmX68° orbit from Vandenberg is 22,230 kg.

So there really is a performance problem with SSU from Vandenberg AFB.

The FWC code was using the mass of the regular boosters; a fixed version has been checked in.

Do you know what throttle setting was being used? IIRC, 109% thrust was to be used for some of the Vandenberg missions. This might explain any remaining performance issues.

---------- Post added at 11:51 PM ---------- Previous post was at 11:50 PM ----------

Just checking here: Is any body besides me not having any manual rotation RCS control of the orbiter following ET sep in the SLC-6 test scenario? Translational controls work fine, but the rotational controls are dead.

I can confirm this problem.

 

[DaveS]

A couple of noticed omissions:

• No GOX venting from the GOX Vent Arm
• No lights at the pad
• No TSM T0 carrier plate animations

 

[SiameseCat]

Just checking here: Is any body besides me not having any manual rotation RCS control of the orbiter following ET sep in the SLC-6 test scenario? Translational controls work fine, but the rotational controls are dead.

This should also be fixed now.

 

[DaveS]

This should also be fixed now.

Will check it out. Is there a way to set up the ascent autopilot to use a descending node trajectory instead of the standard ascending node trajectory?

 

[SiameseCat]

Will check it out. Is there a way to set up the ascent autopilot to use a descending node trajectory instead of the standard ascending node trajectory?

No, but I could add it. What do you need this for? AFAIK, the autopilot already chooses the correct headings for both KSC and VAFB.

 

[DaveS]

No, but I could add it. What do you need this for? AFAIK, the autopilot already chooses the correct headings for both KSC and VAFB.

It doesn't. Launches from Vandenberg AFB head south(descending node), not north/northeast like launches from KSC.

So if I specify 72.5°s as the inclination in the mission file, the vehicle heads north, not south out over the Pacific as it should.

 

[SiameseCat]

Thanks. The autopilot code currently assumes that any inclination less than 90 is from KSC, and anything greater than 90 is a VAFB launch. I'll revise the inclination limits.

 

[Donamy]

Couldn't you try 139 deg ?

 

[DaveS]

Thanks. The autopilot code currently assumes that any inclination less than 90 is from KSC, and anything greater than 90 is a VAFB launch. I'll revise the inclination limits.

I think it would be best to change the limits to 57° for KSC(maximum allowed from KSC).