SSU Development Thread (2.0 to 3.0)

Status
Not open for further replies.
Yes, attachments are fully user-defined in their run-time behavior - you can have a IUS at ANY other attachment in the scenario file, if you want it so.

Any preference of where those checks will be made (upper stage vessel vs SSU subsystem)?
 
Any preference of where those checks will be made (upper stage vessel vs SSU subsystem)?

I think that attachments should be part of the Atlantis class. Maybe we should make a smoke test in clbkPostCreation to test if the attachments are all valid, after loading a scenario.

For runtime changes (like installing a IUS into SSU in the RSS), the check should be delegated in a sane way to the subsystem, since even attachments with valid ID might be illegal at a point.
 
I think that attachments should be part of the Atlantis class. Maybe we should make a smoke test in clbkPostCreation to test if the attachments are all valid, after loading a scenario.

For runtime changes (like installing a IUS into SSU in the RSS), the check should be delegated in a sane way to the subsystem, since even attachments with valid ID might be illegal at a point.

Then it probably should go in the trunk, and maybe wait until after the release. If I forget to do it, somebody remind me please.
 
Then it probably should go in the trunk, and maybe wait until after the release. If I forget to do it, somebody remind me please.

Its no urgent problem, who creates an illegal scenario deserves to be punished. :lol:

But the mission editor should of course produce legal scenarios.
 
I know I'll be shot for asking this so late, but could this external airlock "spacer/EVA hatch" be added?
9461087260_af86f291d7_h.jpg
KSC-95EC-1615.jpg

STS-118_approaching_ISS.jpg


IMO there's a strong case for having it forward of the airlock (for STS-74 and 88, top images), as without it the RMS probably can't dock Unity/DM to the ODS. As for the "aft" version for EVA access, we could leave it for addon devs for now, but we should consider also having the capability to add it.
 
The "spacer" is called the Tunnel Adapter Assembly (TAA) and was first used on STS-9. It is 2.1336 m (84") long and has an inside diameter of 1.6 m (63").
 
I have one I did for my STS-88 mission. I could make it available for SSU.
 
I have one I did for my STS-88 mission. I could make it available for SSU.

Is it to scale? If yes, than there could be done support for it analog to the Airlock/ODS.

For the 4.0 version... do you also have the insides of tunnel and airlock? maybe we could combine this with a Spacelab interior to extend the middeck a bit...

Would be a rather cheap feature compared to the other ones.
 
Is it to scale? If yes, than there could be done support for it analog to the Airlock/ODS.

For the 4.0 version... do you also have the insides of tunnel and airlock? maybe we could combine this with a Spacelab interior to extend the middeck a bit...

Would be a rather cheap feature compared to the other ones.

An mission file option for turning this on, and maybe another for choosing the placement would be enough for now.
 
An mission file option for turning this on, and maybe another for choosing the placement would be enough for now.

For now is until August 18. I already try to gather tickets for the next iteration, which will come.
 
I'd be interested in seeing how all this turns out after the events of late. But I am pleased it's making forward progress. Please by all means keep up the great work. Don is a very generous man, and the adapter is a fine work.

The comments above remind me of a line...

"Don't touch that please, your primitive intellect wouldn't understand alloys and compositions and things with... molecular structures." ~Ash, Army of Darkness.

A line which has no specific meaning or application here, just a random memory.
 
For now is until August 18. I already try to gather tickets for the next iteration, which will come.

For me the next version should be (in order of importance):
>> 2015 upgrade (if it comes out)
>> mission editor
>> ET or SRB mesh corrections so they match
>> add upper stages (at least IUS and Centaur)
>> dps upgrades (do away with CRTMFD, common memory, displays)
>> upgrade all talkbacks and lights
 
For me the next version should be (in order of importance):
>> 2015 upgrade (if it comes out)
>> mission editor
>> ET or SRB mesh corrections so they match
>> add upper stages (at least IUS and Centaur)
>> dps upgrades (do away with CRTMFD, common memory, displays)
>> upgrade all talkbacks and lights

I agree absolutely there. I would also include ALL upper stages that flew into the version, simply to have it done. The PAMs are much simpler than the IUS or Centaur.

(And a PKM could allow us to give STS-49 a shot, after talking so much about it)

I already think about giving the Mission Editor a first experimental shot this evening. Nothing to be proud of, really. Just some "Hey, lets do it and look how it turns out in 8 years".
 
Last edited:
Is it to scale? If yes, than there could be done support for it analog to the Airlock/ODS.

For the 4.0 version... do you also have the insides of tunnel and airlock? maybe we could combine this with a Spacelab interior to extend the middeck a bit...

Would be a rather cheap feature compared to the other ones.

To the scale of the SSU shuttle. and yes it has the interier. Have also added the hatches for the airlock.
 
To the scale of the SSU shuttle. and yes it has the interier. Have also added the hatches for the airlock.

To quote our holy emperor Francis: "Is it already christmas?"

:thumbup:
 
The "spacer" is called the Tunnel Adapter Assembly (TAA) and was first used on STS-9. It is 2.1336 m (84") long and has an inside diameter of 1.6 m (63").

Inside or outer dimensions ? What are the hatch dimensions.
 
Inside or outer dimensions ? What are the hatch dimensions.
The hatch dimensions are 1.016 m in diameter across the the arc of the "D" while the bar is 0.914 m across. The inside diameter (ID) of the cylinder section is 1.6 m. Total length including the two conical sections is 2.1336 m. The length of each cone section is 0.406 m.
 
The hatch dimensions are 1.016 m in diameter across the the arc of the "D" while the bar is 0.914 m across. The inside diameter (ID) of the cylinder section is 1.6 m. Total length including the two conical sections is 2.1336 m. The length of each cone section is 0.406 m.

Could you do a drawing with arrows ?
 
This is a photo of the aft hatch on the External Airlock but it applies to the TAA hatches as well:

D_hatch_dimensions.jpg
 
I've been looking at how to add this TAA, and we could do away with the ODSZPos mission option, which defines the position of the External Airlock along the payload bay, and choose that parameter internally, according to whether or not the TAA is used (forward of the airlock). Any problems with this?
Another thing: could there be 2 TAAs used (one on each side)? Or shall we allow only one?
 
Status
Not open for further replies.
Back
Top